RTOS/TDA3XEVM: TI Sys_Bios task stack

Myat Zin

Part Number: TDA3XEVM

Tool/software: TI-RTOS

I was debugging on the issue when one of my high priority task was blocked and low priority task was running.

I can see the task state using RTOS Object View(ROV). I also know that the task was blocked by for example Event:0x123456.

I would like to find out more about the event which is blocking my high priority task. Can I know how can I see the stack of my high priority task so that I can tell if it is because of Hwi, Swi or semaphore or some external event from some other modules.

over 7 years ago

0 Alex Bashkov over 7 years ago

TI__Genius 13980 points

Hello,

Do you have the Details and Raw tab in your ROV? If so, additional information can be seen there.

Some modules also load up a "Data" tab with for example a memory heap.

Also, see a related e2e which explains an api to distinguish the HWI/SWI tasks e2e.ti.com/.../226533

Hope it helps,

thanks,
Alex

0 Myat Zin over 7 years ago in reply to Alex Bashkov

Intellectual 540 points

Thank you for your reply. I tried to build the BIOS.libType = BIOS.LibType_Debug.

But, unfortunately, I cannot see the Callstacks and got this error from ROVserver.

I think if I can see the Callstacks. I would have some clue on which event is blocking my higher priority task. Any idea how to fix it?

I have my doubt that the lower priority task is using memcpy to copy some data. Do you think memcpy is using some Hwi which disables the Higher priority task from preempt lower prior task?

0 Alex Bashkov over 7 years ago in reply to Myat Zin

TI__Genius 13980 points

Hello,

Let me try to bring in more experts here for comments. Not sure how these tasks intervene in your scenario.

thanks,

Alex

0 Myat Zin over 7 years ago in reply to Alex Bashkov

Intellectual 540 points

Hello Alex,

Thank you so much for helping me. Additionally, I have logged a CSR ticket OMAPS00344381 as I would like to seek TI support with this issue.

0 ToddMullanix over 7 years ago in reply to Myat Zin

TI__Guru* 96960 points

Hi Myat,

We have a known issue with Callstack with unconstructed Task objects. ROV finds Task_Structs and displays them in ROV. If a Task_construct has not been done on the Task_Struct, most views state something like "Uninitialized Task object". For the CallStacks, it freezes instead:( We have fixed it in a future release. You can refer to this thread to get a work-around: e2e.ti.com/.../2845514

Todd

Processors

Processors forum

RTOS/TDA3XEVM: TI Sys_Bios task stack