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

Unknown firmware crash on BLE connect

Hi, i have a wierd behavior on my board. On my nrf52832 custom board i have sdk14.1 with DEBUG flag and NRF_LOG enabled. Usualy when my board crash i got into some kind of Falat error message.

But two times today my board has crashed when trying to connect with mobile phone to the board without any message.

Is there something else i can turn on to catch the source of this error?

Parents
  • Yes, debugging BLE applications can be tricky, but if your board crashes you don't care about timing sensitivity. You only care about what your nRF52 is doing when/after it has crashed.

    You say that you get some kind of Fatal error message. My guess is that your application crashes because one of your functions return an error, the error is inspected using APP_ERROR_CHECK(err_code), which finally sends your application into the function called app_error_fault_handler() (located in app_error_weak.c). If you use a debugger and set a breakpoint inside this function you can get the error code and the filename and line number of where the error originated.

Reply
  • Yes, debugging BLE applications can be tricky, but if your board crashes you don't care about timing sensitivity. You only care about what your nRF52 is doing when/after it has crashed.

    You say that you get some kind of Fatal error message. My guess is that your application crashes because one of your functions return an error, the error is inspected using APP_ERROR_CHECK(err_code), which finally sends your application into the function called app_error_fault_handler() (located in app_error_weak.c). If you use a debugger and set a breakpoint inside this function you can get the error code and the filename and line number of where the error originated.

Children
No Data
Related