Debugging NRF51422?? How can i use err_code to debug my nrf51422??

RE: Debugging NRF51422?? How can i use err_code to debug my nrf51422??

syntroniks — Thu, 11 Jun 2015 14:42:40 GMT

I wanted to add that I supplied my own app_error_handler and could not get line number & filename without the DEBUG preprocessor directive. Hope this helps someone in the future.

RE: Debugging NRF51422?? How can i use err_code to debug my nrf51422??

Rahul Faizu — Tue, 09 Jun 2015 06:33:09 GMT

Thanks Martin for your help.

RE: Debugging NRF51422?? How can i use err_code to debug my nrf51422??

MartinBL — Mon, 08 Jun 2015 11:34:54 GMT

One way to use the err_code is to define DEBUG globally, like shown in the image, and hence use APP_ERROR_CHECK(err_code); to assert the error code. This way, if you get an error, you will end up in a while forever loop in app_error_handler() (defined in app_error.c) and you can find out in which file and line number your error occurred using the debugger.

RE: Debugging NRF51422?? How can i use err_code to debug my nrf51422??

Susheel Nuguru — Sat, 06 Jun 2015 19:41:09 GMT

The error code does not get stored anywhere. You have to either print it on serial port devzone.nordicsemi.com/.../

or Segger RTT devzone.nordicsemi.com/.../

or you have to set a break in keil debugger and break at the line error is generated and find out what error code is. Once you know the error code number, you can find its documentation in the relevant header files.