CCS/EK-TM4C1294XL: fatal error #10296: cannot open output file "Test.out" for writing after debugging

This is a peculiar problem. We have not seen it internally but I see a couple of similar reports on the forums. Could you please have a look at the related threads below and see if the suggestions provided there help in your case?

https://e2e.ti.com/support/tools/ccs/f/81/p/577565/2119582#2119582

https://e2e.ti.com/support/tools/ccs/f/81/t/848421

No, nothing helped.

I tried the -clean command.

I tried to start as administrator.

I tried a new workspace.

I tried to delete the old project folder and clone a new one from repo.

Some other advice. Right now CCS is unusable because I have to restart CCS after every code change.

Kind regards

René

Sounds like something is preventing the .out file from being written. Have you checked permissions on the directory where it is being written, etc? Is the directory containing the .out file somewhere on your local machine or in a source control repository?

Did you try rebooting the computer as was mentioned in one of the referenced threads? 

It sounds like there might be something specific to your environment that is triggering this. I'm not quite sure what but perhaps some additional details will help.

- How exactly are you cloning/importing the project? Please provide as much details as possible.
- After starting a debug session, is the error triggered when you try to build the project again while the debug session is still active, or even after the debug session is terminated?
- Are you connecting to a LaunchPad using the onboard ICDI?

Just to be correct it´s not compiling thats get failed it´s linking.

Yes, I restart my computer.

The projekt is on a local folder "C:\Work\CCS\CCS93\Drive_Main\Debug"

I use Git as repository.

I use Kaspersky as antivirus and firewall. I deactivate it but this doesn´t help also.

I can recompile as long as I didn´t start a debug session. If I start one, debugging works fine but when I compile again the error shows up.

Even stopping the debug session with the red button nor terminate and remove will work.

Recompile is not working.

I tried to delete the .out file inside windows explorer. There I get the error message that ccstudio.exe has opend this file - deleting not possible.

I use a EK-TM4C1294XL with the onboard debugger.

The .out file is 16MB.

I tired the release compile option (with optimization and no debug info, .out file size 3MB) this is working.

I changed the project properties for my debug config to "Suppress all symbolic generation (--symdebug::none)" and this works also (.out flie size now 3.3MB).

Unfortunatelly I couldn´t debug now anymore but maybe thats a hint where it comes from.

Hope that helps

Rene H. said:

I use Kaspersky as antivirus and firewall. I deactivate it but this doesn´t help also.

Kaspersky has been known to give trouble from time to time. But you mention that you see the issue even after completely disabling Kaspersky?

Since you've already tried and eliminated the usual suspects, the next step would be to try to reproduce the behavior at our end. Would you be willing to share the project with us? You can send it to us via private conversation if you do not wish to post here on the public forum. Working with the same project at our end will help zero in on whether the issue is specific to your environment (firewall, anti-virus, etc) or a broader CCS issue.

Another thing we could try (in the absence of the full project) is to look at the debug server log to see if it provides any clues. Please see this post for information on when and how to generate debug server log. I don't know how much this will tell us but worth a shot if you are unable to share the project.

René,

I just found this related thread with the same error/situation as yours. In that case the user isolated the issue to a conflict with their anti-virus software. After setting up their anti-virus software to not scan the entire CCS installation directory, they were able to resolve the issue. I suspect the root cause may be similar in your case. Could you please double-check whether all anti-virus software are completely disabled and/or tell it not to scan CCS directories and see if that helps?

No. It´s still not working.

I added the whole TI path and the project path to exclude from antivirus (it´s still disabled).

But why could I build the project as much as I want until I start a debug session? That doesn´t sound like an anti virus problem.

It´s more like that the debugger doesn´t release the file handler after flashing the software. And only if there are debug infos available in the out file and with this only if the file has more than 3MB (or even more).

I have an other projekt - an older dev branch from the project. File size 7MB - the same problem.

And I have an other project - an bootloader. That works - file size 3MB.

That problem is only related to my computer - an college hasn´t that problem and we work on the same project. So it´s not related to the project.

Rene H. said:

That problem is only related to my computer - an college hasn´t that problem and we work on the same project. So it´s not related to the project.

So you mean that your colleague who works on the same project in a different computer does not have this issue with the same 16MB .out file (generated with debug symbols)? 

In that case could you generate the debug server log as requested in my earlier post and attach it here? 

3021.DebugServerLog.zip

This is what I´ve done for the file

- started CCS

- compile the project

- start debug session

- run program on uC

- edit source code

- compile again => error

Hi Rene,

Could check if this makes any difference?

• Open a Windows command prompt
• type "set TI_DS_OFS_USE_ENTIRE_FILE = 1"
• CD to the install location of the ccstudio EXE (IE C:\ti\ccs930\ccs\eclipse")
• run ccstudio.exe
• run your test case again and let us know if this changes anything

The symbol management code does various optimizations to reduce memory usage. This flag turns a specific optimization off that might affect what you are seeing.

No, that doesn´t change anything.

DebugServerLog2.zip