• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 562 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/TMS320F28379D: Questions about onborad debugging system

user78960159
Prodigy 120 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: LAUNCHXL-F28379D

Tool/software: Code Composer Studio

Hi，all

Recently I've been learning something about onboard debugging systems.

I learned that EEPEOM requires configuration. To burn EEPEOM, FT_PROG, the burning tool of FTDI, is required.

Using this tool, I first read the onboard EEPEOM content of the 28069M LaunchpadXL:

When I compared the reads, it seemed that only a few words, VID, PID, and bcdDevice could be associated with the description of the document.

Then, I read the on-board EEPEOM content of 28379D Launchpadxl and compared it with the on-board EEPROM content of 28069 Launchpadxl, as shown below:

As you can see, there are some differences between the two results. The "XDS100Ver2.0" emulator model can be seen from the contents at the back of the memory.

Question 1. FT_PROG can be used to read the contents of TI LaunchpadXL on-board EEPROM. Can the same function be achieved by burning the contents read to the on-board debugging system designed by oneself?

Question 2. With FT_PROG, burning contents of EEPROM can be configured. Can TI provide guidance documents?

Question 3. I don't know how the content in EEPEOM corresponds to the simulation type number selected by TargetConfiguration when burning in CCS development environment. From my personal understanding, in FT2232H, multi-protocol Synchronous Serial Engine (MPSSE) supports JTAG, and CCS software is installed with its own emulator driver. From EEPEOM, you can see the model number of XDS100Ver2.0 emulator. Is the so-called configuration in the onboard system telling CCS software that the current simulation number used by LaunchpadXL is XDS100Ver2.0, so as to establish an association, if the TargetConfiguration selected is not XDS100Ver2.0, an error will be reported.

Question 4. The onboard debugging system is the JTAG implemented by FT2232H multi-protocol Synchronous Serial Engine (MPSSE). Isit can be considered as a general JTAG debugging interface design, not exclusive to XDS100 or TI company. Are the faster XDS200 emulators, or other types such as 560 and 510, made with FPGA?

Question 5. Whether 28069 or 28379, can TI give a detailed explanation of the contents in EEPROM?

  • 0
    TI__Guru* 80510 points

    Thanks for reaching out to the E2E Forum; Answers below:

    Question 1. FT_PROG can be used to read the contents of TI LaunchpadXL on-board EEPROM. Can the same function be achieved by burning the contents read to the on-board debugging system designed by oneself?

    A1)This binary is specific to the FTDI2232 device on the launchpad.  Certainly if you had another FTDI2232 you could do what you are asking, but for any other CLPD from another vendor I can't say that this would work.

    Question 2. With FT_PROG, burning contents of EEPROM can be configured. Can TI provide guidance documents?

    A2)I need to do more research here, but I beleive that all TI provides is the binary to program the FTDI as both a JTAG interface(1st channel) and UART comms with the host(2nd channel).  I would assume that FTDI has published documents on their website on how to program the chip to do different things.

    Question 3 I don't know how the content in EEPROM.....

    A3)I'm not exactly sure of the question here, but the contents of the EEPROM configure the primary channel on the LAUNCHXL-F28379D as an XDS100V2, and your corresponding .ccxml file would also need to pick this emulator for compatibility.

    Question 4. The onboard debugging system is the JTAG implemented by FT2232H multi-protocol Synchronous Serial Engine (MPSSE). Isit can be considered as a general JTAG debugging interface design, not exclusive to XDS100 or TI company. Are the faster XDS200 emulators, or other types such as 560 and 510, made with FPGA?

    A4)This "XDS100vx" type debugger is designed to support TI devices with a JTAG interface, at a low cost implmenetation.  As you mentioned there are more expensive emulators, like XDS200, or XDS560 that are supported by 3rd parties and the 3rd parties own the IP that goes into them.  As far as I know this source is not shared by TI nor the vendor.  I do not have knowledge on what IC these other emulators use.

    Question 5. Whether 28069 or 28379, can TI give a detailed explanation of the contents in EEPROM?

    A5)I will check to see if we have any guidance; but again I beleive the intent was to have a distributable binary to behave in the manner I mentioned before.  At least on the exteral web I don't see any "how to" from TI in this regard.  I believe this would need to come from the vendor, in this case FTDI.

    Best,

    Matthew

  • 0 in reply to MatthewPate
    TI__Guru* 80510 points

    After speaking with some collegues, I think what you want is actually the XDS driver, which is here: http://processors.wiki.ti.com/index.php/XDS_Emulation_Software_Package

    The FTDI is just acting as a bridge from USB to serial, and its config is quite simple in that regard.

    Best,

    Mathre