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.

Using TI-RTOS with CC3200 SDK 1.2.0

Other Parts Discussed in Thread: CC3200, CC3200SDK

Hello,

I had a version of my CC3200 project running on CC3200 SDK 1.1.0 and TI-RTOS 2_13_00_06.

SDK 1.2.0 has specific bug fixes I'm interested in.

I looked at the highest TI-RTOS version available for the CC3200, and it is 2.16.01.14. This is also the version that the CCS IDE will download through its "app center".

That version of TI-RTOS contains the CC3200 SDK/driverlib version 1.1.0, with this default install path:

C:\ti\tirtos_cc32xx_2_16_01_14\products\CC3200_driverlib_1.1.0

Is there a simple way to use the full TI-RTOS with CC3200 SDK 1.2.0? I understand that the SDK's (including 1.2.0) include a prebuilt TI-RTOS kernel, but my project was using more than just the kernel, using various peripheral drivers including UART. I also understand that there are CC3200 SDK examples of using peripherals such as the UART, but the full TI-RTOS driver has much better functionality such as ring-buffering, etc already built in.

Do I need to wait for an updated TI-RTOS that includes the CC3200 SDK 1.2.0?

Thanks,

-Bob

  • Ok, so it appears I can still use TI-RTOS 2_16_01_14 and at the same time link against the 1.2.0 sdk by having these in my ARM Linker Search Path:
    "${CC3200_SDK_ROOT}/driverlib/ccs/Release/driverlib.a"
    "${CC3200_SDK_ROOT}/simplelink/ccs/OS/simplelink.a"
    "${CC3200_SDK_ROOT}/simplelink_extlib/provisioninglib/ccs/Release/provisioninglib.a"
    where CC3200_SDK_ROOT = C:\ti\CC3200SDK_1.2.0\cc3200-sdk

    So far my tests are coming out ok. Can anyone confirm that TI-RTOS 2_16_01_14 can link and run against CC3200 SDK 1.2.0 without causing new issues?
    Thanks,
    -Bob
  • Bob,

    Yes, it is possible to use TI-RTOS 2.16.01.14 with CC3200 SDK 1.2.0. It sounds like you already figured out how to update your CCS projects. But lets make sure you updated all necessary variables.

    1. Open the CCS project properties. Select Resources > Linked Resources > Path Variables (tab). Scan the list of variables and make sure they look correct.

    2. In the project properties, select CCS Build > ARM Compiler > Include Options. Inspect the list of include paths. In particular, the include paths which contain the products folder will have hard-coded version strings for the products. For example,

      ${COM_TI_RTSC_TIRTSOCC32XX_INSTALL_DIR}/products/CC32XX_driverlib_1.50.05.00

      If these products have changed, you will need to update these include paths manually.

    3. In the project settings, select CCS Build > ARM Linker > File Search Path. Inspect the library paths and look for embedded version strings to the products folder. Similar issue as the include paths above.

    One good technique is to rename the old TI-RTOS product and then clean and rebuild your project. If you have any reference to the old product, the build will fail.

    As you must have noticed, the TI-RTOS product name has changed between 2.13 and 2.16: tirtos_simplelink_2_13_00_06 to tirtos_cc32xx_2_16_01_14. You might have other project settings which reflect the old name that need to be updated.

    Finally, sometimes the board configuration files change. For example, if you move to TI-RTOS 2.20.00.06, the board file changed quite a bit. But I don't beleive they changed between 2.13 and 2.16. However, one good test is to compare the same example from both releases. You will find them in the tirtos_###_examples folder.

    One word of caution. If you have both TI-RTOS 2.13 and TI-RTOS 2.16 "installed" into CCS, when you import an example using the TI Resource Explorer, it will always import from the latest version, regardless which version you have selected in preferences. If you wish to import an example from each version, you must have only one version installed at a time. Use the "uninstall" button to remove an installed product version.

    ~Ramsey

  • Great! Thank you for all the info.
    -Bob
  • Thanks Ramsey, this is very useful! I am in a similar predicament. However, I'm using the makefile build system with the TI AWS git  -

    where the paths are specified in the products.mak file

    ###### User Step: Update install paths to XDCtools, TI-RTOS, and Compiler ######
    19	
    XDC_INSTALL_DIR       = /path/to/xdctools_installation
    20	
    TIRTOS_INSTALL_DIR    = /path/to/tirtos_installation
    21	
    TI_ARM_CODEGEN_INSTALL_DIR = /path/to/TI_ARM_compiler
    22	
    23	
    ###### Below dependencies are determined automatically ######
    24	
    TIDRIVERS_INSTALL_DIR := $(wildcard $(TIRTOS_INSTALL_DIR)/products/tidrivers_*)
    25	
    BIOS_INSTALL_DIR    := $(wildcard $(TIRTOS_INSTALL_DIR)/products/bios_*)
    26	
    UIA_INSTALL_DIR     := $(wildcard $(TIRTOS_INSTALL_DIR)/products/uia_*)
    27	
    NS_INSTALL_DIR      := $(wildcard $(TIRTOS_INSTALL_DIR)/products/ns_*)
    28	
    29	
    CCWARE_INSTALL_DIR := $(wildcard $(TIRTOS_INSTALL_DIR)/products/CC3200_driverlib*)
    30	
    CC3200SDK_INSTALL_DIR := $(TIDRIVERS_INSTALL_DIR)/packages/ti/mw/wifi/cc3x00

    It looks like I would have to modify CCWARE_INSTALL_DIR and CC3200SDK_INSTALL_DIR to point to the CC3200SDK installation. Any official steps for the same would be greatly appreciated. 

    Thanks,
    Sridhar

  • Hi Sridhar,
    We generally discourage posting a new question to an old closed thread because the person who answered before may no longer be available, and also it will allow whomever is currently assigned to monitor the forum to respond to you more quickly. For these reasons, I suggest you start a new thread with your question and reference this thread.

    Thank you