Core blinking white and not booting up

Hi all,

I’ve been trying my best to resolve this using all the great suggestions already posted by this community but nothing has helped. Since a few days one of my cores all of a sudden stopped working and blinks white as soon as I power it on. When pressing the mode button (while flashing white) it turns to a steady white.
I’ve tried flashing the core using dfu-util (as it won’t connect through the particle-cli “particle flash --usb firmware” process as the core doesn’t boot up as it seems) but that does resolve anything either (although it does flash yellow and seems to flash the firmware as expected). Factory reset doesn’t do anything either.

I’m starting to think my core is broken, in which case I hope it still has some kind of warranty, but want to rule out any software/firmware options first. Any guidance as to ensure I’ve tested all DFU-UTIL options first?

So I’ve tested the following options:





Firmware binaries flashed:
core-firmware.bin
cc3000-patch-programmer.bin
cc3000-patch-programmer_1_14.bin
core-tinker.bin
deep_update_2014_06.bin

Any ideas??

Thanks,

Joe

Bumping the thread, hoping someone can give me a few pointers… Help!! :slight_smile:

@MrT, have you tried a factory reset on your Core? Does it go in to DFU mode (flashing yellow)? What OS are you using?

Hey @peekay123, thanks for your follow up.
Yes tried factory reset (assuming you mean pressing mode button until core moves from DFU mode to rapidly flashing white LED).
The core does go to DFU mode and I can flash it using the articles above, but after all updates it keeps reverting back to breathing white at reboot.

The above test I’ve done using windows 10.
On my iMac OS X (El Capitan) the core is no longer recognized as a serial device (and I’m no Unix/Linux hero nor a power user on Mac, so prefer to use Windows which I do know pretty well).
Other cores do work on OS X once they boot up, but as this particular core does not seem to boot at all I’m stuck…

Thanks again for your follow up.

Cheers,

Joe

@MrT, does Windows 10 see the Core and do you have the Zadig driver installed? Just remind me if CLI works with the Core on Win10?

@peekay123, yep Win10 and CLI are buddies and work just fine. Other cores (I have 5 in total) work fine except 1 which was running a simple temperature measuring program for days prior to getting stuck in a the white flash routine.

@MrT, the CC3000 can be weird. The first thing I would do is to flash over a good factory reset image using:

particle flash --factory tinker

Then reflash the cc3000 firmware and tinker app with:

particle flash --usb cc3000
particle flash --usb tinker

After the cc3000 patch, the Core should go to DFU mode. I had a Core that refused to do that so after the patch I did a factory reset used CLI to reset the wifi creds. Try that to see what happens.

Hey @peekay123, the problem is that due to the fact the core does not boot beyond the white flashing it cannot be flashed using CLI. Best I can do is flash it using DFU-Util, which I tried using the firmwares listed above.

But to be sure I’ve done it properly, would you have the DFU-Util command I should use as well as the order of the firmware flashes?

Really appreciate the helping hand. Cheers,

Joe

@MrT, if you can get the Core in DFU mode then you can flash using CLI. Do you have the latest CLI installed?

1 Like

Let me check… thanks! :smile:

Just checked using CLI, but for some reason it doesn’t find my DFU device.
This is a problem I had before which is why I switched to using the DFU-Util option… By default CLI wants to use DFU device: “05ac:8215” while the actual Core if DFU Device: “1d50:607f”

Details below as FYI

-=- Error after using “particle flash --factory tinker” command in Admin CMD -=-
Cannot open DFU device 05ac:8215
Cannot open DFU device 17cc:1101

Error writing firmware…Cannot open DFU device 05ac:8215
Cannot open DFU device 17cc:1101
-=- end -=-

-=- When running the DFU-Util -l command I get -=-
C:\Users\zunen\Documents\Visual Studio 2015\Projects\Particle.IO\dfu-util-0.8-binaries\win32-mingw32>dfu-util.exe -l
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

Deducing device DFU version from functional descriptor length
Cannot open DFU device 05ac:8215
Deducing device DFU version from functional descriptor length
Cannot open DFU device 17cc:1101
Found DFU: [1d50:607f] ver=0200, devnum=6, cfg=1, intf=0, alt=1, name="@SPI Flash : SST25x/0x00000000/51204Kg", serial=“8D7123605654"
Found DFU: [1d50:607f] ver=0200, devnum=6, cfg=1, intf=0, alt=0, name=”@Internal Flash /0x08000000/20
001Ka,108*001Kg", serial=“8D7123605654”
-=- end -=-

@MrT, do you have the zadig driver correctly setup for that Core? Do you have any other USB devices plugged in?

1 Like

Hey @peekay123, I’ve got Zadig 2.1.2 (build 677) and set the Cure DFU driver to use WinUSB. (I’ve just peeked again at the Win10 install instructions here: [Particle Official] Windows 10 Full CLI and DFU Setup and made sure I had selected WinUSB (v6.1.7600.16385), as until just now I had the “libusbK (v3.0.7.0)” mode/driver selected).
I do have other USB driver (iMac has memory card and camera build in, as well as a external soundcard). Is it mandatory to use CLI to flash my core? If so I guess I’ll need to disable all devices (even the build in ones)?

When using: particle flash --factory tinker
I get:
Cannot open DFU device 05ac:8215
Cannot open DFU device 17cc:1101

Error writing firmware…Cannot open DFU device 05ac:8215
Cannot open DFU device 17cc:1101
-=-

Cheers,

Joey

Download this: https://github.com/spark/particle-cli/raw/master/binaries/core_tinker.bin

and run this: dfu-util -d 1d50:607f -a 1 -s 0x00020000 -D core_tinker.bin

Done and worked successfully… Now reboot?

-=- Log -=-
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!!!
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 #1
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: "SPI Flash : SST25x"
Downloading to address = 0x00020000, size = 79996
Download [=========================] 100% 79996 bytes
Download done.
File downloaded successfully

What’s the status of the core now?

It remained in DTU mode after the flash. So reset the Core. Once I let go of the reset button it starts breathing white led again…

Can you perform a factory reset?

Assuming I’ve done this correct (basically press mode/reset, let go of reset while holding mode button until it flashes white like its 1999 then let go of mode button) it goes back into the white breathing led loop.

So using above flow:
Press Mode + Reset (only small blue led remains on)
Let go of Reset while holding Mode
Core goes to DTU - keep holding Mode button
Core goes into flashing rapid white LED - keep holding Mode button
Core goes into steady white LED - let go of Mode button
Core starts blinking rapid White led
Core resets and goes into breathing white :frowning:

Sounds like the cc3000 is not responding… might want to keep it on for a while and see if it enters blinking green and so on.