• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 21046 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 5.5, Invalid project path: Include path not found

BadMonkey
Expert 2090 points

I have an MSP430, CCS 5.5, that shows a "greyed-out" (grayed-out ?? "http://grammarist.com/spelling/gray-grey/") path in under "Includes" in the Project Explorer..

Additionally, I get the warning (Note: carriage returns inserted for readability):

Invalid project path: Include path not found
(C:\ti\ccsv5\eclipse\Debug\"C::\SFTDEV\ADS5\Peripherals\Target\Boot).    
Boot        pathentry    Path Entry Problem

For the life of me, I cannot find where in the settings this path is being added to the includes. I had another bad path but found it in the settings and fixed it. Further, I don't even want this path at all. I see that this path is defined under CCS Build->Builder (a tab). The path is defined there using the "workspace_loc" expansion macro for the first part. However, I have other projects that show this same concatenated path using the "workspace_loc" expansion macro and the project name. In those other MSP430 projects, that path is not shown under "Includes" in the Project Explorer.

Any ideas?

Regards,

Jim

  • 0
    TI__Guru**** 169894 points

    Jim,

    Do you know what workspace_loc exactly translates to? This will give a hint on what may be happening. To get that info, simply right click on the project --> Properties --> Build --> tab Variables --> click on the box "Show system variables" --> scroll down to reach the variable "workspace_loc" --> click on the button Edit and see what it translates to.

    Also, if you take a look at the box "Summary of flags set" in both the compiler and linker options, that will help see where the paths are failing to be properly translated. This box can be found when you right click on the project --> Properties --> Build --> MSP430 Compiler (or Linker). Thus you can compare the items in the --include_path options with the entries in either Include Options (for Compiler) or File Search Path (for Linker)

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Expert 2090 points

    I did look at (and fix) entries in the compiler and linker includes as well as linked resources before I posted. See the attached .jpg files.

    Regards,

    Jim

    5811.MSP430 TI forum post.zip

  • 0 in reply to BadMonkey
    TI__Guru**** 169894 points

    Jim,

    Despite the screens you sent give some additional insights on the problem, they don't expand the variables being used. Do you see anything abnormal on the "summary of flags set" of the compiler and linker?

     

    Jim said:

    I see that this path is defined under CCS Build->Builder (a tab). The path is defined there using the "workspace_loc" expansion macro for the first part.

    The place you mentioned uses "workspace_loc" to build the path to the output directory, therefore it would be useful to inspect its value on this particular project. As I mentioned before, to check this value follow the procedure I mentioned before in the same screen as your second screenshot.

    You can safely delete the output directory or move it somewhere else - I imagine that one of the internal make files may have become corrupted.

    As a last resource, open the .cproject file in a text editor and see if there is a messed up path there (do a text search). It is possible this file became somehow corrupted. Obviously that you should make a backup copy before doing any changes, thus you avoid the risk of losing anything.

    Hope this helps,

    Rafael 

  • 0 in reply to desouza
    TI__Expert 3520 points

    Hi Rafael,

    Thank you for the detailed outline of steps above to resolve the issue.  Although the 'Summary of flags set' screen did not show the particular include path causing some trouble, the generated compiler output and .cproject file you mentioned did have one include path with two quote marks (") at the start that was invalid.  This line was part of a list of include paths within the .cproject file, and was deleted per your advice.  Once this line was deleted, CCS reopened, and the project opened the grayed out 'problem' include path was no longer present and the project built successfully.

    Thank you once again for your rapid and thorough support.

    Best Regards,

    Mark-