[Bug]: XRTOS Zephyr Thread Status and Priority inconsistent with Call Stack

[ReinhardKeil]

Description

CMSIS-Debugger 1.2.0

The Thread Status and Priority output of XRTOS view and CALL STACK view are inconsistent

'blinky' sample: in this case XRTOS view seems to be off. Priority shows only ???

'thread' sample: in this case the CALL stack seems to show wrong thread status.

Steps to Reproduce

https://github.com/Arm-Examples/CMSIS-Zephyr - target-type: FRDM-MCXN947 (requires merge of Arm-Examples/CMSIS-Zephyr#9)

Related

#623

[jreineckearm]

RTOS Views (XRTOS) source code for Zephyr can be found here: https://github.com/mcu-debug/rtos-views/blob/main/src/rtos/rtos-zephyr.ts

[RobertRostohar]

pyOCD thread states and priorities should be addressed with #623.

XTROS has issues with Idle state and priorities and should be updated.

Information about Zephyr thread states and priorities:

• there is only one running thread - retrieved from a specific kernel variable (thread state variable does not indicate that a thread is running)
• thread state when not running and is not the idle thread, can be retrieved from the thread state variable and can be (according to kernel_structs.h): Pending, Sleeping, Dead, Suspended, Aborting, Suspending or Ready (Queued)
• thread priority can be retrieved from the thread priority variable (except for idle thread)
• idle thread is either Running or Ready (regardless of thread state) and has always the lowest priority (priority should not be displayed)