Firmware update


#1

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.


#2

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/

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


#3

Thank you Ashish - that has worked!


#4

That URL no longer works - just gives the ‘Not Found’ page.

What is the correct URL now ?


#5

http://source.sierrawireless.com/resources/legato/wpfirmwarerelease/


#6

Thanks!

:relaxed:

Cross-post on the Sierra Wireless forum: https://forum.sierrawireless.com/viewtopic.php?f=177&t=9565#p38629


#7

The “Customer Config” update worked fine, but the “Carrier Config” just hangs at “Switching device to boot & hold mode …”

It has had well over 15 minutes now …


#8

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.


#9

Can you please make sure you have the latest drivers on your PC:
http://mangoh.io/getting-started.html

We have seen this issue when drivers are not latest.


#10

I had downloaded & installed the drivers immediately before trying this.

Is there a way to uninstall all the drivers, and start again from scratch?


#11

So just setting the switch is not sufficient - it also needs a power-cycle.

Then I get this:

Which doesn’t look good?


#12

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


#13

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…


Firmware Update: Customer Config OK; Carrier Fails
#14

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.


#15

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.


#16

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


#17

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**_


#18

Here are the methods I tried to get into boot mode:
From 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.


#19

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.


#20

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"?