Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Panel | ||||
---|---|---|---|---|
| ||||
Why does the hardware watchdog not reset the device? |
Panel | ||||
---|---|---|---|---|
| ||||
In the "Technical data reference guide" revision 5 in chapter "3.12 Watchdog" the hardware watchdog unit is explained. In "Table 9" the escalation paths of the watchdogs are shown. Together with "Figuer 12" you are able to see, that the watchdogs available on application side escalate to the communication side. Only the communication side is able to reset the chip. So the communication sides watchdog has to be configured and used. The FAQ on Software Reset has to be considered. |
Panel | ||||
---|---|---|---|---|
| ||||
What is the intended way to reset the device? |
Panel | ||||
---|---|---|---|---|
| ||||
The FAQ on Software Reset describes this. |
Panel | ||||
---|---|---|---|---|
| ||||
Why is the hardware watchdog on communication side not used? |
Panel | ||||
---|---|---|---|---|
| ||||
For debugging and diagnostic purposes it is not feasible to reset the chip if an error occurs. The protocol stacks contain their own watchdog mechanisms to deal with non responsive systems. You might like to take a look into DPM - Dual Port Memory - Channel Watchdog. Another reason is explained in the FAQ for the Software Reset. |
Panel | ||||
---|---|---|---|---|
| ||||
Do you have some example code on the watchdog even if it does not reset the chip? |
Panel | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
Of course, here it is. But if you consider to reset the chip on your own please have a look into Software Reset.
|
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|