MCU Watchdog Controller Usage Caveats
www.ti.com
358
SWRU543–January 2019
Submit Documentation Feedback
Copyright © 2019, Texas Instruments Incorporated
Watchdog Timer
10.4 MCU Watchdog Controller Usage Caveats
10.4.1 System Watchdog
Figure 10-9 shows the watchdog flow chart.
Behavior:
• The system WDOG timer expiry forces the MCU and network processor through a reset cycle, but the
WLAN domain (MAC and Baseband) is not reset.
• Subsequent recovery takes MCU and NWP out of reset at the same time.
Issue:
• The preceding behavior does not allow a clean reset of a WLAN domain.
• The recovery flow order is not congruent to the software flow (NWP start-up is always initiated by the
MCU once the MCU boot loading is completed).
Resolution: The MCU application must detect a recovery from the WDOG trigger and force the device
into complete hibernation with a wake-up associated with an internal real-time clock (RTC) timer. This
ensures a complete system cleanup.
NOTE: For CC3220 variants, this step is not needed because it is done by the MCU ROM
bootloader.
To Next Page
Loading...
