Argon SOS Wont Enter DFU or Listening Mode

[ssnow]

Hello!

My Argon has entered an SOS state with 10 blinks, which the reference docs list as an assertion error. I have tried using the particle device doctor to solve the issue, however in its current state the cli command does not recognize the argon board while its plugged in via serial. We cannot use particle flash either, as the board cannot be put into dfu mode.

This post:

Boron Flashing Red SOS - Blink 10 - Cannot Recover

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. Download the correct system part for your device Argon system part 1.2.1-rc.1 Boron sys…

discusses similar issues, however the solution that is provided also requires the argon be put either in dfu or listening mode.

Currently, our argon will not change mode. Holding RESEST and MODE, then releasing/tapping reset sends the argon briefly into magenta (SAFE?), and then immediately into quickly flashing light green. Not yellow like dfu, or green like searching for internet, but a light green. After this, it returns into SOS, and continues to be unresponsive.

Any insight into how to progress would be sincerely appreciated! Thank you.

[ScruffR]

@ssnow

riefly into magenta (SAFE?), and then immediately into quickly flashing light green.

That's not supposed to happen, but a borked MODE button might explain that too.
Can you try a jumper wire from MD to GND instead of press/holding MODE?
Can you also post a video of the process?
Have you taken the Argon off the anti-static sponge it came on?

[ssnow]

MD to GND did the trick! Maybe it was a borked MODE button. We did take the argon off the anti-static sponge, but sit it on an ESD mat and ground ourselves before using. Not sure what caused it, but we really appreciate the quick tip!

Once in DFU mode the steps from @jvanier worked great.
Thanks again!

[Jeff_Burch]

My argon is blinking the SOS 10-blink pattern. It fails to respond to the mode button but does respond to the reset button. Grounding the MD pin has no impact.

I used the OPENOCD command with both argon 3.0.1 and also 2.0.1 with commands like this:

bin/openocd -f share/openocd/scripts/interface/cmsis-dap.cfg -f share/openocd/scripts/target/nrf52-particle.cfg -c “adapter_khz 1000” -c “transport select swd” -c “init” -c “reset halt” -c “nrf5 mass_erase” -c “flash write_image c:/temp/argon_2_0_1.hex” -c “reset” -c “exit”

During the openocd commad, the SOS pattern stops with the LED off. Once the command finishes, the SOS pattern resumes. Here’s an example output:

image c:/temp/argon_2_0_1.hex" -c “reset” -c “exit”
Open On-Chip Debugger 0.10.0+dev-00920-g6ea43726 (2019-07-02-23:12)
Licensed under GNU GPL v2
For bug reports, read
OpenOCD: Bug Reporting
Info : auto-selecting first available session transport “swd”. To override use 'transport select '.
adapter speed: 1000 kHz

Warn : Transport “swd” was already selected
swd
Info : CMSIS-DAP: SWD Supported
Info : CMSIS-DAP: FW Version = 1.10
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
Info : clock speed 1000 kHz
Info : SWD DPIDR 0x2ba01477
Info : nrf52.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : Listening on port 3333 for gdb connections
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc
Info : nRF52840-QIAA(build code: C0) 1024kB Flash
Info : Flash write discontinued at 0x0002659c, next section at 0x00030000
Warn : using fast async flash loader. This is currently supported
Warn : only with ST-Link and CMSIS-DAP. If you have issues, add
Warn : “set WORKAREASIZE 0” before sourcing nrf51.cfg/nrf52.cfg to disable it
Info : Flash write discontinued at 0x000a2898, next section at 0x000d4000
Warn : using fast async flash loader. This is currently supported
Warn : only with ST-Link and CMSIS-DAP. If you have issues, add
Warn : “set WORKAREASIZE 0” before sourcing nrf51.cfg/nrf52.cfg to disable it
Info : Flash write discontinued at 0x000d6adc, next section at 0x000f4000
Warn : using fast async flash loader. This is currently supported
Warn : only with ST-Link and CMSIS-DAP. If you have issues, add
Warn : “set WORKAREASIZE 0” before sourcing nrf51.cfg/nrf52.cfg to disable it
Warn : using fast async flash loader. This is currently supported
Warn : only with ST-Link and CMSIS-DAP. If you have issues, add
Warn : “set WORKAREASIZE 0” before sourcing nrf51.cfg/nrf52.cfg to disable it
Warn : using fast async flash loader. This is currently supported
Warn : only with ST-Link and CMSIS-DAP. If you have issues, add
Warn : “set WORKAREASIZE 0” before sourcing nrf51.cfg/nrf52.cfg to disable it
Warn : no flash bank found for address 0x10001100
wrote 684116 bytes from file c:/temp/argon_2_0_1.hex in 17.242510s (38.746 KiB/s)

Any suggestions on what to try next?

Thanks!

[particle7888]

Hi Jeff,
Thanks for this post and logging the ticket. We will work on the ticket and update you.

[oraclerouter]

I have the same issues. Did you get it fixed?