Cannot flash boron-clouddebug-v121-rc3.bin

mawrob · July 7, 2019, 1:43pm

I have been experiencing connectivity issues with my new Borons and would like to run the Cloud Debug application and provide feedback. My devices are on v1.3.0-rc.1 not v1.2.1-rc.3 as described above.

Will the following instructions described above work for my v1.3.0-rc.1 devices:

Use the Particle CLI upgrade your Device OS and flash the cloud-debug firmware to your device
- Put your device into DFU mode (flashing yellow)
  - particle flash --usb <device>-system-part1@1.2.1-rc.3.bin
  - particle flash --usb <device>-clouddebug-v1.2.1-rc.3.bin
- Put your device into listening mode (blinking blue)
  - particle flash --serial <device>-bootloader@1.2.1-rc.3.bin
Open up a serial terminal by issuing the following CLI command:
- particle serial monitor --follow

(I ask because I have bricked Borons to a red flashing state trying to downgrade previously)

ScruffR · July 7, 2019, 3:21pm

You can run applications targeted at lower version numbers on devices with a higher version installed.

mawrob · July 7, 2019, 3:54pm

Thanks Scruff. So only flashing:

particle flash --usb <device>-clouddebug-v1.2.1-rc.3.bin

should be necessary then?

mawrob · July 7, 2019, 4:33pm

Well - that unfortunately was the wrong thing to do.

I put the 1.3.0-rc.1 Boron in DFU mode and ran:

C:\Users\rober\Downloads>particle flash --usb boron-clouddebug-v121-rc3.bin
Error writing firmware: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
dfuse_download: libusb_control_transfer returned -9

the Boron is now flashing yellow and I tried power cycling, resetting, holding the mode button down, safe start but nothing I do gets it out of this mode.

ScruffR · July 7, 2019, 5:20pm

Try with particle flash --usb boron-clouddebug-v121-rc3.bin -v (to get verbose output).
Flashing boron-clouddebug-v121-rc3.bin to a 1.3.0-rc.1 Boron should not cause issues.

However, this should help getting out of DFU Mode

particle flash --usb tinker -v

mawrob · July 7, 2019, 5:31pm

Tried:

particle flash --usb tinker -v

C:\Users\rober\Downloads>particle flash --usb tinker -v
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

Opening DFU capable USB device...
ID 2b04:d00d
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 = 11412
Download        [=========================] 100%        11412 bytes
Download done.
File downloaded successfully
Transitioning to dfuMANIFEST state
Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!

Flash success!

Still flashing yellow (DFU mode) after this.

Tried:

C:\Users\rober\Downloads>particle flash --usb boron-clouddebug-v121-rc3.bin -v
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

Opening DFU capable USB device...
ID 2b04:d00d
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 = 0x00030000, size = 754448
Download        [                         ]   0%            0 bytesInvalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
Error during download get_status
Error writing firmware: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
Error during download get_status

VError: Error writing firmware: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
Error during download get_status

    at Promise.resolve.then.then.then.then.then.then.catch.err (C:\Users\rober\AppData\Local\particle\node_modules\particle-cli\dist\cmd\flash.js:198:13)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:189:7)
caused by: Error: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
Error during download get_status

    at ensureError (C:\Users\rober\AppData\Local\particle\node_modules\particle-cli\dist\lib\utilities.js:670:14)
    at Promise.resolve.then.then.then.then.then.then.catch.err (C:\Users\rober\AppData\Local\particle\node_modules\particle-cli\dist\cmd\flash.js:198:24)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:189:7)

C:\Users\rober\Downloads>

It failed.

Also tried holding mode then reset (yellow, white, yellow) then:

C:\Users\rober\Downloads>particle flash --usb boron-clouddebug-v121-rc3.bin -v
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

Opening DFU capable USB device...
ID 2b04:d00d
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 = 0x00030000, size = 754448
Download        [                         ]   0%            0 bytesInvalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
dfuse_download: libusb_control_transfer returned -9
Error writing firmware: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
dfuse_download: libusb_control_transfer returned -9

VError: Error writing firmware: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
dfuse_download: libusb_control_transfer returned -9

    at Promise.resolve.then.then.then.then.then.then.catch.err (C:\Users\rober\AppData\Local\particle\node_modules\particle-cli\dist\cmd\flash.js:198:13)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:189:7)
caused by: Error: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
dfuse_download: libusb_control_transfer returned -9

    at ensureError (C:\Users\rober\AppData\Local\particle\node_modules\particle-cli\dist\lib\utilities.js:670:14)
    at Promise.resolve.then.then.then.then.then.then.catch.err (C:\Users\rober\AppData\Local\particle\node_modules\particle-cli\dist\cmd\flash.js:198:24)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:189:7)

C:\Users\rober\Downloads>

Thanks for your help.

ScruffR · July 7, 2019, 5:37pm

I have moved this conversation to a separate thread to keep the original one more tidy.
Can you check your particle --version

mawrob · July 7, 2019, 5:41pm

C:\Users\rober\Downloads>particle --version
1.42.0

ScruffR · July 8, 2019, 10:34am

I have now tried flashing boron-clouddebug-v121-rc3.bin to my Boron 2G/3G v1.3.0-rc.1 and didn’t see any issue - as expected.

Maybe you have some driver issues.
Uninstall CLI and reinstall via the lastes Windows Installer and make sure to tick both checkboxes (remove and install drivers).
And for superstition restart your Windows too

Also try using a different USB port and cable.

After that try revive your Boron with these steps (again)
(in DFU Mode)

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

After that your Boron should be back to 1.1.1 breathing cyan and running Tinker.

mawrob · July 9, 2019, 10:30am

Problem solved. It was a batch of bad USB cables.

Thanks for your help @ScruffR

Sorry for wasting everyone’s time.

Topic		Replies	Views
Device is Running Debug Firmware...? Libraries boron	7	465	December 15, 2020
Boron code not updating Developer Tools boron	3	945	February 1, 2021
Boron Lose communication with the cloud Cloud	6	315	February 1, 2023
No app will flash (USB Hub issue?) Getting Started boron	2	1004	May 22, 2021
Mbed OS on Boron General boron	20	1953	February 27, 2019

Cannot flash boron-clouddebug-v121-rc3.bin

Related topics