CCS/TMS320C6678: CCS 7.1 no longer support relative path for GEL file in Target Configuration?

Part Number: TMS320C6678

Tool/software: Code Composer Studio

I found that in CCS 7.1 I cannot write a path that is relative to the .ccxml file itself for a GEL file in the Target Configration -> initialization script. From now on, the path seems always relative to ccsv7/ccs_base/common/targetdb.

I have my own GEL files and some target configuration files, and I also want to make them portable among different PCs which installed CCS and projects in various places.

Is there possibility that TI re-add this feature again in next release or patch version?

15 Replies

  • Genius 13390 points
    Could you clarify how you are writing the path in your GEL file? Are you using the $(GEL_file_dir) macro?
  • In reply to AndyW:

    Hi AndyW,

    I didn't use the $(GEL_file_dir) macro and how I used the relative path is described below:

    • The folder/file tree is like this:

    - gel

         |- c6678.gel

    - tgtconf

        |- xds2xx.ccxml

    • In the earlier release of CCS, like 7.0 or 6.x, I can type the relative path "../gel/c6678.gel" in the initialization script field of the target configuration file, and it works.
    • In the release of CSS 7.1, I can on longer do this and CCS will notify me it cannot load the  GEL file from the path "ccsv7/ccs_base/common/gel/c6678.gel".

    So the old method is not usable any more, but is there any new way for replacement?

  • canfoderiskii
    I found that in CCS 7.1 I cannot write a path that is relative to the .ccxml file itself for a GEL file in the Target Configration -> initialization script. From now on, the path seems always relative to ccsv7/ccs_base/common/targetdb.

    With CCS 7.1.0.00014 under Windows 7 I can't repeat this problem.

    I had a project originally developed with CCS 6 in which the custom GEL files for a AM3352 target are in a path relative to the .ccxml file. CCS 7.1 is still letting me enter "..\..\gel_files\AM3352_SOM_ethernet.gel" as the initialization script and the GEL files are found OK:

    In case it matters, in my example for the Cortex_A8 above all the GEL files are in the same directory within the workspace.

  • In reply to Chester Gillon:

    Hello canfoderiskii,

     

    Can you tell us if the CCXML file and the relative GEL are inside your project?

    If so, is it possible to send us a small project that demonstrate the issued?

    Can you specific the OS version you are running CCS on ( Win, Linux, Mac)?

    What is your exact CCS Version from the “Help/About box”?

     

    I was trying to reproduce your problem but everything worked for me in CCS 7.1 as expected. Here is want I did:

    I created a small MSP430 project and the CCXML file was automatically added in my project in the “targetConfigs” folder.

    I added a simple GEL file inside a folder of my project “gelFolder/myGel2.gel”

    myGel2.gel has a “StartUp()” function in it.

    I modified my CCXML file to reference the GEL file: In the advance tab of the CCXML editor, which I select the core I have setup initialization script “..\gelFolder\myGel2.gel”.

    When I stat a debug session I see that my Gel’s startup function is executed.

     

    Please let me know how your use case differs from mine.

    Thanks

    Dobrin

     

  • In reply to Dobrin Alexiev:

    Hi, Dobrin:

    Here describes my environment:

    • OS: Win7 x64
    • CCS: 7.1.0.000014
    • The folder/file tree:

    - gel

         |- c6678.gel

    - tgtconf

        |- xds2xx.ccxml

    - proj

       |- name_of_the_ccs_proj

    As u can see, in my situation, the CCS project does not contain any Target Configuration file.

    How did I use the Target Configuration file:

    • opened Target Configuration view
    • import the .ccxml file as link file
    • start Debug Session directly from that file which is not connected with any project, in this way I can load any program file I want.

    After starting the Debug Session, the CCS notifies me that it can't find the gel file. 

    I can repeat those steps without any problem in CCS 6.x or CCS 7.0.

  • In reply to canfoderiskii:

    Hello canfoderiskii,

     

    Can you attach to this forum post your CCXML and GEL Files?

     

    I tried reproducing the program as close as you described it, but I still cannot reproduce it.

     

    I installed the latest available CCS 7.1.0.0015.

    I had on my disk the following structure:

     

    F:\temp\bugs\form-1\tgtconf\MSP430FR6989.ccxml

    F:\temp\bugs\form-1\gel\myGel.gel

     

    In my Target Configurations views I imported the CCXML file as “Link to file”.

    I have no projects at all.

    I stared a debug session by selecting the CCXML file and did a context menu “Launch Selected Configuration”.

    A debug session started the GEL executed perfectly.

     

    Here is my GEL Files:

     

    StartUp()

    {

              GEL_TextOut("ABC");

    }

     

    Here is my CCXML file.

     

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>

    <configurations XML_version="1.2" id="configurations_0">

        <configuration XML_version="1.2" id="configuration_0">

            <instance XML_version="1.2" desc="TI MSP430 USB1" href="connections/TIMSP430-USB.xml" id="TI MSP430 USB1" xml="TIMSP430-USB.xml" xmlpath="connections"/>

            <connection XML_version="1.2" id="TI MSP430 USB1">

                <instance XML_version="1.2" href="drivers/msp430_emu.xml" id="drivers" xml="msp430_emu.xml" xmlpath="drivers"/>

                <platform XML_version="1.2" id="platform_0">

                    <instance XML_version="1.2" desc="MSP430FR6989" href="devices/MSP430FR6989.xml" id="MSP430FR6989" xml="MSP430FR6989.xml" xmlpath="devices"/>

                <device HW_revision="1.0" XML_version="1.2" description="MSP430FR6989" id="MSP430FR6989" partnum="MSP430FR6989" simulation="no">

                        <cpu HW_revision="1.0" XML_version="1.2" description="MSP430 CPU" deviceSim="false" id="MSP430" isa="MSP430FR59xx">

                            <property Type="filepathfield" Value="..\gel\myGel.gel" id="GEL File"/>

                        </cpu>

                    </device>

                </platform>

            </connection>

        </configuration>

    </configurations>

     

     

    Regards

    Dobrin

     

  • In reply to Dobrin Alexiev:

    c6678.zip

    The CCXML and GEL files are uploaded here.

    Maybe I can upload the CCS from 7.1.0.00014 to 7.1.0.00015, and try again.

  • In reply to canfoderiskii:

    Thank you. 

    I wound't move from v *.14 to  *.15 just for this. Since I was not able to reproduce it with *.03 or *.15 I don't think it will make any difference for this issue.

    Dobrin

  • In reply to Dobrin Alexiev:

    Hello,
    I noticed that the first core - C66xx_0 is does not have value for the "GEL File" while all other cores have it.
    Is that intentional?

    <cpu HW_revision="1.0" XML_version="1.2" description="C66xx CPU" deviceSim="false" id="C66xx_0" isa="TMS320c66xx">
    <property Type="filepathfield" Value="" id="GEL File"/>
    </cpu>

    <cpu HW_revision="1.0" XML_version="1.2" description="C66xx CPU" deviceSim="false" id="C66xx_1" isa="TMS320c66xx">
    <property Type="filepathfield" Value="..\gel\evmc6678l.gel" id="GEL File"/>
    </cpu>
  • In reply to canfoderiskii:

    Hello,

    I tried to reproduce this. I am using a nearly similar environment. The only difference is I am using the slightly newer build 15.

    canfoderiskii
    • opened Target Configuration view
    • import the .ccxml file as link file
    • start Debug Session directly from that file which is not connected with any project, in this way I can load any program file I want.

    I followed these steps and it seemed to work ok. My environment looked like the below:

    When you hover over the gel file in the GEL Files view, what absolute path is given?

    thanks

    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal