program TM4C129x using EK-TM4C123GXL LaunchPad

Hi Kien,

Do you plan to do a custom board for TM4C129X?

Regards

Amit Ashara

Yes I intend to make a custom board for it, which I hope to be not too difficult.

My goal is for other students to use, so I intend to make it as low cost in 40-50 boards quantity. Thank you very much for the answer. 

Sorry, I'm not seeing an answer here, is it possible to program the TM4C129X with the EK-TM4C123GXL?

Hi Paul,

Above Amit Ashara specified:

Amit Ashara said:

it is not possible to get the JTAG from the EK-TM4C123GXL. You would need an external debugger like XDS100v2

Which means no, we can't. I had to buy the XDS100v2 for this purpose.

Hello Kien, Paul,

After some work we got the EK-TM4C123GXL to work as a debugger. I have attached a snapshot of the board configuration.

Regards

Amit

Hi Amit,

I just want to confirm this: so we can use the EK-TM4C123GXL configured as you mentioned above (move the switch to debug, remove the header, and jump out the debugging wires) to debug the TM4C129x chips?

Sincerely,

Kien Dang.

Hello Kien,

Yes, that is correct. The image shown was from the actual debug of a TM4C129.

Regards

Amit

We need to connect all vcc, ground, reset circuit and oscillator to get another tiva controller get programmed? Do we need any other external circuit for programming?

Hi,

For all interested, if you have enough resources, you can build your own XDS100 interface, the full documentation is on this page:

http://processors.wiki.ti.com/index.php/XDS100#XDS100v1

Petrei

 This is feasible but for a few more US$ you can get tiva connected launchpad EK-TM4c1294XL that has full JTAG internal/external socket available. Are the internal usable as for board debug like the one on DK board? Is the external connector one way or two way again like DK? I am missing micro cable from old stellaris ICDI to do direct test.

 Finally I grasped how it work...

 From page 18 of http://www.ti.com/lit/pdf/spmu365 user manual:

Debug out of the ICDI is possible by removing resistors R6, R7, R8, R10, R11, R15, R16 and R40 from
the Connected LaunchPad and use the ICDI to drive JTAG signals out on U6 for the purpose of
programming or debugging other boards. To restore the connection to the on-board TM4C1294NCPDTI
microcontroller, install jumpers from the odd to even pins of X1 or re-install the resistors. Removal of R40
disables the detection of an attached external debugger. R40 must be installed to use an external debug
adapter to program or debug the Connected LaunchPad.

 From page 32 on schematic U6 is the external JTAG connector and is just in parallel to JTAG TM4C129xxx connection, inserting an external debugger sense pin 3 <external debug> and disable driving JTAG from ICDI, so removing R40 and all resistor internal uC is disconnected and no external sense is detected so ICDI drive external U6 and internal X1 ICDI side. Clever!!!

 Also Connected launchpad behave as programmer like the DK board, difference is some rework are needed to do job.

 On right the external connector usable as program or programmer interface.

 to left R40 external jtag sensing, remove to act as internal on these pin or leave pin 3 uf U6 unconnected.

 X1 side X marked on green is in parallel to JTAG U6 connector

separation resistors marked S are in parallel to even/odd pin of X1, when removed inserting a .1 inch strip on x1 can be populated by jumper to do same job of resisor or removed to use as external programmer.

 Test point TP16 and TP17 marked G are ground pin, connect FIRST!

 (edited error and added some word)

Use of, "launch" for such application seems much like, "pushing a boulder up a mountain!"

Launch appears so much more market-hype than reality.  (launch per Webster implies, "speed/ease/simple!"

Kudos to Petrei for a superior approach - which escapes marketing, "over-reach..."

@Roberto - love ya man (you know) - but my God man - eyes crossed (even more than normal) just glancing at your diagram.  BTW - which added wire goes to the (sub's) nuclear reactor?

cb1_mobile said:

@Roberto - love ya man (you know) - but my God man - eyes crossed (even more than normal) just glancing at your diagram.  BTW - which added wire goes to the (sub's) nuclear reactor?

 Naaaa...

 I am using launchpad to test software and anyway I wish to test on my board so it can be better to use on both way same programmer, XDS100 or ICDI, XDS100 appear slower than ICDI and may be I buy the expensive XDS560 or similar when all thing are working...

 So you are thinking why I checked what sub reactor?

 ICDI chip on all board appear to be the same, I need debug multiprocessor with isolated ground to avoid noise and burn pc too.. So malsane ideais:

 All pin are TP accessible and some signal appear promising like DEBUG active, when I go to lab I connect logic analyzer and if it work I can use an ISO chip to have a low cost isolated JTAG adapter. To debug high voltage maybe I need more than two and XDS560 are not so cheap to buy as nuts and bolt.

Hello Amit,

Please help me, I'm having trouble transfering code from Tiva C launchpad to my tm4c123g board . I connected wire as same as your picture, also removed the jumper below power led of launchpad, switching "Debug". I use  "LM Flash Programmer" and CCS, but it not working. :( 

-------------------------------------------------------

(launchpad) TCK ------> PC0 (tm4c123g) (my tm4c123g board)

(launchpad) TMS ------> PC1 (tm4c123g)

(launchpad) TDI -------> PC2 (tm4c123g)

(launchpad) TDO ------> PC3 (tm4c123g)

(launchpad) EXT -------> GND

(launchpad) GND ------> GND (tm4c123g)

---------------------------------------------------------

My tm4c123g  board:

3.3V ----> VDD, VDDA

GND ----> GND, GNDA

Thank you. :)