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

How can I track what cause the nrf52840 "fatal error"?

I am debugging a BLE system with multi peripherals to one central via NUS(Nordic Uart Service). When I add peripherals to the BLE network. The central board kept resetting and the message is "fatal error" read by J-Link RTT Viewer. I don't know what cause the fatal error in my code. How can I track the problem? Thanks.

Parents
  • Hi,

    When you see "fatal error" in the log but no more explanation, you would benefit from testing a debug build. Then you will get logged the file name, line number and error code. If you use SES, just select "Debug" from the build configuration dropdown. If using another toolchain, define "DEBUG" and "DEBUG_NRF" for the project. Please test that and let me know which function returned which error code.

Reply
  • Hi,

    When you see "fatal error" in the log but no more explanation, you would benefit from testing a debug build. Then you will get logged the file name, line number and error code. If you use SES, just select "Debug" from the build configuration dropdown. If using another toolchain, define "DEBUG" and "DEBUG_NRF" for the project. Please test that and let me know which function returned which error code.

Children
Related