CCS/EVMK2G: CCS/EVMK2HX: Problem connecting using XDS200 port

Hello Hakan,

Your XDS200 connection seems fine. The issue appears to be communication with the target EVM itself:

Hakan Pekmezci said:

The value is '-180' (0xffffff4c).
The title is 'SC_ERR_CTL_NO_TRG_POWER'.

The explanation is:
The controller has detected a target power loss.
The user must turn-on or connect the power supply for the target.

Please see:

https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html#power-loss

Check that the board is properly powered

Thanks

ki

Hi Ki,

The board is powered by 12V,7A power adapter which comes in the box. We assume the manufacturer supports the power properly. I also tried to plug the second USB mini cable in (if it wants all usb ports externally powered for debug reasons) which goes to base EVM board but no success.

EVMK2HX Evaluation Module comes with its Mezzanine XDS2XX Onboard USB preassembled by the manufacturer(TI/Advantech/eInfochips). I followed the Quick Start Guide "out of the box" and TI online guidelines for this product. As you said XDS200 is fine but TVRef Pin is wrong and voltage doesn't exist there. How would we proceed as an end-user to run out-of-the-box demonstration then?

What would be the solution to get it running? Shall we contact with your reseller Mouser UK to obtain replacement of the module? Because it's bought recently to develop our project and see the feasibility of C66AK2H14 for further projects. Now it's causing a delay which effects our project deadline.

Many thanks,

Hakan

Hakan - I'm not too familiar with that specific EVM. I will bring this thread to the attention of the device experts.

Thanks

ki

Hi,

For k2H EVM:

• 12V, 7A adaptor is sufficient
• The USB on the board is for UART, the USB on the mezzanine card is for XDS200 JTAG
• The TI link for how to setup EVM HW is correct
• Things you can try is to replace with a shorter USB cable for JTAG, and unplug/plug then tighten the Mezzanine card in case the contact to the EVM is loose
• The BMC 1.0.2.6 is the latest, EVM Rev 4.0 is also the latest
• The EVM should shipped with the latest UCD
• Please try to see if you can update the BMC and UCD following the same HW setup link, we know some EVM has JTAG failure, but resolved after updating the BMC and UCD

If that still doesn't work, please contact the vendor for a replacement. I have an older K2H EVM and tested JTAG connection without problem.

[Start: Texas Instruments XDS2xx USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\a0xxxxx\AppData\Local\TEXASI~1\
CCS\ccs930\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
The library build date was 'Nov 25 2019'.
The library build time was '14:43:38'.
The library package version is '8.4.0.00006'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '13' (0x0000000d).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

This emulator does not create a reset log-file.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS2xx USB Debug Probe_0]

Regards, Eric

Hi,

Thanks for confirming that we followed all steps and it's up-to-date. It simply doesn't work out-of-the-box.

We contacted the vendor that service request is 562870. They told us the part is obsolete. They wait for TI's confirmation for replacement/refund.

Regards,

Hakan