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 Build always says "Fatal error #1965: cannot open source file"

Hello,

I'm running CCS 5.5.0.00077 on two different machines - one is Windows XP, one is Windows 7 (using a floating network license).  My WinXP installation works just fine, no problems at all editing, building, and debugging projects at will.

But I cannot get the Win7 installation to build ANYTHING.

For example, if I go:

File->New->CCS Project->(give it any name, any configuration it doesn't matter, and select Empty Project with main.c).  

Then immediately select Build Project, I get this error:

"C:\\ti\\ccsv5\\utils\\bin\\gmake" -k all
'Building file: ../main.c'
'Invoking: ARM Compiler'
"C:/ti/ccsv5/tools/compiler/arm_5.1.1/bin/armcl" -mv6 --code_state=32 --abi=ti_arm9_abi --include_path="C:/ti/ccsv5/tools/compiler/arm_5.1.1/include" -g --diag_warning=225 --display_error_number --diag_wrap=off --preproc_with_compile --preproc_dependency="main.pp" "../main.c"
Fatal error #1965: cannot open source file "../main.c"
1 catastrophic error detected in the compilation of "../main.c".
Compilation terminated.

Main.c is obviously there, but it doesn't see it.  If I go in and change the command-line pattern to name it specifically, I get a bunch more errors about "cannot open .pp file" and even:

INTERNAL ERROR: C:\ti\ccsv5\tools\compiler\arm_5.1.1\bin\armlnk.exe experienced a fatal internal fault

This is a serious problem. Please contact Customer
Support with this message and a copy of the input file
and help us to continue to make the tools more robust.

The exact same problem happens if I go to the TI Resource Explorer->Examples->(select any example, like the ADC_DISPLAY_RM48)->Import it->Build it.  I get a lot of errors, but the first one is:

**** Build of configuration Debug for project ADC_DISPLAY_RM48 ****

"C:\\ti\\ccsv5\\utils\\bin\\gmake" -k all
'Building file: ../sys_main.c'
'Invoking: ARM Compiler'
"C:/ti/ccsv5/tools/compiler/arm_5.1.1/bin/armcl" -mv7R4 --code_state=32 --float_support=VFPv3D16 --abi=eabi -me -g --include_path="C:/ti/ccsv5/tools/compiler/arm_5.1.1/include" --include_path="C:/CCSTest/ADC_DISPLAY_RM48/include" --diag_warning=225 --display_error_number --enum_type=packed --preproc_with_compile --preproc_dependency="sys_main.pp" "../sys_main.c"
Fatal error #1965: cannot open source file "../sys_main.c"
1 catastrophic error detected in the compilation of "../sys_main.c".
Compilation terminated.

I am totally stumped as to what the issue is.  Even if I manage to overcome the compiler not seeing the source file (by manually editing each entry and directly entering in the file name), I get multiple other errors all related to can't find certain files.  I feel like I'm missing something simple, but I just can't figure it out.

I've tried the following already:

1) Uninstalling and re-installing CCS,
2) Putting the project on the local C drive (avoiding network drives).
3) Adding files as "Linked" and making sure the Resources all line up (still will crash with ".pp" errors and linking completely fails).
4) Disabling anti-virus software.
5) Making sure no permissions or other file issues are causing a barrier.

There has to be something about the way my Win7 machine is working differently than my WinXP machine, but they both run the same anti-virus software.  I just can't build a project on the Win7 machine.

