• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1304 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.

Original question:

CCS/TM4C1294NCPDT: XDS200 Debug probe and XDS200 Onboard Debug probe Difference

CCS/TMDSIDK437X: XDS GDB agent with XDS200 external debug probe

Clifford Geschke
Prodigy 160 points
Part Number: TMDSIDK437X


Tool/software: Code Composer Studio

I have a AM437x IDK Evaluation board interfaced via an external XDS200 probe connected to a Linux system via USB.  I can download to the board using CCS7 and everything is fine.

I am trying to use GDB as a debugger and have fired up the XDS GDB console agent as described in http://processors.wiki.ti.com/index.php/XDS_GDB_Agent  I can connect but I have discovered that it is using the built-in XDS200 on the development board.  That device downloads very slowly (1Kbyte/sec) and is unusable.  I proved that by disconnecting the USB cable plugged directly to the IDK board (leaving the external probe connected) and verified the CCS7 works fine but XDS GDB does not connect.

I followed the instructions for finding the "testBoard.dat" file to configure the XDS GDB agent.  Does anyone how to change the configuration so that the XDS GDB agent will use the external probe?

Thanks,

Cliff

  • 0
    TI__Guru**** 171309 points

    Cliff,

    I was able to connect to my AM437x IDK board (no software previously loaded to the board) using my XDS200 debug probe (the AM437x IDK has a XDS100v2 built in, which is quite slow).

    Instructions on how to create the testBoard.dat file are shown below.

    If you follow these instructions carefully, the file you get is quite similar to the one attached below. 

    Hope this helps,

    Rafael

    AM437x_XDS200.dat