• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 756 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/CCSTUDIO: Code Composer Studio 8.3: Incompatible Workspace

StephanS
Genius 4077 points
Part Number: CCSTUDIO

Tool/software: Code Composer Studio

Hi,

I have updated from CCS 8.1 to 8.3 (separate installations) and found that I can't use my existing workspace any more: The debug settings are lost.

In the debug configurations, the program to load is empty.

In the flash settings, the erase sector selection is at default (all sectors checked).

In the target program/memory load options, the checkmarks are at default.

Maybe there are also other differences.

When opening the same workspace with CCS 8.1, everything is fine - my adapted settings are still there.

To have a deeper look into this, I changed the debug settings for one load configuration and found some changes:

There is a new key for ATTR_DEBUGGER_PROPERTIES

<stringAttribute key="com.ti.ccstudio.debug.debugModel.ATTR_DEBUGGER_PROPERTIES.C:\Projekte\DSP\Piccolo_28035_C2000XDS510LCUSB.ccxml.Spectrum Digital C2000 XDS510LC Emulator_0/C28xx" value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot; ?&gt;&#10;&lt;PropertyValues&gt;&#10;&#10;  &lt;property id=&quot;AddCIOBreakpointAfterLoad&quot;&gt;&#10;    &lt;curValue&gt;0&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;  &lt;property id=&quot;ConnectOnStartup&quot;&gt;&#10;    &lt;curValue&gt;1&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;  &lt;property id=&quot;FlashSectorA&quot;&gt;&#10;    &lt;curValue&gt;0&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;  &lt;property id=&quot;FlashSectorB&quot;&gt;&#10;    &lt;curValue&gt;0&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;&lt;/PropertyValues&gt;&#10;"/>

although there are already some existing keys

<stringAttribute key="com.ti.ccstudio.debug.debugModel.ATTR_DEBUGGER_PROPERTIES.Spectrum Digital C2000 XDS510LC Emulator_0/C28xx" value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot; ?&gt;&#10;&lt;PropertyValues&gt;&#10;&#10;  &lt;property id=&quot;AddCIOBreakpointAfterLoad&quot;&gt;&#10;    &lt;curValue&gt;0&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;  &lt;property id=&quot;ConnectOnStartup&quot;&gt;&#10;    &lt;curValue&gt;1&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;  &lt;property id=&quot;FlashSectorA&quot;&gt;&#10;    &lt;curValue&gt;0&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;&lt;/PropertyValues&gt;&#10;"/>
<stringAttribute key="com.ti.ccstudio.debug.debugModel.ATTR_DEBUGGER_PROPERTIES.Spectrum Digital C2000 XDS510LC Emulator_0/C28xx_0" value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot; ?&gt;&#10;&lt;PropertyValues&gt;&#10;&#10;  &lt;property id=&quot;ConnectOnStartup&quot;&gt;&#10;    &lt;curValue&gt;1&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;  &lt;property id=&quot;FlashSectorA&quot;&gt;&#10;    &lt;curValue&gt;0&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;&lt;/PropertyValues&gt;&#10;"/>
<stringAttribute key="com.ti.ccstudio.debug.debugModel.ATTR_DEBUGGER_PROPERTIES.Spectrum Digital XDS510 Parallel Port-PCI  Emulator_0/C28xx" value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot; ?&gt;&#10;&lt;PropertyValues&gt;&#10;&#10;  &lt;property id=&quot;ConnectOnStartup&quot;&gt;&#10;    &lt;curValue&gt;1&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;  &lt;property id=&quot;FlashSectorA&quot;&gt;&#10;    &lt;curValue&gt;1&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;  &lt;property id=&quot;FlashSectorB&quot;&gt;&#10;    &lt;curValue&gt;0&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;  &lt;property id=&quot;FlashSectorC&quot;&gt;&#10;    &lt;curValue&gt;0&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;  &lt;property id=&quot;FlashSectorD&quot;&gt;&#10;    &lt;curValue&gt;0&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;  &lt;property id=&quot;FlashSectorE&quot;&gt;&#10;    &lt;curValue&gt;0&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;  &lt;property id=&quot;FlashSectorF&quot;&gt;&#10;    &lt;curValue&gt;0&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;  &lt;property id=&quot;FlashSectorG&quot;&gt;&#10;    &lt;curValue&gt;0&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;  &lt;property id=&quot;FlashSectorH&quot;&gt;&#10;    &lt;curValue&gt;0&lt;/curValue&gt;&#10;  &lt;/property&gt;&#10;&#10;&lt;/PropertyValues&gt;&#10;"/>
<setAttribute key="com.ti.ccstudio.debug.debugModel.ATTR_HIDE_CONFIG_ELEMENT_TYPES">

