[SOLVED] Cyan blinking with quick red burst


#1

I’ve just got my first Duos, and the first one was just fine to set up, but the second is just constantly flashing cyan with a quick red burst ever so often.
I know this issue from the Particle devices indicating a problem with the keys, and there I’d just say

particle keys doctor <deviceID>

But here I’m stuck.
I’ve already reflashed DCT using

dfu-util -d 2b04:d058 -a 0 -s 0x08004000 -D duo-dct.bin

and all the other binaries too, since the above just didn’t help - but still no dice

I also tried (as suggested here)

C:\Particle\RedBearDuo\device-provisioning-helper-master>npm install
npm WARN package.json [email protected] No repository field.
[email protected] node_modules\request
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] ([email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected], [email protected])

C:\Particle\RedBearDuo\device-provisioning-helper-master>node main.js <deviceID>
using generic public key
attempting to add a new public key for device <deviceID>
Provisioning Error:  Permission Denied

[Solved] Cant connect to particle or claim
#2

Hi @scruffr,

It seams like your Duo hasn’t been recorded on the Particle cloud. Please send me your Duo’s device ID via PM – I’ll help provision it first and then you can provision it yourself.

Best regards,
guohui


#3

I guess, you just did it - my device has come online just now :thumbsup:


#4

Definitely right! It will connect to cloud immediately upon it been provisioned while it is trying its best to connect to cloud.


#5

Hi there,

I’m having the same issue. How is this best resolved?


#6

Hi @kab26, please read the section “Step 3: Provision your Duo if needed” of this topic:

If it prompted “Permission denied” when provisioning, send me your Duo’s device ID, I’ll help provision it first.

Kind regards,
guohui


#7

I’m now up and running on the particle cloud :slight_smile:

I simply re-flashed the DCT binary and reset, after redbear provisioned for me again, and it worked.

Thanks for your help.

Regards


#8

Hello,

Sorry reviving a old topic, the symptoms of my problem are the same. After normal and continuous use with the particle cloud, given a power problem, my Duo has fallen into Listening mode.

After I entered the credentials(via USB), I see the same behaviour of this topic, It is connected to internet(I can ping) but according to documentation not to the cloud therefore not retrieving the last firmware.

I can flash it with Arduino and change the mode.
I switched to DFU to check the private key… and it is different from the one I retrieved when I brought up the device from first time.

Is this my problem?

Anyhow I try to restore it but:

[email protected]:~/workplace/RedBear$ dfu-util -d 2b04:d058 -a 1 -s 34 -D device_private_key.der
dfu-util 0.5

© 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc.
© 2010-2011 Tormod Volden (DfuSe support)
This program is Free Software and has ABSOLUTELY NO WARRANTY

dfu-util does currently only support DFU version 1.0

Filter on vendor = 0x2b04 product = 0xd058
Opening DFU USB device… ID 2b04:d058
Run-time device DFU version 011a
Found DFU: [2b04:d058] devnum=0, cfg=1, intf=0, alt=1, name="@DCT Flash /0x00000000/01*016Kg"
Claiming USB DFU Interface…
Setting Alternate Setting #1
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 4096
No valid DFU suffix signature
Warning: File has no DFU suffix
DfuSe interface name: "DCT Flash "
Error: Last page at 0x00004021 is not writeable

There is a problem in the last line.

I tried provisioning as well as indicated: https://github.com/redbear/Duo/blob/master/docs/devices_provisioning_guide.md

What is happening in my case?


#9

According to the log, you were using version 0.5 of the dfu-util. Please try the dfu-util 0.8 first.


#10

Hello,

Had to update whole ubuntu system, to fetch this version. (Ubuntu 14.04 goes until dfu-util 0.5)

Unfortunately the error still shows up:

[email protected]:~/workplace/RedBear$ dfu-util -d 2b04:d058 -a 1 -s 34 -D device_private_key.der
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 [email protected]

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device…
ID 2b04:d058
Run-time device DFU version 011a
Claiming USB DFU Interface…
Setting Alternate Setting #1
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 4096
DfuSe interface name: "DCT Flash "
Downloading to address = 0x00000022, size = 16384
dfu-util: Last page at 0x00004021 is not writeable

However retrieving again the private key with 0.8, I have seen different sizes compared to the keys I retrieved with 0.5.

-rw-rw-r-- 1 oliver oliver 16350 dic 14 18:08 device_private_key3.der
-rw-r–r-- 1 oliver oliver 16384 oct 29 23:55 device_private_key.der

First was retrieved today with dfu-util 0.8, second, at some point of time, with dfu 0.5.
The additional bytes retrieved with 0.5 are the reason of the problem to fail to perform the restoration.

Solutions:

1.- Ensure when retrieving & restoring the private key you are using dfu-util is 0.8

2.- If (as me) your key was retrieved with dfu-util 0.5 (or size is 16384) there is still an option, because in my case the additional bytes were filed with 0xff so make a copy of your keyfile and truncate the file:

$ cp original_0_5_retrieved_key.der original_0_5_retrieved_key_reduced.der
$ truncate original_0_5_retrieved_key_reduced.der -s 16350

Restore it with dfu-util, and back to cloud!

Thanks again for your hint @guohui !


#11

And you should have noted that the offset -s 34 plus the valid der file size 16350 equals to 16384, which is the size of the DCT. So the essential reason is that the der file you dumped using dfu-util 0.5 to be downloaded from offset 34 will definitely exceed the DCT area.


#12

Sorry to dig up an old post but this exactly the problem I’m having. I had 3 Duos that bricked because of an OTA upgrade from 2.2 to 2.4. I set them aside and today successfully upgraded 2 of them to ver 3.1.

I have one that seems to fail with the same red blink that @scruffr reported. I have gone through the provisioning process with the following good result.

C:\DFU\device-provisioning-helper>node main.js
using generic public key
attempting to add a new public key for device
Success - Device Provisioned!

But it continues to fail the particle cloud connect with the short red flash and then keeps trying over and over again.

My dfu-util version is 0.8

What do I do next or is there something I’ve missed?

Thanks in advance for your help,
Joerg


#13

Never mind.

I found this post

And these release notes

My problem is now solved.


#14

I have the same problem :frowning: where can I send my device id?


#15

I updated to 3.1.Connected to soft AP and then to my wifi.
Led is blinking cyan rapidly.Initially it blinked red too.

I reset device private key and provisioned again.Did that several times
but cannot claim to particle.

The update to 3.1 was done with dfu-til version 0.8
Any ideas how I can claim it to Particle Cloud?


#16

Hi @xneo1, you are also supposed to update the server public key: https://github.com/redbear/Duo/blob/master/docs/firmware_deployment_guide.md#update-dct-device-configuration-table

Good luck!