Please help!

  • Hi,

    This is a very odd behavior, and I am unsure what else to try in the light of whatever you already did (most of the steps you did are also shown in the Troubleshooting CCSv5 page).

    Usually when I have some build issue that I can't explain, I tend to remove the IDE from the picture (I think better with a command prompt).

    To do this, can you open a DOS command prompt, go to the project directory/Debug (or /Release, depending on the Build configuration you are using) and run gmake? This should build your project.

    If gmake.exe cannot be found, try passing the full path (C:\ti\ccsv5\utils\bin\gmake) 

    Another alternative is to copy and paste the command line itself to see if main.cpp is able to be found.

    Running from the command line usually brings up things that are not obvious from a command line, therefore it is possible that something else is at play.

    One additional detail that just occurred to me. Can you create a fresh workspace and try building a simple hello world project?

    Hope this helps,

    Rafael

  • Hi Rafael,

    Well ... the plot thickens.  I created a new workspace and then a new project with just main.c.  I went to the command prompt and ran "gmake" and got this:

    C:\DTest\TestProg\Debug>gmake

    'Building file: ../main.c'
    'Invoking: ARM Compiler'
    "C:/ti/ccsv5/tools/compiler/arm_5.1.1/bin/armcl" -mv6 --code_state=32 --abi=ti_arm9_abi --include_path="C:/ti/ccsv5/tools/compiler/arm_5.1.1/include" -g --diag_warning=225 --display_error_number --diag_wrap=off --preproc_with_compile --preproc_dependency="main.pp" "../main.c"

    Command-line error #1966: cannot open preprocessing output file "main.pp": Permission denied
    1 catastrophic error detected in the compilation of "../main.c".
    Compilation terminated.

    It seemed to find "main.c" this time, but it gave a "Permission denied" on creating "main.pp", which I guess could explain why I'm having so much trouble.  But I am really confused as to why (and who) is denying permission.  Something in the Win7 security must be the issue, although it doesn't seem to matter where I have the workspace (it has the same problem on my network S drive, the local C drive, and the local D drive).

    Thank you for the help, and if you have any suggestions on where to look for permission issues please let me know.

    - Rebecca

  • Ok ... I found a solution!

    I created a new User Account with Full Admin rights (same as my current account).  Logged into this new account and now CCS works just fine.

    Very strange. I'm not sure what is different between the two accounts, but I am very glad to have a solution. Thank you for your help.

    - Rebecca

  • Rebecca,

    That is very strange indeed, especially due to the fact your original user had admin rights (otherwise you would not be able to create another user).

    What I suspect is that some utility (backup, a network administrator software, an antivirus scanning the disk) was somehow repeatedly preventing access to that specific directory.

    One wild idea is to try to run CCS as Administrator, by right-clicking on the icon and selecting Run as Administrator - not sure, but I wonder if a file was somehow locked by one of the utilities or another user and it is somehow being prevented by this access.

    Another idea is to force full control permissions to the workspace directory (something you probably already have, but it does not hurt trying) - check this link on how to do it.

    Apart from these things, I am really unsure on what may be happening in this particular case.

    In any case, I am glad you have at least a workaround.

    Regards,

    Rafael

  • Hi Rafael,

    I had already tried running CCS as an administrator with no luck.  I also tried moving the workspace to different drives in case that directory or files had some permission issue, but nothing helped.  I had also tried changing the permissions of the directory and files itself, but that made no difference either.

    It was complete puzzle to me.  No other software seemed to have any problem (I could freely edit and do whatever I wanted with the files in the directory with a standard text editor).  It was just CCS - somehow it was specifically being blocked from building anything in any directory or drive for reasons unknown.

    I thought it might be the anti-virus software, so I tried disabling it to the degree possible, but that made no difference either.

    Crazy huh?

    At this point I don't care.  Now that it is working on the new account I'm happily updating the code and doing what I need to from my Win7 machine (doing it all on the old WinXP computer was a drag!)

    - Rebecca

  • Hi, I have the same problem. Disappeared on a different account.

    ==BUT== What I've noticed - if I remove all the quote symbols (that is - ") from the Makefiles and run gmake from terminal it builds successfully.

    What I also noticed - in the Makefiles there are lines with only LF ...and we know that Windows wants CR LF.

    Hope this helps somehow! Will investigate further cus another account is not OK for me ...