Did that happen right after? or over the course of a few minutes?
And it works fine between times?
CC3000 support has been a nightmare - it seems the CC3000 chip will sometimes just not respond to a request for data, and that will cause TI's drivers to crash. I've re-written big lumps of them in order to remove interrupts completely, add timeouts to everything, and to try and make it recover when the module does lock up - but I don't know what more I can do.
If you're interested, the 4101 error is when Espruino is calling TI's accept function, and it just never returns (despite the socket being put into non-blocking mode previously). Espruino calls that function in the idle loop, so it gets called quite often. 99.99% of the time it'll be fine, but occasionally the CC3000 just doesn't respond and has to be rebooted.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Did that happen right after? or over the course of a few minutes?
And it works fine between times?
CC3000 support has been a nightmare - it seems the CC3000 chip will sometimes just not respond to a request for data, and that will cause TI's drivers to crash. I've re-written big lumps of them in order to remove interrupts completely, add timeouts to everything, and to try and make it recover when the module does lock up - but I don't know what more I can do.
If you're interested, the 4101 error is when Espruino is calling TI's
accept
function, and it just never returns (despite the socket being put into non-blocking mode previously). Espruino calls that function in the idle loop, so it gets called quite often. 99.99% of the time it'll be fine, but occasionally the CC3000 just doesn't respond and has to be rebooted.