When I enter break points inside ble_evt_handler(), it always ends up at NRF_BREAKPOINT_COND

[KEITH]

I'm using SDK version 15.0.0_a53641a on nRF52840 with softdevice s140_nrf52_6.1.0_softdevice.hex.

When I enter break points inside ble_evt_handler, it always ends up at NRF_BREAKPOINT_COND; // On assert, the system can only recover with a reset.

In the past when running softdevice s132_nrf52_5.0.0_softdevice.hex on the nRF52832 I never had an issue placing break points inside ble_evt_handler.

Any suggestions as to what is causing this?

[Sigurd]

Hi,

When you set breakpoints in the ble_evt_handler, you will halt the CPU when you hit the breakpoint. The SoftDevice will not be able to transmit any BLE packets in this case, and when you continue execution again/resume the CPU, the SoftDevice detects it was not able to transmit the necessary BLE packets in time, and the SoftDevice will then assert, and you will enter the app_error_fault_handler() function.

Note for Segger Embedded Studio: When hitting the NRF_BREAKPOINT_COND in the error-handler, you can step into app_error_save_and_stop() (assuming you are you using the SES Debug project configuration)  by clicking on the “Step into” button in the disassembly window.

[KEITH]

Thanks Sigurd, Do you happen to have instructions on how to setup the SES Debug project configuration?

[KEITH]

One other thing, why would this not affect the nRF52832 using softdevice s132_nrf52_5.0.0_softdevice.hex? I'am able to set breakpoints for that chip with no problems within ble_evt_handler. 

[Sigurd]

KEITH said:

Do you happen to have instructions on how to setup the SES Debug project configuration?

Yes, just select "Debug" in the Project Explorer.

[Sigurd]

KEITH said:

One other thing, why would this not affect the nRF52832 using softdevice s132_nrf52_5.0.0_softdevice.hex?

The behavior should be the same here. Are you using the same BLE example as you did with the S132 v.6.1 when you test this?

[KEITH]

There are some differences between the two examples but, the ble_evt_handler() is using the same code for both. Just different softdevices.

[Sigurd]

If you get the assert or not, will depend on what type of operation the SoftDevice need to do.

If you are in a connection with a phone, you set the breakpoint, and enable some BLE notification on the phone, or try to send some data from the phone to the nRF, the SoftDevice will assert.