• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 3 answers
  • Subscribers 99 subscribers
  • Views 542 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.

AM623: I'm trying to decide on debuggers for a new BSP

RG
Intellectual 480 points
Part Number: AM623
Other Parts Discussed in Thread: TMDSEMUPROTRACE,

Where can I find an explanation of the utility or advantages of one over the other.

https://www.ti.com/tool/TMDSEMUPROTRACE (3500)

https://www.blackhawk-dsp.com/store/12161.html (2500)

https://www.ti.com/tool/TMDSEMU560V2STM-U (900)

When your not using an M core .vs. when you are using an M core in addition to the A core etc.

How this might help in SMP, AMP, or between threads accessing peripherals from different cores.

Sorry for the broad support question - suggestions on intro documents would be helpful.

<EDIT>

Found that: A target board that sports one of the compatible JTAG headers (MIPI HSPT 60-pin or TI 60-pin). is required for the TMDSEMUPROTRACE. Our new board will only have a TI cJTAG connector.

Thus this debugger is overkill for our useage.

  • 0
    TI__Guru**** 466231 points

    Hello,

    RG said:
    https://www.ti.com/tool/TMDSEMUPROTRACE (3500)

    The main advantage of ProTrace is the 2GB trace buffer if your device and board supports trace over pins:

    https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_debug-main.html#pin-trace

    RG said:
    Thus this debugger is overkill for our useage.

    Yes if your board does not support trace over pins (MPIP60 header) then it has no additional value.

    RG said:

    https://www.blackhawk-dsp.com/store/12161.html (2500)

    https://www.ti.com/tool/TMDSEMU560V2STM-U (900)

    The main difference between the above two is that the former supports debug over ethernet while the latter is strictly via direct USB connection to the debug probe.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru 63145 points

    Ki, I seem to recall another thread where you said the latest TI CCS tools do not support the external trace buffer available in the Pro Trace debugger for AM62x devices. If so, there would be no advantage for anyone to purchase Pro Trace debugger if it were only be used with the AM62x device.

    Can you please confirm for RG's benefit?

    Regards,
    Paul

  • 0 in reply to peaves
    TI__Guru**** 466231 points

    Paul, you are correct in that we are no longer supporting pin trace in newer devices. I can't recall off the top of my head where the cut off was. I believe you are correct that AM62x is not supported by pin trace. I defer to the device experts. In such cases, there is absolutely no benefit for having a Pro Trace pod. As mentioned earlier, both the board and device must support pin trace for the Pro Trace pod to be useful.

  • 0 in reply to Ki
    TI__Guru 63145 points

    From my understanding the lack of support for pin trace is purely a function of software support.  We still provide an option to route the trace signal functions to pins on all Sitara devices. They are implemented on pins shared with other signal function, so it may not be desirable to use the pin for trace.

    Regards,
    Paul

  • 0 in reply to peaves
    TI__Guru**** 466231 points

    Thanks for clarification. Yes, now I recall. CCS no longer supports pin trace but other 3 party vendors like Lauterbach may still be an option.

  • 0 in reply to peaves
    Intellectual 480 points

    @Peaves,

    Are you saying the  cJTAG can support the extraction of ETB trace data into the more expensive PRO trace at a later date with a SW upgrade to CCS?

    The clarification I'm looking for here is the need for the MIPI HSPT 60-pin or TI 60-pin connector.

    Specifically,

    I see I can use any Debugger with cJTAG and still get the ETB data from traces. This is great, but the buffer on the AM623 is limited to 64K. Which is why you might want a bigger external capture memory device like the PRO trace.

    However, I think that device works because it allows a SERDES like 2 or 4 LVDS highspeed signal to dump the trace real-time to the PRO trace (which is why it would require more lines to the debugger). This is what I'm guessing.

    So that is the point of the extra pins correct? I'm asking/proposing why this would imply not just SW change but also the need for additional PINS (correct)???

    [At least more PINS than are available on the cJTAG? - which could limit the debugger you choose]

  • 0 in reply to RG
    TI__Guru 63145 points

    You would need to connect the AM62x pin trace (TRC_x) signals and JTAG signals to the MIPI connector and purchase a Lauterbach debugger that supports external trace if you need a bigger trace buffer than the on-die ETB.

    Note the pin trace (TRC_x) signal functions are implemented on pins that are shared other signal functions that may be important for your application. If so, you may not be able to connect these pins to the MIPI connector.

    Regards,
    Paul 

  • 0 in reply to peaves
    Intellectual 480 points

    Thanks All, @Peaves (I will check on the routing mentioned above for TRC_x) 

    Confirming:

    But really, I'm trying to understand if the same cJTAG from the SK-AM62x EVK would support more than basic ETB extraction. Would the PRO version even work with the EVK for external trace? IF not then as indicated above - not only overkill but not compatible pin count/signals - correct?

    Potential Concluding remarks:

    SPRUHM7B (pre AM62x Sitara) & Trace Analyzer. SPRU655

    I think I understand for capturing EXTENDED traces TI trace-enabled emulator is needed (the PRO Version with a header that supports more PIN outs). This allows continuous trace while running.

    But for basic tracing (onboard ETB buffer, when a break point is hit you can extract the trace from the buffer)

    SPRUHM7B: ETB data can be read from the target using any emulator (XDS100, XDS200, XDS560, etc.)

    Summary:

    Given our design is TI 20-pin CTI (replicated from the SK-AM623B)

    We can perform using the CCS tool suite.

    1. normal debug
    2. trace using the ETB/ETM only and limited to 64KB. 
    3. profiling

    And for a minimal system, XDS200 would be useful for interacting with the AM62x, while not providing highspeed off SOC trace memories.

    https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds200.html

    XDS200 is compatible with Code Composer Studio (CCS) version 5.2.0 and newer  (in video he states 5.3 is first compatible for xds200)

    And the XDS560v2 higher end with Ethernet & USB, But other than that what other functions can it add (given the TI JTAG C ) EVK limited signal lines?

  • +1 in reply to RG
    TI__Guru 63145 points

    The AM62x EVM does not support external trace.

    Yes, you can use CCS for normal debug and trace with the internal ETB trace function via the standard JTAG signals.

    Note, we do not support implementing your own XDS110 controller for onboard JTAG. Custom boards should use external emulators to enable debug capabilities.

    Regards,
    Paul