• Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 537 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.

Trace port tradeoffs between MIPI60 and Mictor38

Jonathan Brandmeyer89
Prodigy 230 points

Is the TMS570LC43xx capable of using a 16-bit trace port connected to the ARM 38-pin Mictor connector?  A user from a couple years ago discussed a success with this port and connector on an earlier model in the R3 line.  If so, what are the performance tradeoffs between 16-bit trace and 32-bit trace?

  • TI__Guru 69070 points
    It may be - but you would need to consult with the trace tool vendor to see if they support the particular ETM version we have on the LC4357. The MIPI60 is supported by the TI PROTRACE emulator.

    The difference would then be the bandwidth available for trace, obviously, and it's going to be 1/2 bandwidth compared to 32-bit trace. The PROTRACE only supports 24-bit trace data - so you'd be 2/3 of the PROTRACE bandwidth.

    With 24 bits of trace data - we still drop packets during high activity. The trace port is designed for this - and it will note where the FIFOs overflowed (loss of data) and automatically resync... so it's like looking at a history with occasional 'holes'. To combat this you can be selective about what type of information is sent out on the trace port (filter it).

    So with 2/3 of the bandwidth - you could probably expect to need to do a lot more filtering and/or deal with more loss of information.