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

RM48L952ZWT, ETM and JTAG

Ubaid Mahmood
Intellectual 970 points

Other Parts Discussed in Thread: TMDSEMU560V2STM-UE

Hello,

In the below HDK schematic, various lines TDI, TDO, TMS and other lines are multiplexed between JTAG and ETM (for MIPI Connector). In SPNS177B ETM does not include TDI, TDO, TMS and other lines.

Can you please clarify the discrepancy between SPNS177B and the HDK? as well as how the lines are used in ETM/MIPI?

Thanks.

Ubaid

  • 0
    TI__Guru 69070 points
    Ubaid,

    The pins you are asking about are listed in the datasheet under "Test and Debug Modules Interface".

    The MIPI-60 connector includes both the JTAG Debug and the Trace interfaces. So when you plug in the XDS560 PROTRACE it's one box that does both your normal JTAG debug and your tracing, and you only plug one small cable into the MIPI60 header to do all the work. It's not like having separate headers for a logic analyzer and JTAG debug... it's very nice and compact now.

    I don't know how much room you have on your board, but it's a 'convenience' to have two different JTAG headers. You could get away with the MIPI60 and then use an adapter that adapts it down to a different footprint for folks that are not using a PROTRACE.
  • 0 in reply to Anthony F. Seely
    Intellectual 970 points

    Thanks for the clarification Anthony!  That makes sense and is what we were assuming.

    We do have a XDS560v2, but we are not able to connect to ETM using the MIPI Connector because the DCAN1 connector is blocking us.  How can we connect for ETM to the HDK board?

    Also, how do we use ETM?  Is there any specific documents available on this?  Would we be using CC6 as the application?

    Thanks

    Ubaid

  • 0 in reply to Ubaid Mahmood
    TI__Guru 69070 points

    Hi Ubaid,

    Good questions.  

    I am actually able to connect the XDS560v2 STM emulator to the HDK - as your photo shows,  but the adapter board does touch the top of CAN connector.   It's not actually blocked - but it is a tight fit and if I were using CAN at the same time as the emulator I'd want to insulate so that the PCB on the emulator doesn't touch the screw terminals on the CAN connector.

    You could probably flip the CAN connector to the bottom side of the board or remove it as the easiest 'fix'.

    Alternatively the MIPI 60 connector is available in different stacking heights.

    The XDS560v2 STM however does not support ETM Trace.   So you don't actually *need* to plug it into the MIPI60.

    You could with an adapter plug it into the ARM20 pin header.  I think you should have an ARM 20 pin header in the box w. your XDS560v2... usually these emulators come w. a pack of adapters.

    For ETM Trace you need the XDS560v2 PROTRACE emulator.  It has a different JTAG header, instead of a right angle it has a vertical header and lots of clearance... as shown below:

    CCS has a 'Hardware Trace Analyzer' tool that will present the ETM interface to you.

    There are some basic options like checking/unchecking cycle accurate or data trace alltogether that are simple to understand,

    and then there are more advanced options avaiable through a configuration interface where you can select address ranges, 

    read vs. write, etc as filters. 

    There are some Wiki pages that appear to be a little dated (looks like CCSv4) but still seem pretty accurate in terms of content.

    Just note that the RM48 device you have does not have an on-chip ETB - so ignore those parts of the wiki.  You have to use a PROTRACE and capture from the ETM port:

  • 0 in reply to Anthony F. Seely
    Intellectual 970 points
    Thanks Anthony,

    That is a lot of good information. I appreciate it. Will need to review it in more detail.

    I am a little confused in that, we have the TMDSEMU560V2STM-UE, and it is described as having system trace features. What type of system trace capabilities is supported on this device if not ETM?

    Thanks.
    Ubaid
  • 0 in reply to Ubaid Mahmood
    TI__Guru 69070 points

    Hi Ubaid,

    System trace is something else, there is a description here processors.wiki.ti.com/.../STM
    that differentiates it from Core Trace (ETM falls into the core trace category).


    EDIT:  I should clarify - Hercules devices currently do not have logic on chip for System Trace. 
    My understanding is that this is mostly seen on the more complex SOCs  (like the Sitara/OMAP parts)


    I think from an emulator standpoint though it boils down to the capabilities to capture data ... the bandwidth that the STM emulator can grab is a lot lot less than what the PROTRACE is capable of. I think STM has only a handful of trace pins.. Not sure about memory. The PROTRACE can currently capture 19 data pins and has something like 2Gigabytes of buffer...