Issues with migrating SoftDevice S132 to S140

RE: Issues with migrating SoftDevice S132 to S140

Susheel Nuguru — Thu, 28 Jul 2022 20:00:58 GMT

There are lots of post explaining how to debug an hardfault. Like this one and this one.

Normally your application's hardfault handler should have been called to give more context and nature of the hardfault. There are some logs in the application's hardfault handler delivered in the examples of SDK which throw out more information. If you are stuck at 0XA60, then most likely you are in debug mode??

RE: Issues with migrating SoftDevice S132 to S140

rareBit — Thu, 28 Jul 2022 15:21:19 GMT

[quote userid="6207" url="~/f/nordic-q-a/90275/issues-with-migrating-softdevice-s132-to-s140/378364"]you need to first find out which instruction in the application caused the hardfault.[/quote]

Could you explain how to do that?

RE: Issues with migrating SoftDevice S132 to S140

Susheel Nuguru — Fri, 22 Jul 2022 16:25:21 GMT

[quote user=""]When I run the debugger, the terminal prints "<info> app_timer: RTC: initialized." and crashes at unknown function at 0xA60. This is puzzling to me because it suggests the Softdevice isn't supported right? So I'm not sure which step I've missed to do this successfully. [/quote]

0XA60 is the hardfault handler inside the softdevice, you need to first find out which instruction in the application caused the hardfault. If it is only the memory section that is different, then it does look like the memory section and the softdevice might not be compatible.