WDT kicking in, disabling NRF_FAULT_ID_SD_ASSERT PC 0xA62

[TomDavies]

The watchdog timer is kicking in our code base and I am having trouble tracking down the cause. In a bit to try and debug the issue I disabled the WDT and now I am getting a NRF_FAULT_ID_SD_ASSERT with the PC at 0xA62.

At this point I'm stuck as to how to keep debugging the issue, are there some common tricks to use to get more info? I see a few posts with the same fault but no reference I can check for this value.

We are using the nRF5 SDK, 17.1.0 and softdevice S140 7.2.0

[Susheel Nuguru]

Is it the the disable WDT that caused the assert? 0xA60 sounds familiar as the softdevice assert handler, not sure why it shows you 0xA62.

Can you start the debugger and see if it is the disabling WDT itself that causes this or it happens after few milliseconds after disabling the WDT?

Any chance you can help me reproduce this on DK?

[TomDavies]

During testing we are seeing the WDT kick in. To try and help identify what the issue is, I rebuilt the firmware where we do not enable the WDT. It is more difficult to get it to fail but when it does, that is when we see assert with the PC @ 0xA62.

I don't think it will be reproduceable on the DK. When I've made changes, to try and identify the issue, quite often it is very difficult, or I'm unable to, reproduce the issue.
I will spend the day tomorrow trying to debug this and will add any further infomation I can gather,