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.

CCS/TMS320F28379D: GEL File Not Found When Trying to Debug

Part Number: TMS320F28379D

Tool/software: Code Composer Studio

Greetings,

    In preparing to checkin some new code, I have moved my development code into a different folder which contains our latest code.  The resulting code seems to work.  But when I click the debug button, I get the following errors.  Note that the folder in the first group does not exist, and the Target Configuration has been setup to use a folder, in the new code, which does contain the files.

 

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

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

 

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

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

 

What could I have done to cause this?

Thank you,

Ed

  • Hi Ed,

    Ed Sanders said:
    Note that the folder in the first group does not exist, and the Target Configuration has been setup to use a folder, in the new code, which does contain the files.

    Can you share the ccxml being used? Please attach the file to this thread.

    Thanks

    ki

  • TMS320F28379D.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <configurations XML_version="1.2" id="configurations_0">
    <configuration XML_version="1.2" id="Texas Instruments XDS2xx USB Debug Probe_0">
    <instance XML_version="1.2" desc="Texas Instruments XDS2xx USB Debug Probe_0" href="connections/TIXDS2XXUSB_Connection.xml" id="Texas Instruments XDS2xx USB Debug Probe_0" xml="TIXDS2XXUSB_Connection.xml" xmlpath="connections"/>
    <connection XML_version="1.2" id="Texas Instruments XDS2xx USB Debug Probe_0">
    <instance XML_version="1.2" href="drivers/tixds560icepick_c.xml" id="drivers" xml="tixds560icepick_c.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds560c28x.xml" id="drivers" xml="tixds560c28x.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds560cla1.xml" id="drivers" xml="tixds560cla1.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds560cs_child.xml" id="drivers" xml="tixds560cs_child.xml" xmlpath="drivers"/>
    <platform XML_version="1.2" id="platform_0">
    <instance XML_version="1.2" desc="TMS320F28379D_0" href="devices/f28379d.xml" id="TMS320F28379D_0" xml="f28379d.xml" xmlpath="devices"/>
    <device HW_revision="1" XML_version="1.2" description="" id="TMS320F28379D_0" 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" 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" id="C28xx_CPU1" isa="TMS320C28XX">
    <property Type="filepathfield" Value="..\..\..\..\..\GelFiles\f28379d_cpu1.gel" id="GEL File"/>
    </cpu>
    </subpath>
    </router>
    </device>
    </platform>
    </connection>
    </configuration>
    </configurations>
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    Hi Ki,

     It should be attached.  The site won't let me send a ccxml file so I changed the file's extension to 'txt'.

    I compared the two cases, when it works and when it doesn’t, and the ccxml files are identical.  Within the file, looking at the paths to the GEL files, and assuming that they start in the Debug folder of the CPU1 project, which is the project which had the focus when I clicked the debug button, then the relative paths to the two files are correct.

    Ed

  • Your ccxml file has a relative path to the GEL files like so:

    ..\..\..\..\..\GelFiles\f28379d_cpu1.gel

    If a relative path is provided to the startup GEL file, it will always be relative to: <CCS INSTALL DIR>\ccs\ccs_base\common\targetdb

    In my case, I have CCS installed in C:\ti. Hence '..\..\..\..\..\GelFiles\f28379d_cpu1.gel' would translate to 'C:\ti\GelFiles\f28379d_cpu1.gel' for me.

    Where are the GEL files you are trying to use?

  • Hi Ki,

    The files are on my C drive as well, but in our project folder structure. In this circumstance, both projects are on my C drive, but have different root folder names. The project in the folder with the older code does not have this issue. The project in the folder with the newer code, into which I’m merging, has the issue. Both are using the same relative path. The relative path was created when I was used the Target Configuration tool to Browse... to the folder in our project structure to select the file.

    Could it be that the <CCS INSTALL DIR> is used if it can’t find the file relative to the Debug folder?

    Thanks,

    Ed

     

     

  • Ed Sanders said:

    In this circumstance, both projects are on my C drive, but have different root folder names. The project in the folder with the older code does not have this issue. The project in the folder with the newer code, into which I’m merging, has the issue. Both are using the same relative path. The relative path was created when I was used the Target Configuration tool to Browse... to the folder in our project structure to select the file.

    Could it be that the <CCS INSTALL DIR> is used if it can’t find the file relative to the Debug folder?

    I think you are right. I was thinking of standalone ccxml files but ones that are part of a project could default to the project folder first, then "<CCS INSTALL DIR>\ccs\ccs_base\common\targetdb" second (if the folder name changed). I'll need to confirm this with the engineers. Note that it is a long weekend here so I won't be able to get back to you until Tuesday.

    Thanks

    ki

  • Hi Ki,

    I believe I have the answer.  The files in the .launches folder had a mixture of paths, old and new.  I deleted the folder, and now it is working fine.

    Ed