• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 381 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/CC3220SF-LAUNCHXL: CCS/CC3220SF-LAUNCHXL

kameshwaran V
Prodigy 80 points
Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: CC3220SF

Tool/software: Code Composer Studio

I am new to the environment of CCS. I have just started to work with CC3220SF Launchpad. I am trying to toggle the LED's to get used to GPIO pins. I have enabled the Pins in PINMUX TI tool. The code i am trying to run is as follows,

#include "hw_types.h"

#include "hw_ints.h"

#include "hw_memmap.h"

#include "hw_common_reg.h"

#include "interrupt.h"

#include "hw_apps_rcm.h"

#include "prcm.h"

#include "rom.h"

#include "rom_map.h"

#include "prcm.h"

#include "gpio.h"

#include "utils.h"

#include "pin_mux_config.h"

 

void main()

{

PinMuxConfig();

while(1)

{

GPIOPinWrite(GPIOA1_BASE, 0xFF, 0x02);// pin 64 Red LED

UtilsDelay(8000000);

GPIOPinWrite(GPIOA1_BASE, 0xFF, 0x04); // pin 1 yellow LED

UtilsDelay(8000000);

GPIOPinWrite(GPIOA1_BASE, 0xFF, 0x08); // pin 2 green LED

UtilsDelay(8000000);

}

}

But I am getting the following error while compiling even after describing the resource path location,

Description Resource Path Location Type
#1965 cannot open source file "ti/drivers/utils/List.h" .ccsproject /led line 358, external location: C:\TI\simplelink_cc32xx_sdk_3_10_00_04\source\ti\drivers\Power.h C/C++ Problem

I have also attached the screenshots of the error.

  • 0
    TI__Guru**** 173310 points

    kameshwaran V said:
    Description Resource Path Location Type
    #1965 cannot open source file "ti/drivers/utils/List.h" .ccsproject /led line 358, external location: C:\TI\simplelink_cc32xx_sdk_3_10_00_04\source\ti\drivers\Power.h C/C++ Problem

    In your screenshot it seems that you tried adding the entire path to the #include. Instead the recommended solution is to leave the #include in Power.h as it originally was (#include <ti/drivers/utils/List.h) and add the path to it to the project's compiler include path option. 

    Also it appears that you are trying to create a new project from scratch using the New Project wizard in CCS. If so, I would recommend against that and would suggest starting instead with one of the example projects from the SimpleLink SDK. The SDK includes many examples, you could pick one closest to what you want to do, and modify it to suit your needs. The reason we recommend this is that the example projects already have the appropriate source/header/linker command files added to the project and also have the relevant compiler include paths and linker libraries and paths already set. To start a project from scratch would take a lot more effort and understanding of the files and libraries to achieve the same result. 

    For example, this is what the compiler include path is set to in the gpiointerrupt example. Note the path ${COM_TI_SIMPLELINK_CC32XX_SDK_INSTALL_DIR}/source. This path combined with the path in the #include statement should correctly resolve the path to List.h and avoid that compiler error.

  • 0 in reply to AartiG
    Prodigy 80 points

    Dear sir,

    Thank you for your kind reply..

    I had one more issue as you suggested to try out examples first, i may not able to find such GPIO related examples for the same and also while following as you suggested steps to link INCLUDE_PATH, i'm may not able to find my include_path library,

    kindly view the images attached here and suggest me how can I add my library for the same program

    thank you..

  • 0 in reply to kameshwaran V
    TI__Guru**** 173310 points

    kameshwaran V said:
    kindly view the images attached here and suggest me how can I add my library for the same program

    The libraries to be included depend entirely on the application and what functions it calls. Typically most applications need driverlib.a, but if you look at some of the example projects you will notice that there are several other libraries as well. This is another reason we suggest starting with an example project rather than starting from scratch and figuring out all these details. When you start with an example, you can always remove/delete source files and/or libraries that you don't need. That will be easier to do than building it up the other way around.