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.

How to install device-variant descriptor?

Other Parts Discussed in Thread: CONTROLSUITE, TMS320F28069, CCSTUDIO

I made a new install of CCS v5.2.100018 and ControlSuite on a Ubuntu Linux machine.

When trying to comile a project developed on a different machine (Win7), I get the error:

"This project was created for a device-variant that is not currently recognized: TMS320C28XX.TMS320F28069.EXPKITF28069. Please install the device-variant descriptor, or migrate the project to one of the supported device-variants by adjusting project properties."

But how can I install a variant-descriptor?

Joachim

  • Hi Joachim,

    did you install C2000 support when installing?  Do you launch CCS with the same permissions as you installed it with? ie install as sudo and launch as sude or conversely install as user and launch as user.

    How did you import the project?  Did you do a Project->Import existing CCS/Eclipse Project? 

    What do you see under window->preferences->code composer studio->build->code generation tools?

    Best Regards,
    Lisa

  • Hi Lisa,

    > did you install C2000 support when installing?

    No, there was no chance to do so. It only allowed to install "c28x 32-bit Real-time MCUs", which I did.

    > Do you launch CCS with the same permissions as you installed it with? ie install as sudo and launch as sude or conversely install as user and launch as user.

    I installed sudo and start as user.

    Meanwhile I figured out that CCS is not multi user qualified. Neither on Linux nor on Windows.

    > How did you import the project?  Did you do a Project->Import existing CCS/Eclipse Project?

    yes.

    > What do you see under window->preferences->code composer studio->build->code generation tools?

    Under build there is only "Compilers" and it shows
    ARM ti v4.9.5
    C2000 ti v6.1.0

    I think the main problem could be that on Windows Control Suite is installed into CCS but on Linux it's not.
    So CCS has no access to samples and libs that go with Control Suite.

    Best Regards,
    Joachim

  • Hi Joachim,

    yes I would make sure you have Control Suite and also launch as sudo.   Please keep us informed.

    Best Regards,
    Lisa

  • Hi Lisa,

    the problem is that Control Suite runs on Wine. Thus it can not cooperate with CCS. So I have to manually install the feature into CCS. But how?

    Best Regards,
    Joachim

  • Hi Joachim,

    have you tried going to Window->Preferences->Code Composer Studio->Build->RTSC->Products and pointing CCS to ControlSuite?  Or alternatively via Help->INstall new software?

    Please keep us informed.
    Best Regards,
    Lisa

  • Hi Joachim,

    just wanted to see if there was any update with your enquiry.

    Best Regards,
    Lisa

  • Hi Lisa,

    I was a litte stuck into different project.

    Adding the ControlStuite path in the products window didn't help. It's not a product I want to install but a device variant.

    I found that there is a file expkipF28069.xml in the targetdb directory on Windows and Linux. But only the Windows CCS offers me "Experimenter's Kit - Piccolo F28069" as device variant in the properties dialog.

    Meanwhile I told my customer to rethink his decision for using ti.

    Best Regards,
    Joachim

  • Hi!

    I tried changing the target variant to "controlSTICK - Piccolo F28069" to at least compile the sources. (Which won't help to much as it's not the target I need.)

    The result was a Null pointer exception. (CCS 5.2.1.00018 on ubuntu)

    I'm sorry but if there is no reliable way to compile for a certain target platform this is not usable for industrial development / production. And as I have seen this is not the only thread in this forum that complains that projects can't be build after changing the PC or the compiler version.

    --------------------------------------- project.log -------------------------------------------------------------

    !ERROR: java.lang.NullPointerException
        at com.ti.ccstudio.project.core.internal.initializer.CCSConfigurationInitializer.doCopyBuildOptions(CCSConfigurationInitializer.java:438)
        at com.ti.common.project.core.internal.initializer.AConfigurationInitializer.copyBuildOptions(AConfigurationInitializer.java:116)
        at com.ti.common.project.core.internal.initializer.AConfigurationInitializer.internalCopyBuildOptions(AConfigurationInitializer.java:325)
        at com.ti.common.project.core.internal.initializer.AConfigurationInitializer.internalInitializeBuildOptions(AConfigurationInitializer.java:272)
        at com.ti.common.project.core.internal.initializer.AConfigurationInitializer.initializeFromExisting(AConfigurationInitializer.java:92)
        at com.ti.common.project.ui.internal.properties.ConfigurationPropertiesPage.saveConfiguration(ConfigurationPropertiesPage.java:315)
        at com.ti.common.project.ui.internal.properties.ConfigurationPropertiesPage.forEach(ConfigurationPropertiesPage.java:270)
        at org.eclipse.cdt.ui.newui.AbstractPage$5.sendOK(AbstractPage.java:620)
        at org.eclipse.cdt.ui.newui.AbstractPage$5.run(AbstractPage.java:650)
        at org.eclipse.ui.actions.WorkspaceModifyDelegatingOperation.execute(WorkspaceModifyDelegatingOperation.java:69)
        at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
        at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
        at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
        at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
        at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
        at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
        at org.eclipse.ui.internal.progress.ProgressManager$RunnableWithStatus.run(ProgressManager.java:1346)
        at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
        at org.eclipse.ui.internal.progress.ProgressManager$7.run(ProgressManager.java:1184)
        at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:180)
        at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150)
        at org.eclipse.swt.widgets.Display.syncExec(Display.java:4330)
        at org.eclipse.ui.internal.progress.ProgressManager.runInUI(ProgressManager.java:1182)
        at org.eclipse.cdt.ui.newui.AbstractPage.performSave(AbstractPage.java:666)
        at org.eclipse.cdt.ui.newui.AbstractPage.performOk(AbstractPage.java:545)
        at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:964)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
        at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
        at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:944)
        at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:447)
        at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233)
        at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
        at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
        at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
        at org.eclipse.jface.window.Window.open(Window.java:801)
        at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:158)
        at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
        at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
        at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
        at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
        at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
        at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
        at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
        at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

  • Hi Joachim,

    I would like to try and help you and to see if I can reproduce this locally.  Would you be willing to send the ccxml file offline?  Would you be willing to install Control Suite direclty in Linux?  I am not sure how stable a connection there might be, if much of one between CCS and Wine.  Did you launch as sudo?

    Are you able to create a new project for the F28x part you are using?

    Best Regards,

    Lisa

  • Hi Joachim,

    just thought I would check whether there is any update to your enquiry. 

    Best Regards,

    Lisa

  • Hi Lisa,

    I won't follow this thread any more because I stopped using CCS on Linux.

    I can see no reasonable trade off between the work to get the system running and the money I could earn with that. I am developping embedded software on a professional basis. CCS is nice for hobbyists that want to spend some time getting it to work.

    Best Regards,
    Joachim

  • Hello Lisa,
    I'm facing a nearly identical problem. I've got CCS installed and working, and Control Suite installed and working on Linux (Debian). I need to now tell CCS about the location/path to the ControlSuite installation.

    I tried using "Window > Preferences > CodeComposerStudio> RTSC > Products"
    as well as
    "Help > Install new software" but neither method worked - i get the error "No software site found at file:/opt/ti/controlSUITE"

    Any ideas?