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.

Compiler (IDE) issue on CCS 6.

This is a user I am having trouble tracking down.   I am working through the Tiva c lab book for the TM4C123G..  When I try to compile I get error such as   "Can not open C:\TM4C123G_LaunchPad_Workshop\lab3\project\Debug\lab3.out".   I installed CCS on another computer and t ran with no issue (up to lab 4).  I suspect there is some include path wrong somewhere.

Any suggestions on how t trace it down.  I tried reinstalling bu there must have been some hidden config file that continued the error.

Great microprocessor and great IDE.  

Happy New Year to all.  

Tom Schmitt

Atlanta Ga.

  • Hi Thomas,

    Post the other compile errors here.

    - kel
  • Hello Thomas,
    I don't use CCS so cannot directly help you. However, one thing that may help is ProcMon from what used to be sysinternals.com, now part of Microsoft. It's free and doesn't mess about with the system. Set it up and configure ProcMon's exclusions to get rid of all the spurious system activity. Then run CCS upto the point where it generates the error, clear the ProcMon display, then generate the error in CCS, then freeze the ProcMon display. This should tell you where CCS was looking in the filespace and for what. Doing it on a working machine at the same place may give you something to compare against.
    Hopefully somebody else that uses CCS might tell you a quicker and easier way of doing it. But ProcMon is a useful tool to have anyway.
  • Thomas Schmitt said:
    "Can not open C:\TM4C123G_LaunchPad_Workshop\lab3\project\Debug\lab3.out".   I installed CCS on another computer and t ran with no issue (up to lab 4).  I suspect there is some include path wrong somewhere.

     Hi Tom, I fear the folder where file reside need access right, so try open C:\TM4C123G_LaunchPad_Workshop folder, set access right to you then propagate to all subdirectory, this need administrative priviledge or whatever new winzz call them.

     On early version archive bit reported as read only was disturbing, I suppose this early problem got solved if this don't solve issue ask again or better try post on CCS dedicated section.