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.

Solution for "create policy error" with task creation is hidden

Other Parts Discussed in Thread: SYSBIOS

You can get the "create policy error" when first starting to use dynamically created tasks.  This error string is not documented and only shows up deep inside code generated by the XDC system.


I am posting this so it shows up in searches for the error string.

Here is the console output you will see:

[CORTEX_M4_0] System Clock: 120000000
ti.sysbios.knl.Task: create policy error
xdc.runtime.Error.raise: terminating execution

The solution is to check the "Enable Dynamic Instance Creation" box on the BIOS Runtime Options dialog as shown below.   It is not clear why a "Suggest checking Runtime Options setup" is not one of the messages that happens in response to this error.

Here is the dialog you need to set up:

  • I forgot to mention in the first post that this setting does not show up in the app.cfg script.  Basically everything you do when changing app.cfg shows up in the script.  For some reason this one occurs "under the covers", so you have to go look at the dialog to see if this is on or off rather than looking at the script.

  • Hi Raymond,

    Thanks for posting that solution.  Could you please mention the version of BIOS and XDC tools you are using (which coincide with this solution)?

    Did you mean to post a screen shot as well?

    Also, was this in response to a different forum post you made?

    Steve

  • Steven Connell said:

    Hi Raymond,

    Thanks for posting that solution.  Could you please mention the version of BIOS and XDC tools you are using (which coincide with this solution)?

    Did you mean to post a screen shot as well?

    Also, was this in response to a different forum post you made?

    Steve

    Steve:

    I am using CCSv6 (6.0.0.00190) along with RTOS (tirtos_tivac_2_00_01_23) and XDC (xdctools_3_30_01_25_core)

    This was not in response to another post.  I just ran across this the hard way and wanted to try to save others the pain of  trying to figure it out.  Almost everything shows up in app.cfg script, but this one happens "under the covers".

    I did mean to post a screen shot and it appeared to be in the text entry, but went away after posting. here is another try at it:

  • Steve:

    Any suggestions on how to get the screen shot into the forum?  Or can you do one and post it?

    Thanks.

    Ray

  • Ray,

    When you are in the edit view for the post, you  should see a little green icon, highlighted in red in below screen shot.

    Steve

  • From what I saw on the forum, there are other instances where you have to be sure to change from static (in XDC and app.cfg) to dynamic support for RTOS features.  If you get a "create policy error", be sure to check that you have dynamic creation turned on for that feature.

    OK, one last try to get that screen shot for the tasks since this one does not show up in the app.cfg script:

  • Alright, looks like the screen shot posted!

    If you don't mind, would you please mark this thread as "verified" in order to close it out?

    Since your post was just informational, you could probably mark your own previous post (with the screen shot) as the "verified answer."

    Steve

  • Steve:

    Great minds think alike... I hit the "Yes" button on "Did this answer your question" before you sent your request, but it does not give me a "verified" option.  Is there some way for the moderator to mark it as verified?  Hitting "Yes" has apparently done something but still leaves the thread open with an option to reply to the last post.  Of course it could be something I am doing on my end!

    Ray

  • @Raymond and @Steve,

    The thread was set to be a discussion thread which disables the "verified" buttons from appearing. I've switched this thread to being a Q&A thread, so the buttons are now present and feel free to now utilize accordingly.


    Blake