SOLVED -- Cannot connect Photon - blinking cyan with red flashes


#1

Brand new Photon, right out of the box - can’t connect it to the cloud. Blinking cyan with red flashes.

  • The Tinker app setup fails
  • Using the CLI (on Mac running for 10.11.2) for USB setup fails
  • Then I’ve done:

Manual Firmware Update, following instructions here:
https://docs.particle.io/support/troubleshooting/common-issues/photon/#flashing-cyan

  • Then I’ve done:

Public Key Reset, following instructions here:
https://docs.particle.io/support/troubleshooting/common-issues/photon/#flashing-cyan

  • Then I hit the Particle forum and tried this:

• place Photon in DFU-mode
• particle update
• place Photon in DFU-mode
• particle flash --usb tinker
• hold on to the SETUP button until the device blinks blue
• release SETUP button and press and hold until it blinks blue rapidly to clear wifi credentials
• particle serial wifi to setup Wifi credentials

Network meets all of the Wi-Fi network requirements. I’ve tried it on multiple networks (that I’ve connected other Cores and Photons to).

I don’t know what else to try. Just a bad unit maybe? Can I get a new one? Anyone got any suggestions?

Thanks


Solved my strange connection problem!
[SOLVED] Anyone ever seen this behavior?
Photon behaving very strangely - can't put in into safe mode - Lost Public Key
Abort the setup process
Can't get new Photon to join WiFi network
#2

I just had the same problem, scroll down to 60th comments where I solve this issue.


#3

Who solved your issue(s)?


#4

Hahaha touche


#5

Thanks so much, but the solutions from that thread did not work.

I put the device in DFU mode and pasted in the device id with this command:

particle keys doctor paste-device-id

It failed and I got this message:

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: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
Saved!
running openssl rsa -inform PEM -in paste-device-id_rsa_new.pub.pem -pubout -outform PEM -out /var/folders/sy/trb7qvx90hj2fqxfd96xt7n00000gp/T/116024-20605-1etqrk0.pub.pem
running openssl rsa -pubin -inform PEM -in paste-device-id_rsa_new.pub.pem -pubout -outform PEM -out /var/folders/sy/trb7qvx90hj2fqxfd96xt7n00000gp/T/116024-20605-1etqrk0.pub.pem
attempting to add a new public key for device paste-device-id
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

This thing will not connect! Any other suggestions would be appreciated. Thanks all.


#6

Just out of curiosity
How often have you replaced your Device ID in the output pasted there?


#7

Just once. Well maybe twice - I inadvertently ran the “paste-device-id” command without the Device ID number and got the message below. Then I ran it properly and got the message above.

***************************************************************
   Warning! - device id was shorter than 24 characters - did you use something other than an id?
   use particle identify to find your device id
***************************************************************
running dfu-util -l
Found DFU device 2b04:d006
running dfu-util -l
Found DFU device 2b04:d006
running openssl genrsa -out paste-device-id_rsa_new.pem 1024
running openssl rsa -in paste-device-id_rsa_new.pem -pubout -out paste-device-id_rsa_new.pub.pem
running openssl rsa -in paste-device-id_rsa_new.pem -outform DER -out paste-device-id_rsa_new.der
New Key Created!
running dfu-util -l
Found DFU device 2b04:d006
running dfu-util -l
Found DFU device 2b04:d006
running dfu-util -d 2b04:d006 -a 1 -s 34:612 -U backup_rsa_paste-device-id_rsa_new.der
running openssl rsa -in backup_rsa_paste-device-id_rsa_new.der -inform DER -pubout -out backup_rsa_paste-device-id_rsa_new.pub.pem
Unable to generate public key from the key downloaded from the device. This usually means you had a corrupt key on the device. Error:  { [Error: Command failed: /bin/sh -c openssl rsa -in backup_rsa_paste-device-id_rsa_new.der -inform DER -pubout -out backup_rsa_paste-device-id_rsa_new.pub.pem
unable to load Private Key
20539:error:0D07207B:asn1 encoding routines:ASN1_get_object:header too long:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-59/src/crypto/asn1/asn1_lib.c:153:
20539:error:0D068066:asn1 encoding routines:ASN1_CHECK_TLEN:bad object header:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-59/src/crypto/asn1/tasn_dec.c:1328:
20539:error:0D06A03A:asn1 encoding routines:ASN1_COLLECT:nested asn1 error:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-59/src/crypto/asn1/tasn_dec.c:1212:
20539:error:0D094071:asn1 encoding routines:d2i_ASN1_SET:error parsing set element:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-59/src/crypto/asn1/a_set.c:218:address=140221475812576 offset=1994379272
20539:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-59/src/crypto/asn1/tasn_dec.c:1341:
20539:error:0D06C03A:asn1 encoding routines:ASN1_D2I_EX_PRIMITIVE:nested asn1 error:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-59/src/crypto/asn1/tasn_dec.c:845:
20539:error:0D08303A:asn1 encoding routines:ASN1_TEMPLATE_NOEXP_D2I:nested asn1 error:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-59/src/crypto/asn1/tasn_dec.c:765:Field=iqmp, Type=RSA
20539:error:0D09A00D:asn1 encoding routines:d2i_PrivateKey:ASN1 lib:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-59/src/crypto/asn1/d2i_pr.c:99:
]
  killed: false,
  code: 1,
  signal: null,
  cmd: '/bin/sh -c openssl rsa -in backup_rsa_paste-device-id_rsa_new.der -inform DER -pubout -out backup_rsa_paste-device-id_rsa_new.pub.pem' }
