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/CC1350STK: Can't find a source file at xxxxxxx Locate the file or edit the source lookup path to include its location.

Part Number: CC1350STK

Tool/software: Code Composer Studio

I am new to CCS, so this question maybe kinda wierd and noob....( I use RTOS)

when I opened the decleration of a function, I could only see a function type decleration in .h file, in this case, it is "extern RF_EventMask RF_runCmd(xxxxx)", which is in a .h header file, but  I couldn't see the function body. When in debug mode, when I stepped into this function, CCS showed:

Can't find a source file at "/db/vtree/library/trees/zumaprod/zumaprod-o06/exports/tirtos_cc13xx_cc26xx_2_21_00_06/products/tidrivers_cc13xx_cc26xx_2_21_00_04/packages/ti/drivers/rf/RFCC26XX_singleMode.c"
Locate the file or edit the source lookup path to include its location.


so the RF_runCmd function should be in the file RFCC26XX_singleMode.c, and I am using every function from RFCC26XX_singleMode.c, am I correct?

Here's my question: If I want to use the functions in the source file RFCC26XX_multiMode.c which is in the same path as of  RFCC26XX_singleMode.c,what should I do?

Also, can u plz advise me why I couldn't see the function body? Is that because something related to RTOS?

  • I found sth here.... is that the way I can choose different C files? But why I couldn't see the function body using "open decleration" command?

  • Hi Jason,

    Jason Lee60 said:
    Can't find a source file at "/db/vtree/library/trees/zumaprod/zumaprod-o06/exports/tirtos_cc13xx_cc26xx_2_21_00_06/products/tidrivers_cc13xx_cc26xx_2_21_00_04/packages/ti/drivers/rf/RFCC26XX_singleMode.c"
    Locate the file or edit the source lookup path to include its location.

    this type of message is pretty common and explained in the link below:

    http://software-dl.ti.com/ccs/esd/documents/users_guide/sdto_ccs_debug-handbook.html#debugging-library-code

    hence you can either ignore the warning or use the option to browse to the source file in the path that exists in your local environment. Once the debugger is told where the file exists in your environment, it will open it and keep a reference to the location. It can also find other source files from the library using the first path as a reference. This should also resolve the "jump to declaration" (and other related) functionality.

    Thanks

    ki