EDIT: Skip to next post first, then back here if no joy.
Here’s some steps I just followed and some observations I made, with a known working core …
- Factory reset
- Core into DFU mode
spark flash --usb deep_update_2014_06
- Core reboots and enters listening mode (flashing blue). Deep update flash not performed yet.
spark setup wifi … but using bogus credentials, so the core cannot connect. Core is now flashing green for a long time. Deep update is still not performed.
- Place core back in listening mode
spark setup wifi with correct credentials. Core reboots, connects, then performs deep update, indicated by flashing crimson (purple). Core eventually reboots and connects to cloud.
This tells us that the core must be able to at least establish a WiFi access point connection before it will perform the the deep update. (I highly doubt a cloud connection would be required. But I’m not sure.)
So @ciukes … my question for now is, did you actually witness the lengthy session of crimson/purple LED flashing indicating that the deep update was in progress, directly after the DFU-
spark flash --usb deep_update_2014_06 command? (I am guessing “No”.)
My main reason for asking right now is only so that I can replicate the events, to see if I can get my core in the exact same state as yours.
P.S: Incidentally, I’m not sure I have ever witnessed a core flashing cyan in quite that same ‘erratic’ manner. Rapid and for a long time, yes … erratic, no. I originally put this down to video frame rate interpolation, though. Perhaps you could confirm?