• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 102 subscribers
  • Views 108 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.

AMIC110: Lauterbach Trace32 with AMIC110

Falk Bastille
Prodigy 60 points
Part Number: AMIC110

We are successfully using a Lauterbach with JTAG to debug on the AMIC110 MCU on our platform.

What we would like to use is the ETM of the AMIC110 with our LA7690 PowerTrace-ETH-512M.

Our question is which lines are required from this MCU to get the PowerTrace working?

I assume that EMU 0..4 are the lines that may be used. Unfortunately we only have EMU0, EMU1 and EMU4 available. EMU2 and EMU3 are (pin)configured to be used with the MMI of a connected PHY.

We would like to know if EMU0, EMU1 and EMU4 are sufficient to get the Trace functioning?

Can these lines be configured?

Thanks for your help. 

  • 0
    TI__Guru 55375 points

    I'm checking with our debugger expert and will try to provide an answer to your question shortly.

    Regards,
    Paul

  • 0 in reply to peaves
    TI__Guru 55375 points

    Here is the reply I received from our debugger expert.

    AMIC110 does not support TPIU trace and the Cortex-A8 ETM is only provided to the on-chip CSETB.

    The EMU0-4 signals are associated with an early STM (System Trace Module) that supported both on-chip (CSETB) and off-chip trace export—I’m not sure if this is supported by Lauterbach tools.

    Regards,
    Paul

  • 0 in reply to peaves
    Prodigy 60 points

    Hello Paul, thanks for the info. I have been in contact with Lauterbach on the issue, so I'd like to share all the answers and the solution that we have worked out.

    As you have suggested the on-chip trace is the methode of choice for this MCU and the configuration that I have described earlier. The on-chip trace works fine with the internal 32kByte ETB. Even though the amount of trace data is limited to around 80 us of runtime information, it helped us alot to clarify an optimisation issue. To get the on-chip trace to work with the Lauterbach Trace the following settings should be applied in the load script (cmm):

    Trace.CLOCK 300.MHZ
Trace.METHOD ONCHIP
ETM.CYCLEACCURATE ON 
ETM.TRACE ON
ETM.ON

    As for the other question about using only a selection of the EMU lines for off-chip trace Lauterbach suggested the following:

    - only consecutive lines may be used. EMU0,1,2,3 is OK, EMU0,1,4 is NOT OK.

    - a 2 bit recording width for off-chip trace is not recommended

    I have not investigated if STM as Paul has pointed out is supported.