Difference between revisions of "CCS4 open old CCS3 DSP/BIOS project"

From DSignT Support Database
Jump to: navigation, search

 
(Pushed from DSignT Issue Database.)
Line 1: Line 1:
=== Problem ===
+
== Problem: ==
 
after opening old DSP/BIOS project CCS4 fails to link due to several errors like:<br>
 
after opening old DSP/BIOS project CCS4 fails to link due to several errors like:<br>
 
* run placement fails for object ".abc"
 
* run placement fails for object ".abc"
Line 5: Line 5:
  
  
=== Solution ===
+
== Solution: ==
 
CCS4 already uses all defined sections from database without generating a linker command file. Old DSP/BIOS projects contain automatically generated linker command files. These *.cmd files are imported by CCS4 to the current project and linked again to the current executable. Exclude these files from build for proper link process.
 
CCS4 already uses all defined sections from database without generating a linker command file. Old DSP/BIOS projects contain automatically generated linker command files. These *.cmd files are imported by CCS4 to the current project and linked again to the current executable. Exclude these files from build for proper link process.
  
 +
== Additional Tags ==
 +
CCSv4, [[Migrating C2000 Projects from CCSv3.3 to CCSv4|Migrating old projects]]
  
 
[[Category:CCS4 Usage]]
 
[[Category:CCS4 Usage]]

Revision as of 14:50, 15 December 2011

1 Problem:

after opening old DSP/BIOS project CCS4 fails to link due to several errors like:

  • run placement fails for object ".abc"
  • absolute symbol "XYZ" being redefined


2 Solution:

CCS4 already uses all defined sections from database without generating a linker command file. Old DSP/BIOS projects contain automatically generated linker command files. These *.cmd files are imported by CCS4 to the current project and linked again to the current executable. Exclude these files from build for proper link process.

3 Additional Tags

CCSv4, Migrating old projects



Contact Post.png Support Tool.png