This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

sd_softdevice_enable stops program execution

Hi,

I am having some problems getting the s110 SoftDevice working (sd_softdevice_enable stops the program execution) on a custom PCB. I have seen several issues similar to this in the forum where the answer is to use the same SDK/SoftDevice versions, but I don't think this is the case for me, as I got it to work (with the same SW/SoftDevice) on the nrf6310 board (and the SDK/SoftDevice I am using are compatible, according to the release notes).

Setup on custom board:

NRF51822 QFABB20

S110_nRF51822_7.0.0

nrf51_sdk_v6_1_0_b2ec2e6

ble_app_hrs, with minor modifications.

Issue: Fails after calling sd_softdevice_enable. Unable to read error code (not sure why), but have verified (using breakpoints) that this is the function that returns an error and stops the program.

Note: I also created a different BLE program from scratch using SDK_7.1.0/SoftDevice_7_1_0, which failed in the same function. In that case I was able to print the error_code, which was 0x1001 (NRF_ERROR_SVC_HANDLER_MISSING).

Setup on NRF6310:

NRF51822 QFAAFA

S110_nRF51822_7.0.0

nrf51_sdk_v6_1_0_b2ec2e6

NRF6310

ble_app_hrs, with minor modifications (same as above except definition of UART pins, LEDs etc.).This setup works without any issues.

Additional information:

linker file: intvec start: 0x00016000

ROM start: 0x00016000, ROM end: 0x0003EFFF

RAM start: 0x20002000, RAM end: 0x20003FFF

Toolchain: IAR Embedded Workbench for ARM v7.30.3

I can see that QFABB20 is not explicitly mentioned as tested in the sdk, but I assume this is OK. I assume that the PCB is not the problem (for now), as TWI, UART, etc. are working, and the antenna etc. does not matter at this point. Note that the nrf51822 chip versions differ, but both should be compatible with the SDK/SoftDevice, as far as I can tell.

So assuming that the header files and SoftDevice are OK, any ideas as to what could be the problem?

Any help would be greatly appreciated.

Related