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/LAUNCHCC3220MODASF: SimpleLink SDK Include and Library Paths Empty

Part Number: LAUNCHCC3220MODASF

Tool/software: Code Composer Studio

I've installed Code Composer Studio 8 and the SimpleLink SDK: simplelink_cc32xx_sdk_2_10_00_04.  I started a new Code Composer project, and checked the SimpleLink CC3220 SDK box under the products list in the general properties for it.  In the include options, it has ${COM_TI_SIMPLELINK_CC32XX_SDK_INCLUDE_PATH} as the first entry, but this variable has nothing in it, and when I try to use a driver, such as GPIO, it can't find the header file that I include.

Same problem with the libraries, it has ${COM_TI_SIMPLELINK_CC32XX_SDK_LIBRARIES} in the list of library files to include, but this variable is empty.  Both variables indicate that they were contributed by product SimpleLink CC3220 SDK.

Why are these variables empty?  Did I install something incorrectly or miss a checkbox in the properties somewhere?

  • Hi Kevin,

    If you're just trying to create your own project from scratch, then I suggest you instead import a simple example from the SDK and strip out what you don't need.
    As you've seen, creating a new project and adding in the CC32XX SDK doesn't really do everything that need for a running project. Furthermore, starting from nothing and adding in all of the required libraries, compiler options, linker options, etc. is probably going to prove frustrating as you'll miss something and have to debug painfully just to get a hello world executing.

    If you take something like the httpget example and import it into your CCS workspace, what you'll find is a CCS project with all of the correct compiler/linker options setup, as well a main_tirtos.c and a platform.c that properly initializes the CC3220 + networking. If you remove the httpget.c, and then remove the httpThread spawn function in mainThread(), then you've effectively made a blank slate application that you can develop from. The only extraneous addition to the resulting project will probably be inclusion of the httpclient_release.a library in the linker options. Once you're removed that, you can add all of your own project code, and then spawn your own threads from mainThread() where the httpThread spawn used to be.

    I hope that helps. Let me know if you need further guidance or have additional questions.

    Regards,
    Michael
  • Oh, that helps, thanks.  Will starting with an example also have all the libraries set up for the various drivers like UART and SPI?

  • Hi Kevin,

    Yes, by importing an existing example you'll have all of the peripheral drivers linked and also configured correctly, assuming that you are using a Launchpad.
    Of course, you'll still need to write code to exercise the UART and SPI peripherals. There are examples in the SDK that show you how to do so using UART/SPI_open(), UART/SPI_write(), etc..

    Regards,
    Michael