nrf5340 - how to print thread priority

[Gabriele]

Hi,
I'm with NCS v2.4.2 and Zephyr v3.3.99.
I wanted to get a runtime log of thread priorities and stack usage, for tuning purpose.
I've found a valuable Zephyr support to print some information automatically once every 20 seconds.

CONFIG_THREAD_NAME=y
CONFIG_THREAD_ANALYZER=y
CONFIG_THREAD_ANALYZER_AUTO=y
CONFIG_THREAD_ANALYZER_RUN_UNLOCKED=y
CONFIG_THREAD_ANALYZER_USE_PRINTK=y
CONFIG_THREAD_ANALYZER_AUTO_INTERVAL=20
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_THREAD_ANALYZER_ISR_STACK_USAGE=n

The results looks like this

Thread analyze:
 stesth              : STACK: unused 9512 usage 728 / 10240 (7 %); CPU: 0 %
 hgwd                : STACK: unused 328 usage 696 / 1024 (67 %); CPU: 0 %
 0x200049d8          : STACK: unused 648 usage 376 / 1024 (36 %); CPU: 0 %
 BT RX               : STACK: unused 2000 usage 200 / 2200 (9 %); CPU: 0 %
 BT TX               : STACK: unused 752 usage 272 / 1024 (26 %); CPU: 0 %
 thread_analyzer     : STACK: unused 144 usage 880 / 1024 (85 %); CPU: 0 %
 sampler_low         : STACK: unused 456 usage 568 / 1024 (55 %); CPU: 0 %
 sampler_high        : STACK: unused 528 usage 496 / 1024 (48 %); CPU: 0 %
 ctrla               : STACK: unused 304 usage 720 / 1024 (70 %); CPU: 0 %
 comuf               : STACK: unused 284 usage 740 / 1024 (72 %); CPU: 0 %
 usbd_workq          : STACK: unused 64 usage 960 / 1024 (93 %); CPU: 0 %
 sysworkq            : STACK: unused 1976 usage 824 / 2800 (29 %); CPU: 0 %
 idle                : STACK: unused 172 usage 148 / 320 (46 %); CPU: 95 %

Unfortunately this support don't print thread priorities.
How to get this additional feature ?

[Elfving]

Hello Gabriele,

I am not sure if there is an easy config that can print the thread priorities in the same way. But maybe the new Thread Viewer in our VSC debugger would fullfill your requirements? 

Though it doesn't really print in the same way as what you've shown me, it does give some of the same info.

Regards,

Elfving

[Gabriele]

Unfortunately I do not use VSC.
It would be enough obtaining someway the thread ID from struct thread_analyzer_info, and then using
k_thread_priority_get (k_tid_t ID).

[Elfving]

Sorry about the wait Gabriele, I've been sick for a few days.

Is this still an issue you are working on, or have you found solution?

Not sure exactly how you could get all the thread IDs from that struct. Though I see you could do it using k_thread_priority_get() like you mentioned. This is for instance how it is done in the dining philosophers sample, though with k_thread_priority_get(k_current_get()).

Alternatively you also have a way to iterate over all the threads using k_thread_foreach.

Regards,

Elfving