[SOLVED] Unknown issue with Photon EDIT: Photon cannot connect to cloud


#41

When it’s flashing all colors (like a rainbow), you’d normally name the device. Press the reset button, and let us know what it does after that. Does it breathe cyan?


#42

reset button breathes cyan for few seconds then quickly goes through several colours in 0.5seconds and repeats itself @Moors7


#43

What colors does it show, exactly?


#44

@Moors7 sorry for late reply, cyan flashes for a long time actually and then randomly yellow red (?) comes for a quick second. Quicker than I can tell what colour it exactly is…


#46

The first step is to tell us about the type of WiFi you are trying to connect to, and to ensure it’s a 2.4GHz network.


#47

Provide a link to the thread to avoid asking, suggesting and trying the same things over and over again!


#48

Actually I have contacted the support team, they took me as far as getting the device to rapidly breathe cyan. However I am getting could not claim device error on particle build site. And yes it is a 2.4Ghz signal

@mdma

I should add that at the beginning theres rapid cyan and quick burst of red and yellow which later turns into just rapid cyan and continues as rapid cyan


#49

If that’s the case, there’s probably an issue with your cloud keys. Updating the system firmware might help, and if not, you’ll most likely have to put some new keys on there. You can find out how to do that over here: https://docs.particle.io/support/troubleshooting/common-issues/photon/#flashing-cyan
Give that a try if you will. In the meantime, please don’t open yet another topic for this same issue.


#50

okay thank you! I shall give it a try now


#51

So I have followed the link and I have tried flashing the photon using the windows tutorial. Then I have also tried following the cyan with orange/red tutorial. Both involved dfu-util commands.

Still couldn’t claim the device…


#52

Well… what happened? Lovely that you tried it, but without telling us what it did, it’s not of much help.

Ditto :point_up:

Correct, that’s kinda what the guide tells you to use :wink:

What is the LED doing? Please mention ALL details. Saying it’s blinking cyan, while it’s actually also blinking orange/red, is not the most helpful thing either. The LED colors/patterns are a vital part of the process, so look carefully.


#53

Please ignore my pjs.
Its blinking cyan rapidly with quick burst of red Orange.

So after the flashing, and following the tutorial provided by moors7, I have went gone through power cycle to get the cyan led so that I could claim the device by going to particle build. However upon providing my device ID, it said “could not claim device”


#54

Well, that’s at least the color… Just so I’ve said it: a still image won’t be able to show which patterns it goes through, nor does it show different colors, should there be any.

That’s the interesting part.

So, what happened when you tried to do a firmware upgrade? Can you should us the output of that?
What happened when you followed the instructions mentioned here? Output from that might help with debugging.

A blinking Cyan light with flashed of red/orange is not the same thing as breathing cyan. Until it does that, there’s no reason to try the build IDE, since it won’t work.


#55

for flashing the device through the tutorial, here are the results:

    C:\Users\Atique>cd C:\Users\Atique\Desktop\Photon

C:\Users\Atique\Desktop\Photon>dfu-util -d 2b04:d006 -a 0 -s 0x8020000 -D system-part1-0.4.7-photon.bin
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

Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 2b04:d006
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 4096
DfuSe interface name: "Internal Flash   "
Downloading to address = 0x08020000, size = 249740
Download        [=========================] 100%       249740 bytes
Download done.
File downloaded successfully

C:\Users\Atique\Desktop\Photon>dfu-util -d 2b04:d006 -a 0 -s 0x8060000:leave -D system-part2-0.4.7-photon.bin
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

Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 2b04:d006
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 4096
DfuSe interface name: "Internal Flash   "
Downloading to address = 0x08060000, size = 169832
Download        [=========================] 100%       169832 bytes
Download done.
File downloaded successfully

Sorry drew over the hex because I wasn’t sure if I was supposed to show it or not

So then I’ve gone through resetting the public key for which the results were this on the cmd

C:\Users\Atique\Desktop\Photon>dfu-util -d 2b04:d006 -a 1 -s 2082 -D cloud_public.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

Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
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 = 402
Download        [=========================] 100%          402 bytes
Download done.
File downloaded successfully

Then I went through power cycle again to bring cyan rapid led to claim device, but failed :frowning:

This is the behaviour that I was talking about, this is just 3 seconds gif. Usually the cyan goes on for minutes and then that quick burst of colours pop in.

I have also tried particle keys doctor (I inserted my device ID)

This is the result
C:\Users\Atique>particle keys doctor <device ID>
running dfu-util -l
Found DFU device 2b04:d006
running dfu-util -l
Found DFU device 2b04:d006
running openssl genrsa -out <device id>_rsa_new.pem 1024
Error
 creating keys... Error: Command failed: C:\WINDOWS\system32\cmd.exe /s 
/c "openssl genrsa -out <device id>_rsa_new.pem 1024"
'openssl' is not recognized as an internal or external command,
operable program or batch file.

Make sure your device is in DFU mode (blinking yellow), and that your computer is online.
Error - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "openssl genrsa -out <device id>_rsa_new.pem 1024"
'openssl' is not recognized as an internal or external command,
operable program or batch file.

Then I went through a brief power cycle, still same result.


#56

Is your device still blinking cyan with orange flashes?


#57

when i connect it yes, but gradually its cyan only just like the gif on previous comment


#58

You need to be specific for me to know what’s the symptom.

Blinking cyan or Breathing cyan? Any orange flashes?

Do you have the Particle Cli installed?


#59

i provided a gif to show you on comment 55, yessss i do have cli installed :smile:


#60

Make sure you have the device id and place the device in dfu mode.

Use the command particle keys doctor paste-device-id


#61

ive also tried that, the results are on comment 55 near the end