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

"Create policy error" when trying to create a clock.

Marc Bunyard
Intellectual 535 points
Other Parts Discussed in Thread: SYSBIOS

I am still trying to get the Task_sleep function to work.  I have been able to create a clock, but when I step through the call to Task_sleep, the call to xdc_Ptr ti_sysbios_knl_Clock_Object__create__S end up trying to post the error message "create policy error".  I've looked through the documentation, and I'm not getting a handle on this error.  I thought that creating the clock through XGCONF created it statically, but there is a call to clock object create.  I've got something wrong.  What is it?

  • 0
    TI__Mastermind 30830 points

    Marc,

    You've been victimized again by the example you started with.

    It goes out of its way to minimize the code and data footprint of the application.

    To do this, it eliminates all optional functionality unnecessary for the example.

    In this case it has disabled dynamic instance creation.

    This corresponds to the "Enable Dynamic Instance Creation Support" option on the SYS/BIOS - Basic Runtime Opitons GUI page.

    If you enable that feature and then rebuild, I think you'll get a little further along.

    Dynamic clock object creation occurs whenever an application invokes an API with a timeout (ie Task_sleep() or Semaphore_pend()).

    To achieve the timeout behavior, a private Clock object is created and added to the Clock module's Clock queue.

    When the private Clock object is no longer in use (ie after the Task_sleep() timeout occurs), the object gets destroyed...

    Alan

  • 0 in reply to Alan DeMars
    Intellectual 535 points

    Thank you Alan. That was it.  In fact, taking my lead from your previous response, I discovered the button.  Adding the clock and necessary features, however, leaves me going over the code size for the chip.  Different problem.