• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 460 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.

EK-TM4C1294XL: EK-TM4C1294

Gary Armstrong
Expert 1845 points
Part Number: EK-TM4C1294XL
Other Parts Discussed in Thread: CC3200

I need to make sure I understand programming a TIVA TM4C1294. I have inherited a design from an engineer that has left the company. We have the e2s project acting as a bridge from Ethernet to Serial but we have trouble talking to the chip on a custom board.  I can download to the EK-TM4C1294XL launchpad using the onboard ICDI (which I am assuming is a XDS100v2) and the e2s project works fine. I removed the jumpers from header X1 and the resistors along side of of X1 (R6-R16).

Question 1. Even though X1 header this looks temptingly like a14-pin JTAG, it definitely is not.

Question 2. The schematic says to remove R40 for "debug out" next to a small ARM 10-pin JTAG (J6) but I am curious as to what I could do with that? Section 2.3.2 on p.22 (SPMU365C) refers to the IAR and KIEL debugger but can I use this as a XDS100v2 on my custom board?

Question 3. 2.3.3 on p.22 (SPMU365C) refers to a Virtual Com Port. I can see this working when I download using the ICDI to the TM4C1294 on the launchpadd by using TeraTerm. I assume that an ordinary JTAG will not support the use of the Virtual Comm Port.

Question 4. Is there anything equivalent to SOP[2:0]  that I need to pay attention to for  aTM4CM1294?

  • 0
    TI__Guru 72500 points

    Gary Armstrong said:
    Question 1. Even though X1 header this looks temptingly like a14-pin JTAG, it definitely is not.

    Correct, it is not.

    Gary Armstrong said:
    Question 2. The schematic says to remove R40 for "debug out" next to a small ARM 10-pin JTAG (J6) but I am curious as to what I could do with that? Section 2.3.2 on p.22 (SPMU365C) refers to the IAR and KIEL debugger but can I use this as a XDS100v2 on my custom board?

    If what you are trying to do is use the EK-TM4C1294XL as a JTAG debugger to program and debug on your custom board, remove R40. That keeps the on-board TM4C129 device from driving TDO on X1. U6 is for using an external scan controller to program/debug the on-board TM4C129 device.

    Gary Armstrong said:
    Question 3. 2.3.3 on p.22 (SPMU365C) refers to a Virtual Com Port. I can see this working when I download using the ICDI to the TM4C1294 on the launchpadd by using TeraTerm. I assume that an ordinary JTAG will not support the use of the Virtual Comm Port.

    Correct.

    Gary Armstrong said:
    Question 4. Is there anything equivalent to SOP[2:0]  that I need to pay attention to for  aTM4CM1294?

    Sorry, I don't know what SOP[2:0] is.

  • 0 in reply to Bob Crosby
    Guru 92251 points

    Bob Crosby said:
    Sorry, I don't know what SOP[2:0] is.

    Bob, I think SOP[2:0] refers to the sense-on-power (SoP) pins on Wireless Connectivity devices such as the CC3200, which are sensed during power up to determine the boot flow. E.g. selecting two-pin SWD mode, four-pin JTAG mode or Factory/Lab Flash/SRAM load through UART.

    On Tiva devices there are no equivalent pins sampled during power-up, since the debug probe can send a sequence to switch between JTAG or SWD mode.