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.

Incompatble COFF files between CCS3.3 and CCS4.1???

Other Parts Discussed in Thread: DM3730, OMAP3530

We seem to be having a problem using CCS4.1 Syslink/Procmgr running on OMAP3530 or DM3730 loading COFF files generated by CCS3.3 Code Generator.  When loading a COFF file from CCS3.3 we get an Address Fault aways at an address not present in the COFF load map.  I believe it's interpreting the wrong field as a hex address usually 0x00000100 or 0x0000000A.  We need the Syslink/Procmgr to load the DSP, set the MMU and take the DSP out of reset, but we would prefer developing code in the CCS3.3 environment because of the Blackhawk JTAG support for the OMAP3530 being more reliable.  Any suggestions?

WR Macre