Hi @li3,
You can find inside RTD_WDG_UM.pdf the function for this:
This is located inside the Wdg module for S32DS installation path:
"C:\nxp\S32DS.3.5\S32DS\software\PlatformSDK_S32K3\RTD\Wdg_TS_T40D34M40I0R0\doc"
As for the second question, there are some posts from the MCU on Eclipse forum for these issues:
- https://mcuoneclipse.com/2012/11/04/how-not-to-secure-my-microcontroller/
- https://mcuoneclipse.com/2014/10/05/unlocking-and-erasing-flash-with-segger-j-link/
- https://mcuoneclipse.com/2021/05/20/recovering-cortex-m-microcontroller-with-a-power-glitch/
Best regards,
Julián
Hi NXP,
I wonder how POR_WDG feeds the dog?
How does it determine if the MCU is stuck?
Which register does it read?
Best regards,
Li 3.
Hi @li3,
You can refer to the Swt_Ip example for the sequence on initializing and servicing the Watchdog:
Also, please read the introduction for 34.4 Reset sequence monitoring:
"On every reset event, POR_WDG starts monitoring the reset sequence (including the functional reset entry sequence, in case of functional reset event).
If the chip does not exit the reset sequence within the POR_WDG timeout threshold, then POR_WDG initiates a POR sequence to recover the chip from a stuck or hung scenario. You can view the POR_WDG status in DCM's DCMROPPn registers to obtain:
- Diagnostic status
- Chip details in the event of a POR_WDG reset."
Best regards,
Julián
