Photon setup flashing cyan with a "quick red burst" (now orange burst) [Solved]


#165

I suppose you have replaced dev_id with your actual device ID.

You may also want to shoot this after particle keys doctor <yourDeviceID>

particle keys server

And make sure your CLI is 1.16.0 (or newer)


#166

Whoah! :open_mouth: That did it! :smiley:

Device is connected, back in my dashboard as well and uploading is going great again.

Many thanks :smile:


#167

5 posts were split to a new topic: Flashing Cyan


#168

Hey @omarojo – your most recent post is a bit different than the original topic, “Photon setup flashing cyan with a “quick red burst” (now orange burst)”, so I am going to move it into a new post with the title, “Flashing Cyan”.

Thanks!


#169

Hi guys, having a nightmare here with a soldered in photon flashing cyan/red…

Tried everything in this article (with an updated CLI):

 - particle keys server cloud_public.der
 - particle keys new
 - photon particle keys load photon.der 
 - particle keys send 430032000F51353338363333 photon.pub.pem 
 - particle keys doctor 430032000F51353338363333 
 - particle keys server 
 - particle update
 - particle flash --usb tinker

Still no luck :pensive:.
I can see the system firmware is 0.5.3 and when I try the command:

 - particle device add 430032000F51353338363333

I get: Failed to claim device, server said: [object Object]

Can someone help? @BDub can you try provisioning a new key like you did before?


#170

Can you post the output of these commands?

(in Listening Mode blinking blue)

particle identify

(in DFU Mode blinking yellow)

particle keys server
particle keys doctor 430032000F51353338363333

And also a video of the blinking LED to see what exactly we are up against?


Trying again to fix the whole Particle experience
#171

Having a look at the output of particle update wouldn’t hurt either.


#172

Thanks for your quick replies.
@ScruffR ;
Response to particle identify

Your device id is 430032000f51353338363333
Your system firmware version is 0.5.3

Response to particle keys server

Found DFU device 2b04:d006
checking file C:\Users\dcsim\AppData\Roaming\npm\node_modules\particle-cli\keys\rsa.pub.der
spawning dfu-util -d 2b04:d006 -a 1 -i 0 -s 2082 -D C:\Users\dcsim\AppData\Roaming\npm\node_modules\particle-cli\keys\rsa.pub.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 dfu-util@lists.gnumonks.org

Opening DFU capable USB device...
ID 2b04:d006
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 = 0x00000822, size = 512
Download        [=========================] 100%          512 bytes
Download done.
File downloaded successfully
Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
Okay!  New keys in place, your device will not restart.

Response to particle keys doctor 430032000F51353338363333

Found DFU device 2b04:d006
Found DFU device 2b04:d006
New Key Created!
Found DFU device 2b04:d006
This file already exists, please specify a different file, or use the --force flag.
Continuing...
checking file 430032000F51353338363333_rsa_new.der
spawning dfu-util -d 2b04:d006 -a 1 -i 0 -s 34:leave -D 430032000F51353338363333_rsa_new.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 dfu-util@lists.gnumonks.org

Opening DFU capable USB device...
ID 2b04:d006
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 = 608
Download        [=========================] 100%          608 bytes
Download done.
File downloaded successfully
Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
Saved!
attempting to add a new public key for device 430032000F51353338363333
submitting public key succeeded!
Okay!  New keys in place, your device should restart.

@Moors7, response to particle update

> Your device is ready for a system update.
> This process should take about 30 seconds. Here goes!

! System firmware update successfully completed!

> Your device should now restart automatically.
> You may need to re-flash your application to the device.

Here is the video of the blinking LED (sorry for poor quality, I may have over-compressed it): https://drive.google.com/open?id=0B318xmkMW6WJd2pWaXF6Wk9Ta28


#173

I see you’ve got the Photon soldered to a custom PCB, so chances are that the external circuitry does overstress the USB power supply on connection attempt causing the key hanshake to fail or your PCB design does cause degraded antenna performance.

