• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1721 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.

CCS/CCSTUDIO: Where can I find documentation on Task_sleep?

spanky
Expert 2710 points

Part Number: CCSTUDIO

Tool/software: Code Composer Studio

Since this question went unanswered in the haste to close/lock thread, I figured I'd ask it here.

Where can I find documentation on Task_sleep?

Original question, which was totally appropriate to ask in the context of the thread:

Can you guys add a "reopen thread" button? Or maybe a "user thinks this is unanswered" option. I realize TI prioritizes content generation over useful documentation (quantity over quality), but I've come across many locked threads that do not address the issue and its pretty frustrating that I have to start a new thread to answer a question that was already posed.

  • 0
    TI__Guru* 96960 points

    Hi Spanky,

    You can find a link in the SYS/BIOS Release Notes (look for API Reference or cdoc). You can navigate directly via <SYS/BIOS Install Dir>/doc/cdoc/index.html.

    Once it is open, you can navigate to the Task module and select Task_sleep.

    I understand the frustration of locked threads. When a thread is created, we assign it to an engineer who tries to resolve the question/issue. Many groups have engineers rotate into forums. If we did not lock the threads after some period of inactivity (I forgot the exact period), a post could be added and the assigned engineer would be notified. However, that engineer might not be on forum duty at that time, in the same business unit or even with the company anymore. To avoid this, we lock instead and force people to open a new thread. Since it starts unassigned, we can act on it faster. I know it's not ideal, but I believe it has helped on our support model.

    Todd

  • 0 in reply to ToddMullanix
    Expert 2710 points
    Holey Moley! That's exactly what I was looking for. The problem was I didn't have sys/bios package installed, but I did have the tirtos package (I'm still not overly clear on the difference... sometimes I read stuff that says they're the same, then times like this, they appear to be separate). Anyways, for anyone on this path in the future, installing the sys/bios package was done through the resource explorer.

    also here:
    dev.ti.com/.../Task.html

    I do appreciate you guys answering questions. I feel like I should have been able to find this on my own, so I think its just my frustration that something so simple should be so obscure and difficult. Hopefully this thread will be indexed along with that other unanswered one for anyone looking for this in the future.
  • 0 in reply to spanky
    TI__Guru* 96960 points

    The branding of SYS/BIOS vs TI-RTOS has been rocky. Here it is in a nutshell. Note: when I say "product" below, that means an installable product.  SDKs are products also

    We have had a SYS/BIOS product for several years. It is basically a kernel. It does not include drivers or stacks. A few years ago, we started bundling the SYS/BIOS kernel, RTOS-aware drivers and stacks together for MCUs (e.g. MSP43x, CC32xx, CC13xx, CC26xx, C2000, and TM4C).  We called this the TI-RTOS  product. For the "Processors" devices (e.g. C6x, Sitara, etc.), SYS/BIOS was already bundled into their SDKs (along with drivers and stacks). So everyone just using the term TI-RTOS even though for processors, it was SYS/BIOS. Note: in the TI-RTOS product, SYS/BIOS was basically added as is into TI-RTOS product for backward compatibility.

    Last year (2017), for the CC13xx, CC26xx, CC32xx, and MSP432 devices we came out the the SimpleLink SDKs that include TI-RTOS. So for those devices, we recommend using the SimpleLink SDKs and have stopped making TI-RTOS product releases. Now the new TI-RTOS features are going into the new SimpleLink SDKs.

    For C2000, we never made C2000 drivers, so it's really just the kernel, so we recommend you just use the SYS/BIOS product directly.

    For Processors SDKs, we give them new SYS/BIOS releases to add into the SDK.

    I hope that helps clear things up some.

    Since you are using TI-RTOS product, another way to get to the docs was the Docuementation Overview html page in the doc directory. This seems like a relatively easy way to find things.

  • 0 in reply to ToddMullanix
    Expert 2710 points
    Thanks Todd,

    That explanation is incredibly helpful. I wish something like that was more prominently available for the beginner.

    How does EasyLink fit into that? Is that a "Product" or just an example?
    processors.wiki.ti.com/.../SimpleLink-EasyLink
  • 0 in reply to spanky
    TI__Guru* 96960 points

    I'm not sure about EasyLink. I know there examples in the SimpleLink CC13x0 SDK.

    Note: in SimpleLink Academy, there is a TI-RTOS Basics where I tried to describe this also.