Both of my cores cannot be claimed via the app. Both have the same light sequence.
Blinking blue: Listening for Wi-Fi credentials
Solid blue
Blinking green
Blinking cyan
Breathing cyan for about 2 seconds
Solid Magenta
The app will then eventually tell me my core cannot be claimed.
I tried through the usb but I am just getting back into this and about as novice as one can get. Everytime I fix an error given by Command Prompt a new one pops up and it’s getting frustrating to get Spark Cli installed. I also tried claiming it through the Spark Build with the core’s id…to no avail. Many resets later I am still nowhere.
I have tried however I can’t get the CLI installed. I think it has something to do with visual studio but I’m not sure. I tried grabbing the ID and claiming through the Spark Build but that didn’t even do anything, the app will at least trigger the spark core but still won’t find a core.
You don’t technically need the Spark CLI; you can use a terminal emulator like PuTTY as the instructions say. You can claim the core in the webIDE with the number core ID from the terminal program.
@kennethlimcp had a good idea–a video would help us figure out what is wrong.
On startup it will go into listening mode. When I try to to connect through the app on my phone it will go into the sequence I posted. I don’t recall it ever blinked magenta for an update. I can’t count all the resets I’ve done.
I am able to claim core without problems, but in first minute or two after power up. It is visible trough clould too, but after minute or so after turning solid magenta, it goes offline.
Tried:
factory reset, and reconnecting to wireless via usb / serial
deleting and reclaiming core again
different cable and power supply
different wireless network
I tried to program it, but it seems that “online window” is to short, so i am unable to do that trough cloud.
During the 1-2 minutes when the core gets online, did you perform any task? Like flash firmware etc…
I will be happy to help you fix this but it will take some effort on your part. Otherwise, we can arrange for an exchange.
My guess is that the core default firmware and the factory reset firmware is giving us a headache since factory reset did not helped. Or the CC3000 needs a patch!
A combination of these will solve the issue and i’m confident it will work
Another way to get some idea is to grab an access-token from the Web IDE and open this url:
api.spark.io/v1/devices/events?access_token=xxxxx
You will see some output when the core gets online. This should give us some idea what’s going on as well as the CC3000 patch version!
Yep, this is kickstarter edition, but it was almost unused since now, no, it is OSX, i already installed spark-cli and dfu-util ( https://github.com/spark/spark-cli ) , and will try to update it later today.
So, if i got it correctly, i should put it in DFU mode