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

"ble_app_uart" project app is going to down to at the point app_error_fault_handler() on SES.

I just tested with the example project, "ble_app_uart" using SDK, "nRF5SDK17009d13099.zip" on nRF52DK (labelled with PCA10040 1.2.4 2018.23) board on Segger embedded studio.

After 5 minutes, "ble_app_uart" project app without any added code is going to down to at the break point in function, "app_error_fault_handler()" on SES as following attached capture shot image.

I think it may have bugs on that example. please let us know how to fix it.

The shot image in case the problem occurs is as following and the image is the captured SES screen with debugging information and call stack.

  • Hi

    This is because the ble_app_uart example will try to go to sleep (system OFF) mode after five minutes. If the device tries to enter this mode while you are debugging, you will get a fatal error like this when trying. You can confirm this by setting NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED to 0 in sdk_config.h and include DEBUG to your preprocessor definitions. Then you should see something along the lines of this in the Debug Terminal:

    <info> app_timer: RTC: initialized.
    <info> app: Debug logging for UART over RTT started.
    <error> app: ERROR 8198 [Unknown error code] at C:\nordicsemi\SDK\nRF5_SDK_17.0.0_9d13099\examples\ble_peripheral\ble_app_uart\main.c:323
    PC at: 0x0002ABCF
    <error> app: End of error report

    This points to the error occurring in line 323 of main.c which is the APP_ERROR_CHECK after sd_power_system_off();

    Best regards,

    Simon

Related