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.

Which XDS100v2 to select for hobbyist work on TM4C?

Other Parts Discussed in Thread: MSP-FET, CC3200

There are three options for the XDS100v2, all which appear to support the Tiva TM4C lineup of MCUs:

How do I decide which to use? Would any selection here work? I am doing hobbyist 'in-the-garage' work with the TM4C, and just need something to program and debug with. Kind of like the MSP-FET :)!


Which one should I choose, and why?

  • Justin Reina89 said:
    Which one should I choose, and why?

    They have the same functionality, but differ in the pinout of the JTAG connector. See http://processors.wiki.ti.com/index.php/JTAG_Connectors#Pinout for the different JTAG connectors. Where the ARM XDS100v2 supports both the ARM 10-Pin and ARM 20-Pin JTAG connectors.

    Is there a specific development board you are going to use, or are you creating a custom design?

  • Hi,

     I will be generating my own board, a development board in EAGLE, using a personal reflow oven for assembly. This board will feature JTAG connection, a CC3200 with SPI to the TM4C, a small selection of actuators and an assortment of sensors.

    Misc. Question

     Why does each JTAG connection have different listed pin configurations, with such a large number of extras (see image below, e.g. EMU0, GNDDetect, TRACECLK, etc.)? I would think you just need the basics as described in SPMA056 - Table 9see attached (JTAG Interface.pdf)

    JTAG Interface.pdf

  • Justin Reina89 said:
     Why does each JTAG connection have different listed pin configurations, with such a large number of extras (see image below, e.g. EMU0, GNDDetect, TRACECLK, etc.)?

    The extra pins are for device and/or emulator specific functionality. 

    GNDDetect can be used by target system for debugger presence detection, as per the ARM documentation. GNDDetect would only be needed if your board needs to change it behavior if an external debugger is connected. E.g. if your board had an on-board debugger, which needed to be disabled when an external debugger was connected.

    EMU0 and EMU1 are pins which are used on some DSP devices, and are not applicable to Tiva devices. See What are the EMU0/1 pins used for?

    The trace pins are used to allow the Embedded Trace Macrocell (ETM) within the Tiva device to output instruction trace capture to an emulator. Only the high-end emulators such as the XDS560v2 PRO TRACE Receiver & Debug Probe support ETM, and so if you are using a XDS100v2 no need to connect the trace pins of the Tiva device.

    Justin Reina89 said:
    I would think you just need the basics as described in SPMA056 - Table 9see attached (JTAG Interface.pdf)

    Agreed. Although as I haven't designed a Tiva board maybe you should ask on the Tiva device forum for confirmation.

  • From what I have seen most people use the ARM Cortex 10pin header for these types of devices. If you use that header you will want to get the TMDSEMU100v2U-ARM. It is the only one of the XDS100s that has the correct adapter. The upcoming XDS110 will also include an adapter for this header.

    John
  • new thread in progress, thank you!!

    I will post the concluded answer and result from that thread here one complete :)

  • solution was generated from help by Amit (as always, he is spot on), thank you guys :)!!

    See below for solution