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.

CCS/TMS320F28388D: First Task Period is not consistent with SYS/BIOS Task Configuration

Part Number: TMS320F28388D

Tool/software: Code Composer Studio

Hi Todd,

   Recently I found that the first task period is not consistent with SYS/BIOS configutation. For instance, several tasks are listed below:

  

Periodical Tasks 100us task 1ms task 1ms isr 2ms task 10ms task 100ms task
First Task Period 46.2us 0.5ms 1ms 1.49ms 4ms 83.4ms

Only the first task period is abnomal, the follow-up periods are accurate.

What should I do to solve it?

Thanks a lot!

QL

  • QL,

    To be sure I understand, is the delay in each column the first timeout for five different tasks, and one ISR, after the application is started?  And if there were a second row, the times those expire would be at the next expected timeout as listed at the top of each column?

    If yes, can you describe when in the startup sequence each of these is started?  And, how each of the tasks are waiting, for example on a Sempahore_pend() with a timeout?  

    I expect some of the difference on first execution depends upon the phase of starting these tasks with respect to the Clock tick period.  For example, if Clock has a 1 millisecond tick period, when the first expiration happens will depend upon where the start happens within a 1 millisecond window,  from just after the last tick all the way up to just before the next Clock tick.  So the first timeout is out of sync with Clock, but subsequent timeouts should line up.

    If I’m missing the question can you please reword the question.

    Thanks,
    Scott