Firmware update

mangOH Green
21

I’ve already tested on Windows machine after loading all the drivers. I had the same result. The device was not detected.

23

What do you see if you do ifconfig on Linux machine?

24

Firmware update is much easier now: Update to new Firmware: SWI9X15Y_07.11.22.00 r33729 CARMD-EV-FRMWR1 2017/01/11 18:04:06

*Note: 1.this new firmware only supports one interface to ssh to the board: usb0 or eth0. After update, you still can ping the mangOH via Ethernet , but cannot ssh to it. You need to follow the instruction from Kevin Sabau’s post to configure to use Ethernet over USB. For more details, please see: SSH over Ethernet – Legato version 16.10.x
2: After firmware update, all your applications will be removed from the mangOH board and you need to reload them back after the update. Be prepare.

Here is the instructions:

  1. connect the mangOH board to your windows computer and make sure you can ssh to the mangOH board.
  2. download the “Windows EXE” file under one of the"Combined Images" session according to your carrier from this URL: http://source.sierrawireless.com/resources/legato/wpfirmwarerelease/
  3. click on “Windows EXE” after it finished downloading. Wait for it to complete flashing firmware and resetting the mangOH board and hit “Enter” to exist the install windows.
  4. ssh back to the mangOH via 192.168.2.2(usb0). Type “cm info” to find out the firmware version that has been installed.
2 Likes
25

Hi,

I’m trying to perform a firmware update as well, from a PC running Windows. When I connect the board, I can ssh to it. Here are its version information:

login as: root
Linux swi-mdm9x15 3.14.29ltsi-bfda7d39c8_a010fd6d72 #2 PREEMPT Fri Oct 30 13:25:12 PDT 2015 armv7l GNU/Linux
root@swi-mdm9x15:~# cm info
Device: WP8548
IMEI: 359377060009023
FSN: LL542500181303
Firmware: SWI9X15Y_07.11.09.00 r32989 CARMD-EV-FRMWR1 2016/08/11 18:03:20
Bootloader: SWI9X15Y_07.11.09.00 r32989 CARMD-EV-FRMWR1 2016/08/11 18:03:20
root@swi-mdm9x15:~#

But when I run the Windows EXE file to perform the update, I get this message back:

FDT version: 5.1.1604.0
Checking modem mode …
Disabling selective suspend …
Switching device to boot & hold mode …

Firmware download failed.
Primary error code: 51 - Failed to switch device to BOOT&HOLD mode.
Secondary error code: 51 - Failed to switch device to BOOT&HOLD mode.
Device error code: 0x0 - Unknown device error code.
Total time elapsed: 2187 ms.
Press Enter to continue …

I tried from Linux as well. On Linux, the board appears as a CDC Ethernet device, not a DM device. I ssh’ed to it and enterd the command configECM off. But nothing happened…

What should I check?

26

I have not seen this issue before, but maybe you can switch to usb0 to perform the update instead of using eth0? See if it helps.

27

Using a brand new installation of Linux Mint (a distribution based on Ubuntu) and switching the board to bootload mode, I was able to perform the update. My installation notes are available here.

2 Likes