• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 2648 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.

Import CCsV2.2 project into CCsV4

Max Forster
Intellectual 485 points

Hi everybody,

I worked until now on WinXP - CCsV2.2 (with XDS510USB). Now I have a Win7 machine and try to evaluate the CCsV4, therefore I must import my old CCsV2.2 projects into CCsV4, which is, as I understand from this forum and the wiki of CCs, very hard.

Correct me if I am wrong:

  1. The bios changed from CCsV2.2 so that I must update first my V2.2 projects to CCsV3.x (tcf format) 
  2. After I did that I must (can) import it in CCsV4 (and there the bios will be updated to the latest version 6)

So how can I update my CCsV2.2 projects to tcf bios format if the CCsV3.x is not available anymore? Is there a 'how to' available, which steps has to be performed to get files from CCsV2.2 to CCsV4 (or higher)?

Regards,

Max

  • 0
    TI__Guru**** 451061 points

    Hi Max,

    Max Forster said:
    The bios changed from CCsV2.2 so that I must update first my V2.2 projects to CCsV3.x (tcf format) 

    You mainly need to convert your BIOS 4.x CDB file to BIOS 5.x tcf file. You can do this outside CCSv3.3 also, though opening the project in v3.3 will automate the procedure.

    NOTE that if you want BIOS RTA support in v4, you need to move to BIOS 5.4 (CCSv3.3 comes with BIOS 5.3). So I would just use the tools in the BIOS 5.4 install that comes with CCSv4 and use the command line tools to migrate your CDB to a BIOS 5.4 TCF.

    http://processors.wiki.ti.com/index.php/Migrating_from_BIOS_4.9_to_BIOS_5.x

    Max Forster said:
    After I did that I must (can) import it in CCsV4 (and there the bios will be updated to the latest version 6)

    NO. CCSv4 supports BIOS 5 and BIOS 6. So if you have a BIOS 5 project, CCSv4 will not update it to BIOS 6. If you want to use BIOS 6, you need to migrate it yourself:

    http://www.ti.com/lit/an/spraas7g/spraas7g.pdf

    Max Forster said:
    So how can I update my CCsV2.2 projects to tcf bios format if the CCsV3.x is not available anymore?

    As I mentioned before, you don't necessarily need CCSv3.3 to convert your CDB files to TCF.

    Max Forster said:
    Is there a 'how to' available, which steps has to be performed to get files from CCsV2.2 to CCsV4 (or higher)?

    The URL's above I mentioned is for converting BIOS config files. You can use the CCSv4 legacy import wizard to convert your CCS project:

    http://processors.wiki.ti.com/index.php/Importing_CCSv3_Projects_into_CCSv4

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 485 points

    Hello,

    I am sorry that I not answered earlier, but I some other projects in between. Here are my observations (which maybe help some other poor guys there outside) regarding the issue "porting CCSV2 project with bios and csl to CCSV4".

    First a observation, I tried to do update my bios version with the help files and unfortunately I have no success. I tried it with the cmd line, but I got the following error:

    C:\ti\CCSV4\bios_5_41_10_36\packages\ti\bios\config\update>cdb2tcf C:\ti\CCSV4\bios_5_41_10_36\packages\ti\bios\include  C:\Works_Software\MCWD20\c6713.cdb
    Application: C:/Works_Software/MCWD20/c6713.cdb
    Original seed file: c:/ti/ccsv4/bios_5_41_10_36/packages/ti/bios/config/update/4.90.270/c6x1x.cdb
    Loading application CDB file
    Device name: 6713
    Catalog: ti.catalog.c6000
    Generating CSL files
    Unloading the application CDB file
    Loading original seed: c:/ti/ccsv4/bios_5_41_10_36/packages/ti/bios/config/update/4.90.270/c6x1x.cdb
    Finding user changes
    Loading new seed file
    New seed: c:/ti/ccsv4/bios_5_41_10_36/packages/ti/bios/config/cdb/c6x1x.cdb
    Couldn't open c:/ti/ccsv4/bios_5_41_10_36/packages/ti/bios/config/cdb/c6x1x.cdb
    Error code 25

    Because I did not find an other option I tried the same with the 'gconf' tool which is included in each bios package and the cdb file gets correctly updated. BUT as I tried to open the new tcf file I get the following error:

    js: "C:/ti/CCSV4/bios_5_41_00_06/packages/ti/bios/config/bios_6713.tci", line 87: Error: Can't find configuration seed: ti/bios/config/cdb/c6x1x.cdb

    I really searched long I can't find the error, I tried it with different bios packages but everytime the same. The last time as I tried it I look for the file 'c6x1x.cdb' in the ti/bios/config/cdb/c6x1x.cdb and it was there, I make a backup of the file before updating with the gconf tool my cdb and was really curious the gconf tool deletes the file after update successfully out of the ti/bios/config/cdb/c6x1x.cdb folder. Now if i use my backup everything works quite fine, I can open my tcf file without a problem.

    Why the gconf tool delete the seed file?

    Regards,

    Max

  • 0 in reply to Max Forster
    Intellectual 485 points

    Hey everybody,

    now I was able to convert my project. That are the steps to import CCSV2.2 project (with CSL and BIOS 4.9) to CCSV4.x:

    1) Go to CCSV4\bios_5_41_10_36\packages\ti\bios\config\cdb folder and make a backup of c6x1x.cdb file (or the corresponding seed file to your plattform)

    2) Start gconf tool which is located in CCSV4\bios_5_41_10_36\packages\ti\bios\config\gconf\bin

    3) Open your old *.cdb file, it will be converted

    4) Go back to CCSV4\bios_5_41_10_36\packages\ti\bios\config\cdb folder, the seed file is deleted (whatever reason) rescue the file out of your backup

    5) Open the *.tcf file, which should now be in your project folder with the gconf tool, if you can open it that was the first step :)

    6) Download CSL from ti homepage, unzip/install it in your CCSV4 installationfolder

    7) Start CCSV4 and use the 'Project>Import Legacy CCsV3.3 Project Option' on your project

    8) Add your new *.tcf file to the project (I think you can delete the *.cdb file out of the project tree)

    9) Go to Project>Properties and add your CSL\Include folder to "Include Options" in Compiler options and to "File Search Path" in Linker options

    10) Compile!

    Unfortunately I get now a lot of unresolved symbol errors which I can not explain...

    undefined           first referenced                              
      symbol                 in file                                   
     ---------           ----------------                              
     _CACHE_reset        C:/Works_Software/MCWD20/Debug/main.obj       
     _EDMA_allocTable    C:/Works_Software/MCWD20/Debug/edma_mcasp1.obj
     _EDMA_intAlloc      C:/Works_Software/MCWD20/Debug/edma_mcasp1.obj
     _EDMA_intDispatcher C:/Works_Software/MCWD20/Debug/c6713cfg.obj   
     _EDMA_intHook       C:/Works_Software/MCWD20/Debug/edma_mcasp1.obj
     _EDMA_map           C:/Works_Software/MCWD20/Debug/edma_mcasp1.obj
     _EDMA_open          C:/Works_Software/MCWD20/Debug/edma_mcasp1.obj
     _EDMA_resetAll      C:/Works_Software/MCWD20/Debug/main.obj       
     _GPIO_clear         C:/Works_Software/MCWD20/Debug/gpio.obj       
     _GPIO_open          C:/Works_Software/MCWD20/Debug/gpio.obj       
     _I2C_open           C:/Works_Software/MCWD20/Debug/i2c0.obj       
     _MCASP_enableClk    C:/Works_Software/MCWD20/Debug/mcasp1.obj     
     _MCASP_enableFsync  C:/Works_Software/MCWD20/Debug/mcasp1.obj     
     _MCASP_enableHclk   C:/Works_Software/MCWD20/Debug/mcasp1.obj     
     _MCASP_enableSers   C:/Works_Software/MCWD20/Debug/mcasp1.obj     
     _MCASP_enableSm     C:/Works_Software/MCWD20/Debug/mcasp1.obj     
     _MCASP_open         C:/Works_Software/MCWD20/Debug/mcasp1.obj     
     _MCASP_reset        C:/Works_Software/MCWD20/Debug/mcasp1.obj     
     _TIMER_open         C:/Works_Software/MCWD20/Debug/timer1.obj     
     __IRQ_eventTable    C:/Works_Software/MCWD20/Debug/main.obj       

    error: unresolved symbols remain
    error: errors encountered during linking;
       "C:/Works_Software/MCWD20/Debug/MCWD20_Debug.out" not built

    Is there any other libary I have to add? Or is there a file I have to add because I changed the bios version (additional to the *.tcf file)?

    Regards,

    Max

  • 0 in reply to Max Forster
    TI__Genius 12770 points

    Max,

    Were you able to resolve the symbol errors listed above?

    If so, could you provide the steps that were required to resolve the errors?

    This will be greatly beneficial to others that go through this migration process in the future.

  • 0 in reply to Austin Miller
    TI__Guru**** 451061 points

    Austin,

    Those errors look like it was caused because the CSL library was not linked in.

    ki

  • 0 in reply to Ki
    Intellectual 485 points

    Hi Austin,

    sorry for my late reply. Ki is right, you have to add the CSL libary direct. I added that issue in a new post (because it is a other topic then the initial one), please see here.

    Regards,

    Max