• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 175 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F28335: CCSv 6.2.0.00050: Breakpoint errors in the console and error showing up in the problems window while debugging

stevenh
Guru 20035 points
Part Number: TMS320F28335

Hello,

The project I am working with was originally created in CCSv6.   A while back I moved to CCSv9 and now I am want to go back to CCSv6 to work on GUI Composer.

I am using XDS100v2 debugger.

I am able to compile and debug a CCSv6 project, however, while debugging  "could not be resolved" errors show up in the problems window and and I get breakpoint errors in the console window (see below).

How can I correct this issue.

Stephen

C28xx: GEL: Error loading file 'C:\ti\ccsv6\f28335.gel': unable to open GEL file 'C:\ti\ccsv6\f28335.gel'
C28xx: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x326c76: (Error -1066 @ 0x326C76) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.0.27.9)
C28xx: Breakpoint Manager: Retrying with a AET breakpoint
C28xx: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x326c56: (Error -1066 @ 0x326C56) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.0.27.9)
C28xx: Breakpoint Manager: Retrying with a AET breakpoint
C28xx: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x326c76: (Error -1066 @ 0x326C76) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.0.27.9)
C28xx: Breakpoint Manager: Retrying with a AET breakpoint

  • 0
    TI__Genius 17499 points

    Hi,

    It looks like the path to your GEL file cannot be resolved. Can you ensure that you've correctly defined your target configuration file in your project. You can verify the path to the GEL file under the Advanced tab in the target configurations window. Look at the CPU properties window, under subpath_0.

    Regards,

    Ozino

  • 0 in reply to Ozino Odharo
    Guru 20035 points

    The GEL file was not the issue. I had already fixed the issue.  I just needed to create a new target configuration file.  I haven't had time to analyze why the previous target configuration file was causing the issue.

    I pasted the Target Config files below.

    Stephen

    Previous Target Config File:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    <?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 XDS100v2 USB Debug Probe_0">
    <instance XML_version="1.2" desc="Texas Instruments XDS100v2 USB Debug Probe_0" href="connections/TIXDS100v2_Connection.xml" id="Texas Instruments XDS100v2 USB Debug Probe_0" xml="TIXDS100v2_Connection.xml" xmlpath="connections"/>
    <connection XML_version="1.2" id="Texas Instruments XDS100v2 USB Debug Probe_0">
    <instance XML_version="1.2" href="drivers/tixds100v2c28x.xml" id="drivers" xml="tixds100v2c28x.xml" xmlpath="drivers"/>
    <property Type="choicelist" Value="2" id="The JTAG nTRST Boot-Mode"/>
    <property Type="choicelist" Value="2" id="The Power-On-Reset Boot-Mode"/>
    <platform XML_version="1.2" id="platform_0">
    <instance XML_version="1.2" desc="TMS320F28335_0" href="devices/f28335.xml" id="TMS320F28335_0" xml="f28335.xml" xmlpath="devices"/>
    <device HW_revision="1" XML_version="1.2" description="" id="TMS320F28335_0" partnum="TMS320F28335">
    <cpu HW_revision="1.0" XML_version="1.2" description="CPU" id="C2800" isa="TMS320C28XX">
    <property Type="filepathfield" Value="C:\ti\ccsv6\f28335.gel" id="GEL File"/>
    </cpu>
    </device>
    </platform>
    </connection>
    </configuration>
    </configurations>
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    New Target Config File:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    <?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 XDS100v2 USB Debug Probe_0">
    <instance XML_version="1.2" desc="Texas Instruments XDS100v2 USB Debug Probe_0" href="connections/TIXDS100v2_Connection.xml" id="Texas Instruments XDS100v2 USB Debug Probe_0" xml="TIXDS100v2_Connection.xml" xmlpath="connections"/>
    <connection XML_version="1.2" id="Texas Instruments XDS100v2 USB Debug Probe_0">
    <instance XML_version="1.2" href="drivers/tixds100v2c28x.xml" id="drivers" xml="tixds100v2c28x.xml" xmlpath="drivers"/>
    <platform XML_version="1.2" id="platform_0">
    <instance XML_version="1.2" desc="TMS320F28335_0" href="devices/f28335.xml" id="TMS320F28335_0" xml="f28335.xml" xmlpath="devices"/>
    </platform>
    </connection>
    </configuration>
    </configurations>
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to stevenh
    TI__Genius 17499 points

    Glad to hear you got it working. After comparing the two files. The one major difference is that the old target config file has a reference to that GEL file and some custom boot options. I'm not sure why they are generated in the old file but I'm sure these are the root cause.