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

Task_sleep() Issue in CCS5.2 SYS/BIOS

manjunath tapasi
Intellectual 450 points
Other Parts Discussed in Thread: TMS320F28335, SYSBIOS

Hi guys,

I am using CCS5.2 SYS/BIOS for my project.

I have some HWI,SWI and tasks statically configures in my project.

In Task i have used Task_sleep() function,I dont know how to configure it statically or dynamically.

I am using TMS320F28335 for development.

Can anyone provide me the details to do so,

Thanks,

manju

  • 0
    TI__Mastermind 30830 points

    Manju,

    I'm assuming that what you mean by configuring Task_sleep() is that you want to understand and set the time units passed to Task_sleep().

    The "ti.sysbios.knl.Clock" module is used by all SYS/BIOS APIs that have timeout arguments (Task_sleep(), Semaphore_pend(), etc).

    By default, the Clock.tickPeriod configuration parameter which defines the timeout period is set to 1000 microseconds (ie 1ms).

    Consequently, the default units for all timeout arguments is 1ms.

    This means that If you call Task_sleep(10), the task will block for 10ms.

    Setting Clock.tickPeriod to another value will change the timeout units for ALL SYS/BIOS APIs which have a timeout argument.

    Currently, Clock.tickPeriod can only be configured statically.

    Alan

  • 0 in reply to Alan DeMars
    Intellectual 450 points

    Alan,

    Thanks alot for the answer.