Argon stuck in DFU no matter what I do

I have no idea what happened but shortly after setup, my Argon started blinking yellow. I looked it up and I assumed I was stuck in DFU mode. I’ve attempted flashing over terminal, did not work. I’ve attempted putting it into different modes, the light changed color for a moment but then returned to flashing yellow. Even tried re-setting it up on my phone but it didn’t work (though I did delete the device from my account…). At my wits end - can’t find anything describing this issue.

Sidenote: I’m very much a beginner with anything related to Terminal.

PLEASE HELP

This is something the hardly ever solves anything but often enough causes additional issues - so it's best to avoid that.

How did you do that exactly?

You can try

particle flash --usb tinker -v
particle update -v
particle flash --usb tinker -v

Additionally to some possible issue with the current firmware state of your device another reason for that issue could be that your MODE/SETUP button got stuck in the connected state or you have something holding the MD pin low.

4 Likes

Hi @coco -

Welcome to the Forum :slight_smile:

@ScruffR gave you some good advice, let us know what whether you have been able to resolve the issue. If not, we will try to assist you further.

Regards,
Friedl.

When I do this, I get:

CarolinleelsMBP:~ Coco$ particle flash --usb tinker -v

dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.

Copyright 2010-2016 Tormod Volden and Stefan Schmidt

This program is Free Software and has ABSOLUTELY NO WARRANTY

Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature

dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!

Deducing device DFU version from functional descriptor length

Opening DFU capable USB device...

ID 2b04:d00c

Run-time device DFU version 011a

Claiming USB DFU Interface...

Setting Alternate Setting #0 ...

Determining device status: state = dfuIDLE, status = 0

dfuIDLE, continuing

DFU mode device DFU version 011a

Device returned transfer size 4096

DfuSe interface name: "Internal Flash "

Downloading to address = 0x000d4000, size = 11972

Download [=========================] 100% 11972 bytes

Download done.

File downloaded successfully

Transitioning to dfuMANIFEST state

Flash success!

It's now flashing cyan!!

I did this a second time (I assume that's what you were indicating?) and I got this:

CarolinleelsMBP:~ Coco$ particle flash --usb tinker -v

!!! I was unable to detect any devices in DFU mode...

Your device will blink yellow when in DFU mode.
If your device is not blinking yellow, please:

  1. Press and hold both the RESET/RST and MODE/SETUP buttons simultaneously.

  2. Release only the RESET/RST button while continuing to hold the MODE/SETUP button.

  3. Release the MODE/SETUP button once the device begins to blink yellow.

Error writing firmware: No DFU device found
VError: Error writing firmware: No DFU device found
at /Users/Coco/.particle/node_modules/particle-cli/dist/cmd/flash.js:208:13
at async CLI.runCommand (/Users/Coco/.particle/node_modules/particle-cli/dist/app/cli.js:160:7)
at async CLI.run (/Users/Coco/.particle/node_modules/particle-cli/dist/app/cli.js:190:14)
caused by: Error: No DFU device found
at ensureError (/Users/Coco/.particle/node_modules/particle-cli/dist/lib/utilities.js:427:14)
at /Users/Coco/.particle/node_modules/particle-cli/dist/cmd/flash.js:208:24
at async CLI.runCommand (/Users/Coco/.particle/node_modules/particle-cli/dist/app/cli.js:160:7)
at async CLI.run (/Users/Coco/.particle/node_modules/particle-cli/dist/app/cli.js:190:14)

What should I do now that it's blinking cyan?

Yup, that was what I meant, to make sure that you actually have Tinker installed in case step 1 or 2 did fail to bring the device back to breathing cyan.

When it's breathing cyan you are set for whatever you want to do as this is the expected/default state.

1 Like

Thank you so much for your help and for your fast replies! I put it into listening mode and set it up on my phone again.

1 Like

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.