Try a different cable (these old Spark USB cables weren’t too good), a 2A minimum USB power supply and possibly a uFL antenna (needs to be selected in code too).
How does your keepout area around the chip antenna look?

There was another thread by @UMD having troubles with a mounted Photon and reception a while back
Photon SoftAP mode - mobile cannot obtain address

and also this
Photon SMD Antena, keepout zones, and ground loops


#174

The boards have DC jacks fitted and an LDO regulator capable of supplying > 2A, but connecting to the plug does not help.

Here is the keepout area:

I don’t think it is a hardware problem since I’ve got 5 others working fine! The only difference with this one is the way I set it up; instead of using the Particle app, I tried the CLI to set the WiFi credentials using particle setup wifi. It connected and was breathing cyan but would not allow me to add the ID to my account. Thinking there may be a problem with the keys, I generated fresh ones, which is when the problems started…


#175

Maybe pinging @BDub again might help.
You can also open a support ticket with a reference to this thread.


#176

So the update went through, but you’re still ‘stuck’ on 0.5.3, which is not the latest version. Try updating your CLI and give it another shot?


#177

Updated CLI and photon again, it’s version has changed to 0.60 but the red light problem still persists (even after another go at key doctor).


#178

@Moors7 @ScruffR, so I opened a support ticket and came to a solution - it turns out the IDs are case sensitive! In other words, if there is a letter in there, it must be LOWERCASE! I just had to run the key doctor with lowercase “f”.

Sometimes the solution is so simple…
Thanks for your help though guys.


#179

Darn, this has bitten again!

This is an open issue for CLI which should have been addressed a year ago.




#180

Thanks Scruff this worked great - particle keys doctor 123456789ID particle keys server

Nothing else had worked at all

Cheers


#181

so the topic has been solved.


#182

This fixed the issue!! (out of all the others – like generating new keys, uploading them, etc). Thank you!!


#183

Hey, so im going to bring this topic back to life because i havnt been able to fix it for almost a week now.
I have a classroom set of sparkfun photon redboards, with the majority running the 0.5.3 firmware. Im trying to get them all up and running on the latest firmware which is 0.6.2, but when i update them, they devices turn into bricks!
i get the cyan flashing with 3 red flashes. I have tried everything listed in this thread to get it working:
particle keys doctor deviceid
particle keys server device.der
particle keys new
particle keys load device.der
particle keys send deviceid device.pub.pem

and every other variation all all sorts of orders

i have tried reverting back to old firmware such as 0.5.3, but each time i try to update the key on the server using ‘send’ or ‘doctor’ i get a
Error sending public key to server: Permission Denied

eg: particle keys doctor deviceid

C:\Users\ioannidisa>particle keys doctor 230025000e47343337373737
Found DFU device 2b04:d008
Found DFU device 2b04:d008
New Key Created!
Found DFU device 2b04:d008
This file already exists, please specify a different file, or use the --force flag.
Continuing...
spawning dfu-util -d 2b04:d008 -a 1 -i 0 -s 34:leave -D 230025000e47343337373737_rsa_new.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 dfu-util@lists.gnumonks.org

Opening DFU capable USB device...
ID 2b04:d008
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 = 609
Download        [=========================] 100%          609 bytes
Download done.
File downloaded successfully
Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
Saved!
attempting to add a new public key for device 230025000e47343337373737
Error sending public key to server: Permission Denied
Make sure your device is in DFU mode (blinking yellow), and that your computer is online.
Error - undefined

I cant finish the particle setup to claim the device as when it goes to connect to the cloud, the bad key still blocks it :frowning:

i need some new ideas!!!


#184

Try opening the command prompt as an administrator, and make sure the device is in the proper mode. Also, running Particle update and Particle flash --usb tinker, shouldn’t hurt :slight_smile: