# Firmware update attempt for SL8080T

**URL:** <https://forum.sierrawireless.com/t/firmware-update-attempt-for-sl8080t/7530>\
**Category:** Legacy AirPrime modules\
**Created:** [November 4, 2014, 4:40pm UTC](https://forum.sierrawireless.com/t/firmware-update-attempt-for-sl8080t/7530 "2014-11-04T16:40:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![waltsacuta](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@waltsacuta](https://forum.sierrawireless.com/u/waltsacuta)\
**Post date:** [November 4, 2014, 4:40pm UTC](https://forum.sierrawireless.com/t/firmware-update-attempt-for-sl8080t/7530/1 "2014-11-04T16:40:41Z")

</div>

I have been using the SL8080T on the Sierra Wireless SL series development board. Attempts to make an HTTP connection were working, but buggy. The firmware version was 7.50xxx, so I wanted to update the firmware to 7.52xxx. The updates were found on the “Firmware package 7.52” page. I downloaded “Clear Terminal” version 2.0.0.4 and followed the instructions. My attempt to load “SIERRA\_OAT\_FW\_752\_68\_FULL\_sl808x.dwl” started (using Xmodem), but didn’t complete as described in other posts.

The bootloader “SIERRA\_BOOT\_S4.1.0.13\_SL808x.dwl” seemed like it might need an update, so I sent it using the Xmodem on Clear Terminal. Now the SL8080T is in a state where I can’t use it properly. Commands are no longer echoed, only OK responses are sent. It won’t respond properly to AD+WDWL (it just replies OK). ATI3 gives the following:

Sierra Wireless, Incorporated  
SL8080T  
APP3  
OK

All other commands just result in OK responses, so I can’t use the module and I don’t know how to make it operational again. Any help would be much appreciated.

---

<div class="post-metadata">

**Author:** ![waltsacuta](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@waltsacuta](https://forum.sierrawireless.com/u/waltsacuta)\
**Post date:** [November 4, 2014, 6:26pm UTC](https://forum.sierrawireless.com/t/firmware-update-attempt-for-sl8080t/7530/2 "2014-11-04T18:26:01Z")

</div>

This problem was solved with help from the rep using an updater over USB to get to to V7.52.0xxx.
