• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 1159 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.

F2802x Piccolo Launchpad - Can't find source file adc.c

David Breen
Prodigy 80 points
Other Parts Discussed in Thread: CONTROLSUITE

Hi,

I am getting the following error:

Can't find a source file at "C:/controlsuite_gitorious_dev/device_support/f2802x/version/f2802x_common/source/adc.c"
Locate the file or edit the source lookup path to include its location.

I strongly believe that the compiler is looking in the wrong directory, as the controlsuite folder on my pc is located in my ti folder. It is suggested that I edit the source lookup path to include its location, but should I really have to do this? Thanks,

David

  • 0
    Guru 20525 points

    Hello!

    You can find this file here ti\controlSUITE\device_support\f2802x\v210\f2802x_common\source\

    Regards,

    Igor

  • 0
    TI__Guru*** 130875 points

    Hi David,

    also have a look at this link/or try bringing in the controlsuite example from the resource explorer.

    http://processors.wiki.ti.com/index.php/Include_paths_and_options

    Please keep us informed.

    Best Regards,
    Lisa 

  • 0
    Guru 92251 points

    David Breen said:
    I strongly believe that the compiler is looking in the wrong directory, as the controlsuite folder on my pc is located in my ti folder. It is suggested that I edit the source lookup path to include its location, but should I really have to do this?

    I think what is happening is that when link against a pre-build library, then the debug information in the library refers to the source directories on the computer on which the library was built, rather than the actual location the library is installed on your computer. In that case, you have to point the debugger at the location the library source code is installed on your computer via "source lookup path".

    The Debugging Without a Project section of http://software-dl.ti.com/ccs/non-esd/training/CCSv5-TipsAndTricks.pptx describes the options for setting the Source Lookup Paths.

  • 0 in reply to Igor Gorbachev
    Prodigy 80 points

    Igor,

    Thanks for pointing that out, I appreciate it. Out of curiosity, I noticed there were several folders under the f2802x folder, and was wondering if the common/header/example files contained in the v210 folder, for example, were just updated versions of the v200, v129, v128, .... folders. Thanks again,

    David

  • 0 in reply to David Breen
    Prodigy 80 points

    Thank you Chester and Lisa also, for your links and explanations. Helped a lot!

    David