• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 1305 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.

CCS/TMS570LS3137: CCS/TMS570LS3137

jimj2713
Expert 2375 points
Part Number: TMS570LS3137
Other Parts Discussed in Thread: TMDS570LS31HDK, , LAUNCHXL2-570LC43, LAUNCHXL2-TMS57012, LAUNCHXL2-RM57L, LAUNCHXL2-RM46

Tool/software: Code Composer Studio

Can the XDS510-USB be used to JTAG-debug the TMS570LS3137? The XDS510 documentation states that it supports this family, but I have found multiple documents and tried multiple pinout combinations to connect the XDS510 to my TMDS570LS31HDK (before we design our own boards), and I cannot get it to work. There are various conflicting documentation from ARM, spectrum-digital, the TI datasheet, and this forum. In addition, I found this app-note from Lauterbach (at www2.lauterbach.com/.../app_arm_jtag.pdf) that states both ARM reset lines must be manipulated in a specific sequence to get JTAG access. None of the above documents describe a two-reset interface. 

Is there a JTAG-debugger that works out-of-the-box with Code Composer 7 and with this TMDS570LS31HDK 20-pin interface? If so, which one?

Does the XDS510-USB work with the "standard" TI 14 pin interface? If so, what are the pin connections? Note the TI-datasheet pin-outs and the XDS510-stated pinouts do not work on this dev-board.

Thanks,

Jim

  • 0
    TI__Guru 59540 points

    Hello Jim,

    The simple answer here is yes, absolutely. In fact, our four newest launchpad kits have XDS110 emulators integrated into their design. For reference, they are the LAUNCHXL2-570LC43, LAUNCHXL2-RM57L, LAUNCHXL2-TMS57012 and LAUNCHXL2-RM46. There are schematics for these kits on their respective wiki pages. The links to the wiki pages are in the descriptions of the kits on their respective product pages (click on the part number above to go to the associated product page). For ease of access, here is a link to the wiki for the LAUNCHXL2-570LC43  where the design files can be found .

    Note that the design of the launchpads have an un-populated surface mount header for the CTI20 interface which the XDS110 supports.so you should be able to utilize the same interconnect for your board.

    To reference the JTAG headers available on the HDK, the design provides a header for a 20-pin ARM connection with the following pinout.

    .This is also shown in the schematics for the HDK located on the product page here with the signal connections can be seen in the schematic for the HDK. The schematics are located in the link to the design files zip on the HDK product page here . 

  • 0 in reply to Chuck Davenport
    Expert 2375 points
    Let me reword the question; I have a working TMS570LS31 development board with the on-board XDS1xx debugger. I am trying to use the available external-debugger interface to wire up to my external XDS510-USB, because I want to know what the exact wiring is before I design a new LS3137-based board.

    I have found many conflicting descriptions about JTAG wiring to an ARM, and I think I have narrowed done the problem to the reset-signals. I did not look at all of the dev-kits you mentioned, but the first LAUNCHXL2-570LC43 schematic shows 2 different reset-inputs (MR and TRSTn) on the 20-pin header -- my question is how does the XDS510-USB support a TMS570 when the XDS510 only has 1 reset (TRSTn) output?

    Note I tried tying the XDS510-USB TRSTn to both TMS570LS3137 reset inputs, but that did not work.

    Thanks,
    Jim
  • 0 in reply to jimj2713
    TI__Guru 59540 points

    Hello Jim,

    The TRSTn is the debug reset and is used to hold the debug logic in reset when not connected to an emulator. When connected to an emulator, it drives this pin high to de-assert reset and enable the debug logic.

    In regard to MR connection, if you trace this back in the LAUNCHXL2 design you will see that it connects to the power on reset circuit so that the XDS110 can assert a hard reset. In the ARM 20 pin connector on the HDK board the nSRST pin connects to the nRST pin or a warm reset. There is some debate over which is more applicable. For certain, the nPORRST will take the device back to a hard restart while the nRST is only a soft reset leaving some registers in a non-default state. I believe the if nPORRST is asserted, the device will disconnect from the debugger and have to be reconnected by the user. If an nRST is asserted, the debug connection is not lost. In our HDKs XDS100v2 implementation, a System Reset in CCS is this soft reset to give you some idea of the behavior. As noted, an nPORRST will cause the debugger to loose the connection and will display a notification that the reset occurred on the device.

    To utilize the XDS110 external emulator with the ARM 20 pin header that is included on the HDK, you will need to make an adapter to "swizzle" the connections or you can purchase an adapter from one of the emulator manufacturers. This is a link to a BlackHawk listing of available converters including the CTI20 to ARM20 converter I found this with a relatively quick search using google so I can't give any endorsement and I am simply including it as an example of an available converter.

    If you would like to make your own using a bread board or prototyping board, the picture below shows the signal mapping between the two connection types.

    Note the different colored lines have no real meaning and I colored them for the express purpose of making the diagram easier to read.