• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 32 subscribers
  • Views 824 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OS task can not be put into run mode after a burst of CAN packages came in

QJ Wang
Guru**** 200496 points

Other Parts Discussed in Thread: TM4C123GH6PZ

My customer reported a issue related to the OS they are using-TI SYS/BIOS, there is a task in their system that is waiting for the event posted in CAN interface HWi handler. When the issue is reproduced, the symptom is that the task can not be put into run mode after a burst of CAN bus packages came in(frequently posted events in CAN HWi). Could you please give some advice on how to debug this? Thank you!

 

 

 

  • 0
    TI__Guru 72500 points
    Hi Erik,
    Can you provide more details?
  • 0 in reply to Bob Crosby
    TI__Intellectual 1600 points
    Hi Bob,

    Thank you for reply. The customer is using SYS/BIOS with TM4C123GH6PZ MCU and the product is T-BOX for Automotive. In this application, there are 2 Tasks, task#1 is used to process CAN packages and task#2 is used to do ohter jobs such as power control and so on. 2 Hardware interupts are implemented in this application, one is GPIO, the other one is CAN interface. events are pending in Task#1 for waiting can packages. Related events are posted in CAN interface Hwi isr to wakeup Task#1 for further processing. There are 2 CAN channels used in this application. The issue is that, when the CAN interupt happens with very high frequency, Task#1 will be stucked and can not be scheduled by OS for running. I suspect it is an OS issue and do following workaround: remove event post activity in the CAN HWi, replace with flag setting, and create another task#3 to check the CAN package flag with 5ms interval, if the flag is set, Task#3 will post the event that Task#1 is waiting for, this workaround can work well, but the customer still want to know the root cause, since there are some projects in mass production with the HWi triggered event architecture.

    Please help to analysis the possible root cause, any input is needed, please let me know.

    Thank you very much.

    Eric
  • 0 in reply to Eric Fu1
    TI__Guru 72500 points
    Can you create a project that recreates the issue and attach to this post (or, email it to me directly).