If you have a test environment that produces a lot of CFOD Please try this test file and report back:
This has recovery code in it to detect the CFOD and does a reconnect in about 20 second total.
I have ran it for over 72 hours with no issues (hangs or faults) and recovers from network issues in 20 seconds.!
It will Log CFOD;s as
0000164364: void SPARK_WLAN_Loop() (582):Resetting CC3000 due to 2 failed connect attempts
The test will send a udp packet every 60 seconds to 10.10.0.1 and also does an http get of a lot (3880+ bytes) of data from nscdg.com
Log data goes to Serial1 (3.3V tx,rx pins)
All the log data is critical, because the faults are logged after being detected and mitigated so they do not sent the CPU into a hardfault. Please send the logs and LED observations. (if it dies in a red …—… Blink N …—…)
1(Faults,RGB_COLOR_RED,HardFault) 12 (Faults,RGB_COLOR_RED,NMIFault)
3 (Faults,RGB_COLOR_RED,MemManage)4 (Faults,RGB_COLOR_RED,BusFault)
10 (Softare,RGB_COLOR_RED,AssertionFailure)11 (Softare,RGB_COLOR_RED,InvalidCase)