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

Migrating CCSv3.3 example project to CCSv6

James Basso
Prodigy 120 points
Other Parts Discussed in Thread: CCSTUDIO

Hi,

When I try to import a legacy DVSDK 1.11 application I am having several issues:

1) I am seeing a Warning in my project.log when I run the CCSv3.3 import wizard from CCS6:

!WARNING: Unresolved tool: com.ti.ccstudio.buildDefinitions.C6000.Debug.1858260972::XDC

I assume this stems from the following line in the project file?

Tool="XDC"

Is this something to be concerned about or can it be safely ignored?

2) Also, the cmd_file that the compiler looks for is specified as:

cmd_file = "${SRC_ROOT}/=${PROJECT_ROOT}/xdcconfig/compiler.opt"

which produces an erroneous path. I see this regardless of which project I try to install.

Regards,

James

  • 0
    TI__Guru**** 420650 points

    Hi James,

    CCSv6 ships with a more stripped down version of XDC (XDC core). Since you are using some legacy BIOS project, you'' most likely need the full version. I tryinstalling one of the standalone XDC 3.3x non-core versions:

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/index.html

    thanks

    ki

  • 0 in reply to Ki
    Prodigy 120 points

    Hi Ki,

       Looks like the link you provided is only for the  XDC Core versions.

    Also, any idea why the path to the compiler.opt file is so messed up in the generated build-related files?

    Best,

    James

  • 0 in reply to James Basso
    TI__Guru**** 420650 points

    James Basso said:
       Looks like the link you provided is only for the  XDC Core versions.

    Use this version:

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/3_30_01_25/index_FDS.html

    James Basso said:
    Also, any idea why the path to the compiler.opt file is so messed up in the generated build-related files?

    Not sure what is happening there. I'm hoping have a correct XDC installation will help.

  • 0 in reply to Ki
    Prodigy 120 points

    Ki,

        I installed the stand-alone version of 3_30_01_25. That version was detected when I started up Code Composer and I added it and then went to Windows->Preferences->Code Composer->RTSC and selected that version in the pull-down for XDC tools.

       However, when I imported the legacy v3.3 project via the wizard (I used video_preview project from DVSDK 1_11) I still get the error:

    !WARNING: Unresolved tool: com.ti.ccstudio.buildDefinitions.C6000.Debug.37064202::XDC

  • 0 in reply to James Basso
    Prodigy 120 points

    Hi Ki,

          We never really got very far with our project migration even when using one of TI's standard demo projects that came with the DVSDK. I don't know if it is a problem with the migration wizard or our development environment. Do you have any recommendations as to who we could talk to in order to get support with our migration. We would be open to having a paid consultant come to our site to assist with the migration work. Does TI have a consulting group or are those services only available through the Design Network of certified consulting vendors?

    Best Regards,

    James 

  • 0 in reply to James Basso
    TI__Guru**** 420650 points

    Hi James,

    CCSv3.3 -> CCSv6 migration can be tricky because of the jump in major revision number.

    I assume you are using the DSP/BIOS DVSDK. I'll try this migration myself. What device are you using? And what is your host OS?

    ki

  • 0 in reply to Ki
    Prodigy 120 points

    DVSDK 1.11

    DM6437

    Windows 7, 32 bit

  • 0 in reply to James Basso
    TI__Guru**** 420650 points

    Thanks.

    I was able to migrate video_preview. It was a pain in the butt as you probably already know. My lack of DVSDK knowledge didn't help me either.

    The vast majority of the steps you need are documented in this forum thread. See Anthony's last post:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/319603/1131766.aspx#1131766

    One extra thing I had to do was to fix the path to the compiler.opt file in the compiler options under Build -> C6000 Compiler -> Advanced Options -> Command Files

    I decided to create another *.cmd file and simply added all the libraries there (with a bug cut&paste) instead of manually adding each one in the linker options. But how you want to add the libraries is up to you.

    Thanks

    ki