Saved!
checking file paste-device-id_rsa_new.der
spawning dfu-util -d 2b04:d006 -a 1 -i 0 -s 34:leave -D paste-device-id_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

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: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 = 610
Download	[=========================] 100%          610 bytes
Download done.
File downloaded successfully
Saved!
running openssl rsa -inform PEM -in paste-device-id_rsa_new.pub.pem -pubout -outform PEM -out /var/folders/sy/trb7qvx90hj2fqxfd96xt7n00000gp/T/116024-20525-160309o.pub.pem
running openssl rsa -pubin -inform PEM -in paste-device-id_rsa_new.pub.pem -pubout -outform PEM -out /var/folders/sy/trb7qvx90hj2fqxfd96xt7n00000gp/T/116024-20525-160309o.pub.pem
attempting to add a new public key for device paste-device-id
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
c-6106-cp:~ doug$ particle keys doctor paste-device-id 3D0020000347343339373536
***************************************************************
   Warning! - device id was shorter than 24 characters - did you use something other than an id?
   use particle identify to find your device id
***************************************************************

#8

Hmm, it still doesn’t make sense tho’

I think you are misunderstanding the suggested command line
It’s not meant to be

particle keys doctor paste-device-id 3D0020000347343339373536

but

particle keys doctor <replace-this-with-your-device-id>

so in your case

particle keys doctor 3D0020000347343339373536

#9

Well, that could be. I think I used your second command there, but I might not have - command line still somewhat new to me. I’ll try again. Thanks.


#10

Ok I ran the key doctor command while in DFU mode,

$ particle keys doctor 3D0020000347343339373536

got this:

running dfu-util -l
Found DFU device 2b04:d006
running dfu-util -l
Found DFU device 2b04:d006
running openssl genrsa -out 3D0020000347343339373536_rsa_new.pem 1024
running openssl rsa -in 3D0020000347343339373536_rsa_new.pem -pubout -out 3D0020000347343339373536_rsa_new.pub.pem
running openssl rsa -in 3D0020000347343339373536_rsa_new.pem -outform DER -out 3D0020000347343339373536_rsa_new.der
New Key Created!
running dfu-util -l
Found DFU device 2b04:d006
running dfu-util -l
Found DFU device 2b04:d006
running dfu-util -d 2b04:d006 -a 1 -s 34:612 -U backup_rsa_3D0020000347343339373536_rsa_new.der
running openssl rsa -in backup_rsa_3D0020000347343339373536_rsa_new.der -inform DER -pubout -out backup_rsa_3D0020000347343339373536_rsa_new.pub.pem
Saved!
checking file 3D0020000347343339373536_rsa_new.der
spawning dfu-util -d 2b04:d006 -a 1 -i 0 -s 34:leave -D 3D0020000347343339373536_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

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: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
Saved!
running openssl rsa -inform PEM -in 3D0020000347343339373536_rsa_new.pub.pem -pubout -outform PEM -out /var/folders/sy/trb7qvx90hj2fqxfd96xt7n00000gp/T/116024-24342-2td6bk.pub.pem
running openssl rsa -pubin -inform PEM -in 3D0020000347343339373536_rsa_new.pub.pem -pubout -outform PEM -out /var/folders/sy/trb7qvx90hj2fqxfd96xt7n00000gp/T/116024-24342-2td6bk.pub.pem
attempting to add a new public key for device 3D0020000347343339373536
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

#11

From the above, this seems significant:

attempting to add a new public key for device 3D0020000347343339373536
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


#12

Well, now it might be time to call The Keymaker @kennethlimcp

And I guess you had checked the things noted

And you had run particle login and particle device add 3D0020000347343339373536 (or had it claimed) beforehand.


#13

Think so. I’ll review / try agian. Thanks again.


#14

Device has never been claimed. Never successfully connected.


#15

Definetly something for Kenneth then (or Particle during office hours).


#16

If the device hasn’t been claimed then you don’t need to send the key to the cloud. If it’s still not connecting, then please try also flashing the server key to the device.


#17

Maybe this is a chance for me to get clear on the nomenclature. “Claiming” is going through the process of setting up the device, under my account, connecting it to a wifi network and to the cloud, yes?

This process has never been successfully completed. It bonks at the end of the setup process (either tinker app or usb / CLI) and blinks cyan with red flashes…then I’ve tried all of the things mentioned in this thread. I’ll try Kenneth. Thanks all.


#18

Solved!!

Though I had previously flashed the server key to the device, I did it one more time, on mdma’s suggestion, after running the keys doctor command and voila!! Connected, claimed! I have indeed won the internet.

Thanks so much, everyone in this thread, for hanging in there with me.