reinstalling Code Composer V4.1 after hard drive crash

Try to create empty workspace and update your CCS with all features.

Hi Bob,

CCv4.1 and Windows 98?? That is going waaay back here for me :)

I suspect that you are missing some components from the original CCv4.1 install when you saved the *.wks file. Either a specific ISA support or if you were using some third party emulator, you are missing the drivers for it. Hence CCS can't open the *.wks file on reopen in the new environment.

You'll need to make sure you have all components you had in the original install on your current one.

Thanks

ki

Ki thanks for yor reply.

We have the third party emulator drivers and are able to program our DSP thru the emulator.  We can use the gel commands to program the DSP just fine.  We just can not get the .wks file working.  We can not read the .wks file to figure out what is wrong with it.  We have determined our current code composer setup does not like our "startup" command line in original the .gel file.  When we remove this command from the .gel files it runs.  We don't know how to recreate a .wks file.  If we could we would try to make a .wks file without the startup command to see if this is truely the issue.  Because this is controlled software we would rather not make any changes.  We would like to get the original .wks file working again. 

We did note that code composer uses an init.gel on startup.  In this init.gel it has a startup command simialar to the one in our .gel file.

Our work around is to write our programming instructions using the .gel file and not use the .wks file.  We verified in Final test that the correct code is on the DSP, so we know this method works.   At this point we don't think we will ever know why our .wks file will not run in our current installation.

Thanks again for your post...

Bob Paroline said:

We can not read the .wks file to figure out what is wrong with it.

It's a binary file. You would not be able to read it

Bob Paroline said:

We have determined our current code composer setup does not like our "startup" command line in original the .gel file

Can you attach this GEL file?

Bob Paroline said:

We don't know how to recreate a .wks file.  If we could we would try to make a .wks file without the startup command to see if this is truely the issue.

You can create a new one by 'File -> Workspace -> Save Workspace'.

StartUp() { } Burn() { GEL_Reset(); GEL_Load("a:\\Prog.out"); GEL_Go(main); GEL_MemoryLoad(0x87FE00,0,0x1D4,"a:\\Intram.dat"); GEL_MemoryLoad(0x922000,0,0x2C3,"a:\\CONFIG_A.dat"); GEL_MemoryLoad(0x923C00,0,0x2C,"a:\\CC_A.dat"); GEL_MemoryLoad(0x924000,0,0x508,"a:\\Bootf.dat"); GEL_MemoryLoad(0x928000,0,0x5A8,"a:\\Boots.dat"); GEL_MemoryLoad(0x930000,0,0x29CD,"a:\\Main.dat"); GEL_Run(); }

When we remove the StartUP(){} section we are able to load and run the .gel file. 

-Bob

StartUp() is empty?