• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 82 subscribers
  • Views 669 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.

TMS320F28379D: GEL Files not Found

Ed Sanders
Genius 4105 points

Part Number: TMS320F28379D
Other Parts Discussed in Thread: C2000WARE,

Greetings,

I am using CCS 9.1.0.00010, and have a project in which the Target Configuration has been setup to use our normal GEL files which I have confirmed are in the correct folder. But when I try to debug the project, I get the error messages below. There are other messages, but I believe they have resulted because our GEL files are not seen by the launch. Is there something else which should be setup?

C28xx_CPU1: GEL: Error loading file 'C:\ti\ccs910\ccs\GelFiles\f28379d_cpu1.gel': unable to open GEL file 'C:\ti\ccs910\ccs\GelFiles\f28379d_cpu1.gel'
C28xx_CPU2: GEL: Error loading file 'C:\ti\ccs910\ccs\GelFiles\f28379d_cpu2.gel': unable to open GEL file 'C:\ti\ccs910\ccs\GelFiles\f28379d_cpu2.gel'

Thank you,

Ed

  • 0
    TI__Mastermind 32655 points

    Hi Ed,

    Are you using the ccxml file from the C2000ware? Looks like the gel file path mentioned in the ccxml file is incorrect. Please use the ccxml from C2000ware or create a new one from CCS or update the current ccxml to use the correct file.

    For updating the ccxml, go to Advanced tab, select the CPU core and update the initialization script.

    Regards,

    Veena

  • 0 in reply to Veena Kamath
    Genius 4105 points

    Hi Veena,

    I am using the same ccxml file which I had used in a different development less than a month ago.  And it uses the same relative path which we always use to get to our GEL files.  I’ve even tried to update the path, just to be certain it is correct, and it doesn’t change.  So there is nothing to save, and the save button is grayed out.  Is there a setting which I could have inadvertently changed which prevents that path from being used?

    Thank you,

    Ed

  • 0 in reply to Ed Sanders
    TI__Mastermind 32655 points

    Hi Ed,

    Can you check the device xml and confirm the gel path mentioned there is correct. You can find the xml file in <CCS>\ccs_base\common\targetdb\devices. The xml file name can be found in the ccxml source view

    Regards,

    Veena

  • 0 in reply to Veena Kamath
    Genius 4105 points

    Hi Veena,

    The project does not pull the GEL files from <CCS>\ ccs_base\common\targetdb\devices.  It pulls them from our code base.  But I checked the location you specified, and can see that it doesn’t have the information you are looking for.  So I checked the ccxml file in the project, and can see that the relative path is correct.  The file is small, so I’ve copied it below.

    Sorry for the messy look.  I can't find a way to attach it as a picture.  I've tried png and bmp formats.

    Regards,

    Ed

     

    <?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="Texas Instruments XDS100v3 USB Debug Probe" href="connections/TIXDS100v3_Dot7_Connection.xml" id="Texas Instruments XDS100v3 USB Debug Probe" xml="TIXDS100v3_Dot7_Connection.xml" xmlpath="connections"/>

            <connection XML_version="1.2" id="Texas Instruments XDS100v3 USB Debug Probe">

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

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

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

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

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

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

                    <device HW_revision="1" XML_version="1.2" description="" id="TMS320F28379D" partnum="TMS320F28379D" simulation="no">

                        <router HW_revision="1.0" XML_version="1.2" description="ICEPick_C router" id="IcePick_C_0" isa="ICEPICK_C">

                            <subpath id="Subpath_1">

                                <property Type="numericfield" Value="0x11" desc="Port Number_0" id="Port Number"/>

                            <cpu HW_revision="1.0" XML_version="1.2" description="C28xx CPU" deviceSim="false" id="C28xx_CPU2" isa="TMS320C28XX">

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

                                </cpu>

                            </subpath>

                        <subpath id="Subpath_0">

                                <cpu HW_revision="1.0" XML_version="1.2" description="C28xx CPU" deviceSim="false" id="C28xx_CPU1" isa="TMS320C28XX">

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

                                </cpu>

                            </subpath>

                        </router>

                    </device>

                </platform>

            </connection>

        </configuration>

    </configurations>

  • 0 in reply to Ed Sanders
    TI__Mastermind 32655 points

    Hi,

    Can you try adding the absolute path to the gel file? The relative paths might be using the CCS folder as the base. Eg: By default it uses the path ..\..\emulation\gel\f28388d_cpu1.gel which is related to the CCS internal folder.

    Regards,

    Veena

  • 0 in reply to Veena Kamath
    Genius 4105 points

    Hi Veena,

    As I was changing the ccxml to the full path, I realized that the reported issue had gone away yesterday.  I hadn't noticed it because I was ignoring all the lines with red due to the fact that everything else was working.  I don't know what changed to make that happen.  But changing the path made no difference in the subsequent failures which are still present.  I had originally attributed them to the inability to find the GEL file, but maybe that was incorrect.  At any rate, this is the other error I am seeing.  I am using the same GEL file which we use for all of our projects, and it sets up the memory map for the F28379D processor.  So I wasn't expecting this issue to exist once CCS was able to see the GEL files.  Since this is off the original topic, should I open a separate question for it?

    C28xx_CPU1: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x87c05: (Error -1066 @ 0x87C05) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.2.0.00004)

    C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

    Thank you,

    Ed

  • 0 in reply to Ed Sanders
    TI__Mastermind 32655 points

    HI Ed,

    Yes, please create a new thread for this, so that it will help other forum users with similar issue

    Regards,

    Veena

  • 0 in reply to Veena Kamath
    Genius 4105 points

    I cleared out everything from my workspace, and deleted all the build outputs.  After a new build and a launch, everything is now fine.  It's hard to fix a problem you can't duplicate :^(.

    Ed