Spark Core breathing white

@mute,

usually a breathing white status means that the CC3000 is not responding…

I guess the core was working fine before? Let’s it power up and sit for some time and see if it eventually enters blinking green

Core was working fine before, then it just stopped letting me flash from the website no matter what I tried.

I just let it sit plugged in for 8 hours and it never stopped breathing white. :frowning:

Sounds like the CC3000 is not working…

Hey @mute, send an email hello@spark.io and we’ll get you sorted out. Reference this thread please!

Did Spark.io ever get back to you about this? what was the solution? I’ve encountered the same issue.

-Brent

The spark team took care of me, I’d suggest contacting them and see if they can help.

Hello!

I have the same issue (white breathing and unable to bring it to listening mode) and tried already also the firmware update over DFU.
Is there also a public solution or do I have to write to somewhere extra?
Core is from the beginning of year 2014

@andres_particle,

hope this helps: [Spark core] Common issues

Looks like my Core has the same issue: it was working fine but then started with white breathing and unable to bring it to listening mode. Tried several times to factory-reset but still no way to get it into listening mode. Does anyone have a suggestion or a solution?

Did you try the suggestions given in the post linked directly prior your own post?

Of course.

And what was the output of all these particle CLI calls?

Well, it does not even appear on USB (message with Core in DFU mode: “No devices available via serial”. I tried also a serial monitor to see if it reacts, but nothing. I also tried the Particle Firmware Manager, which also does not detect any device on USB.

If you were using the commands as shown in the post you wouldn’t get that message as DFU Mode (and in that way particle flash --usb ...) does not expect to find a device via serial.

Have you got DFU drivers installed correctly?

What OS are you on?

I am on Mac OS and I think the drivers are OK. I have no problems interacting with my Photons and Electrons (unless they use a different way of communicating than the Core.

Anyway, I tried particle flash --usb tinker and I get this response in the terminal:

running dfu-util -l
Found DFU device 1d50:607f
checking file /usr/local/lib/node_modules/particle-cli/binaries/core_tinker.bin
spawning dfu-util -d 1d50:607f -a 0 -i 0 -s 0x08005000:leave -D /usr/local/lib/node_modules/particle-cli/binaries/core_tinker.bin
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

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 1d50:607f
Run-time device DFU version 011a
Claiming USB DFU Interface…
Setting Alternate Setting #0
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash "
Downloading to address = 0x08005000, size = 79996
Download [=========================] 100% 79996 bytes
Download done.
File downloaded successfully
Transitioning to dfuMANIFEST state

Flash success!


After that, I get exactly the same behaviour as described above by mute (15 Februare posts and thereafter). This means - the Core is back breathing white after the flashing.

  • after pressing the reset button it is immediately breathing white again
  • holding the Mode button does not bring it into listening mode.

I tried another thing: particle flash --usb CC3000 and I get this response:
running dfu-util -l
Found DFU device 1d50:607f
checking file /usr/local/lib/node_modules/particle-cli/binaries/cc3000-patch-programmer.bin
spawning dfu-util -d 1d50:607f -a 0 -i 0 -s 0x08005000:leave -D /usr/local/lib/node_modules/particle-cli/binaries/cc3000-patch-programmer.bin
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

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 1d50:607f
Run-time device DFU version 011a
Claiming USB DFU Interface…
Setting Alternate Setting #0
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash "
Downloading to address = 0x08005000, size = 25068
Download [=========================] 100% 25068 bytes
Download done.
File downloaded successfully
Transitioning to dfuMANIFEST state

Flash success!


After that, the is blinking magenta indicating it is in “OTA FIRMWARE UPDATE” (https://docs.particle.io/guide/getting-started/modes/core/#ota-firmware-update). It was in that mode for about ten minutes and nothing changed. After pressing reset, it immediately goes back to the same magenta blinking pattern and holding the mode button does not bring it into listening mode.

@hbierau, put the Core back into DFU mode and run particle flash --usb tinker.

Done, same outcome as above.

@hbierau, if I recall, I had that happen to one of my old Cores as well. I ended up introducing it to the garbage can and replacing it with a Photon.

@peekay123, that would be my next step as well. Great minds think alike. Thanks anyway, also to @ScruffR

2 Likes