• State
  • Locked Locked
  • Replies 10 replies
  • Subscribers 32 subscribers
  • Views 1325 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.

Hardware trace on Tiva series MCU's

Guy Ovadia
Intellectual 400 points
Other Parts Discussed in Thread: TM4C1294KCPDT, SEGGER

Hi,


I am trying to determine what are the hardware trace capabilities of the Tiva series MCUs. I'm currently working with TM4C1294KCPDT.

Here's what I gathered so far:

There is an ITM trace module in the MCU, which supports only statistical function profiling, watching only a single(?) variable over time, and interrupt profiling. This is nice, but not a full hardware trace. I understand it requires an XDS200 probe and uses SWD + the SWO pin for communications, and the Code Composer supports this (but not the free license).

I understand there is also an ETM module in the MCU that supposedly can do low-level instruction trace (great!) but I haven't found any information on how to utilize it. what hardware and software do I need? does Code Composer support this or do I have to use a third party IDE? what kind of interface does it use (which pins etc)? what exactly can I achieve with it?

I also noted there are trace pins on the MCU, labeled TRD0 through TRD3, plus TRCLK. what capability do they provide? perhaps they are related to the mysterious ETM...?


thanks,

Guy.

  • 0
    Guru 117855 points
    Greetings,

    My small firm works w/many ARM MCUs - thus we chose a "pro" IDE - not limited to single vendor - and far more capable/comprehensive. (IAR is ours - Keil also is superb)

    Now I've no experience (nor desire) to use the IDE you've mentioned - yet you can gain far more understanding by venturing to Segger's site - along w/IAR - and keying upon "trace." Usually - but not always - the higher pinned out parts better support "trace." Segger produces both J-Link & J-Trace - which enable a far more comprehensive experience than that resulting from ones you've mentioned.

    Should note that my firm is a client of Segger - and is unrewarded for this writing.
  • 0
    TI__Guru**** 244400 points
    Hello Guy,

    The TRD0-3 and TRCLK provide for the ETM Trace on the TM4C129x devices. We are working on an application note for debug and trace which will list the usage of the interface.

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Intellectual 400 points

    Hello Amit,


    thanks, I saw in a thread from earlier this year that an appnote is planned, but I do need at least basic information now. just a sentence or two to describe what it can do, and what hardware / software is needed would help.

    thanks,

    Guy.

  • 0 in reply to cb1_mobile
    Intellectual 400 points
    thank you cb1 for your IDE recommendations. I am in fact considering alternative IDEs and one of the important considerations is hardware trace support, and to what level. I still don't know though (not from your answer and not from Amit's answer) what kind of trace capabilities I can get from this ETM module and what hardware or IDE is needed.
  • 0 in reply to Guy Ovadia
    Guru 10570 points
    Take a look at the information on Segger's pages. They will likely tell you how h/ w capabilities map to trace.

    Robert
  • 0 in reply to Robert Adsett72
    Guru 117855 points

    Agree Robert - Segger was my (earlier) suggestion.   Poster's persistence (appears) to exceed his "search" diligence. (i.e. the info is available, "now")

  • 0 in reply to cb1_mobile
    Intellectual 400 points
    cb1, I am definitely going to check out Segger's documentation as you and Robert suggest. However, I also want to understand more broadly, what Segger probably doesn't tell - i.e. what Code Composer supports, what hardware (from various vendors, not just them) can be used for the hardware trace, and so on. The big picture, not just Segger's smaller scope.
  • 0 in reply to Guy Ovadia
    Guru 10570 points
    Segger's documentation may (I suspect likely) tell you more than you think. Their small scope covers the major IDEs and almost all the ARM vendors. The only place you are likely to get more definitive information is from ARM itself.

    Robert
  • 0 in reply to Guy Ovadia
    Guru 117855 points

    Guy Ovadia said:
    The big picture, not just Segger's smaller scope.

    My friend - unlike this vendor - Segger's business IS various "hooks & aids" which support the major IDEs.  (to include the Trace info you seek)

    Wise that you digest that (Proper tool to the task) fact.   This vendor's focus is device - not so much the "fine Trace detail" you crave.   (and vendor's Trace App Note is "planned" yet unspecified - that's not especially comforting - is it?)

    CCS is the "limited" and "new kid" on the IDE "block" - thus "it" is most representative of the "smaller scope" you note...

    You will not regret the use of a "real" IDE and J-Link (or better - if you can afford).   Single, limited IDE implementation (i.e. one you note) - not so much...

  • 0 in reply to cb1_mobile
    Guru 10570 points
    Indeed, because of CCS's single vendor focus it is destined to remain a backwater.

    Robert