My device is freezing and restarting

RE: My device is freezing and restarting

bjorn-spockeli — Wed, 07 Jun 2017 07:22:45 GMT

If you take a look at the Call Stack, you'll see from which function call the error originated and then you'll have to refer to the documentation of that function on Infocenter. The error codes returned by our drivers/libraries are usually global error codes, i.e. one of the error codes listed here. Note: The link is specific to S132 v4.0.2, if you're using another SD, then you should look up the global error codes for the SD you're using.

RE: My device is freezing and restarting

Chocol8 — Mon, 24 Apr 2017 19:46:42 GMT

How to determine what does an error code mean? Is there any resource to read from?

RE: My device is freezing and restarting

tyler — Wed, 01 Mar 2017 21:32:28 GMT

Where do you need to define DEBUG? I tried putting it in my main.c and I don't think it worked.

RE: My device is freezing and restarting

luke — Wed, 25 Jan 2017 14:36:35 GMT

hello, i have a case where debug is causing a system reset. when i call this function "sd_ble_gap_adv_start" it seems im getting system reset every 60 seconds. im running the same code on multiple devices (multiple prototypes custom made in china and dev kits) only one prototype is showing this malfunction. when i try to do the debug configurations in options for target like the step above, the prototype doesnt even start. im suspecting that the prototype has a deffective nrf52832. any ideas or advice?

RE: My device is freezing and restarting

Anders Strand — Tue, 08 Dec 2015 12:51:11 GMT

Why?

In the SDK examples, we check return codes with the macro APP_ERROR_CHECK. This function calls the function app_error_handlerin app_error.c. Here we find this code:

#ifndef DEBUG
    NVIC_SystemReset();
#else

This means that by default, the response to ANY return code other than NRF_SUCCESS will cause a system reset.

If we have defined DEBUG, this happens:

m_error_code = error_code;
m_line_num = line_num;
m_p_file_name = p_file_name;
UNUSED_VARIABLE(m_error_code);
UNUSED_VARIABLE(m_line_num);
UNUSED_VARIABLE(m_p_file_name);
__disable_irq();
while(loop);

We disable interrupts and stay in a loop forever. In this case we can either print out or read (with a debugger) the error code, line number and file name that returned the error code.

Note the warning in the documentation of app_error_handler:

@warning This handler is an example only and does not fit a final product. You need to analyze * how your product is supposed to react in case of error.

Finding the error with the Keil debugger:

1.Set optimization level 0 in target options -> C/C++ and define DEBUG in the preprocessor symbols.

2.Place a break point next to while(loop); (right click ->Insert breakpoint)

3.Run the program, and wait for the error to occur.

4.Read the information by hovering the mouse cursor over the value. Alternatively you can add the values to a watch by doing right click->add to watch X. To display the values in decimal format rather than in hexadecimal, right click the variable (in watch window) and click on "Hexadecimal Display".

Find more information about debugging with Keil here.