• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 1241 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.

BIOS Tasks run once, hang on Task_sleep()

Robert Wolfe
Mastermind 7860 points
Other Parts Discussed in Thread: SYSBIOS

Hello,

I made some changes to a project, and now the tasks only execute once, and then hang on the Task_sleep() at the end of the while loop processing in them.  Can you please tell me what I should start looking at, to debug this?  I believe the Task_sleep() calls are driven by the timer that BIOS uses for the system tick.  So I've wondered if somehow that's not working/counting ticks.  Attached are the BIOS properties for it:

Regards,

Robert

 

 

  • 0
    Genius 4375 points

    Robert,

    Yes, you are right--it's possible that the BIOS clock timer isn't ticking which would cause Task_sleep to never return.  Do you see yourself in the Idle task when you halt the core?  Could you use ROV (Tools->ROV) to determine the number of ticks counted by the ti.sysbios.knl.Clock module after calling Task_sleep?  If this value is consistently '0' this is an indication that the timer isn't ticking at all.

    Which device/core are you using?

    Regards,

    Shreyas

  • 0 in reply to Shreyas Oppanthaya
    Mastermind 7860 points

    Thanks for the reply.  The code was in the idle loop, and it seemed the timer wasn't ticking at all.  

    Initially the tasks were running, but then I incorporated some TI non-BIOS code that does Mega Module configuration (for C6748).  Commenting out sections having to do configuration of interrupts, for that code, resulted in the tasks running properly again.  I'm not quite sure why yet.  The portions removed, to make the tasks run again include setting up the addressing mode register, IER, EVTMASK, interrupt multiplex registers and changing the interrupt service vector from ROM to RAM.

    Are all these things configured by SYS BIOS, and shouldn't be manipulated in the user's application code?  Apparently by setting some of those things in the application code, I had disabled at least the system timer tick mechanism/interrupt.

    Robert