CC3135MOD: How can a CC3135 device recover from crash

Hi,

In normal operation, there should be no case where the CC3135 is unable to respond to MCU commands. That being said, there have been cases where due to a bug or device serial flash corruption where CC31xx devices have become unresponsive.

There are two types of unresponsiveness, with a different resolution to each:

1. If there is an fatal error condition or bug from some runtime condition that causes the CC3135 to become unresponsive, the main action to resolve the issue is to restart the CC3135 through toggling the nHIB signal. This can be done in software by calling sl_Stop/sl_Start, and should be done that way in order to ensure that the CC31xx host driver gets reinitalized correctly. Restarting the CC3135 will clear its RAM and reset it to its power-on defaults stored on external flash. Thus, you should have handlers in your application code that restarts the NWP if a fatal error is detected or unresponsive behavior occurs.

2. If there is a persistent error, or if the CC3135 does not start up correctly, then reprogramming or otherwise restoring the serial flash to a know-good state will resolve any remaining unresponsiveness. For the CC3120 and CC3135, there is a hardware factory reset failsafe feature that will allow both devices to self-reprogram the module's serial flash to whatever state it had at initial programming. By resetting to its initial programming, that will clear any persistent settings and possible memory corruption. You can find documentation on this factory restore feature in section 8.13 of the programmer's guide: http://www.ti.com/lit/swru455

Let me know if you need more clarification on the recovery procedure of the CC31xx, or have further questions on this topic.

Regards,

Michael

Hi Michael，

Thank you! Your reply is so professional and detailed!