I too have the dreaded problem connecting with the blink cyan/ single red blink phenomenon
The photon is one of a number I have in medical datga loggers that are being readied for clinical trials commencing very shortly. Suddenly one ran into this problem.
Having read several previous posts I tried to use
particle keys doctor device-id’
But ran into the following erro message
PS C:\WINDOWS\system32> particle keys doctor 290041001347343438323536
Found DFU device 2b04:d006
Found DFU device 2b04:d006
New Key Created!
I couldn’t find the file: 290041001347343438323536_rsa_new.der
Make sure your device is in DFU mode (blinking yellow), and that your computer is online.
Error - I couldn’t find the file: 290041001347343438323536_rsa_new.der
The computer was on line and the photon was in DFU mode
Advice as to how to proceed from here would be appreciated.
One thing that should ease your mind about the risk for such thing happening in future: 0.7.0 is currently in RC2 state and should take care of this by itself without the need for keys doctor in future again.
The other thing might be that your CLI isn’t installed in the correct spot.
If you are using Windows I’d suggest you uninstall and remove all instances of CLI and reinstall CLI via the Windows Installer (including all drivers and OpenSSL)
With any other OS go with
sudo npm uninstall -g particle-cli
sudo npm uninstall particle-cli
sudo npm install -g particle-cli
and try again
particle keys server
particle keys doctor <yourDeviceID>
1 Like
Thanks.
I uninstalled and removed CLI and openSSL then reinstalled.
Unfortunately I continue to see the same error message as below
PS C:\WINDOWS\system32> particle keys server
Found DFU device 2b04:d006
spawning dfu-util -d 2b04:d006 -a 1 -i 0 -s 2082 -D C:\Users\Bruce\AppData\Local\particle\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.
PS C:\WINDOWS\system32> particle keys doctor 290041001347343438323536
Found DFU device 2b04:d006
Found DFU device 2b04:d006
New Key Created!
I couldn't find the file: 290041001347343438323536_rsa_new.der
Make sure your device is in DFU mode (blinking yellow), and that your computer is online.
Error - I couldn't find the file: 290041001347343438323536_rsa_new.der
PS C:\WINDOWS\system32>
Maybe you should not execute these commands in a write protected directory like SYSTEM32 
I’d cd into your user path or a temp directory and maybe even execute PS with admin privileges.
1 Like
Thanks - careless of me
I was using PS with admin priviledges but had forgotten to cd to a different directory
Problem solved - its back on air
Again - thanks for your prompt assistance
2 Likes