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.

DSP/BIOS+RTSC+BIOS config tool

Hello,

 

I'd liked to compile the 'demo' application shipped with the DM648 BIOS/PSP using CCS4. I followed both this wiki:

http://processors.wiki.ti.com/index.php/Porting_DM648_DVSDK_demo_app_from_CCSv3.3_to_CCSv4

end this post:

http://e2e.ti.com/support/embedded/f/355/t/5285.aspx

 

I created an RTSC project and another one for the source code referencing the RTSC projetc. It all works fine, the application compiles and runs. However when I try opening the dm648_demo.tcf file in the configuration projects with the graphical configuartion tool I get an error : "The project of the selected file does not have DSP/BIOS support". I can edit the file using the text editor.

This is all nice, but since I am very new to all this and on a tite schedule I would really liked to use the graphical tool for now. Is there a way to get the config tool working and using BIOS and RTSC together, as I beleive is the case for CCS3?

 

Thank's in advance.

  • Peter,

    I think what is happening is that there are different types of projects in CCS.

    When you look at the project that contains dm648_demo.tcf in the project view does the little folder icon say "RTSC" across the top or just "C"?  If it says "C" you will get that error when you try to open the file in the graphical editor..  When a project is created if it wasn't created as a BIOS/RTSC project it won't associate the builds build and edit tools with that project.  I am very surprised that it builds as I don't believe the tcf file will be associated with the proper build tool either.

    If you do a rebuild and look at the console do you see something that looks like:

    'Building file: ../dm648_demo.tcf'

    'Invoking: TConf Script Compiler'

    Regards,

    John

     

  • John,

    Thank you for the replyYes, the icon shows RTSC. It is the configuration project containing the RTSC part. According to the guides quoted, I added the .tcf and the .cfg files. The "read inifile.tcf in adition to inifile.tcf" is selected under Build Options->C/C++ Bild->XDCTools->Advanced Options.

    The project was created as an RTSC configuration project. and no it does not do that during build, it does this:

    'Building target: configPkg/linker.cmd'
    'Invoking: XDCtools'
    "C:/Program Files/Texas Instruments/xdctools_3_15_02_62/xs" --xdcpath="C:/Program Files/Texas Instruments/bios_5_40_02_22/packages;C:/Program Files/Texas Instruments/xdais_6_23/packages;C:/Development/DSP/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/packages;C:/Development/DSP/dvsdk_1_11_00_00_DM648/ndk_1_92_00_22_eval/packages;C:/Development/DSP/dvsdk_1_11_00_00_DM648/biosutils_1_00_02/packages;C:/Development/DSP/dvsdk_1_11_00_00_DM648/examples/common/evmDM648;C:/Development/DSP/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/examples;C:/Development/DSP/dvsdk_1_11_00_00_DM648/codecs_1_10_evmDM648/packages-evaluation;C:/Development/DSP/dvsdk_1_11_00_00_DM648/edma3_lld_1_05_00/packages;C:/Development/DSP/dvsdk_1_11_00_00_DM648/framework_components_1_20_03/packages;C:/Development/DSP/dvsdk_1_11_00_00_DM648/pspdrivers_1_10_00/packages;" xdc.tools.configuro -o "configPkg" -t ti.targets.C64P -p ti.platforms.evmDM648 -r whole_program_debug -c "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000" --tcf -x ti.rtdx "../dm648_demo.cfg"

     

    --tcf is telling the XDSTools to incorporate the dm648_demo.tcf file as well. It seems to me that if RTSC is used then the traditional DSP/BIOS .tcf files cannot be created in a project. It is possible to add existing files and using the above switch include them in the .cfg file but they cannot be edited using Tconf graphical editor any more. I presume that once RTSC is specified the a .cfg file is to be used and the above described trick is just to make legacy projects compile. The .tcf files to be used in BIOS only project without RTSC. Ther seems to be clear distiction between BIOS only and RTSC projects even in the create project wizard.

    Is this correct?

     

    Regards,

    Peter

  • Peter,

    Ok so a mix of cfg and tcf in the same project.  CCS will think it is a pure RTSC project.

    The only way I can get it to open in the graphical editor from CCS is to right click on the file and specify "open with -> System Editor".  When you do that it will prompt you for a coupe of things, one is the path to the xdctools installation and the second is the import path (location on the main .tci file your config is referencing.  The problem with this method is that you have to enter that info each time you open the file.  

    I will check around to see if anyone knows a better way

    Regards,

    John

  • Peter,

    I have attached a zip with a script in it.  You will need to modify some variables in the script for it to match your project and installation.  But what this script will do is add a menu item to CCS and a new command in the scripting console that will open a tcf file in the graphical editor.

    Open the scripting console from the view menu

    use loadJSFile openTCF.js to load the file

    type openTCF to run the command or select it from "Scripts" on the main menu.

     

    Regards,

    John

     

    openTCF.zip
  • John,

     

    This worked, though I will have to have a new script for every tcf file. This is obviously a work round.

    Is this a bug or is this the way it should work? I tough the having cfg and tci together is sort of normal.

     

    Anyway thanks for your help. It enables me to progress and that is what is important right now.

     

    Best regards,

    Peter

  • Peter,

    Mixing tcf and cfg was originally something not supported at all so there are some rough edges to it.  I have filed a bug to support directly opening a tcf in the graphical editor from a RTSC (cfg) project.  Likely be a few months before it makes it into a build though as the 4.2.0 release candidate just went out.  The bug number is SDSCM00038019 and you can check the status of it using the link in my signature below.

    Regards,

    John