What does continuous flashing red indicates?
Have reflashed the cc3000 module and update the firmware.
Also changed the flash memory as it appeared broken before.
Is there away to “factory reset” the core without Jtag?
And with factory reset I mean reflash everything from usb.
Continuous flashing orange can indicate a key problem, but there shouldn’t be a continuous solid red. You can reflash most things via USB, just skip the bootloader / jtag / locking parts on my walkthrough here:
Thanks @jgoggins … But sadly no…
After setting the local network info the core goes to orange, and after a while back to blue flashing (no breathing).
Can not see the rainbow flashing when it waits for the name setup.
Guess I have to figure out how to jtag the device.
Is the result as it should be on dfu-util -d 1d50:607f -a 1 -s 0x00002000 -v -D core_private.der ?
Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2012 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org
Filter on vendor = 0x1d50 product = 0x607f
Opening DFU capable USB device… ID 1d50:607f
Run-time device DFU version 011a
Found DFU: [1d50:607f] devnum=0, cfg=1, intf=0, alt=1, name="@SPI Flash : SST25x
/0x00000000/512*04Kg"
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
No valid DFU suffix signature
Warning: File has no DFU suffix
DfuSe interface name: "SPI Flash : SST25x"
Memory segment at 0x00000000 512 x 4096 = 2097152 (rew)
Downloading to address = 0x00002000, size = 610
Poll timeout 50 ms
Download from image offset 00000000 to memory 00002000-00002261, size 610
Poll timeout 30 ms
File downloaded successfully
Managed to get it to talk to the cloud, breathing…
It also answers on Tinker app.
But when downloading a test application it goes back to the old orange problem.
Is your test application doing anything like writing to the external flash? Is it fast flashing orange after doing an over-the-air update, or is it slowly blinking yellow?
Ah darn. Thank you for posting that video! That video indicates that the external flash on your core has a bad region where the over-the-air firmware update is stored. Your core runs and downloads code, but resets into dfu mode after copying the new firmware indicating that it is faulty. Can you email us at hello@spark.io and we can exchange that core for a working one?