Error connecting to the target: (Error -1025 @ 0x0)

Hi,

Please check with the JTAG Integration test by clicking on "Test Connection" in target configuration settings.

This would indicate whether there's issue with the PC-emulator communication or emulator-controller communication.

Regards,

Gautam

Hello Gautam,

1) "Test Connection" in target configuration settings does not exists inside UniFlash tool

2) The issue may come to the fact I was using the wrong device.

but My device sounds not supported by UniFlash (TMS570LSxxxx). Do you know where to find target files for this device ?

Thanks

Vincent

Vincent, 

Could you upload your ccxml file here?

Also, do you have CCS installed? If you do, please try connect to the target with this ccxml file and see if you get any errors.

Victor

Well, before running extra investigation, I suggest to some the first question : how can I update uniflash tool in order to find the TMS570LSxxxx into the list of supported devices ?

I'm installing CCS right now...

Vincent,

Okay I thought this was some other emulation error, but it seems we don't even have the device on ti.com catalog, so there is no support for it. Is this an old device?

Victor

No, it is a new device used for a new mass market automotive project...

Printed reference is TMP570LSxxxx

Vincent,

I will post on the Hercules internal forum and try to get some information from the BU.

Right now we don't have the support files from them to support this device in UniFlash/CCS

I will get back to you when i get some info from them, but it seems it could require emulation updates as well.

Victor

Here is the log file of the Connection Test feature.

I do feel the hardware chain is working fine, what about you ?

I believe we may just have this issue due to the wrong device file, right ?

Vincent

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]


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

C:\Users\VFLOUR~1\AppData\Local\.TI\693494126\
    0\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Aug 20 2013'.
The library build time was '22:56:19'.
The library package version is '5.1.232.0'.
The library component version is '35.34.40.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
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]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

There is no hardware for programming the JTAG TCLK frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

There is no hardware for measuring the JTAG TCLK frequency.

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 512 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 6 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.

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

This test will use blocks of 512 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 512 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]

Yeah this shows the scan chain is good.

However because we don't have the right device files it would fail when trying to setup a connection to the target core.

Hopefully all we need is the right device files. We would need to confirm with the BU on this.

Let's wait so.

Thank you

Hello Vincent,

The part number you referenced is not available publicly (I have redacted the part number in this thread).  Please contact your local TI contact to get the files needed to support this device in CCS and UniFlash.  You can give them my name as the person to contact.

Thank You John,

Just talked with our local TI contact.

Something I need to explain : I also tried to flash using the NowFlash Tool but it fails too.

That tool was provided to me with a customized cfg file including theTMS570LS31xx settings.

But unfortunately the tool fails to connect without being so clear about the failure.

Maybe we should try make this one working, because this works at the dev team side.

Here are the details :

Now flash version v3.42.03

Custom NowFlash CFg file :

6675.nowFlash.cfg

Used command line :

-bl -er -pr -ve  "E:.....\PBL_with_ecc.s37" -d -q -emu TIXDS100V2 -p 000 -cpu CORTEX_RXX -targets 1

Vincent,

Modify your command line with -d after -ve.  That enables more verbose output.

Also, what board are you connecting to?

Hello John,

The -d option is already set in the captured sequence.

I'm running with a basic XDS100v2