TMS320C40: Gel Copy Command Not Working

Hello Joe,

Please keep in mind that C40 is an extremely old device. The processors team is no longer able to answer hardware or software design questions about this part. As someone who has never used this device, Code Composer 4.10, or the tool you are using, the best I can come up with is to make sure that the file actually exists before the gel script tries to access it. I have seen similar issues in totally unrelated software when there was a race condition in the code.

I am sending your thread over to the CCS team in case they have any additional feedback.

Regards,

Nick

Hi Joe,

Joe Federici said:

A legacy system uses Code Composer 4.10 and the tool was ported to a new Laptop.  When running gel scripts that worked on the previous laptop

What was the Windows version of the legacy system?

In your screenshot, it looks like you are running CC on Windows 7?? Is this 64-bit Windows 7? That is remarkable on its own. I've never been able to get it working (well) on anything past XP. We definitely do not recommend anything past XP for a number of reasons - the two biggest being the additional security introduced with Vista and the changes made to the registry. I would strongly recommend sticking with an XP environment. I keep one old XP machine for cases such as this.

Thank you for responding. The laptop is 32-bit Windows 7 - I attached the properties.  Over the years we were able to run on newer versions of Windows as they came out with better security features.  However IT decreed that no 32-bit OS machines are allowed on the network which is how this issue came up. I believe we were able to run on Windows 10 and 11 on the network.  I will look into getting an XP machine.  Thanks again.Laptop_Properties.rtf

Yes, the registry changes made in 64-bit Windows greatly impacts the older CC/CCS tools based on the old MS MFC framework. I'd strongly recommend a native XP-32 machine - especially if you plan on trying to connect to actual hardware.

Still, the error is specific - the debugger was able to access the file in question. If the file actually exists, then I'm not sure what the issue could be. Perhaps try generating and referencing the file using a different location - maybe one in the home folder?

To clarify, the first line that fails is  GEL_System("copy c:/release/modedata/AVCA_STP_T_MODE_00500Inputcc.dat c:/release/modedata/inputdata500.dat");

when file inputdata500.dat does not exist.  If I create that file thru windows, it gets by that line and fails at line:

  GEL_System("copy c:\\release\\modedata\\out500.dat c:\\release\\modedata\\AVCA_STP_T_MODE_00500CC.dat");

and does not create AVCA_STP_T_MODE_00500CC.dat.

Other tests have more than one load and save, and the results are contatenated with a series of GEL_System Copy commands.  I may be able to get around this by doing the file operations outside of Code Composer. 

Its strange because it worked on the previous laptop which I believe was windows 10 or 11.  This is a faster laptop, I don't know if that matters.
 

It sounds like an issue where Code Composer does not have the permissions to execute those GEL_System commands where it may have had those permissions on the previous laptop. Can CC be run with elevated permissions?

I am running it as admin.  I too suspect some kind of permissions issue.

It could be some behavior where while CC is running as administrator, the GEL_System call passes to a system terminal with non-elevated permissions.