Hi
I'm running MDK 5.22 with CMSIS-RTOS2 RTX5 in a simple test using Event Viewer with a UNINK Pro on an STM32F429.
I suspect I'm doing something wrong, but I cannot figure out how to get the Event Viewer to display separate threads. All my threads appear under main(1) as shown in this shared screenshot link: " As you can see, the exceptions (SVCall, PendSV, SysTick, TIM3) are shown separately as one would expect.
Each of the threads are in their own C file, and have unique names.
I am using the JTAG port with the 4bit trace port set up as described here: www.keil.com/.../ulinkpro_STM32F4xx_ETM.htm
I have applied the trace settings as described on this page: www.keil.com/.../uv4_db_dbg_event_viewer.htm
My test project includes RTX5 as source, and the use of "DBG_MSG" as described in the following link, no longer seems relevant in RTX5 :http://www.keil.com/support/docs/3630.htm
Any advice will be appreciated.
Thank you.
For such a question, I would suggest you to contact ARM-Keil technical support via this link directly: www2.keil.com/.../silver
Valid point.
I asked here as it was over the weekend, and I hoped somebody on this forum would know something about that.
Thanks anyway.
If anyone's interested, it is a known bug in the RTX5 Event Viewer and is being worked on by the KEIL developers.
Thank you very much for that, I was going to create a thread too.
But I wonder how they want to do that, in RTX several debug methods where implemented which use the ITM_Port 31:
void dbg_task_notify (P_TCB p_tcb, BOOL create); void dbg_task_switch (U32 task_id); void dbg_init (void);
They are not present in RTX5, so either Keil has to implement a system interpreting the event manager's output or the RTX5 team has to implement the mentioned functions.
Does anybody have more information on that?
Any news?
Was this problem resolved? I see the same issue ..