Zephyr implementation open points

mcu-debug / rtos-views

RTOS views for microcontrollers

MIT License

24 stars 11 forks source link

Zephyr implementation open points #8

Open PhilippHaefele opened 1 year ago

PhilippHaefele commented 1 year ago

[ ] Inform user when CONFIG_THREAD_MONITOR is not set
[ ] Check if stack_info.size is always in Bytes and not number of stack entries and adapt code if the size is in stack entries
[ ] Add support for more arches and inform user when not supported (it's not always callee_saved.psp)
[ ] Try to get information like real address and type of kernel objects (semaphore, mutex etc.) the tasks are pending on (we only have their _wait_q_t *pended_on right now) => when CONFIG_TRACING and CONFIG_TRACING_OBJECT_TRACKING are enabled, it seems that we have lists of all object types => see tracing_tracking.c for link list entry points

rosterloh commented 1 year ago

Works for me

hongshui3000 commented 1 year ago

very much looking forward to

PhilippHaefele commented 1 year ago

very much looking forward to

Anything in mind that you need, as in general Zephyr works?

hongshui3000 commented 1 year ago

All Zephyr objects supported by Zephyr's object tracking system (timers, memory slabs, semaphores, mutexes, stacks, message queues, mailboxes, pipes, and queues) are supported in the rtos-views

dbongartz commented 9 months ago

Do understand correctly that the thread info for zephyr shows "current stack usage"?

If I use "CONFIG_THREAD_ANALYZER=y" I can see that this prints "maximum stack usage". Microsoft's "Embedded Tools" also print maximum size (but not current size).

I had a look at the code here and guess it could be changed to show:

% Current / % Max (Current B / Max B / Size B)

Sadly I am not a TS developer and don't understand much of how to add that correctly.

haneefdm commented 9 months ago

Thanks, @dbongartz Maybe one of our Zephyr experts will chime in. This is 99.8% user-contributed stuff.

PhilippHaefele commented 5 months ago

@dbongartz

First of all, sorry for not responding. Need to find some spare time to work on the extension again.

Do understand correctly that the thread info for zephyr shows "current stack usage"?

I just did check the code and i think it shows the "current" (last saved. See #28) stack usage. I should state that in the header somehow like i did for uC/OS-II.

stemschmidt commented 3 months ago

This is such a great tool! Thank you!