TDA4VH-Q1: Debugger Header options

HW_Guy

Part Number: TDA4VH-Q1

Hello,

I have a board with TDA4VH-Q1. My SW team shall be using different tools such as (LA-3254, XDS560V2 etc.). I have JTAG, EMU (EMU0 and EMU1) and four trace signals to be be provided. Now I see there are different headers with many options. I can see that JTAG and EMU pins can be given access using Compact TI 20-pin header and standard ARM 20 pin header. But I do not see option to include trace signals.

There are also converters from 20IDC to MIPI 60 pins but I don't see the trace signals signals on 20 pin connector to be routed to 60-pin connectors.

What are the least amount of connectors I can have on the target board to include JTAG, four trace signals and two EMU signals which are compatible to most of the tools I am going to use or with off the shelf adapters available?

Regards
MY

over 1 year ago

+1 Robert Eschler over 1 year ago

TI__Guru 52125 points

The MIPI-60 connector supports your requirements, JTAG, EMU, TRACE (4bits).

0 HW_Guy over 1 year ago in reply to Robert Eschler

Prodigy 70 points

Thanks Robert.

In MIPI-60 connector I could map the JTAG and Trace signals but I am not sure where to connect the EMU signals.

I am referring 'Emulation and Trace Headers Technical Reference Manual (Rev. I)' table 12 on page no. 14.

As mentioned just before that table, I am connecting TRC_CTL to TRC_DATA[0][0]. I am connecting TRC DATA 0 - TRC DATA 3 to TRC_DATA[0][1]-TRC_DATA[0][4]. Where do I connect my EMU0 and EMU1 signals?

0 Robert Eschler over 1 year ago in reply to HW_Guy

TI__Guru 52125 points

TI's TDA4VH-Q1 EVM supports MIPI-60 connector interface including JTAG, TRACE, and EMU. See schematic pg 54 for exact pin assignments on connector. Can I ask why you need access to EMU signals?

https://www.ti.com/lit/zip/sprr458

0 HW_Guy over 1 year ago in reply to Robert Eschler

Prodigy 70 points

Got it Robert.

I am hardcore guy and have no idea why our SW team needs it. I see the same gap from my SW team for HW.

Do you have any opinion which I convey to my SW team?

By the way I am trying to understand many things like boot mode options, MUXing in the reference you shared.
I am expected to support many near future project based on this family of devices.

I wish there is a training on these interfaces especially used during development for HW engineers (presuming they do not have any background on SW).

Thanks again.

0 HW_Guy over 1 year ago in reply to Robert Eschler

Prodigy 70 points

I am stuck again. I am going to use just one MIPI-60 pin connector with the pin connection as attached.

My SW team is going to use LA-3253, LA-3254, LA-3253 55, LA-3743X, XDS200 and XDS560V2.

Now I am seeing converters from this page below but not able to figure out how would be the pin connection and if they are compatible.

Could you please let me know if all above tools can be used and suggest me adapters?

0 Robert Eschler over 1 year ago in reply to HW_Guy

TI__Guru 52125 points

I don't have experience or documentation for all those emulators. I have used XDS560v2 - as it has a native MIPI-60 connector. I've used XDS200 with an adapter to MIPI-60.

0 HW_Guy over 1 year ago in reply to Robert Eschler

Prodigy 70 points

OK. May I know which adapter did you use?

XDS560v2 would fit in to MIPI 60-pin connector.

Rest of the tools (LA-3253, LA-3254, LA-3253 LA-3255, LA-3743X) seem to be compatible with ARM 20-pin connector shown on this page.

Now I just need to figure out MIPI 60 to ARM 20-pin adapter. XDS256v2 we have ordered also seems to come with few adapters.

0 Robert Eschler over 1 year ago in reply to HW_Guy

TI__Guru 52125 points

Additional info: www.blackhawk-dsp.com/.../pin-converters

Processors

Processors forum

TDA4VH-Q1: Debugger Header options