Board not bootable after reflashing

#1

hi, I have installed IoT extension board WL18 WiFi/Bluetooth and followed offical instructions to build firmware with bluetooth driver https://github.com/mangOH/mangOH/wiki/Bluetooth-WL18xx-driver-for-mangOH
firmware was build ok and I have flashed ‘yocto_wp85.cwe’ using Windows Developer Studio’ (flash from external file)
after that board not boot.
connecting to console port I see error:

questions:

  1. how to recover board which not boot after that
  2. how to use Bluetooth on extension board ?!

thank you in advance,

Bluetooth success story
#2

Hi, mango. :slight_smile:

I’m no expert in this area, but I have a few questions that might help an expert to solve the problem for you:

  1. What WP module do you have on your mangOH board?
  2. Is this mangOH Red or Green?
  3. What is the on/off state of your boot mode switch (switch 7 on Red) ?

If the boot mode switch is ON, then it will only boot into the recovery mode. In this mode you should be able to reprogram it with a firmware image from Sierra Wireless, even if it has bad firmware on it. After you’ve reprogrammed it with the new firmware image, switch the boot mode pin OFF and reset the board to boot the new firmware.

The programming process happens like this:

  1. Download packed firmware image into the SWIFOTA flash partition on the device.
  2. Reset the device.
  3. Board’s primary bootloader sees the new image in the SWIFOTA partition and starts unpacking it and writing it into other flash partitions.
  4. When programming is done, reset the device. (If interrupted by reset or power loss, will jump back to step 3.)

The author of the official instructions page should be back on-line on Tuesday, but hopefully someone else will be able to help before then.

#3

thank you for reply! I use mangOH Red, WP7702, switch 7 is OFF.

  1. Could you please explain in details how to “Download packed firmware image into the SWIFOTA flash partition on the device” ?

  2. During custom firware compilation many files were generated, for example “boot_wp86.cwe”, shouldn’t they be flashed too ?

  3. I also tried “one-click” firmware updater for Windows, and it is also fails to flash

#4

independently of Switch 7 on RED ‘one-click’ upgrage tool (WP77xx_Release9.1_PTCRB_GCF_EXE.exe) gives:
DT version: 1.0.1806.0
Awaiting adapter …
Enabling selective suspend …
Firmware download failed.
Primary error code: 82 - Failed in checking modem mode.
Secondary error code: 0 - Not applicable.
Device error code: 0x0 - Unknown device error code.

how to recover?

#5

in other thead (https://forum.mangoh.io/t/bluetooth-success-story/2656/5) people telling that they have succeded by following:
we used swicwe to stitch together the new yocto cwe with the bootloader, modem firmware and legato images into a single spk file and flashed it using swiflash

can it be that instructions on https://github.com/mangOH/mangOH/wiki/Bluetooth-WL18xx-driver-for-mangOH miss this step?

how can we recover board which become not bootable after following these instructions?
please help!

#6

If you followed those old WL18 instructions carefully, then you’ve probably loaded your WP77 with an image that was intended for the WP85 or WP75 (which use the Qualcomm MDM9x15-series of module). The WP77 uses a different Qualcomm module and runs quite different software at the bootloader and Linux distro levels. Still, the one-click tool should recover it with switch 7 turned on.

  1. switch 7 ON
  2. power-cycle the mangOH
  3. wait 20 seconds or so
  4. run one-click tool
  5. when it starts downloading the firmware image, you can move switch 7 off so it will boot properly (otherwise, it will still program properly, but may get stuck waiting for the device to reboot afterwards).

If that still doesn’t work, try rebooting your Windows PC. It shouldn’t be needed, but sometimes it helps.

#7

I did exactly as you have described, but still have:

FDT version: 1.0.1806.0
Awaiting adapter …
Enabling selective suspend …
Firmware download failed.
Primary error code: 82 - Failed in checking modem mode.
Secondary error code: 0 - Not applicable.
Device error code: 0x0 - Unknown device error code.

Preexisting images information:
Current:
Firmware:
ImageId:
BuildId:
Configuration:
ImageId:
BuildId:
Final images information:
Current:
Firmware:
ImageId:
BuildId:
Configuration:
ImageId:
BuildId:

OEM PRI:

IMEI:

Total time elapsed: 172 ms.

Images downloaded:

Press Enter to continue …

#8

and corresponding console output attached in first message of this thread

#9

maybe worth mentioning in WL18 instructions that they not works with WP7702?

#10

could you please tell will these instruction work for WP7702 Building Custom Yocto Image ?

#11

OK, I found some help at Sierra Wireless. Apparently, the one-click tool doesn’t work in recovery mode.

You need to get Developer Studio for Windows or use the swiflash tool under Linux.

I found this on source.sierrawireless.com: https://source.sierrawireless.com/resources/legato/wpxxxxrecoveryprocedure/

#12

I’ve also been told that the link you referenced (Building Custom Yocto Image) should work for WP77.

#13

Instead of downloading Developer Studio on Windows, there’s also a smaller tool dedicated to just programming/recovering units using Windows:

https://source.sierrawireless.com/resources/airprime/software/fdt/

Thanks to Sunny at Sierra Wireless for the help!

#14

thank you for reply!
I followed this but still got:

FDT version: 1.0.1702.1
Awaiting suitable port or adapter …
Switching to streaming mode …
Downloading images …
Writing image -
Flashing image -
Enabling selective suspend …
Awaiting adapter …
Enabling selective suspend …
Firmware download failed.
Primary error code: 82 - Failed in checking modem mode.
Secondary error code: 0 - Not applicable.
Device error code: 0x0 - Unknown device error code.

Preexisting images information:
Current:
Firmware:
ImageId:
BuildId:
Configuration:
ImageId:
BuildId:
Final images information:
Current:
Firmware:
ImageId:
BuildId:
Configuration:
ImageId:
BuildId:

OEM PRI:

IMEI:

Total time elapsed: 270703 ms.

Images downloaded:
Image ID: 001.028_001
Build ID: 02.16.06.00_GENERIC
write time: 19547 ms
additional flash time: 9515 ms

Time to reset to application mode: -1 ms.

Press Enter to continue …

#15

it starts to download and then freeze at lines

Awaiting adapter …
Enabling selective suspend …

and after some time show error.
DM COM port is present in Device Manager

WP7702 – MangOH red

tried firmware 9.1 and 9

please help to recover board!!
thank you

#16

Can you try swiflash ?

#17

yes, but what means error in initial message? do you have sources to check?
I tried many times with DIP 7 ON and OFF. flashing and downloading seems to works but later it freeze on
Awaiting adapter …
Enabling selective suspend …

and then
Firmware download failed.
Primary error code: 82 - Failed in checking modem mode.
Secondary error code: 0 - Not applicable.
Device error code: 0x0 - Unknown device error code.

#18

Can you confirm whether swiflash solved your problem? Your error message seems like a FDT error message.

#19

Also, have you tried switching off the recovery mode (dip switch 7 off) and power cycling the board after your attempt with FDT? I have seen programming tools report failure even though they succeeded. This usually happens because the tool is waiting for the board to boot up after being programmed, but the board doesn’t boot because it is still in recovery mode.

#20

yes, I tried to flash with dip switch 7 on and off, and then switch back during flashing… it looks like downloading and flashing is proceeding, but at the end after reboot I see error as in initial post.
I did not tried ‘swiflash’ yet, but isn’t it just linux version of ‘fdt’. I thought it does the same job as Windows tool