CC3200: How short can SL_DRIVER_TIMEOUT_LONG be?

Bill Toohey

Part Number: CC3200

We have a mature product using the CC3200. Extremely rarely, we are seeing the NWP crash somehow and time out - SimpleLink functions will hang and a general event with status SL_DEVICE_DRIVER_TIMEOUT_CMD_COMPLETE is raised.

I've noticed that the default values for SL_DRIVER_TIMEOUT_SHORT and SL_DRIVER_TIMEOUT_LONG are very conservative - 10 and 65 seconds, respectively. These cause our system to lock up for an extremely long time compared to a normal communication cycle, wasting battery.

By reducing these timeouts to 100/200ms, I can replicate the bug during normal operation.

How low can these timeouts safely be set to? I've tried 1 and 2 seconds, and noticed no adverse affect. We're in STA mode and opening a few SSL sockets, transmitting, then hibernating. Wondering if there are any edge cases to be aware of.

over 4 years ago

0 Kobi Leibovitch over 4 years ago

TI__Guru 63006 points

I don't think we have a better number (the number can be changed slightly with each SP).

1 second seems reasonable (if you can bare a higher threshold - use it) for the short timeout (the FS commands can take more especially when writing to flash - they are using the long timeout). I'm not sure what was the reason to pick 10 seconds.

One thing that you can try is to find a value that works during normal operation and set the timeout to 2x or 3x to be on the safe side.

Br,

Kobi

0 Kobi Leibovitch over 4 years ago in reply to Kobi Leibovitch

TI__Guru 63006 points

If you can get NWP log (see instruction in ch. 19 of https://www.ti.com/lit/pdf/swru368) - we may be able to debug the reason for the NWP crash.

Br,

Kobi

0 Bill Toohey over 4 years ago in reply to Kobi Leibovitch

Prodigy 80 points

Thanks for the confirmation!

Unfortunately, the crash is very sporadic and usually on remote, battery powered devices. If we can isolate a cause we'll grab logs for your investigation, but it may not be possible.

Wi-Fi

Wi-Fi forum

CC3200: How short can SL_DRIVER_TIMEOUT_LONG be?