CCS/C2000-CGT: Migration tip for project conversion from CCS 3.3 to CCS 10

Hello,

Shao Ma1 said:

1) I have project which has another nested project all from CCS 3.3. When I import a top level CCS 3.3 project into CCS 10.0. It prints out in "project.log" following message:

!ERROR: This project has DSP/BIOS content, but no DSP/BIOS tools are currently installed. Please install DSP/BIOS tools and re-migrate this project.
!CONFIGURATION: 'com.ti.ccstudio.buildDefinitions.C2000.Default.1352158140' [Thu Jun 11 12:23:18 PDT 2020]

 !TOOL: 'com.ti.ccstudio.buildDefinitions.C2000_20.2.exe.compilerDebug.581946434'

  !WARNING: Unresolved option: com.ti.ccstudio.buildDefinitions.C2000_20.2.exe.compilerDebug.581946434::!--symdebug:dwarf

My question: what is exactly missing for supporting this migration? what does it means to install DSP/BIOS tool - for CCS 10.0 I assume?  I know DSP/BIOS is now SYS/BIOS and I have installed SYS/BIOS (6.82) after my CCS 10.0.

Current CCS versions do not come with DSP/BIOS. But you can get it from the CCS App Center.

Note that DSP/BIOS support has been heavily deprecated in support. Please take a close look at the below wiki article:

https://processors.wiki.ti.com/index.php/DSP/BIOS_Support_in_CCS_Eclipse

Note that SYS/BIOS is the new replacement for DSP/BIOS. There are many changes and moving from DSP/BIOS to SYS/BIOS would require a bit of migration effort. Please see the below application note for more details:

https://www.ti.com/lit/an/spraas7g/spraas7g.pdf

Shao Ma1 said:

  !WARNING: Unresolved option: com.ti.ccstudio.buildDefinitions.C2000_20.2.exe.compilerDebug.581946434::!--symdebug:dwarf

--symdubug:dwarf was an option in the older compiler version which has been deprecated in the newer compiler versions. DWARF is now the default and hence no need for an option to specify it

Shao Ma1 said:

2) I also advice to make change for DWARF and COFF -> ELF. FOr example, I have another message in "project.log" resulted from CCS 3.3 to CCS 10 based on another project that says below:

!CONFIGURATION: 'com.ti.ccstudio.buildDefinitions.C2000.Default.686266129' [Tue Jun 09 08:44:39 PDT 2020]

 !TOOL: 'com.ti.ccstudio.buildDefinitions.C2000_20.2.library.compilerDebug.1959068747'

  !ERROR: org.eclipse.cdt.managedbuilder.core.BuildException: Unexpected value 'p' for option 'Debugging model'! Applicable values are: [, Full symbolic debug (--symdebug:dwarf, -g), Symbolic debug for program analysis (DEPRECATED) (--symdebug:skeletal), Suppress all symbolic debug generation (--symdebug:none), Full symbolic debug (COFF, deprecated) (--symdebug:coff), Function profile debug (COFF, deprecated) (--symdebug:profile_coff)].
   at com.ti.common.project.core.util.CTIProjectCoreUtils.setBuildOption(CTIProjectCoreUtils.java:901)
   at com.ti.common.project.core.util.CTIProjectCoreUtils.setBuildOption(CTIProjectCoreUtils.java:836)
   at com.ti.ccstudio.project.core.internal.legacy.LegacyProjectImporter.setOptionSettings(LegacyProjectImporter.java:1333)
   at com.ti.ccstudio.project.core.internal.legacy.LegacyProjectImporter.processToolOptionSettings(LegacyProjectImporter.java:885)
   at com.ti.ccstudio.project.core.internal.legacy.LegacyProjectImporter.processBuildConfigurationSettings(LegacyProjectImporter.java:827)
   at com.ti.ccstudio.project.core.internal.legacy.LegacyProjectImporter.createManagedMakeProject(LegacyProjectImporter.java:458)
   at com.ti.ccstudio.project.core.internal.legacy.LegacyProjectImporter.doRun(LegacyProjectImporter.java:263)
   at com.ti.ccstudio.project.core.internal.legacy.LegacyProjectImporter.access$0(LegacyProjectImporter.java:224)
   at com.ti.ccstudio.project.core.internal.legacy.LegacyProjectImporter$1.run(LegacyProjectImporter.java:207)
   at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2292)
   at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2312)
   at com.ti.ccstudio.project.core.internal.legacy.LegacyProjectImporter.run(LegacyProjectImporter.java:205)
   at com.ti.ccstudio.project.ui.internal.wizards.importlegacy.ImportLegacyProjectWizard$2.run(ImportLegacyProjectWizard.java:144)
   at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
  

I'm not sure about this one. There is an unrecognized option for the debugging model. This option can't be resolved. I don't recognize it from CCS 3.3 either. In any case, I would recommend using the original compiler used with 3.3. You can use that compiler version with CCS 10.

Also, there is a document on migrating CCSV3.3 project to CCS 10. It may answer some other questions:

https://software-dl.ti.com/ccs/esd/documents/ccs_legacy-project-import.html

Thanks

ki