• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 370 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.

Upgrading from CCS5.3 to CCS5.5 removes some debug configuration selections

Gareth Price
Prodigy 180 points

I have been happily running CCS v5.3 on a windows 7 machine for a few years now. I've been building boot code for a TMS570 and using a Spectrum Digital XDS510 USB to program the device over JTAG. Today I downloaded CCS v5.5 (I wanted support for parallel compilation). I was happy to see that, once it had installed, all my workspaces were available and all my debug configurations were available without me having to import or create them. BUT.... when I tried to download a boot image to the TMS570 it downloaded OK but would not run! I finally tracked the issue down to an unchecked tick box in the debug configuration... it was the one for Auto ECC Generation.

I reproduced this on a colleagues machine. On his CCS v5.3 I checking that Auto ECC Generation tick box was selected, I upgrading to CCS v5.5 and then saw that the Auto ECC Generation tick box was now not selected.

Installation bug? Or maybe v5.5 does not interpret v5.3 generated debug configurations?

  • 0
    TI__Guru**** 421380 points

    Hello,

    Gareth Price said:
    Today I downloaded CCS v5.5 (I wanted support for parallel compilation).

    Note that parallel builds was supported in earlier v5 versions. It's just that you had to manually add the -j gmake option. Starting with later CCSv5 version, there is a nice GUI interface to do this

    Gareth Price said:
    Or maybe v5.5 does not interpret v5.3 generated debug configurations?

    Most likely some changes were made since v5.3 that impacted debug configurations.

    Debug configurations is not something meant to be portable and shared. It is a set of generate meta files. So it is quite possible that it simply needed to be regenerated/reconfigured after the update.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 180 points

    Thanks for the speedy reply ki.

    My worry is that, because the debug configurations appear as before without any user interaction, the user may think that they will work as before. Maybe there should be a disclaimer during installation saying that debug configurations must be regenerated.

    Hopefully this post will help others who are having these issues.

  • 0 in reply to Gareth Price
    TI__Guru**** 421380 points

    Gareth Price said:
     Maybe there should be a disclaimer during installation saying that debug configurations must be regenerated.

    That is a good idea. An FAQ at least and also added to any updating guide. Thanks fro the suggestion, I'll make note of this so it happens.