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

conversion of CCS V3.3 cdb file to CCV4 tcf

Robert Wolfe
Mastermind 7860 points

Hello,

 

I’m trying to convert my CCSV3.3 project, to work with CCSV4, and eventually CCSV5.  So I’ve followed instructions found on converting the .cdb to a .tcf.  But there are problems.  The following is the read out during the cdb2tcf conversion.  It appeared to go ok?

 

c:\Program Files (x86)\Texas Instruments\bios_5_41_10_36>.\packages\ti\bios\config\update\cdb2tcf work.cdb

Application: work.cdb

Original seed file: c:/program files (x86)/texas instruments/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:/program files (x86)/texas instruments/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:/program files (x86)/texas instruments/bios_5_41_10_36/packages/ti/bios/config/cdb/c6x1x.cdb

Applying changes

Saving original work.cdb in work.cdb.Thu_Sep_22_20.40.54_2011

Creating TCF file: c:/Program Files (x86)/Texas Instruments/bios_5_41_10_36/work

.tcf

Tconf search path information is required for running the generated tcf file.

The search path info for the Tconf.exe command line has been saved in

tcfopts.dat.

 

But when using that in the CCSV4 project, and double clicking on it, I get the following:

 

js: "C:/Program Files (x86)/Texas Instruments/bios_5_41_10_36/packages/ti/bios/config/bios_6713.tci", line 38: Can't modify read-only field

js: "C:/Program Files (x86)/Texas Instruments/bios_5_41_10_36/packages/ti/bios/config/bios_6713.tci", line 39: Can't modify read-only field

js: "C:/Program Files (x86)/Texas Instruments/xdctools_3_20_08_88/include/utils.tci", line 582: Error: Can't find import file: 'work.tci' (not found along '<my project directory>/.gconf/<my project directory>;;<my project directory>;C:/Program Files (x86)/Texas Instruments/bios_5_41_10_36/packages;C:/Program Files (x86)/Texas Instruments/xdctools_3_20_08_88/include;C:/Program Files (x86)/Texas Instruments/xdctools_3_20_08_88/packages')

Correct any script errors in <my project directory>/.gconf/<my project directory> /work.tcf using the Configuration Tool or a text editor, if necessary.

  

TConf initialization arguments: -e environment['config.importPath']='<my project directory>;C:/Program Files (x86)/Texas Instruments/bios_5_41_10_36/packages' -e environment['config.scriptName']='work.tcf'

 

Please advise,

Robert

  • 0
    TI__Mastermind 32475 points

    Robert,

    Can you attach your tcf file here along with all your *.tci files its including [Don't need to attach any bios_xxx.tci files].

    The first two issues are coming from some internal bios files while the third problem looks like a path issue.

    I think you should be able to fix the third issue by adding the path to work.tci to the XDCPATH.

    Judah

  • 0 in reply to judahvang
    Mastermind 7860 points

    Thanks for the reply Judah.   I tried to attach the tcf file, but couldn't (file type not allowed in E2E).  So I cut and paste the contents of the tcf file below.  It doesn't appear to to include any tci files?  And I have no work.tci file.

    Robert

    P.S.  This is for a DSK6713.

     

     
    /* loading the generic platform */
    var params = {};
    params.clockRate = 225;
    params.deviceName = "6713";
    params.catalogName = "ti.catalog.c6000";
    params.regs = {};
    params.regs.l2Mode = "SRAM";
    utils.loadPlatform("ti.platforms.generic", params);


    /* enabling DSP/BIOS components */
    bios.GBL.ENABLEINST = true;
    bios.MEM.NOMEMORYHEAPS = false;
    bios.RTDX.ENABLERTDX = true;
    bios.HST.HOSTLINKTYPE = "RTDX";
    bios.TSK.ENABLETSK = true;
    bios.GBL.ENABLEALLTRC = true;

    bios.GBL.ENDIANMODE = "little";

    bios.GBL.C621XCONFIGUREL2 = false;

    /* applying user changes */
    bios.SDRAM = bios.MEM.create("SDRAM");

    bios.SDRAM.base = 0x80000000;

    bios.SDRAM.len = 0x1000000;

    bios.SDRAM.createHeap = 0;

    bios.SDRAM.space = "code/data";

    bios.BOOT = bios.MEM.create("BOOT");

    bios.BOOT.len = 0x400;

    bios.BOOT.createHeap = 0;

    bios.swi_process_0 = bios.SWI.create("swi_process_0");

    bios.task_dsp = bios.TSK.create("task_dsp");

    bios.MEM.STACKSIZE = 0x600;

    bios.MEM.NOMEMORYHEAPS = 1;

    bios.GBL.CALLUSERINITFXN = 1;

    bios.GBL.CHIPTYPE = "6713";

    bios.GBL.BOARDNAME = "dsk6713";

    bios.IRAM.base = 0x400;

    bios.IRAM.len = 0x2fc00;

    bios.task_dsp.fxn = prog.extern("tsk_dsp");

    bios.task_dsp.stackMemSeg = prog.get("IRAM");

    bios.LNK_dataPump.order = 1;

    bios.RTA_dispatcher.order = 0x2;

    bios.IDL_cpuLoad.order = 0x3;

    bios.GBL.USERINITFXN = prog.extern("GBL_setPLLto225MHz");

    bios.PRD_clock.order = 1;

    bios.HWI_INT4.fxn = prog.extern("hwi_eint_4");

    bios.HWI_INT4.useDispatcher = 1;

    bios.HWI_INT5.fxn = prog.extern("hwi_eint_5");

    bios.HWI_INT5.useDispatcher = 1;

    bios.HWI_INT6.fxn = prog.extern("hwi_eint_6");

    bios.HWI_INT6.useDispatcher = 1;

    bios.HWI_INT7.fxn = prog.extern("hwi_eint_7");

    bios.HWI_INT7.useDispatcher = 1;

    bios.HWI_INT8.fxn = prog.extern("irq_sample");

    bios.HWI_INT8.useDispatcher = 1;

    bios.swi_process_0.fxn = prog.extern("swi_process");

    // !GRAPHICAL_CONFIG_TOOL_SCRIPT_INSERT_POINT!

    if (config.hasReportedError == false) {
    prog.gen();
    }

     

     

     

  • 0 in reply to Robert Wolfe
    Mastermind 7860 points

    Here is some additional information Judah.  work.cdb was a CDB file for my DSK6713.  I moved it to c:\Program Files (x86)\Texas Instruments\bios_5_41_10_36.  I then did a

             set BIOS_INSTALL_DIR="."

    and

            .\packages\ti\bios\config\update\cdb2tcf work.cdb

    The result  was the work.tcf file I listed, and which caused the problems listed in my first post.

    Robert

  • 0 in reply to Robert Wolfe
    TI__Mastermind 32475 points

    Robert,

    I took your post of your .tcf file.  Then went into CCSv4 and created a BIOS 5.x hello project for the padk6727 [This was the closest platform I could find to the dsk6713, although I don't think it really matters too much].  Then copy your .tcf file contents over whatever was generated.  The tcf file worked fine for me.  I can even double click in CCS and open it up in gconf.  So your .tcf file is not a problem on my end.

    Have you tried this within CCS?  It might have to do with installation directory or your tconf path aren't setup correctly.

    Judah

  • 0 in reply to judahvang
    Mastermind 7860 points

    Judah,

    Thanks for the reply, and trying my .tcf contents.  I did get things to work, using CCS V5.1.  It was a paths issue, and missing seed file.  You can see all the details here, if wished:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/136794/495340.aspx#495340

    Regards,

    Robert