NRF52, S132, peripheral dev ~180sec interval reboot on without connection

RE: NRF52, S132, peripheral dev ~180sec interval reboot on without connection

Michael — Mon, 12 Mar 2018 14:43:47 GMT

Great. But the problem is that the BLE device should be in sleep most of time, so we must understand why this error/restarts occurred 🙂

Let's wait for the Nordic specialist :)

RE: NRF52, S132, peripheral dev ~180sec interval reboot on without connection

Oleksii — Mon, 12 Mar 2018 14:32:31 GMT

static void on_adv_evt(ble_adv_evt_t ble_adv_evt)
{
uint32_t err_code;

switch (ble_adv_evt)
{
case BLE_ADV_EVT_FAST:
err_code = bsp_indication_set(BSP_INDICATE_ADVERTISING);
APP_ERROR_CHECK(err_code);
break;
case BLE_ADV_EVT_IDLE:
// sleep_mode_enter();
{
int err_code = ble_advertising_start(&m_advertising, BLE_ADV_MODE_FAST);
APP_ERROR_CHECK(err_code);
}
break;
default:
break;
}
}

thank you

code is correctly executed. no reboot
on event - I exe ble_advertising_start

for understanding the problem of
I need to better understand documentation. )

best regards, Oleksii

RE: NRF52, S132, peripheral dev ~180sec interval reboot on without connection

Oleksii — Mon, 12 Mar 2018 12:07:33 GMT

static void on_adv_evt(ble_adv_evt_t ble_adv_evt)
{
uint32_t err_code;

switch (ble_adv_evt)
{
case BLE_ADV_EVT_FAST:
err_code = bsp_indication_set(BSP_INDICATE_ADVERTISING);
APP_ERROR_CHECK(err_code);
break;
case BLE_ADV_EVT_IDLE:
// sleep_mode_enter();
break;
default:
break;
}
}

the idea is partially true. no reboot now

but the device is not scanned after 30 seconds by the application
at #define APP_ADV_TIMEOUT_IN_SECONDS 30

best regards, Oleksii

RE: NRF52, S132, peripheral dev ~180sec interval reboot on without connection

Oleksii — Mon, 12 Mar 2018 11:47:50 GMT

hello, standart example without WDT, I checked.

best regards

Oleksii

RE: NRF52, S132, peripheral dev ~180sec interval reboot on without connection

Michael — Mon, 12 Mar 2018 11:46:55 GMT

I get the error in function sleep_mode_enter(), that placed in on_adv_evt event handler. But restarting I don't see. Try to comment the function - let's see what we get.

RE: NRF52, S132, peripheral dev ~180sec interval reboot on without connection

Adrian Eggenberger — Mon, 12 Mar 2018 11:39:59 GMT

Hi! Do you have a watchdog running?

RE: NRF52, S132, peripheral dev ~180sec interval reboot on without connection

Michael — Mon, 12 Mar 2018 11:31:46 GMT

Interesting... Let's see what one of the Nordic specialists will answer...

RE: NRF52, S132, peripheral dev ~180sec interval reboot on without connection

Oleksii — Mon, 12 Mar 2018 11:27:29 GMT

Hello Michael
I think the problem is in configuring the SDK

uart example nRF5_SDK_14.2.0_17b948a\examples\ble_peripheral\ble_app_uart\main.c`

change

#define APP_ADV_TIMEOUT_IN_SECONDS 30 /**< The advertising timeout (in units of seconds). */

printf("reset UART Start!\r\n");

err_code = ble_advertising_start(&m_advertising, BLE_ADV_MODE_FAST);
APP_ERROR_CHECK(err_code);

// Enter main loop.
for (;;)
{
// UNUSED_RETURN_VALUE(NRF_LOG_PROCESS());
// power_manage();
}

main problem - I can not disable this reboot
log
313056 13:12:41.488 30.261 COM9 reset UART Start!.
313057 13:13:11.749 30.261 COM9 reset UART Start!.
313058 13:13:42.010 30.261 COM9 reset UART Start!.
313059 13:14:12.272 30.262 COM9 reset UART Start!.
313060 13:14:42.533 30.261 COM9 reset UART Start!.
313061 13:15:12.793 30.260 COM9 reset UART Start!.
313062 13:15:43.057 30.264 COM9 reset UART Start!.
313063 13:16:13.317 30.260 COM9 reset UART Start!.
313064 13:16:43.578 30.261 COM9 reset UART Start!.
313065 13:17:13.839 30.261 COM9 reset UART Start!.
313066 13:17:44.101 30.262 COM9 reset UART Start!.
313067 13:18:14.362 30.261 COM9 reset UART Start!.

RE: NRF52, S132, peripheral dev ~180sec interval reboot on without connection

Michael — Mon, 12 Mar 2018 10:56:35 GMT

Hello! Are you sure that the device is not entering into the deep sleep? In this case, on GPIO event it reboots and starts from the beginning :) Check all functions that called like "power_manager, __WFE, __WFI and etc." :)