• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 1616 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.

CCS/DRA71XEVM: xds100v3 gdb agent for dra71x evm

user5067720
Prodigy 120 points
Part Number: DRA71XEVM

Tool/software: Code Composer Studio

Hi TI,

How to connect the dra71x evm to gdb agent console via xds100v3. Then I type the cmd ".\gdb_agent_console.exe testBoard.dat", but it did not work. log below:

.\gdb_agent_console.exe testBoard.dat
No CPUs that support GDB are defined in configuration file

Thanks.

  • 0
    TI__Guru**** 171044 points
    Hi,

    The error message indicates the testBoard.dat file is not properly configured. How did you create the testBoard.dat file?

    One resource that shows how to create this file is shown at the following short clip:
    https://youtu.be/e84eSq16XO4

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Prodigy 120 points

    7024.testBoard.datHi desouza,

    The testBoard.dat file was created by ccsv8 when test connection clicked. It copied from AppData\Local\Texas Instruments\CCS\ti\0\0\BrdDat\.

    When the gdb_agent_console running, it show error log: No CPUs that support GDB are defined in configuration file

  • 0 in reply to user5067720
    TI__Guru**** 171044 points
    Hi,

    Thank you for sending the .dat file. I see the same problem here but so far I am trying to see where the issue is located.

    I will get back to this thread.

    Regards,
    Rafael
  • 0 in reply to desouza
    Prodigy 120 points

    Hi desouza,

    The dra71x evm was succeed to debug via gdb agent console when ccsv6 used, but failed by ccsv8.

    There are some other problems occurred when gdb_agent_console of the ccsv6 used. When gdb connect to the gdb_agent_console by target remote command, some error logs shown in the gdb_agent_console as below:

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

    CPU Name Port
    -------- ----
    cortex_m4_ipu1_c0 :55001
    cortex_m4_ipu1_c1 :55002
    cortex_m4_ipu2_c0 :55003
    cortex_m4_ipu2_c1 :55004
    cortexa15_0 :55005

    Starting all cores
    CPU Name Status
    -------- ------
    cortexa15_0 Waiting for client
    cortex_m4_ipu2_c0 Waiting for client
    cortex_m4_ipu2_c1 Waiting for client
    cortex_m4_ipu1_c1 Waiting for client
    cortex_m4_ipu1_c0 Waiting for client
    cortexa15_0 Client connected...Connecting to Target
    Unknown device id: 0x75805400 (1d6,15,0,0)
    Unknown device id: 0x0 (0,0,0,0)
    cortexa15_0 - Processor type =UNKNOWN (Big endian)
    cortexa15_0 - Target device is connected
    Using ctools hardware breakpoint support.
    Target connected...Starting server
    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=0,count=4)=ffffffff
    (Error -1205 @ 0x0)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=fffffffc,count=4)=ffffffff
    (Error -1205 @ 0xFFFFFFFC)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=0,count=4)=ffffffff
    (Error -1205 @ 0x0)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=fffffffc,count=4)=ffffffff
    (Error -1205 @ 0xFFFFFFFC)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=0,count=2)=ffffffff
    (Error -1205 @ 0x0)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=fffffffe,count=2)=ffffffff
    (Error -1205 @ 0xFFFFFFFE)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=fffffffc,count=2)=ffffffff
    (Error -1205 @ 0xFFFFFFFC)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=0,count=2)=ffffffff
    (Error -1205 @ 0x0)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=fffffffe,count=2)=ffffffff
    (Error -1205 @ 0xFFFFFFFE)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=fffffffc,count=2)=ffffffff
    (Error -1205 @ 0xFFFFFFFC)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=0,count=4)=ffffffff
    (Error -1205 @ 0x0)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=fffffffc,count=4)=ffffffff
    (Error -1205 @ 0xFFFFFFFC)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=0,count=4)=ffffffff
    (Error -1205 @ 0x0)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=fffffffc,count=4)=ffffffff
    (Error -1205 @ 0xFFFFFFFC)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=0,count=4)=ffffffff
    (Error -1205 @ 0x0)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=0,count=4)=ffffffff
    (Error -1205 @ 0x0)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

    FAILED! GTI_READEMEM_BLK(hpid=03EEA6C8,addr=0,count=4)=ffffffff
    (Error -1205 @ 0x0)
    Device memory bus has an error and may be hung. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 6.0.407.3)

  • 0 in reply to user5067720
    TI__Guru**** 171044 points
    Hi,

    Thanks for sending the additional information; it seems this is a regression problem indeed.

    I was chatting with the dev team and they mentioned that work on OpenOCD support has been much more active in the past years, therefore the suggestion is to move to OpenOCD instead, especially since you are using a XDS100v3 Debug Probe which is fully supported by it.

    Is that a feasible move for you? If not, please let me know.

    Regarding the errors, there is a possibility the device itself is locked by other factors (running pre-loaded software such as Linux, for example) - an explanation for the error can be found at the following reference:
    software-dl.ti.com/.../ccsv7_debugging_jtag_connectivity_issues.html

    I apologize for the inconvenience,
    Rafael
  • 0 in reply to desouza
    TI__Guru**** 171044 points
    Hi,

    Did you have a chance to try OpenOCD? Is this a viable solution?

    Regards,
    Rafael
  • 0 in reply to desouza
    Prodigy 120 points

    Hi desouza,

    I try the openocd, but there is not any configure file(interface/target/board/cpu/chip) of dra71x/dra7x-evm board. Are there any tutorials for debuged dra71x via openocd?

    Thanks. 

  • 0 in reply to user5067720
    TI__Guru**** 171044 points
    Hi,

    Yes, you are correct. It seems that OpenOCD does not have a pre-existing configuration for this device.

    I will try to find such configuration and report back.

    At any rate, I filed the bug number DBGTRC-3927. In a few hours you can inspect its status in the link SDOWP in my signature below.

    In my investigation, I found out the configuration only fails to work with XDS100 and XDS110-class Debug Probes, thus leaving two possible workarounds:
    - Use the older release
    - Use a different debug probe

    I apologize for the inconvenience,
    Rafael