• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 1404 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.

What is the "best practice" to migrate a CCS V2 project into CCS V4?

LLH
Prodigy 30 points


We have to use a CCS V2 project in CCS V4, how proceed?

We have made some tests but the .map and .out files are differents than the CCS2 version.

To use a new version of "Code Ggeneration Tools " is it the only explanation?

 

LLH

 

  • 0
    TI__Guru**** 472291 points

    LLH said:
    We have to use a CCS V2 project in CCS V4, how proceed?

    A v2 to v4 project migration is pretty big. Most people do a v2->v3->v4 migration. But you can try the legacy import wizard... i believe it should work.

    LLH said:
    We have made some tests but the .map and .out files are differents than the CCS2 version.

    Most likely the issue is because you moved to a different version of the Code Generation Tools (CGT). You may still be able to use the same version you were using with v2. What device are you working with? What version of the CGT are you using? Is this a BIOS project?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 30 points

    Hi,

    Yes, the legacy import wizard have worked well to import one of  our v2 project  (without warning or error messages).

    We have two type of  projects to be imported.

    We do not use " DSP BIOS " and "Visual Linker", for our current projects

    1. "C54xx" projects:

    Devices: C549 or C5409

    Code Generation Tools (CGT) used: C54 V3.12

    Those projects have been initially developed with CCS 1.2, then used with CCS V2.1

    We use the following types of file to build it: .gel, .pjt, .mak and .cmd

    2. C55xx” projects:

    Devices: C5502 or C5510

    CGT used: C55 V2.56                                                            

    We use the following types of file to build it: .gel, .pjt and .cmd


    We have made the tests with a “C55xx” project.
    Like explained here: “http://processors.wiki.ti.com/index.php/Compiler_Installation_and_Selection”,
     we have tried adding the “C55 V2.56” CGT (unsupported version).
    The adding has not worked, it “froze” CCS (“no answer” displayed into the task controller).
    We had to “kill” the application to “take the hand”.


    How to proceed?


    About the “C54xx” projects, create a “Standard Make Code composer Project” is it a part of the solution?


    Regards,

    Laurent

     

  • 0 in reply to LLH
    TI__Guru**** 472291 points

    Both the version of CGT are very old and as you noticed, are not officially supported by the v4 project manager. Though CCS should not freeze when selecting an old CGT version...

    LLH said:
    About the “C54xx” projects, create a “Standard Make Code composer Project” is it a part of the solution?

    Yes you can use standard make projects instead if you wish to use the old CGT versions. You can use the CCSv2 export to makefile feature to create a makefile and the simply use that makefile in v4.

     

  • 0 in reply to Ki
    Intellectual 530 points

    I am doing the migration from CCS v2.20 to CCS v4.1, I think it is a big jump from v.2 directly to v.4, I did that, however, *.out file didn't load in v.4 and I couldn't figure out what the problem was. Then, I moved at small paces, from v2.20 to v3.1, then v3.2 and v 3.3. Each step, I encountered some issues, most of them are related to the BIOS (such as CSL is not supported in BIOS any longer), because your project doesn't use BIOS, you may skip one or two steps in v3.

    I am in CCS v3.3 now, after verifying that *.out is loaded and functional, I updated the BIOS and CGT to the same versions as those in CCS v4.1, now I am ready to import CCS3.3 project to CCS v.4.

    Yuhua     

  • 0 in reply to Ki
    Prodigy 30 points

     

    I apologize for the long time without answers but some others "jokes" like "How using an CCS2 project with CCS4 ?" have disturbed me ;-)

     

    Using the standard "makefile" works fine for our purpose "generate the samecompiled file, binary comparison,  with CCS 4 than with CCS2"

    .

    How to proceed?

     

    From your CCS2:
    - Generate an export. This operation produces a "makefile" which is specific to your project.

     

    From CCS4:
    - Create a "Standard Make project"

    - Import your source files into it

    - Configure the project properties, the "C/C++ Make project" item.

    - Edit the "makefile" to adjust the paths and directories.

    To release the compilation you needed to access at the CSS2 libraries, be sure to access to its.

     

    Now you can generate a compiled file, with CCS4, who is like one file produced with CCS2.

     

    Some others information:

    -          The makefile generate by CCS2 have one "target" for each source file needed to the compilation.
    This "target" contain all dependency files of it.
    If you need to add one new source file create the same code is necessary.
    To release that you can obtain the information with the right option of the using compiler.
    Sample:
    - For C file: cl55 -ppi MyNewSource.c -i"INCLUDE_DIRECTORY"
    - For ASM file: cl55 -api MyNewSource.asm -i"INCLUDE_DIRECTORY"

    -          About "Make":
    http://www.gnu.org/software/make/manual/make.html

     

    LLH