AM6442: Debugging AM6442BSFFHAALV via MIPI Interface – Emulator

Hi Pradeepraj M,

As answered in this thread (link), there is no specific recommendation for a debugger probe.

More info on XDS debuggers can be found here:

https://dev.ti.com/tirex/explore/node?node=A__AHPc.Wb9z60G4gncUEl6rA__xdsdebugprobes__FUz-xrs__LATEST

For items 2 and 3 I think you can find answers in this folder:

https://dev.ti.com/tirex/explore/node?node=A__AGXprZQz0MSi03UzcpV7gQ__xdsdebugprobes__FUz-xrs__LATEST

Note the links to external websites inside.

Regards,

Stan

Hi Stan,

1. ETB or On-Chip Trace Support

We are planning to debug the processor core using the XDS560v2 USB emulator via the MIPI-60 connector, and for this, support for Embedded Trace Buffer (ETB) or an equivalent on-chip trace mechanism is essential — particularly to enable instruction trace and non-intrusive debugging.

While reviewing the available documentation for AM6442, we could not find any explicit mention of ETB support. However, as ETB or an equivalent is typically expected on Cortex-A based devices with CoreSight support, we would like to confirm the following:

Does the AM6442 support on-chip trace capture equivalent to ETB functionality?

Can this be used with XDS560v2 USB emulator through the MIPI-60 interface to perform core instruction trace? 

Are there any official documents or app notes that detail the usage or configuration of this feature?

2. MIPI-60 Pinout Discrepancy

We have noticed that the MIPI-60 pinout provided in the TI Emulation and Trace Headers TRM differs from the pinout shared by Blackhawk, and also appears to differ from what is implemented on the TMDS64EVM board. This has caused some confusion while designing our custom board interface.

I have added the documents link below.

TRM - Emulation and Trace Headers Technical Reference Manual (Rev. I)

Blackhawk - Blackhawk JTAG Pin Converters

Could you please clarify:

Which MIPI-60 pinout is correct and officially supported for use with XDS560v2 USB emulator?

Is there a TI-provided document or guideline that confirms the correct MIPI-60 pin mapping?

Regards,

Pradeepraj M

Hi Pradeepraj M,

Let me ask a couple of questions internally. I will come back in 1-2 days.

Thanks,

Stan

Hi Stan,

Any update on the above request.

Regards,

Pradeepraj M

1. Based on the CCS documentation, we understand that ETB (Embedded Trace Buffer) is available on the Cortex-A53, Cortex-R5F, and Cortex-M4F cores present in the AM6442 device. Therefore, we believe it is valid to use the XDS560v2 USB emulator for core-level debugging and trace capture on these cores.

Could you please confirm if this understanding is correct?

2. While reviewing the XDS560v2 USB Installation Guide, we noticed that the MIPI-60 pinout for the target board appears to differ from the pinout used in TI’s EVM schematics.

Additionally, several trace data pins in the guide are grayed out, which raises the following questions:

• Should we follow the XDS560v2 USB Installation Guide pinout for our custom board’s MIPI-60 connector, even though it differs from the EVM?
• Are the grayed-out trace data pins optional or deprecated? Is it acceptable to leave them unconnected if we are only using ETB-based trace and not external streaming trace?
• Is there any impact on debugging or trace functionality if these trace pins are not routed on our board?

We want to ensure full compatibility with CCS and XDS560v2 for core-level debugging and trace capture on the A53, R5F, and M4F cores.

Regards,

Pradeepraj M

Hello Pradeepraj M,

The ticket owner is out of office today. He will be back tomorrow and reply to your question.

Kind Regards,

Anastas Yordanov

Hi Stan,

Any update on above request.

Regards,

Pradeepraj M

Hi Stan,

I’d like to clarify a few points regarding trace support on the XDS560v2 STM debugger:

1. The TRM and platform documentation mention that XDS560v2 STM supports only System Trace, and not Core Trace for ARM and DSP cores.
2. However, the TI website states that all XDS debug probes support Core and System Trace via ETB, which includes instruction-level trace for ARM and DSP cores.

Could you please confirm:

1. Does XDS560v2 STM support Core Trace via ETB for ARM and DSP cores (e.g., on AM6442)?
2. Is streaming Core Trace over trace pins only supported by XDS560v2 Pro Trace?
3. Are there any limitations when using XDS560v2 STM for instruction-level debugging or trace capture?
4. Should EMU signal routing and trace header design on custom boards exclude signals reserved for Pro Trace if only XDS560v2 STM is used?

Also, I understand that System Trace (STM) provides valuable system-level insights, but it does not offer instruction-level visibility. So for debugging core execution flow, Core Trace via ETB would be essential.

Regards.

Pradeepraj M

Hi Pradeepraj М,

I'm checking this internally. Someone from the team will update as I will be OoO next week.

Thanks,

Stan

Hi Stan,

Add on to that, we also plan to use the XDS560v2 PRO TRACE emulator via the MIPI-60 interface for core-level debugging. However, AM6442 is not explicitly listed in the supported devices for this emulator in TI website. Can you confirm if XDS560v2 PRO TRACE is officially supported for AM6442? Also, should we follow the MIPI-60 pinout from the Emulation and Trace Headers TRM, or the one used in TMDS64EVM for compatibility. Please confirm.

Thanks,

Pradeepraj M

Hello,

Stan is out of office until next week.

In the meantime we will also check with CCS team why AM6442 is not showing up in the list of CCS/supported devices for the XDS560v2 PRO TRACE emulator.

Kind Regards,

Anastas Yordanov

Hi Pradeep,

Pradeepraj M said:

Can you confirm if XDS560v2 PRO TRACE is officially supported for AM6442?

The official page does specifies that debugger supports the TI SOCs with PRU, C674x, C66xx, Cortex M, Cortex R and Cortex A cores. 

Please refer TMDSEMUPROTRACE for more details.

Regards,

Tushar

Hello,

We are currently developing a custom board based on the AM64x processor and using the TMDS64EVM for reference. We're planning to interface with a MIPI connector. Can we use the same MIPI pinout as provided on the TMDS64EVM for our custom board?

Regards,

Pradeepraj M

Pradeepraj M said:

Can we use the same MIPI pinout as provided on the TMDS64EVM for our custom board?

I will defer to the device team for this question

Hello,

I will internally discuss your question with a TI debug hardware expert later today to get the answer.

It would take some time.

Please ping this thread if you haven't heard back by Monday next week.

Thanks for your patience !

Kind Regards,

Anastas Yordanov

Hello,

For a MIPI-60 hook up which will work with AM64 you can refer to this other E2E thread for a sister device.

•  https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1496332/j722sxh01evm-j722s-am67d-trace-and-emu 

Hello,

We are planning to remove the 20-pin JTAG header from our custom AM64-based board and retain only the MIPI-60 connector for debug and trace purposes.

Could you please confirm the following setup compatibility?

• Using the MIPI-BH-ADP-60E_MIPI-20T_CTI adapter to connect:
  • XDS200 debugger to the MIPI-60 header
  • XDS560v2 Pro Trace to the MIPI-60 header
  • What is connector MIPI Connecter part no to be placed on target board.

Regards,

Pradeepraj M

The https://www.blackhawk-dsp.com/store/12188.html is an adaptor I have used to go from cTI20 to MIPI-60 on some board.  It likely is good.  However, its not a combination I've tried on this SOC family. My hands on usage is not exhaustive as I have access to only a subset of boards, emulators, and adaptors.

The connector used on the AM67 BOM link is  https://www.ti.com/lit/zip/sprr495  :