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.

TMS320F28069F JTAG programming via Launchpad

Other Parts Discussed in Thread: TMS320F28069F, TMS320F28027F

Hello,

I'm planning to develop a design using the TMS320F28069F processor and I'm looking at how I should go about debugging and programming it with JTAG.

As this will just be a prototype, I'd like to use the hardware that I have on hand already for JTAG - a TMS320F28027F Launchpad and a MSP-EXP432P401R Launchpad. The former has an XDS100v2 programmer attached, but with no pins for debug out use broken out. The latter has the new XDS110-ET onboard, with only the following pins broken out on J103 (The MSP432 board I have is a revision 1.0 board with black silkscreen and white soldermask, different to what appears available for purchase today with red soldermask and later revision):


I'd like to be able to use the onboard XDS110 to program and debug my target board from within CCS. From what I can tell, I only have access to the TMS and TCK JTAG lines. The XDS110 allegedly supports JTAG 1149.7 two-wire interface with just these pins, but I am unsure if the target chip supports this - the datasheet only mentions 1149.1 implementation.

My questions are:

Is there a way to use either of the mentioned Launchpad boards to connect via JTAG to my target board?
Does the TMS320F28069F support JTAG 1149.7 two-wire mode? (if yes, I can use the EXP432P401R Launchpad for JTAG)
Does the latest revision of the EXP432P401R have the necessary pins broken out to do what I'd like (and if so, am I guaranteed to get a new revision board if I order one from TI)?
Is there a way to break out the JTAG pins from the XDS100v2 programmer on the F28027 Launchpad?
What connector footprint should I be placing on my custom board for JTAG use (I assume TI compact 20 pin) and are there any wiring references available?



  • Hi Lucas,

    XDS110 does not support C2000 controllers. Secondly, you can break the JTAG pins on F28027, I've done the same but is very susceptible to noise.
    The actual XDS100v2 is what I would personally suggest.

    Regards,
    Gautam
  • Thanks for the answer.

    I'll try and break out the pins from the TMS Launchpad I have, hopefully that will work.

    I was able to find some information from a TI employee that does state that the XDS110 is compatible with the c2000 range (Target configuration in CCS also seems to allow this option too).
    e2e.ti.com/.../1859563

  • Lucas Berezy51 said:
    I was able to find some information from a TI employee that does state that the XDS110 is compatible with the c2000 range (Target configuration in CCS also seems to allow this option too).

    Check this wiki:

    This does not mention support for C2000 family.

  • Thank you again for the reply.
    The wiki also doesn't mention explicit support for any processor, nor does it have a list of unsupported devices so I'm still unsure.

    I've found another resource that appears to imply that it is compatible (with all TI ISAs excluding MSP430).
    www.ti.com/.../debug.page

    It'd be nice to get a TI employee in here to answer this definitively. I've seen postings that a stand-alone design is planned for the end of this (2016) year, and that it would be intended to be open-source (potentially aiming to replace the XDS100 series). The naming convention certainly seems to fit.
  • Hi Lucas,

    xds110 emulator with C2000:  Yes, this is possible. However, the interface to the C2000 may not be exactly the same as one to the MSP432.

    Using the xds110 emulator on the MSP432 launchPAD with a C2000: I am not sure about this.  A 10pin-ARM JTAG interface does not contain a TRSTn signal, which is necessary for C2000 devices.  Note that the 10-pin ARM connector has a nRESET signal, but I do not believe it is equivalent to TRSTn.

    Using the xds100v2 emulator on the launchPAD with your own board.  If you sacrificed the board (ie removed the isolators and added blue wires), you should be able to make this work. 

    The F28069 does not support either of the 2-wire JTAG interfaces.

    I'd place a 14pin-TI JTAG header on your board.

    Unfortunately, my best recommendation may be to invest in a new external xds100v2 emulator.  Perhaps one like the below:
    http://www.ti.com/tool/TMDSEMU100V2U-14T

    ===

    The following wiki article is a good reference (if you have not found it already):
    http://processors.wiki.ti.com/index.php/XDS_Target_Connection_Guide


    Thank you,
    Brett

  • Lucas,

    In short:  It is possible to debug the F28069 with an XDS110, but probably not with the hardware you have.

    Additional comments and explanation:

    CCS today already allows you to select a C28x family device with the XDS110.  This was not intentional, but we only discovered it recently when we were preparing to add support for the new standalone XDS110.  However, the existing support does not extend to the CLA core, so you may not be able to use the F28069 device in the configuration but rather need to build the configuration by selecting the probe and adding a C28x CPU.

    Using the XDS110 on an MSP432 LaunchPad does require that the target have 3.3V JTAG I/Os.  The XDS110 on the LaunchPad does not have any voltage level translation.  The F28035 I have here using the docking station is 3.3V, so this may not be a concern.

    Rev. 1.0 of the MSP432 LaunchPad does not bring out TDI and TDO to a header or test points.  The F28069 requires 4-pin JTAG (1149.1), so you need access to TDI and TDO.  You don't have a ready way to get to those pins on the LaunchPad, so this probably blocks trying to debug the F28069 with your LaunchPad's XDS110.

    Rev. 1.9 of the MSP432 LaunchPad does have an ARM 10-pin connector to use the XDS110 to debug an external target.  I have tested this with my F28035 (which is another in the Piccolo family) using the XDS110 on the LaunchPad. I was able to connect and debug the C28x CPU with no issue. This was via a connector stack to go from the ARM 10-pin to the TI 14-pin on the F28035's docking station.

    RESET or nSRST on the ARM 10-pin connector is a board level system reset and not the nTRST debug reset.  If enabled for a particular device, CCS calls this reset "Board Reset."  (The name "System Reset" in CCS is a device level reset usually controlled by the ICEPick router in the device.)

    nTRST is not required to debug C28x devices.  The scan manager layer of the XDS software stack will reset the JTAG state machine by pulling nTRST and then also running the JTAG state machine back to Test-Logic-Reset.  In the absence of an nTRST pin, running the state machine to TLR is generally sufficient to reset the device's debug logic.

    And to the original questions:

    Is there a way to use either of the mentioned Launchpad boards to connect via JTAG to my target board?

    Not without soldering wires and cutting traces.

    Does the TMS320F28069F support JTAG 1149.7 two-wire mode? (if yes, I can use the EXP432P401R Launchpad for JTAG)

    No, the F28069 only supports 1149.1 4-pin JTAG.

    Does the latest revision of the EXP432P401R have the necessary pins broken out to do what I'd like (and if so, am I guaranteed to get a new revision board if I order one from TI)?

    Yes, the latest revision includes an ARM 10-pin header for debugging an external target.  Just be aware that the target needs 3.3V logic.  And no, I don't know that you'd be guaranteed to get that version.

    Is there a way to break out the JTAG pins from the XDS100v2 programmer on the F28027 Launchpad?

    Not without cutting traces and soldering wires, I'm afraid.

    What connector footprint should I be placing on my custom board for JTAG use (I assume TI compact 20 pin) and are there any wiring references available?

    http://processors.wiki.ti.com/index.php/JTAG_Connectors

    Most TI debug probes today come ready for a TI 20-pin header.