Alright, describing colors in text is evidently not working. If possible, upload the video to youtube and post the link here. A dropbox link, or a google drive link should also work. If neither of those is available, try mailing it to support (at) particle.io If so, do reference this thread so they know what itâs about.
With the steps described in my first post, you should be able to get to breathing (not blinking) cyan, which is a mix of red and blue. (I often find it easier to differentiate between colors when I place a thin paper sheet over the LED, diffusing the colors. That makes it more uniform.)
So, the LED shout be breathing cyan, regardless of whether itâs been claimed or not.
Here are the steps I take for a device thatâs in blinking blue mode on startup, thus without credentials. Itâs also unclaimed.
place it in DFU mode by holding setup, and pressing reset. Hold setup until blinking yellow:
Device should now be in blinking blue mode (listening mode). Copy the deviceID for later.
With the Photon still in blinking blue:
To be very sure thereâs no user application on there messing with the LED, place it in DFU mode again:
DFU mode or setup mode in the appropriate places. At this point, the LED shows what you see in the video (no breathing). After holding the setup button until itâs blinking blue, the âparticle identifyâ returns a device id, the âdevice addâ fails, and a âparticle listâ returns âNo devices foundâ so it is certainly stuck somewhere. Hope the vid helps.
C:\Projects>particle keys save mykey.der
running dfu-util -l
Found DFU device 2b04:d006
running dfu-util -d 2b04:d006 -a 1 -s 34:612 -U mykey.der
running openssl rsa -in mykey.der -inform DER -pubout -out mykey.pub.pem
Error saving key from device... Error: Command failed: C:\Windows\system32\cmd.e
xe /s /c "openssl rsa -in mykey.der -inform DER -pubout -out mykey.pub.pem"
unable to load Private Key
10224:error:0D07207B:asn1 encoding routines:ASN1_get_object:header too long:./c
... (rest deleted for space)
Having little to lose, I went ahead with the 'particle keys doctor â command which printed âNew Key Created!â followed by several failures to save the keys (similar âheader too longâ error messages as the previous command). The message âUnable to load Private Keyâ was repeated three times in the output.
The âparticle keys sendâ command did succeed but âparticle listâ and âparticle device addâ do not. LED behavior remains the same. The .new.pub.pem file, if it is valid:
It does not look as though this guy is going to recover. Any other thoughts?
Alack alas, no luck with the latest openssl version. Same error messages as before. I know that a factory reset risks bricking the board, but would it restore a valid key or was the key corrupted when the board was originally factory flashed?
The Photon board would not connect out of the box, and the cause seems to be corrupt encryption keys. Iâve followed the instructions to backup and re-create keys, but the commands fail with openssl errors. It seems that any command to retrieve keys from the device encounter problems with the header length/format. As yet, no luck in getting the board to connect to the cloud and register itself.
Can you download and do a particle keys send DEVICEID junk.pub.pem. Be sure to replace it with the actual deviceID and once you do that, reset the Photon and it should work.
I did the above in DFU mode, then reset the board. No change in the LED behavior. After a âparticle loginâ and âparticle serial wifiâ command, the board remains in the same state as before. Iâm also seeing the same error messages when trying to back up the keys. It doesnât look as though the corrupt keys were replaced.
Yes, I got a âsubmitting public keyâŚâ message followed by âsubmitting public key succeeded!â Same message in DFU mode and setup mode. I also tried the command after the board was reset. No apparent change in behavior. Will the app recognize the board?