The same for ATTR_PROGRAM:

New key

<stringAttribute key="com.ti.ccstudio.debug.debugModel.ATTR_PROGRAM.C:\Projekte\DSP\Piccolo_28035_C2000XDS510LCUSB.ccxml.Spectrum Digital C2000 XDS510LC Emulator_0/C28xx" value="C:\Projekte\DSP\Traction\Belatron_6000_NG\Code\PFC\aktuell\DSP_PFC_6.out"/>

Existing keys

<stringAttribute key="com.ti.ccstudio.debug.debugModel.ATTR_PROGRAM.Spectrum Digital C2000 XDS510LC Emulator_0/C28xx" value="C:\Projekte\DSP\Traction\Belatron_6000_NG\Code\PFC\aktuell\DSP_PFC_6.out"/>
<stringAttribute key="com.ti.ccstudio.debug.debugModel.ATTR_PROGRAM.Spectrum Digital C2000 XDS510LC Emulator_0/C28xx_0" value="C:\Projekte\DSP\Traction\Belatron_6000_NG\Code\PFC\aktuell\DSP_PFC_6.out"/>
<stringAttribute key="com.ti.ccstudio.debug.debugModel.ATTR_PROGRAM.Spectrum Digital XDS510 Parallel Port-PCI  Emulator_0/C28xx" value="c:\Projekte\DSP\PV_Inverter\Code\aktuell\Bootloader_PV\Bootloader__Booster__PV_WR_15_KVA__DEBUG_28062.out"/>

Maybe there are some other changes...

Do I really have to adapt all of my debug configs (there are approx. 100!!)?
Can't this be done automatically?
Why are those changes not documented in the release notes?

Please do not advise "you should always start with a new workspace when using a new CCS version" as this is simply not practical with a higher number of adapted settings and configurations.

Regards,

Stephan

  • 0
    TI__Guru**** 449991 points
    Hello Stephan,
    I used my workspace from CCS 8.0 with CCS 8.3 and the custom settings I made to the debug configuration were preserved in 8.3. Perhaps I need to try an 8.1 to 8.3 migration.

    Can you provide more details about your environment? Perhaps share the project that the launch configuration is generated from?

    Thanks
    ki
  • 0 in reply to Ki
    Genius 4077 points
    Hello ki,

    This problem occurs with a colleage (updating from CCS 7.x), too.

    We use the Debug Configurations as standalone, not directly connected to a project.
    The projects are still there.
    In the standalone debug configurations, we have the target configuration file(this is preserved in 8.3), but also the program to load/flash (with absolute path) and target specific settings.

    From what I described above, it seems that in the Debug Configuration \.metadata\.plugins\org.eclipse.debug.core\.launches\*.launch, there are simply added new lines - the existing config lines are not taken.

    I am not allowed to provide the project here, but can send you the *.launch file if you wish.

    Best regards,
    Stephan
  • 0 in reply to StephanS
    Genius 4077 points
    Any news on this?
  • 0 in reply to StephanS
    TI__Guru**** 449991 points
    I am able to reproduce the issue for a debug launch not associated with a project (stored in: \.metadata\.plugins\org.eclipse.debug.core\.launches).

    I have filed a bug for this. Tracking ID: CCSIDE-3468

    Thanks
    ki
  • 0 in reply to Ki
    Genius 4077 points
    Ok, I will observe the bug ID.
    Thanks!

    Stephan