My devices restart app but no log

[BuuPQ]

When my device receives data from the Xiaomi Zigbee switch, sometimes it reboots without any logs.

(Note: Normally, when there’s a bug, the device pushes logs to UART, but in this case, there’s nothing.)

```

#:[00:01:12.909] APP_DBG callback_handle.c:77 Device send command info:
[00:01:12.918] APP_DBG callback_handle.c:78 Short addr : 0x0C2B
[00:01:12.926] APP_DBG callback_handle.c:79 Endpoint : 1
[00:01:12.933] APP_DBG callback_handle.c:80 Cluster ID : 6 (0x0006)
[00:01:12.941] APP_DBG callback_handle.c:81 Command ID : 10 (0x0A)
[00:01:12.949] APP_DBG callback_handle.c:82 Direction : 1 (To Client)
[00:01:12.958] APP_DBG callback_handle.c:86 Send response : 1 (Do NOT send default response)
[00:01:12.968] APP_DBG callback_handle.c:39 Payload data: (len = 4):
[00:01:12.977] APP_DBG callback_handle.c:40 << START PAYLOAD >>
[00:01:12.984] APP_DBG callback_handle.c:71 0x0000: 00 80 20 03 | .. .
[00:01:12.994] APP_DBG callback_handle.c:73 << END PAYLOAD >>
[00:01:13.002] APP_DBG callback_handle.c:164 [ZCL RSSI] src:0x0C2B cluster:0x0006 cmd:0x0A LQI:169 RSSI:-25 dBm
[00:01:13.014] APP_DBG callback_handle.c:172 CB ==> Handle Client command
[00:01:13.022] APP_DBG callback_handle.c:327 [ONOFF][CLIENT] Report Attribute received from 0x0C2B, endpoint 1
[00:01:13.034] APP_DBG callback_handle.c:328 Payload len = 4
[00:01:13.042] APP_DBG callback_handle.c:336 - Attribute ID : 0x32768
[00:01:13.050] APP_DBG callback_handle.c:337 - Type : 0x32
[00:01:13.058] APP_DBG callback_handle.c:338 - Value : 3 (0x03)
[00:01:13.067] APP_DBG callback_handle.c:355 => Button Action: TRIPLE CLICK
[00:04:21.168] APP_DBG callback_handle.c:77 Device send command info:
[00:04:21.177] APP_DBG callback_handle.c:78 Short addr : 0x0C2B
[00:04:21.185] APP_DBG callback_handle.c:79 Endpoint : 1
[00:04:21.192] APP_DBG callback_handle.c:80 Cluster ID : 6 (0x0006)
[00:04:21.200] APP_DBG callback_handle.c:81 Command ID : 10 (0x0A)
[00:04:21.209] APP_DBG callback_handle.c:82 Direction : 1 (To Client)
[00:04:21.217] APP_DBG callback_handle.c:86 Send response : 1 (Do NOT send default response)
[00:04:21.227] APP_DBG callback_handle.c:39 Payload data: (len = 4):
[00:04:21.236] APP_DBG callback_handle.c:40 << START PAYLOAD >>
[00:04:21.243] APP_DBG callback_handle.c:71 0x0000: 00 00 10 00 | ....
[00:04:21.253] APP_DBG callback_handle.c:73 << END PAYLOAD >>
[00:04:21.261] APP_DBG callback_handle.c:164 [ZCL RSSI] src:0x0C2B cluster:0x0006 cmd:0x0A LQI:169 RSSI:-33 dBm
[00:04:21.273] APP_DBG callback_handle.c:172 CB ==> Handle Client command
[00:04:21.281] APP_DBG callback_handle.c:327 [ONOFF][CLIENT] Report Attribute received from 0x0C2B, endpoint 1
[00:04:21.293] APP_DBG callback_handle.c:328 Payload len = 4
[00:04:21.301] APP_DBG callback_handle.c:336 - Attribute ID : 0x0000
[00:04:21.309] APP_DBG callback_handle.c:337 - Type : 0x16
[00:04:21.317] APP_DBG callback_handle.c:338 - Value : 0 (0x00)
[00:04:21.326] APP_DBG callback_handle.c:346 => Device is now OFF

▒I: nRF5 802154 radio initialized
*** Booting nRF Connect SDK v2.9.2-4ab7b98fc76f ***
*** Using Zephyr OS v3.7.99-aa34a5632971 ***
[00:00:00.016] APP_PRINT app.cpp:33 Starting Zigbee Gateway Application...
[00:00:00.025] APP_PRINT app.cpp:36 Main thread starting
[00:00:00.032] APP_DBG led.cpp:35 Init led
[TaskCreate] TaskSystem id: 0 StackSize: 0x1000 Prio: 10 Cb: 0x000084D9
[TaskCreate] TaskSerial id: 1 StackSize: 0x1000 Prio: 8 Cb: 0x000081D1
[TaskCreate] TaskZigbee id: 2 StackSize: 0x1000 Prio: 10 Cb: 0x00008705
[TaskCreate] TaskConsole id: 3 StackSize: 0x1000 Prio: 10 Cb: 0x00007E85
[00:00:00.501] APP_PRINT app_console.cpp:137 Init console !!!
[00:00:00.508] APP_LOG app_console.cpp:141 [Console] ==> Started [3]
```

Is it possible that the device was rebooted by the ZBOSS library without any logs being pushed to UART? I need some advice on how to debug this issue. It only occurs during data exchange with another device.

[Edvin]

Hello,

Is it possible that the device was rebooted by the ZBOSS library without any logs being pushed to UART?

I have not seen cases of that earlier, at least.

ARe you using the Zigbee Addon? Or another version of NCS?

Can you check your reset reason? You can use this snippet close to the start of your main() function:

    uint32_t my_resetreason = NRF_RESET->RESETREAS;
    printk("Reset reason: 0x%08x\n", my_resetreason);
    NRF_RESET->RESETREAS = my_resetreason;  // This register is retained accross resets. Clearing the bits for this reset for next time.

What does it say when it boots up after a reset without any logs?

You can also look up the reasons in this register here:

https://docs.nordicsemi.com/bundle/ps_nrf54L15/page/chapters/power-and-clock/reset/doc/reset.html#ariaid-title13

Best regards,

Edvin

[BuuPQ]

Hi Edvin ,  my reset code is "Reset reason: 0x00000040". And i use Zigbee R23 add-on + Zephyr OS v3.7.99. My hardware is nrf54l15dk

[BuuPQ]

My devices reboot when I send multiple noti. If there's a RAM overflow or invalid memory access, there should be a log, right?

[Edvin]

Reset reason = 0x40 is a software reset:

BuuPQ said:

If there's a RAM overflow or invalid memory access, there should be a log, right?

I would think so. If it isn't already, can you please try to add CONFIG_ASSERT=y in your prj.conf?

You should also check your application folder. Do a search for "NVIC_SystemReset()" and "sys_reboot()", to see if there is anywhere in your application that any of these are called by accident.

Best regards,

Edvin