@AndyW ditto on what @BDub said, you are an awesome engineer and an incredible asset to Spark! Thank you for the great news!
1 Like
@AndyW Thanks for the update and all your hard work on a solution to the CFOD! Thanks to everyone else who contributed as well!
1 Like
Yeah, thanks for staying on top of this @AndyW, not just on behalf of the 
Community, but also 43Oh.com and all the people out there with buggy CC3000 modules! 
3 Likes
Ditto on the thanks @AndyW !
I am really looking forward to seeing this one in the rear view mirror.
great news guys! @AndyW i owe you a 
ā¦thanks for the detailed updateā¦great stuff!! I thought it might have been a buffer / resource issue. Is there hex & eeprom files for the cc3k that need to get deployed? If so, I have not re-flashed the CC3k before is there a guide to doing so somewhere?
The promised update after our call today with TI:
- We will continue to collaborate with TI and test an official patch candidate (we have something direct from TI engineering at present.)
- If testing does not raise any issues, the plan is for a formal, validated & supported patch to the CC3000 firmware to be available March 28/29.
- We will make this available on the master branch of the CC3000-patch-programmer for users who are comfortable applying patches manually. We will update this topic when that update takes place.
- The next sprint (beginning 31-March) will implement an Over The Air update process for users who are not comfortable applying patches manually, or cannot for other reasons.
- The plan is for the next production run of cores to ship with this patch already applied.
TI remain committed to addressing the underlying root causes of the CC3000 failures, even with the vastly reduced probability of failure.
11 Likes
Great news and great work AndyW! Impressive that a small team can get so much commitment and action from the TI behemoth. 
3 Likes
They may be a small team, but the spark core is a game changer - and they are producing tens of thousands of units IIRC, thatās gotta have some clout! 
4 Likes
Update - we just received the release candidate CC3000 firmware patch from TI.
We and TI are testing in parallel, so that we will have the results in our environment already in hand when TI report their release test results. If both our and TIs testing is successful, then we will release it as quickly as possible, and also incorporate it in the next production run.
This release candidate incorporates the arp workaround and the fix for another CC3000 bug that was initially reported by another TI customer, but they saw the failure in at least one of the debug dumps we sent them, so we should address two known failure modes that result in CFOD with this firmware.
It has only been testing here for 3 hours, but the results are very encouraging.
More news as we have it.
8 Likes
It's like waiting to open presents on Christmas morning as a kid! @bko can be Santa Claus!
3 Likes
The main issue I was having with the Spark Core was when my cellphoneās wireless hot spot would get reset by Verizon it would cause flashing dark blue indicator on the Spark Core that would require a manual rest. This was happening pretty often lately due to high internet traffic.
The latest firmware update via the web IDE has completely fixed that problem it seems. I have not seen any other problems with the Spark Core after about 60 days of usage.
Iām much happier with not having to manually reset the Spark. Hopefully I donāt speak too soon, if I notice anything change Iāll report back.
1 Like
After 26 hours of testing on multiple cores, we have not seen a single failure.
TI reports their first day of formal testing also went well.
Look for another update tomorrow.
5 Likes
How's it been after 5 days?
Today isn't a good day to ask that question. You won't know if he's telling the truth or telling a joke.
3 Likes
I have a found a network that is total rubbish and my core always fails after a while even with the latest CC3300 firmware, so Iāll be happy to test the new patch when itās available and report if it kills the problem forever.
2 Likes
Any update on test results and making this available to the community ?
Testing continues to be positive. I am meeting TI on Monday to tie up any loose ends.
3 Likes
So, any update on the outcome? You really know how to build up tension ;-).
I am dying to get finally a working version of the Spark Core. I would really like to start working with it. But I wonāt start until the connectivity is reliable!
Calling all conspiracy theorists in the community 
Has TI done a runner?, are their open source issues in issuing the update?, is someone making a takeover of spark labs inc ?, the silence is deafeningā¦
What remains the biggest problem with the and 18 days after getting a RC from TI still little word. Appreciate reliable OTA update stuff may be challenging but still nothing for those who flash locally. Certainly firmware v0.2.0 has helped with reliability but the best uptime I can get is < 24hrs
Cāmon @zach @AndyW is there anything you can tell us ?, please.
Hi @deancs,
Thereās no silence from us :), youāre hearing news as soon as we get it.
TI has a large testing lab, and weāre waiting for them to be confident about their cc3000 fix. Weāve done quite a bit of planning, and we want to make sure theyāve tested this patch thoroughly before rolling it out to the community. There should be more details in our post-sprint blog post which should come out sometime Monday since we ended this last sprint just this last Friday.
In a potentially unfair teaser, we continue to hear good things about testing on the patch. As much as we want the patch out quickly, itās also good for them to test very thoroughly. If they find bugs now, that just means more fixes will be included in the next update.
Thanks,
David
1 Like