Unwanted reset

RE: Unwanted reset

FormerMember — Fri, 09 Jun 2017 12:50:23 GMT

To make sure the RESETREAS register gives you the correct it should be cleared after a reset and after reading the value. When you read the value, its meaning can be decoded by reading the register meaning in the nRF51 Series reference manual.

RE: Unwanted reset

Francesca — Fri, 09 Jun 2017 11:51:04 GMT

@kristin I red the first thread that you suggested me. Where do you suggest to write the code uint32_t reset_reason = NRF_POWER->RESETREAS; ? Maybe before the for(;;)? Anyway, I wrote this code before a sd_power_system_off() and the returned value is always 0x00010005. What does it mean?

RE: Unwanted reset

FormerMember — Tue, 06 Jun 2017 13:27:24 GMT

Unless "DEBUG" is defined, APP_ERROR_CHECK() will trigger a reset upon an error, see the APP_ERROR_CHECK() function and this thread.

To read the RESETREAS register:

nrfjprog --memrd 0x40000400

It can also be useful to have a look at this thread.

RE: Unwanted reset

Francesca — Tue, 06 Jun 2017 09:01:11 GMT

@kristin How can I check the reset reason register using Keil uVision5 debugger?

RE: Unwanted reset

Francesca — Tue, 06 Jun 2017 08:56:52 GMT

I discovered which code line is generating the reset. Before entering power manage mode this code is executed

void pre_power_manage_settings(void)
{
	//Timers stop
//	system_timer_stop(); 
	one_sec_timer_stop();
	button_idle_timer_stop();
	//buzzer_timer_stop();
	//rele_timer_stop();
	//led_repetition_timer_stop();
	//led_timer_stop();
	//wdt_refresh_timer_stop();
	three_min_timer_start();

	//Stop advertising
	beacon_advertising_stop();
	
	
}

After having waited 10 minutes the system wakes up and this code is executed

void post_power_manage_settings(void) 
{
	//Timers stop
//	system_timer_stop(); 
	one_sec_timer_start();
	button_idle_timer_start();	
	//Stop advertising
	beacon_advertising_start();		
}

void beacon_advertising_start(void)
{

	uint32_t err_code;
	ble_gap_addr_t ble_gap_addr;

	err_code = sd_ble_gap_address_get(&ble_gap_addr);
	

	err_code = sd_ble_gap_adv_start(&m_adv_params);
	if (err_code == NRF_SUCCESS)
			advertising_start = true;

	APP_ERROR_CHECK(err_code);
}
    void beacon_advertising_stop(void)
{
	uint32_t err_code;
	err_code = sd_ble_gap_adv_stop();
	if (err_code == NRF_SUCCESS)
			advertising_start = false;
	APP_ERROR_CHECK(err_code);
}

In this case the system doesn't reset and advertising starts and timers reload with no problem. The same code is executed after pressing the button but in this particular case the system restarts. In order to avoid reset after pressing button, I should comment the code line beacon_advertising_start(); How can I start advertising again without generating a reset after pressing the button?

RE: Unwanted reset

CBD — Thu, 01 Jun 2017 14:45:30 GMT

This is a good first step. You may also wish to check that you're not initialising your timer when it is already initialised. I have found that this can cause an ASSERT which will then trigger a hardware reset.

RE: Unwanted reset

FormerMember — Thu, 01 Jun 2017 13:53:42 GMT

The first step would be to check the reset reason register (RESETREAS) after the reset. Chapter 12.1.11 in the nRF51 Series Reference Manual explains the various reset sources.