CCS/TMS320C28346: CCS 9.2.0.00013 locks large .out file and won't release it until restart.

Hello

Usually, the main culprit is some security software running on the PC. But based on your last sentence, there is none running. There must be some component that keeps the file locked. If you are using the same workspace folder that you used with CCSv9.1, can you try using a new folder to rule out any issue with the old cached data?

Thanks

ki

Hi,

I've created a new workspace folder and I have the same problem.

This only happens on large .out files, our CI sever running hundreds of smaller test projects has no problems.

The console output shows an error code if its of any use:

fatal error #10296: cannot open output file "project.out" for writing

Thanks

stomp said:

This only happens on large .out files, our CI sever running hundreds of smaller test projects has no problems.

Did you confirm that it occurs with any "large" out file (did it happen with another project)? I would be surprised if this a file size issue. 5MB is also not very big for an out file size, especially for one with full DWARF debug symbols.

Hi,

Sorry it took so long, have had more pressing jobs on.

We currently have ~1100 firmware projects from a range of TI devices from MSP430 up to RM57. These projects are regularly built and tested on hardware from a continuous integration server, we also have desktop developer machines. All about 10 of our projects .out files are greater than 5MB in size, all of the projects (irrespective of size) can be rebuilt on any machine at any time.

However... 

What we have found, and we believe is the problem, is that if we build a project that produces a large .out file and then try and debug it using CCS GUI the file is locked and the only way to recover is to restart CCS.

So we don't believe its the compiler or linker that is holding onto the file, its the debugger.

Thanks.

stomp said:

So we don't believe its the compiler or linker that is holding onto the file, its the debugger.

Do you see the issue only after the out file was loaded to the target? Or will you see it regardless (can you rebuild the project immediately after a successful build)?

Hi,

We've confirmed we see this only after the out file is loaded onto the target.  We use XDS110 probes.

Thanks.

Can you try rebooting your PC like the user in the thread below?

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

If the the reboot does not help, can you try using a clean new workspace folder and see if the issue still occurs?

Thanks

ki

Hi,

The fix is to restart CCS, we don't need to restart the PC or clean the workspace. (neither of these actions fix the issue)

If I restart CCS and link the program, I can link as many times as I want without fault. However I cannot link again after I have downloaded to the target on large .out files.

Thanks.

stomp said:

The fix is to restart CCS, we don't need to restart the PC or clean the workspace. (neither of these actions fix the issue)

I was hoping that a PC restart would clear up the issue so that you don't need to restart CCS anymore. If the restart has no effect, then it is unrelated to the issue of the other user in the other thread.

Did you try using a new workspace folder? Also try starting CCS with -clean.

Thanks

ki

Hi,

Yes I've tried all the usual suspects, anti-virus, windows defender, different PC, new workspace folders, new projects, etc.

Thanks.

I'm really at a loss on what the issue can be. Can you enable debug server logging and then build the program and load it to the target? Then terminate the debug session and attach a zip of the log to this thread.

Thanks

ki