Debug Openthread example

RE: Debug Openthread example

Charlie — Tue, 08 Nov 2022 10:00:18 GMT

Hi Volodymyr,

I am not sure which kind of issue you want to debug with. Different from bare metal, when you develop an application with Zephyr RTOS, there might be several threads on the backend. It will cause unpredictable issues when you set a stop point on the current thread, especially for wireless communication protocol stacks like OpenThread which has time-sensitive interruption handlers.

It is common to enable the debug configuration and read the log file when you encounter one issue to understand what happens with the communication flow or application behaviour.

Best regards,

Charlie

RE: Debug Openthread example

VolodymyrM — Mon, 07 Nov 2022 17:21:13 GMT

Hi Charlie,

Thank you for the update. It works fine when you just run an example without debugging, but when you start j-tag debugger it crashes.

Step to reproduce:

1. Start the debugger with j-tag link

2. Set breakpoint on light_request_handler

3 Debug step-by-step

4. Crash happens

Thanks,

Volodymyr.

RE: Debug Openthread example

Charlie — Mon, 07 Nov 2022 10:06:51 GMT

Hi Volodymyr,

I built the sample C:\NCS\v2.1.1\nrf\samples\openthread\coap_server under NCS v2.1.1 with default settings and everything looks fine. The firmware is attached.

*** Booting Zephyr OS build v3.1.99-ncs1  ***


[00:00:00.527,435] <inf> [N] Mle-----------: Attach attempt 1, AnyPartition 
[00:00:07.034,057] <inf> [N] RouterTable---: Allocate router id 36
[00:00:07.034,423] <inf> [N] Mle-----------: RLOC16 fffe -> 9000
[00:00:07.034,545] <inf> [N] Mle-----------: Role detached -> leader
[00:00:07.082,946] <inf> [N] Mle-----------: Leader partition id 0x7c70ac99
uart:~$

devzone.nordicsemi.com/.../ncs211_5F00_coap_5F00_server.hex

Best regards,

Charlie