This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

No normal continuation after hitting a breakpoint

I’m debugging the ble_app_blinky demo on a nRF52840-Preview-DK board (BOARD_PCA10056, S140). The device name in the debug configuration is nrf52832_xxaa.

Each time a breakpoint has been hit and I press Resume, there is no normal program continuation. A few days ago, the function app_error_fault_handler() was called indicating: Suspended: Signal: SIGTRAP: Trace/breakpoint trap.

But at the moment, the functon app_error_fault_handler() is not called anymore (strange this inconsitent behaviour). But instead the appication is automatically restarted at calling: main(void), etc.

N.B. At the first line of the app I can Resume without problems. Trouble happens after entering the main infinite loop.

Please, could somebody help to solve this unwanted debugging behaviour?

Parents
  • Please search for the many posts here about debugging with the softdevice. You basically can't do it. Once the softdevice starts advertising and most certainly when it's in connection it has very strict timing requirements. You can break, once, and see where it is, but you can't resume again or the softdevice will assert.

    Also see the blog post from last year on monitor mode debugging which will allow you to debug with the softdevice running, for a while.

Reply
  • Please search for the many posts here about debugging with the softdevice. You basically can't do it. Once the softdevice starts advertising and most certainly when it's in connection it has very strict timing requirements. You can break, once, and see where it is, but you can't resume again or the softdevice will assert.

    Also see the blog post from last year on monitor mode debugging which will allow you to debug with the softdevice running, for a while.

Children
No Data
Related