• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 33 subscribers
  • Views 2801 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TM4C123 TRACE WITH BLACKHAWK EMULATOR

WhiteHorse
Genius 4430 points
Other Parts Discussed in Thread: SEGGER

E2e,

We have a customer that wants to use the trace feature of the Blackhawk emulator (USB560v2) with the TM4C123.  The TM4C123 spec talks about Trace Port Interface unit (TPIU), Trace Macrocell, signals TRD0/1, TRCLK.  The emulator documentation talks about EMU0-EMUn signals.  Is it possible to get a drawing of the TI 14-pin to TI 20-Pin, header connected to the TM4C123.

Thanks for your help.

WH

  • 0
    TI__Guru 59540 points
    Hello WH,

    For starters, there are several threads on the Forum that you can reference that might provide some help. The one that might be most helpful is this one: e2e.ti.com/.../371986 which discusses the TRCLK implementation on the TM4C123. From this thread it seems that trace is only available in the serial wire configuration which blackhawk should support. The bigger issue will, most likely, be the IDE they use since most information I have been able to find does not indicate that CCS will support trace functionality (could find out more on the CCS E2E to be certain).

    In regard to the JTAG/ETM headers, the TM4C123 design guidelines has some additional information that should be helpful. The design guideline is located here www.ti.com/.../spma059 and the relevant sections are sections 3.8 and 3.9.
  • 0 in reply to Chuck Davenport
    Genius 4430 points

    Hi Chuck,

    Thanks for those details. I would be great if there was a schematic that showed how to connect the Blackhawk emulator (USB560v2) to the TM4C123. The post that you recommended seemed to conclude that trace is not available on the TM4C123 except in serial wire mode. You mentioned that the IDE could be a problem in you can't find information stating that CCS supports trace mode. Do you mean trace mode in general or trace mode only for the TM4C123?

    Regards,
    WH

  • 0 in reply to WhiteHorse
    TI__Guru 59540 points

    Hi WH,

    In regard to schematics, I don't think we have much on it other than what is covered by the design guidelines document for TM4C123 and, yes, it seems only the single wire mode is supported based on the information I have been able to find. Some of the other posts on the topic discuss successfully using IAR for trace with this device which I believe the XDS560v2 should also support. In regard to the specific hookup, I would recommend you check with blackhawk since they would have more specific information on it and its capability.

    In regard to CCS, I think some trace capability was added in CCS 6 but not for single wire trace support. I also don't know how effective it might be since I don't have any experience using it.

  • 0 in reply to Chuck Davenport
    Guru 47900 points
    If I may (as past contributor to the referenced thread) I can report success w/Trace (via SWO) when using IAR and Segger's J-Link via SWD. (Trace data arrived via SWO.)

    Note that we did this w/past LX4F23x MCU series - yet as it is claimed that these are (very) similar to TM4C123 - you may (reasonably) expect similar results...

    IAR & Segger have extreme focus upon IDE and data-flow. Both the IDE and JTAG/SWD pod are "vendor agnostic" and appear to operate w/many advantages over (extremely) limited (one and only one ARM vendor) "solutions."
  • 0 in reply to WhiteHorse
    TI__Guru**** 244380 points
    Hello WH

    To add to Chuck's point, if the customer is using code composer studio for trace functions, then ETM trace is not supported by Code Composer Studio for Cortex M4 cores.

    Regards
    Amit
  • 0 in reply to Chuck Davenport
    Genius 4430 points

    Hi Chuck, Cb1 and Amit,
     
    Thanks for the additional details. They were helpful.  The customer has already asked Blackhawk for help and their response was to talk with TI.

    Regards,
     WH

  • 0 in reply to WhiteHorse
    TI__Guru 59540 points
    Hello Whitehorse,

    If this is Blackhawk's answer and they aren't willing to support their tool, then I would guess our only recommendation would be to check into Segger's J-Link as we know this has some success with IAR.
  • 0 in reply to Chuck Davenport
    Genius 4430 points
    Hi Chuck,

    That makes sense. Thanks for the recommendation.

    Regards,
    WH
  • 0 in reply to WhiteHorse
    Guru 47900 points

    Perhaps - making even (more) sense - the combination of Segger J-Link (or better) and IAR is facilitated by:

    • IAR's ARM version is vendor agnostic - enables most all of the 40+ ARM MCU vendors to be explored/evaluated!   Is it not foolhardy to believe that, "One and only one" vendor's offering will always prove best/brightest/stocked/cost-effective?   What if you seek to explore "cost down" M0, or M3, or M7 - IAR covers them all!
    • IAR is far more mature than any single (vendor locked) implementation - firms gladly PAY for a quicker, more robust, & more capable experience
    • IAR provides a FREE "Kickstarter" for ARM.   We recommend that you START w/the code-size limited version (32KB)
    • Segger provides an "Educational" version of the J-Link at "substantial" cost reduction.   (And you do NOT have to "pretend" to (still) be a student - simply comply w/Segger's usage guideline)
    • IAR has (for many years) supported the pin-saving SWD interface (still absent here) - the Trace data sought appears along the SWO pin - and almost without any notable execution speed penalty...