• Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 1117 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/TMS320C6670: CCS v7 Command Line project Import gives Assert exception

Rob G.
Intellectual 440 points

Part Number: TMS320C6670
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

I'm building our projects via command line. To do that, I import them into a temporary workspace, and then build them.

When using CCS v6.1.2 command line tools, the import worked fine, but the build would not build the configuration I was asking for (Debug/Release) reliably. So I decided to try the latest CCS. Using CCS v7.0.0, it now builds the projects with the correct configuration. However, when trying to import one particular project, I am getting an AssertFailedException.

The command line to import:

C:\ti\ccsv7\eclipse\eclipsec.exe -noSplash -application com.ti.ccstudio.apps.projectImport -data "./spm34cp_workspace" -ccs.location "./Common/packages/ti/transport/ndk/nimu"

The exception thrown (just the first few lines of it..it's long):

org.eclipse.core.runtime.AssertionFailedException: assertion failed: at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110) at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96) at com.ti.common.project.core.OutputType.createReference(OutputType.java:109) at com.ti.common.project.core.OutputTypeReference.fromString(OutputTypeReference.java:140) at com.ti.common.project.core.internal.settings.AConfigurationSettings.getOutputType(AConfigurationSettings.java:216) at com.ti.ccstudio.project.core.internal.settings.CCSConfigurationSettings.getOutputType(CCSConfigurationSettings.java:105) at com.ti.common.project.core.util.CTIProjectCoreUtils.getOutputType(CTIProjectCoreUtils.java:1225) at org.eclipse.rtsc.xdctools.buildDefinitions.XDC.util.XDCManagedBuildCoreUtils.isRTSCConfigurationProject(XDCManagedBuildCoreUtils.java:88) at org.eclipse.rtsc.xdctools.buildDefinitions.XDC.util.XDCManagedBuildCoreUtils.findReferencedRTSCConfiguration(XDCManagedBuildCoreUtils.java:145) at org.eclipse.rtsc.builddefinitions.xdc.settings.XDCConfigurationSettingsContributor.getInheritedProductsSource(XDCConfigurationSettingsContributor.java:89)

As I see XDC mentioned in the exception, I will say that I am using XDC 3_32_01_22_core. As a test, I went back to CCS v6 for the import, and it works fine. So, at this point, I am going to try and import with CCS v6 and build with CCS v7, but I'd rather not have to do that.

  • Intellectual 440 points
    Well, doing v6 and v7 didn't work. It imported everything (with v6), but when I go to build the project (with v7), it says "Project 'nimu_eth_spm34cp' could not be loaded!, and that's all.
  • in reply to Rob G.
    Guru 56198 points
    Hi Rob,

    Why not try CCS7 project import wizard and see if you get some other error message? I just imported several projects from CCSv5.4 and they all build without error. Had to first migrate compiler versioning equally between studio versions prior to import to CCS7 order to avoid 100's symbol errors in CC& builds. Notice you installed CC7 in the (ti) folder location and I installed at C:\CCS7\ccsv7, (ccsv7) was appended by the installer. My CCS5.4 was installed for many years at C:\CCS5 along with xdctools/uia/bios6 etc...
  • in reply to Genatco
    Intellectual 440 points
    Sorry, I forgot to mention. I have had no problems when using the CCS IDE to accomplish these tasks (importing and building), whether 6.1 or 7.0.

    I'm now attempting to try CCS v 6.2, and it seems promising so far.