Issues with migrating SoftDevice S132 to S140

[rareBit]

nRF 5 SDK 17.0.2

I am working on getting the nfc_pairing_reference example application migrated to S140 on two nrf52840 DKs. I have successfully ported the hardware, the demo runs successfully on the PCA10056 hardware using s132 (v7.2.0). But I am having trouble migrating the example code to s140 (v7.2.0). I followed these instructions.

Here are my placement macros:

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x80000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x10000

FLASH_START=0x00026640

FLASH_SIZE=0x5a000

RAM_START=0x20001d28

RAM_SIZE=0xe2e8

(I used the FLASH_START the debugger recommended)

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. 

Thanks in advance,

Sam

[Susheel Nuguru]

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. 

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.

[rareBit]

Susheel Nuguru said:

you need to first find out which instruction in the application caused the hardfault.

Could you explain how to do that?

[Susheel Nuguru]

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??