Boron Flashing Red SOS - Blink 10 - Cannot Recover

boron
Tags: #<Tag:0x00007fe21eff1588>

#1

Have Boron/Xenon network running in the field. Initialized 2nd Boron connected to cloud, created new mesh network and added one Xenon. No problems. In VS Code, compiled and flash local with firmware 1.2.0-rc.1.1 and same code but device now flashes SOS - Red x 10. Put in DFU mode and reflashed with basic Blink or any other code indicates success, but still flashes red. Cannot put into listening blue mode. Holding Mode button, releasing Setup button results in Magenta->Yellow->White->rapid green which eventually goes back to red SOS sequence. Tried several Particle keys doctor and Particle keys server. Results indicated download success but no change in device behavior. Still flashes red. Suggestions?


#2

Exact same thing happened to me yesterday with a boron. I re-flashed the latest bootloader and everything using the particle swd debugger, after which I was able to flash with boron cloud debug code, and now I just get:

deviceID=(removed but it was here and correct)
manufacturer=
model=
firmware version=
ordering code=
IMEI=
IMSI=
ICCID=
0000117150 [app] INFO: enabling trace logging
attempting to connect to the cellular network…
0000138303 [hal] ERROR: No response from NCP
0000138303 [hal] ERROR: No response from NCP
0000170553 [hal] ERROR: No response from NCP
0000170553 [hal] ERROR: No response from NCP
0000202803 [hal] ERROR: No response from NCP
0000202803 [hal] ERROR: No response from NCP

On a different (brand new) boron, I flashed tinker with 1.2.1-rc.1 and it connects to the cloud and then immediately starts blinking magenta and publishes spark/flash/status that it is updating (although I’m not sure why, it isn’t part of any product) and reporting odd vitals like “-39kB of 32kB RAM used”, and then eventually goes to safe mode and needs to be reflashed with an older deviceOS version to function again. The newer device remains recoverable, however I cant seem to get the old one going again. Unfortunately no suggestions, but you’re not the only one!


Boron LTE Stuck Blinking Green
#3

Hi all,

We are aware of the SOS issue when upgrading Gen 3 devices (Argon, Boron, Xenon) devices from 0.9.0 or older directly to 1.2.1-rc.1.

We implemented a workaround in the cloud by forcing devices to update to Device OS 1.1.0 before going to 1.2.1-rc.1 when flashing through the Cloud.

If you have a device in a bad state, manually flash system part 1.2.1-rc.1 to your device to get it working again.

  1. Download the correct system part for your device
    Argon system part 1.2.1-rc.1
    Boron system part 1.2.1-rc.1
    Xenon system part 1.2.1-rc.1

  2. From Workbench, run command Particle: Launch CLI or open the terminal if you have the Particle CLI installed.

  3. Put your device in DFU mode by holding MODE and RESET, releasing RESET and holding MODE until it blinks yellow. It should then continue blinking yellow.

  4. Flash 1.2.1-rc.1 to finish the update (edit the file name for your device)
    particle flash --usb boron-system-part1@1.2.1-rc.1.bin

If your device also is in an offline state, you will need to flash the bootloader manually:

  1. Download the correct bootloader for your device
    Argon bootloader 1.2.1-rc.1
    Boron bootloader 1.2.1-rc.1
    Xenon bootloader 1.2.1-rc.1

  2. From Workbench, run command Particle: Launch CLI or open the terminal if you have the Particle CLI installed.

  3. Put your device in Listening mode by holding MODE for > 3 seconds until it blinks dark blue. It should then continue blinking dark blue.

  4. Flash 1.2.1-rc.1 bootloader (with the --serial option) to finish the update (edit the file name for your device)
    particle flash --serial boron-bootloader@1.2.1-rc.1.bin --yes


Argon SOS Wont Enter DFU or Listening Mode
#4

Thank you, this seems to have fixed most of the isses, however I am still getting [hal] ERROR: No response from NCP when running the boron cellular debugger, is it safe to assume this is an unrelated hardware issue?


#5

@jvanier I had this issue and now my device is stuck in listening mode. Can I please get clear instructions on how to clear listening mode? I have tried device doctor and issue persists. Please Thank you.

I have a client that needs their Boron to work. We have purchased several to put in the field, but I need to get these working before I can put those in the field. Please help.


#6

Hi @DREAM

On Gen 3, Listening mode can occur for a couple of reasons.

All gen 3 devices have a flag that tell them setup is done. This can be reset on full device resets. This is normally flipped by the mobile application when performing setup, but will not get flipped from CLI setup.

If your device is in this state, your best bet is to follow the CLI instructions for Marking Setup Done as noted in the CLI setup section.

Either flashing the temporary application once or following the CLI instructions using dfu-util should kick the device out of safe mode.

As an additional point (which does not apply to your Boron, but anyone who is seeing this on the Argon). If an Argon has no wi-fi credentials, it will also fall back into listening mode. For the Argon, it is important to both set the setup flag as done and provide at least one set of wifi credentials to your device.