RE: sd_softdevice_enable HardFault

Chris Ergo — Mon, 08 Apr 2019 18:25:22 GMT

Hi Vidar,

It works now. Thank you for the useful information. Comparing the .map files, I determined that the following need to be added to the list of c_preprocessor_definitions for the project:

NRF_SD_BLE_API_VERSION=6;S132;SOFTDEVICE_PRESENT;

Chris

RE: sd_softdevice_enable HardFault

Vidar Berg — Mon, 08 Apr 2019 11:31:44 GMT

Hi,

0x8C8 is the address of the Hard fault handler inside the MBR. This handler is responsible for forwarding the IRQ to the Softdevice which will then forward it to the app, as long as the hard fault breakpoint is disabled in SES.

[quote user=""]The instruction before the one where it halted (0x8C6) is "bx lr", and lr has an invalid address in it (0xfffffff9).[/quote]

This is actually a legal LR value. Please refer to this link for more details (table 2.17): http://infocenter.arm.com/help/topic/com.arm.doc.dui0552a/Babefdjc.html#BABDBEII

[quote user=""]Single-stepping through the SVC call (in my project or ble_app_blinky) doesn't seem to work right. Is that a limitation of the SVC instruction, or are breakpoints always disabled in supervisor mode?[/quote]

The Softdevice will raise an assert if you start single stepping through the code after enabling the Softdevice. The reason for this is that timers used for time-keeping internally are not halted when you hit a breakpoint, only the CPU is. So the protocol stack will detect that it's not meeting its real-time requirements and trigger an assert (error info will be forwarded to the app through the app error handler).

I suspect this has to do with your linker configurations. I would suggest that you compare the *.map file from your build against the one from ble_app_blinky and check if you use the same RAM start address (memory layout with softdevice).