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 emulator to use

Other Parts Discussed in Thread: TM4C123GH6PZ

Hi,

I am new to TIVA C MCU. I am using TM4C123GH6PZ microcontroller.

1) Which emulator I use for TM4C123GH6PZ mcu. I have XDS100V2 emulator

2) How many pins I use for JTAG

3) As per datasheet it shown 10 pin but in software & tool on your website it shows 20 pin xds100v2

please reply me as soon as possible 

  • Hello Sumit,

    You can read this post with a long discussion about emulator options, and some experiences:
    e2e.ti.com/.../358729

    The XDS100V2 you have is just fine. Note that the Launchpad boards already come with an "embedded" emulator, called ICDI, in which case you don't need anything else to start.

    Look again, there are different versions of XDS100V2 on the TI store. For ARM, you want the small 10-pin connector, which happens to be .127 pitch in two rows of 5. If you already own a 20pin emulator, you can build an adapter cable (I have the part numbers written somewhere if needed).

    By the way, I took advantage of the ongoing promotion where TI is giving you a free full CCS licence compatible with the faster emulators when you buy this $295 XDS200 emulator. Might be interesting for you if you want to go to the next step.

    Happy developing!
  • Hello Sumit

    Another useful resource would be the following Application Note for interfacing JTAG with TM4C12x devices.

    www.ti.com/.../spma075.pdf
  • I have blackhawl xds100v2 ARM emulator. It has 10/20 pin JTAG Connector. I don't have launchpad of TivaC 123. Is this xds100v2 ARM is sufficient or not for TM4C123GH6PZ?
  • Yes it is sufficient.

    Make sure you design the proper JTAG communication into your TM4C123.

    Here is a picture of an XDS100v2 connected to a Tiva MCU on a custom board. This one has the smaller 1.27mm connector, but if are the board in which the Tiva is used is your design, you can choose whatever connector suits you.

  • Thank you very much Sir for your prompt reply.
  • Hello Sumit,

    Yes, it is. The Application Note also shows the schematic connection to be made for JTAG on custom board. Please make sure you follow the same.
  • Thanks a lot sir.
  • Greetings Amit,

    Might you comment upon the repeated use of, "Emulator?"

    Firm/my belief is that each/every item mentioned is a full-fledged JTAG "Pod" or "Probe" and, "ACTUAL JTAG QUALIFIED SIGNALS ARE BEING GENERATED!"   Little (i.e. NOTHING) is being emulated!

    Emulation was common in days long past - when very expensive, specialized MCUs (with vast I/O) sat on (rather) large development boards - and the MCU's inner workings were "emulated" via external RAM and other hardware implementations of the MCU's peripherals.   JTAG did not exist (surely not in its present form) at that time.   Emulation was ALL that we had!   (and were glad for it)   (Firm/I own such a 1980's board from Zilog - it is easily 12" x 12" in size - accommodates over 25 ICs - required to achieve "Emulation.")

    Success in this field demands (some) attention to detail.    Oft repeating an incorrect term/word usage does NOT make it correct!

  • Hello cb1

    Gladly. Emulation is still a term used for the prototyping platform, FPGA and large boxes which ran the source of the design at relatively low frequency. JTAG surprisingly has been there for a long time. The correct term is debug probe or debug pod for JTAG devices which allow debug of processor core.
  • Hello Amit,

    Good that and thanks.    

    Yet - while agreed that "Emulator" is NOT CORRECTLY BEING USED w/in this/(most ALL other) threads here - the "Promotion" of the correct terminology, "JTAG Debug Pod/Probe" remains (may I say) "LESS THAN NOTABLE!"  

    This forum is NOT, "prototype platform, FPGA nor large box" centric - thus "emulator" is inappropriate (almost always) when used here!

    As you (constantly) "rescue" users here - it is the accuracy of your analysis and direction - which best insures correctness.

    It appears that "team here" has surrendered to word misuse (Emulator) and the ACCEPTANCE of that incorrect usage (rather than protest against - and CORRECTION) proves "too hard" - which of course is most disappointing...