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.

TMDSEMU100v2U-ARM JTAG connection to tm4c123gh6pm

Other Parts Discussed in Thread: TM4C123GH6PM, CC2640

I am designing a circuit in which I am going to connect ARM 20 Pin JTAG to tm4c123gh6pm using following pins.

As per explained on page processors.wiki.ti.com/.../XDS_Target_Connection_Guide

JTAG connector ARM 20-Pin5
Pin number
1 VTRef
2 VSupply
3 nTRST
4 GND
5 TDI
6 GND
7 SWDIO / TMS
8 GND
9 SWDCLK / TCK
10 GND
11 RTCK
12 GND
13 SWO / TDO
14 GND
15 nRESET
16 GND
17 NC / DBGRQ
18 GND
19 NC / DBGACK
20 GND

These connections will be connected to four standard pins: TCK (52), TMS (51), TDI (50), and TDO (49)

Is this connection correct for TMDSEMU100v2U-ARM 20 pin JTAG to Tiva C series MicroController. ?

Much more confusion on page XDS_Target_Connection_Guide

  • Don't get confused.

    There are two types of JTAG pinouts, one is defined by TI and the other is defined by ARM company. TI has defined 14-pin (TI-14) and 20-pin (cTI-20) versions while ARM has defined 10-pin (ARM-10) and 20-pin (ARM-20) versions. Yes, the two 20-pin versions are different.

    Since you are using TI devices, why do you choose a debugger (TMDSEMU100v2U-ARM) for ARM version? Why not use TI-14 or cTI-20?

    Due to historical reasons, TI also defined EMU0, EMU1... for TI-14 and EMU2, EMU3... for cTI-20. These pins are usually useful sometimes. For example, I usually connect target.UART.TX/RX to EMU2/3 as the UART back channel. If SWO is available (such as CC2640) then SWO is connected to EMU3. So, in my PCBs, I can always output log information through the back UART channel of debugger. EMU0 and EMU1 is important for ARM9, A8... So, please leave them alone. Don't use them for other purposes.

    And yes, I always use cTI-20 since EMU3 is required for me to log messages.

    In addition to TCK, TMS, TDI and TDO, as I know TDIS (pin-4) and TVD (pin-5) are also required for the XDS100 driver. Without TVD, it will show you an error "Power lost". Without TDIS, it will show you error "Cable break".

    In summary, I would recommend you to use debugger with cTI-20 directly. Don't use TI-14 with cTI-20 adaptor, otherwise you won't have EMU3 to log message. You may not use "log" function right now. But you will find it is a useful tool in the future. If you need smaller footprint, design your own adaptor to connect cTI-20.
  • Thank you for instant reply.

    1.  Since you are using TI devices, why do you choose a debugger (TMDSEMU100v2U-ARM) for ARM version? Why not use TI-14 or cTI-20?

    I got little bit confused on selection of programmer and found on this link and ordered TMDSEMU100V2U-ARM.

    Order has been placed two months, It will reach to me in next 2/3 days.

    So now I cant change, Lets assume that there is no way for me.

    2. As I have understood from you that cTI-20 is best recommendation for TI ARM same which you are using.

    Can you help to confirm that below connection TMDSEMU100v2U-ARM will work, any suggestion will be helpful.

    TM4C123GH6PM CPU Pin JTAG connector ARM 20-Pin
    3.3V 1 VTRef
    3.3V 2 VSupply
    pull down resistor 3k3 3 nTRST
    GND 4 GND
    TDI 50 5 TDI
    GND 6 GND
    TMS 51 7 SWDIO / TMS
    GND 8 GND
    TCK 52 9 SWDCLK / TCK
    GND 10 GND
    NC 11 RTCK
    GND 12 GND
    TDO 49 13 SWO / TDO
    GND 14 GND
    NC 15 nRESET
    GND 16 GND
    NC 17 NC / DBGRQ
    GND 18 GND
    NC 19 NC / DBGACK
    GND 20 GND
  • The connection should work.
    Two months? Oh, sounds not reasonable.
  • Thank you for your response.