Re: Breakpoints On WDT Reset
Looking at RCON at start only tells you that a WTD or DMT timeout happend, but not where and why.
Another way to find out about the "where and why" is to set RNMICON.NMICNT to a value and implement _nmi_handler(). This handler gets called on WDT or DMT timeout. Setting NMICNT gives you some time before the reset occurs (which would otherwise occur immediately). You can even remove the respecting flag which stops the reset. And you can set a breakpoint there, or write interesting information into a memory location which is defined with __attribute__((persistent,aligned(16))), which you can still read out after the reset.