# Firmware update **URL:** \ **Category:** mangOH Green\ **Created:** [April 28, 2016, 1:52pm UTC](https://mangoh.discourse.group/t/firmware-update/54 "2016-04-28T13:52:00Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![gnottage](https://avatars.discourse-cdn.com/v4/letter/g/58f4c7/32.png) [@gnottage](https://mangoh.discourse.group/u/gnottage)\ **Post date:** [April 28, 2016, 1:52pm UTC](https://mangoh.discourse.group/t/firmware-update/54/1 "2016-04-28T13:52:00Z")
I have a mangOH green development board with WP8 from Sierra Wireless. It has come with the legato version reporting “15.10.0.Beta\_d8068df175db3bbdddb95ea8bb29ab89”, yet the Ubuntu development environment is expecting 16.01.0.Beta. This means my first “Hello Legato” application cannot be downloaded and run. Where can I get the 16.01.0.Beta and how do I update the mangOH green? I have tried apt-get update but that’s not found. ---
**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\ **Post date:** [April 28, 2016, 3:22pm UTC](https://mangoh.discourse.group/t/firmware-update/54/2 "2016-04-28T15:22:26Z")
> [@gnottage](#): > > I have a mangOH green development board with WP8 from Sierra Wireless. It has come with the legato version reporting “15.10.0.Beta\_d8068df175db3bbdddb95ea8bb29ab89”, yet the Ubuntu development environment is expecting 16.01.0.Beta. This means my first “Hello Legato” application cannot be downloaded and run. Where can I get the 16.01.0.Beta and how do I update the mangOH green? I have tried apt-get update but that’s not found. Hi , You need to do a firmware update on your WP8 module. Could you please follow the instructions given on the following page: [http://source.sierrawireless.com/resources/legato/wpfirmwareupgrade/](http://source.sierrawireless.com/resources/legato/wpfirmwareupgrade/) Please note that you need to know the SKU# of the module you are using and download the firmware accordingly. So how do you know the SKU: a. in a terminal on the mangOH, run microcom -E /dev/ttyAT Then enter AT!ENTERCND=“A710” followed by AT!SKU?. Then CTRL+X to get out of the AT command mode. b. then download the appropriate customer configuration. Please note that this process is only complete when you see the word “Enter…” Do remove the USB plug or power cycle before. I would say wait for 5-7 minutes if you are not sure. c. then download Carrier Configuration. Please note that this process is only complete when you see the word “Enter…” Do remove the USB plug or power cycle before. I would say wait for 5-7 minutes if you are not sure. We will release a simple pdf document in the coming days that clearly shows the steps. But this should get you going. Let us know if you have any issues. cheers, Ashish ---
**Author:** ![gnottage](https://avatars.discourse-cdn.com/v4/letter/g/58f4c7/32.png) [@gnottage](https://mangoh.discourse.group/u/gnottage)\ **Post date:** [April 28, 2016, 3:53pm UTC](https://mangoh.discourse.group/t/firmware-update/54/3 "2016-04-28T15:53:52Z")
Thank you Ashish - that has worked! ---
**Author:** ![awneil](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/awneil/32/486_2.png) [@awneil](https://mangoh.discourse.group/u/awneil)\ **Post date:** [May 19, 2016, 8:49pm UTC](https://mangoh.discourse.group/t/firmware-update/54/4 "2016-05-19T20:49:18Z")
That URL no longer works - just gives the ‘Not Found’ page. What is the correct URL now ? ---
**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\ **Post date:** [May 19, 2016, 8:50pm UTC](https://mangoh.discourse.group/t/firmware-update/54/5 "2016-05-19T20:50:55Z")
[http://source.sierrawireless.com/resources/legato/wpfirmwarerelease/](http://source.sierrawireless.com/resources/legato/wpfirmwarerelease/) ---
**Author:** ![awneil](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/awneil/32/486_2.png) [@awneil](https://mangoh.discourse.group/u/awneil)\ **Post date:** [May 19, 2016, 9:06pm UTC](https://mangoh.discourse.group/t/firmware-update/54/6 "2016-05-19T21:06:01Z")
Thanks! 😌 Cross-post on the Sierra Wireless forum: [https://forum.sierrawireless.com/viewtopic.php?f=177&t=9565#p38629](https://forum.sierrawireless.com/viewtopic.php?f=177&t=9565#p38629) ---
**Author:** ![awneil](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/awneil/32/486_2.png) [@awneil](https://mangoh.discourse.group/u/awneil)\ **Post date:** [May 20, 2016, 9:47pm UTC](https://mangoh.discourse.group/t/firmware-update/54/7 "2016-05-20T21:47:13Z")
The “Customer Config” update worked fine, but the “Carrier Config” just hangs at “Switching device to boot & hold mode …” ![](https://us1.discourse-cdn.com/flex016/uploads/mangoh/original/1X/cdb7711fe3394c97133472a934f32b678e83b97e.png) It has had well over 15 minutes now … ---
**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\ **Post date:** [May 20, 2016, 11:53pm UTC](https://mangoh.discourse.group/t/firmware-update/54/8 "2016-05-20T23:53:13Z")
Can you retry by forcing the module in boot mode: pin 7 of SW401 (TP1\_Boot) to ground? By default, this pin is disconnected and you need to push the switch up to connect it to ground. ---
**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\ **Post date:** [May 21, 2016, 1:47am UTC](https://mangoh.discourse.group/t/firmware-update/54/9 "2016-05-21T01:47:29Z")
Can you please make sure you have the latest drivers on your PC: [http://mangoh.io/getting-started.html](http://mangoh.io/getting-started.html) We have seen this issue when drivers are not latest. ---
**Author:** ![awneil](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/awneil/32/486_2.png) [@awneil](https://mangoh.discourse.group/u/awneil)\ **Post date:** [May 21, 2016, 5:34pm UTC](https://mangoh.discourse.group/t/firmware-update/54/10 "2016-05-21T17:34:14Z")
I had downloaded & installed the drivers immediately before trying this. Is there a way to uninstall all the drivers, and start again from scratch? ---
**Author:** ![awneil](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/awneil/32/486_2.png) [@awneil](https://mangoh.discourse.group/u/awneil)\ **Post date:** [May 21, 2016, 9:35pm UTC](https://mangoh.discourse.group/t/firmware-update/54/11 "2016-05-21T21:35:21Z")
So just setting the switch is not sufficient - it also needs a power-cycle. Then I get this: ![](https://us1.discourse-cdn.com/flex016/uploads/mangoh/original/1X/44c92dee5aef0cc0e7b48d69b5c9b22a1babadd8.png) Which doesn’t look good? ---
**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\ **Post date:** [May 21, 2016, 10:31pm UTC](https://mangoh.discourse.group/t/firmware-update/54/12 "2016-05-21T22:31:22Z")
Can you move the switch back to original position, switch to AT mode and do the following at!priid? at!package? ati At8 Post what you get ---
**Author:** ![awneil](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/awneil/32/486_2.png) [@awneil](https://mangoh.discourse.group/u/awneil)\ **Post date:** [May 21, 2016, 10:47pm UTC](https://mangoh.discourse.group/t/firmware-update/54/13 "2016-05-21T22:47:39Z")
at OK at!priid? PRI Part Number: 5501011 Revision: 01.15 Carrier PRI: 9999999\_9904559\_SWI9X15Y\_07.09.02.00\_00\_GENERIC\_001.019\_000 OK at!package? 9101011\_5501011\_WP8548-G\_06.03.55.00\_00\_DevKit\_001.006\_000 OK ati Manufacturer: Sierra Wireless, Incorporated Model: WP8548 Revision: SWI9X15Y\_07.09.02.00 r31541 CARMD-EV-FRMWR1 2016/03/31 20:05:28 IMEI: 359377060000865 IMEI SV: 41 FSN: LL516403850102 +GCAP: +CGSM OK At8 ERROR ati8 Legato Ver: 16.01.2\_9e91388c2b14980a4d419259910a4d65\_modified Yocto Ver: SWI9X15Y\_07.09.02.02 Fri Apr 15 02:39:24 PDT 2016 OS Ver: Linux version 3.14.29ltsi-13c67b16ff\_922830eb31 (gsmbuild@CARMD-EV-FRMWR1) (gcc version 4.9.1 (GCC) ) #2 PREEMPT Fri Apr 15 02:38:16 PDT 2016 LK Ver: 1.3.0\_a50272dbb2 RootFS Ver: unknown UserFS Ver: unknown OK **Edit** : Sorry, the forum won’t let me add another reply - but suggests I edit a previous one! How would I check the mangOH Rev? Or “app status”? Yes, it’s quite old - one of the ones given out at the Sierra Wireless Developer Summit in Paris last year. I can download an app from Dev Studio, and it seems to work, but Dev studio complains before down loading saying: Legato version in app is 16.01.0.Beta Legato version on device is 16.01.2\_9e… ---
**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\ **Post date:** [May 21, 2016, 11:19pm UTC](https://mangoh.discourse.group/t/firmware-update/54/14 "2016-05-21T23:19:12Z")
what version of mangoh are you using rev7 or rev8? Your module sku looks pretty old. Can you do app status? Can you download FW again and carrier again? This time with boot pin to ground for both the cases and post the image at completion at each time. Also post the at data I asked earlier again. Just want to double confirm everything is ok before you start l. ---
**Author:** ![deheljoh](https://avatars.discourse-cdn.com/v4/letter/d/f1d935/32.png) [@deheljoh](https://mangoh.discourse.group/u/deheljoh)\ **Post date:** [June 24, 2016, 8:40pm UTC](https://mangoh.discourse.group/t/firmware-update/54/15 "2016-06-24T20:40:49Z")
I just received my MangOH board and have never been able to get it in boot DM mode. I never see any ttyUSB ports enumerated on my system. I’m using Ubuntu 12.04. I tried all the different methods you mentioned to enter boot mode including one not mentioned here but found in the reference manual sys\_reboot bootloader. In each case the terminal indicates it’s in bootloader mode and doesn’t boot into Linux. But no ttyUSBX ports show up on the host. I think what happened in the above case is that once he updated, the ttyUSBx was broke as is mine. Here are the answers to your questions above for my board. Rev 8 board at!priid? PRI Part Number: 9905383 Revision: 01.02 Carrier PRI: 9999999\_9904559\_SWI9X15Y\_07.08.02.00\_00\_GENERIC\_001.018\_000 at!package? 1102816\_9905383\_WP8548\_07.08.02.00\_00\_Generic\_001.002\_000 ati Manufacturer: Sierra Wireless, Incorporated Model: WP8548 Revision: SWI9X15Y\_07.08.02.00 r31088 CARMD-EV-FRMWR1 2016/02/05 23:29:29 MEID: 35937706001639 ESN: 12808972115, 8088E753 IMEI: 359377060016390 IMEI SV: 41 FSN: LL609500260705 +GCAP: +CGSM At8 ERROR ati8 Legato Ver: 16.01.0.Beta\_aa0684bddf31f5ea2d457b53d2218972 Yocto Ver: SWI9X15Y\_07.08.02.00 Sat Feb 6 02:38:29 PST 2016 OS Ver: Linux version 3.14.29ltsi-5d7a6bf7c6\_ed88cc68b5 (gsmbuild@CARMD-EV-FRMWR1) (gcc version 4.9.1 (GCC) ) #2 PREEMPT Sat Feb 6 02:37:18 PST 2016 LK Ver: 1.3.0\_a50272dbb2 RootFS Ver: unknown UserFS Ver: unknown I’ve been able to connect using devstudio and even did some sort of firmware update from there. It wasn’t clear to me what I was updating. I downloaded 1102816\_9905383\_WP8548\_07.10.04.00\_00\_Generic\_001.006\_000-field.spk 9999999\_9904559\_SWI9X15Y\_07.10.04.00\_00\_GENERIC\_001.020\_000-field.spk and updated using those. Now here are the results: _\*\*root@swi-mdm9x15:~# microcom -E /dev/ttyAT \*\*_ _ **at!priid?** _ _ **PRI Part Number: 9905383** _ _ **Revision: 01.02** _ _ **Carrier PRI: 9999999\_9904559\_SWI9X15Y\_07.10.04.00\_00\_GENERIC\_001.020\_000** _ _ **OK** _ _ **at!package?** _ _ **1102816\_9905383\_WP8548\_07.08.02.00\_00\_Generic\_001.002\_000** _ _ **OK** _ _ **ati** _ _ **Manufacturer: Sierra Wireless, Incorporated** _ _ **Model: WP8548** _ _ **Revision: SWI9X15Y\_07.10.04.00 r32393 CARMD-EV-FRMWR1 2016/06/01 20:30:40** _ _ **MEID: 35937706001639** _ _ **ESN: 12808972115, 8088E753** _ _ **IMEI: 359377060016390** _ _ **IMEI SV: 42** _ _ **FSN: LL609500260705** _ _ **+GCAP: +CGSM** _ _ **OK** _ _ **At8** _ _ **ERROR** _ _ **ati8** _ _ **Legato Ver: 16.04.0\_63633d9200de787b7c2a6dca03d2cff3** _ _ **Yocto Ver: SWI9X15Y\_07.10.04.00 2016-06-02\_06:32:28** _ _**OS Ver: Linux version 3.14.29ltsi-c14b887744\_39dcf2256d (gsmbuild@CARMD-EV-FRMWR1) (gcc version 4.9.1 (GCC) ) #2 PREEMPT Wed Jun 1 23:37:34 PDT 2016**_ _ **LK Ver: 1.3.0\_a50272dbb2** _ _ **RootFS Ver: SWI9X15Y\_07.10.04.00 2016-06-02\_06:32:28** _ _ **UserFS Ver: unknown** _ I still don’t get any ttyUSBx port in boot mode. ---
**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\ **Post date:** [June 24, 2016, 9:57pm UTC](https://mangoh.discourse.group/t/firmware-update/54/16 "2016-06-24T21:57:22Z")
Hi, Can you redo firmware upgrade as described earlier in the email trail: So how do you know the SKU: a. in a terminal on the mangOH, run microcom -E /dev/ttyAT Then enter AT!ENTERCND=“A710” followed by AT!SKU?. Then CTRL+X to get out of the AT command mode. b. then download the appropriate customer configuration. Please note that this process is only complete when you see the word "Enter…" Do remove the USB plug or power cycle before. I would say wait for 5-7 minutes if you are not sure. c. then download Carrier Configuration. Please note that this process is only complete when you see the word "Enter…" Do remove the USB plug or power cycle before. I would say wait for 5-7 minutes if you are not sure. Let me know what you see then. regards, Ashish ---
**Author:** ![deheljoh](https://avatars.discourse-cdn.com/v4/letter/d/f1d935/32.png) [@deheljoh](https://mangoh.discourse.group/u/deheljoh)\ **Post date:** [June 24, 2016, 10:26pm UTC](https://mangoh.discourse.group/t/firmware-update/54/17 "2016-06-24T22:26:07Z")
Here are the results: AT!ENTERCND="A710" OK AT!SKU? SKU: 1102816 OK I believe I’ve downloaded the correct packages. But I can only update in devstudio since I get no ttyUSBx in bootloader DM mode. Therefore swiflash doesn’t work. (Nor fastboot). I think it updated to the two packages right? **Carrier PRI: 99999999904559\_SWI9X15Y\_07.10.04.00\_00\_GENERIC\_001.020\_000** \_ Model: WP8548 **Revision: SWI9X15Y07.10.04.00 r32393 CARMD-EV-FRMWR1 2016/06/01 20:30:40** \_ **Yocto Ver: SWI9X15Y07.10.04.00 2016-06-02\_06:32:28** \_ RootFS Ver: SWI9X15Y07.10.04.00 2016-06-02\_06:32:28\*\*\_ ---
**Author:** ![deheljoh](https://avatars.discourse-cdn.com/v4/letter/d/f1d935/32.png) [@deheljoh](https://mangoh.discourse.group/u/deheljoh)\ **Post date:** [June 24, 2016, 10:45pm UTC](https://mangoh.discourse.group/t/firmware-update/54/18 "2016-06-24T22:45:56Z")
Here are the methods I tried to get into boot mode: From [http://source.sierrawireless.com/resources/airprime/software/swiflash/](http://source.sierrawireless.com/resources/airprime/software/swiflash/) **Set switch 7 on and unplug**. Then plug in again. (No terminal output showing kernel loading) **_Check on host for new ttyUSBx (none)_** **AT!BOOTHOLD** OK rcK: Executing run\_K\_scripts… Stopping linkmon: stopped linkmon (pid 727) done \*\*\* Simple RIL / QMI test console v2.0 \*\*\* \*\*\* starting console \*\*\* Type in simple RIL commands and observe feedback Use ‘quit’ command to terminate simple RIL Stopping tcf-agent: [SIMPLE\_RIL\_INTEGRITY] simple ril init complete [SIMPLE\_RIL\_INTEGRITY] simple ril NW reg init complete SUCCESS (UNCONDITIONAL) OK Stopping mbimd: stopped restart\_mbimd (pid 702) [89.222005] mbim\_read: Waiting failed [89.227102] mbim\_release: Close mbim filestopped mbimd (pid 713) done Legato shutdown sequence Stopping Legato… DONE. Finished Legato Start/Stop Sequence Stopping QCMAP\_ConnectionManager: no QCMAP\_ConnectionManager found; none killed Stopping netmgrd: stopped netmgrd (pid 579) done Stopping adbd: [99.028658] adb\_release stopped adbd (pid 691) done Stopping qmuxd: done [99.345765] ch\_notify on a closed smd\_pkt\_dev\_msm id:0 [99.435708] ch\_notify on a closed smd\_pkt\_dev\_msm id:1 [99.485487] ch\_notify on a closed smd\_pkt\_dev\_msm id:2 [99.545460] ch\_notify on a closed smd\_pkt\_dev\_msm id:3 [99.625667] ch\_notify on a closed smd\_pkt\_dev\_msm id:4 [99.695467] ch\_notify on a closed smd\_pkt\_dev\_msm id:5 Stopping diagrebootapp: stopped diagrebootapp (pid 364) done stopping DNS forwarder and DHCP server: dnsmasq… [99.775614] ch\_notify on a closed smd\_pkt\_dev\_msm id:6 stopped /usr/bin/dnsmasq (pid 698) done. [99.835800] ch\_notify on a closed smd\_pkt\_dev\_msm id:7 Deconfiguring network interfaces… no ntpd found; none killed [100.204578] smsc95xx 1-1.3.1:1.0 eth0: hardware isn’t capable of remote wakeup done. Stopping qti: stopped qti (pid 329) done Stopping syslogd/klogd: stopped syslogd (pid 348) stopped klogd (pid 352) done Stopping Dropbear SSH server: stopped /usr/sbin/dropbear (pid 675) dropbear. stopping time daemon Stopping time\_services: stopped time\_daemon (pid 247) done stopping ntpd no ntpd found; none killed K96mount\_unionfs: RO rootfs will be fudged. K98mount\_early: Executing mount\_early\_user\_stop… K98mount\_early: Executing mount\_early\_legato\_stop… sh: on: unknown operand K98mount\_early: Executing mount\_early\_userrw\_stop… rcK: Executing kill\_all\_proc… rcK: Executing umount\_fs\_generic… rcK: Executing print\_shutdown\_msg… \*\* SYSTEM SHUTDOWN COMPLETE \*\* The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes)/root# Requesting system reboot[103.501113] reboot: Restarting system [103.503921] Going down for rest� **_Check on host for new ttyUSBx (none)_** And finally from the Legato reference manual page 889 **sys\_reboot bootloader** sys\_reboot bootloader [79.718113] reboot: Restarting system with command ‘bootloader’ [79.723943] Going down for restAndroid Bootloader - UART\_DM Initialized!!! **_Check on host for new ttyUSBx (none)_** I think I saw somewhere that you can set up usb to support different interfaces, DM being one. I will try to find that again. ---
**Author:** ![deheljoh](https://avatars.discourse-cdn.com/v4/letter/d/f1d935/32.png) [@deheljoh](https://mangoh.discourse.group/u/deheljoh)\ **Post date:** [June 24, 2016, 11:16pm UTC](https://mangoh.discourse.group/t/firmware-update/54/19 "2016-06-24T23:16:09Z")
Here’s what I found concerning the USB port from the Legato reference manual You can change the support for usb by setting up /etc/legato/usbmode. I set mine to the following: diag ecm acm nmea serial adb But still no ttyUSBx shows up either when it boots or enters boot mode. ---
**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\ **Post date:** [June 24, 2016, 11:46pm UTC](https://mangoh.discourse.group/t/firmware-update/54/20 "2016-06-24T23:46:15Z")
Can you try on a windows machine ? Make sure all the drivers are installed. Do you see any ports show up? Also what do you mean by " boot DM mode"? [Next page](https://mangoh.discourse.group/t/firmware-update/54.md?page=2)