NRF52840：Thread communication debugging is restarted

RE: NRF52840：Thread communication debugging is restarted

Maria Gilje — Tue, 14 Feb 2023 08:59:39 GMT

Hello,

Increase the stack size for openthread by setting CONFIG_OPENTHREAD_THREAD_STACK_SIZE in your prj.conf. It is either 6240 or 3168 by default depending on whether CONFIG_OPENTHREAD_COMMISSIONER or CONFIG_OPENTHREAD_JOINER are set or not.

You can print the thread analyzer log in a serial terminal by including the following lines in your prj.conf:

# Thread analyzer
CONFIG_THREAD_ANALYZER=y
CONFIG_THREAD_ANALYZER_USE_PRINTK=y
CONFIG_THREAD_ANALYZER_AUTO=y
CONFIG_THREAD_ANALYZER_AUTO_INTERVAL=5
CONFIG_THREAD_NAME=y

The lines above will enable the thread analyzer to print a report regularly to the terminal.

Best Regards,
Maria

RE: NRF52840：Thread communication debugging is restarted

Lon — Tue, 07 Feb 2023 07:07:15 GMT

Hi,

Thank you for your reply. May I ask where I should modify the size of the Thread? I used Zephyr Thread Analyzer but I don't know how to print out the log. dk_set_led_toggle() is a flashing check that you can directly delete without affecting the test.

RE: NRF52840：Thread communication debugging is restarted

Maria Gilje — Wed, 21 Dec 2022 14:14:17 GMT

Hello,

This could be a stack overflow for the thread named openthread. Try to increase the stack size for that thread.

To get an overview of the stack usage for all threads you can enable the Zephyr Thread Analyzer to get reports on the stack usage for each thread.

An additional note: In your attached code on line 112 there is a declaration of dk_set_led_toggle() but I can't find the implementation.

Kind Regards,
Maria