TMDX570LS20SUSB: Unable to connect to target

Hello Lena,

What worries me is that you mention your setup to be working fine a few days ago... If the only thing that changed is that you used the HET IDE to develop code, I can't think of anything that would have changed in your CCS or nowFlash setup...

Can you send me a snapshot of the nowFlash utility setup?

What happens in CCS when you hit the "Test Connection" button in the Target Configuration window?

Best regards,

Luc

Hello Luc,

thank you for your answer. Here the screenshot of nowFlash:

And that is the result of pressing "Execute":

Where can I find the button "Test connection"? I can't find it in the Target Configurations view.

I don't know, if this is important: the microcontroller TMS570LS doesn't get hot, only the "EFTDI" at the backside gets only warm, but when it worked, every IC, microcontroller and condensator got very hot after a short time.

Kind regards,

Lena

Lena,

Can you try in CCS the following?

Select from the top menu, View->Target Configuration.
From the target configuration windows, double click on TMS570LS20216SPGE (or the configuration you use for this device)

If you don't have a valid configuration, you can create one by doing a right click in the target configuration windows and select New Target Configuration.
Use the following example to create this new configuration.

When it is created and saved, click on "Test Connection".
You can copy paste the result and send it so I can check what is going on.

Lena Neumeier said:

Hello,

I'm developing on a TMDX570LS20SUSB kit with XDS100 and have a problem:

When I want to flash, I get the following errors:

in nowFlash v3.42: Error 199 - Unable to connect to target on port address 0x000

in code Composer Studio v4.2.3:

Error connecting to the target:
(Error -151 @ 0x0)
This utility failed to open the adapter for a custom emulator.
The adapter returned an error.
(Release 5.0.333.0)

I've read this thread: http://e2e.ti.com/support/microcontrollers/hercules/f/312/t/130226.aspx   and tried the hint of Mr. Weng in the verified answer (I used the Reset-button), but it doesn't work. (By the way: when I click the Reset-Button, no blue LEDs are blinking any more)

I also reinstalled the driver and the CCS, but it doesn't work, too.

In the microsoft device manager, the kit is listed under the USB-Controller as USB Serial Converter A and B and one USB-Verbundgerät  - all three devices without errors.

The crazy thing about it: it worked a few days ago! In the meantime, I developed with the "HET Simulator" - but that doesn't matter, does it?

Mr. Weng also wrote something about the C5 on the back of the board - I found it, but am I allowed to short it? Can I destroy the board by shorting the C5?

HW: Shorting C5 has no risk at all. It is the nRST signal. As I said in that post, short C5, run nowFlash, wait until 'connect' showing up in the DOS/command windows, release 'short' C5,... Try a couple of times if it does not work the 1st time. It provides a workaround for erasing bad code in the flash (e.g PLL frequency is so high that CPU is dead).

I hope, you can help me.

Thank you in advance.

Kind regards,

Lena

Hello Jean-Marc,

I haven't this button:

Hello again

I shorted the C5 ca. 30 times and the only thing happened was the PC said "new hardware found" and "connection too slow for hardware-device" because it's a fast usb-device and the connection is none. After these messages I tried a few times to short the C5, but nothing happened anymore. Is the connection to the PC to slow?

I tried also to connect the device to another usb-port. Then the device-manager showed additional two USB Serial Ports and (as before too) USB Serial Converter A and B and one "USB-Verbundgerät". Here a screenshot of my device-manager (red framed devices appear when I connect the device):

Are my connections OK?

Kind regards,

Lena

Hi Lena,

I don't understand how it is possible that you don't have a 'Test Connection' button in the Target Configuration window.

Can you sent me the details on your target configuration? Here is what I have for TMS570LS20216ZWT:

Hi Luc,

my screenshot of the target configuration:

Does it look so because of the version (4.2.3)?

Hi,

now I've installed CCS 5, my target configuration is the same as in the screenshot I sent before and the "Test Connection" result in this message:

[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:\DOKUME~1\neuml\LOKALE~1\ANWEND~1\.TI\
    213602635\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'.

An error occurred while soft opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-151' (0xffffff69).
The title is 'SC_ERR_FTDI_OPEN'.

The explanation is:
One of the FTDI driver functions used during
the connect returned bad status or an error.
The cause may one or more of: invalid emulator serial number,
blank emulator EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the emulator can be located.

[End]

I searched the folder "common\uscif" and found in it the files "dbgjtag.exe" and "jioserdesusb.dll" so the emulator is installed. How can I see that it is correct installed?

And the PC of my colleague (Windows 7) detects the device as a TI-device. Why doesn't detect my PC (Windows XP) this device?

I hope you can help me.

Kind regards,

Lena

Hello again,

meanwhile I've connected CCS to the IcePick (as described here: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/195554.aspx)
The result:

When I pressed the Reset-button, the "Not In Reset" changes for ca. a second to "In Reset". Because of this change, I tried to reset the device before flashing with nowflash (as before), but with no success. And I got another test connection message - but I haven't saved it. But it was like that: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/195554.aspx (I even tried to connect the device to another PC-port - with the same result)

Then I re-installed the drivers in the device manager, the PID/VID values (as here: http://processors.wiki.ti.com/index.php/XDS100#Q:_How_can_I_check_if_the_VID.2FPID_for_the_EEPROM_are_programmed_correctly.3F) and the driver, downloaded from http://www.ftdichip.com/FTDrivers.htm

Now, I even can't connect to IcePick!? I don't understand it!

When I test the connection I get the other message as before!
Who can help me?

I heard that the device doesn't work on 32bit-systems??? When this is true, where can I find the right drivers for a 32bit-system?

Please help me! I'm at my wit's end!

Hello,

meanwhile I think it's a problem with the driver: I found out that the right driver is already installed but wasn't used.

In this thread I uploaded a screenshot of the device manager and inserted more information.

I hope you can help me.

Lena

http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/312/0511.XDS201EEPROM2.ept

Can you read the EEPROM image using MProg (google to download it)? I uploaded the correct image. PLease compare them.

Haixiao

Yes, I read it and it was sth. strange with "Beagle Bone", then I programmed it and it says:

Read EEPROM successful Device 0
0000 : 01 08 03 04 D0 A6 00 02 80 C8 08 00 CC 0C 9A 06   .. .. .. .. .. .. .. ..
0010 : A0 4A EA 12 00 00 00 00 56 00 00 00 00 00 00 00   J. .. .. .. .V .. .. ..
0020 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   .. .. .. .. .. .. .. ..
0030 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   .. .. .. .. .. .. .. ..
0040 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   .. .. .. .. .. .. .. ..
0050 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   .. .. .. .. .. .. .. ..
0060 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   .. .. .. .. .. .. .. ..
0070 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   .. .. .. .. .. .. .. ..
0080 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   .. .. .. .. .. .. .. ..
0090 : 00 00 00 00 00 00 00 00 00 00 06 03 54 00 49 00   .. .. .. .. .. .. .T .I
00A0 : 4A 03 54 00 65 00 78 00 61 00 73 00 20 00 49 00   .J .T .e .x .a .s .. .I
00B0 : 6E 00 73 00 74 00 72 00 75 00 6D 00 65 00 6E 00   .n .s .t .r .u .m .e .n
00C0 : 74 00 73 00 20 00 49 00 6E 00 63 00 2E 00 58 00   .t .s .. .I .n .c .. .X
00D0 : 44 00 53 00 31 00 30 00 30 00 20 00 56 00 65 00   .D .S .1 .0 .0 .. .V .e
00E0 : 72 00 20 00 32 00 2E 00 30 00 12 03 54 00 49 00   .r .. .2 .. .0 .. .T .I
00F0 : 56 00 56 00 50 00 43 00 58 00 4A 00 00 00 10 28   .V .V .P .C .X .J .. ..

Then I disconnected and connected the device, restarted the PC and now the device manager uses the right driver (VID=0403, PID=A6D0):

But nowFlash shows the same error (Error 199 - Unable to connect to target on port address 0x000)

When I test the connection in CCS it shows this:

[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:\DOKUME~1\neuml\LOKALE~1\ANWEND~1\.TI\
    213602635\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 'Apr  2 2012'.
The library build time was '21:41:04'.
The library package version is '5.0.681.0'.
The library component version is '35.34.39.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]

Why can't it find the hardware?

Then I tried to connect to IcePick (the JTAG-LED blinks):

When I press the Reset-button, the Clock and Power go off, the clock down shortly goes to active, the Not In Reset changes shortly to In Reset

When I try to connect to the target, I get this Error (it doesn't matter if I press the Reset-button):

Sorry it didn't paste the screenshot:

When I change the TCLK to 488Hz (in CCS) and test the connection, I get this message:

[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:\DOKUME~1\neuml\LOKALE~1\ANWEND~1\.TI\
    213602635\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 'Apr  2 2012'.
The library build time was '21:41:04'.
The library package version is '5.0.681.0'.
The library component version is '35.34.39.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 JTAG IR instruction path-length was not recorded.

-----[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

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-154' (0xffffff66).
The title is 'SC_ERR_FTDI_WRITE'.

The explanation is:
One of the FTDI driver functions used to
write data returned bad status or an error.

[End]

What does this mean?

When I change the TCLK to 1kHz, I get the same message except for the last lines:

This error is generated by TI's USCIF driver or utilities.

The value is '-183' (0xffffff49).
The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.

The explanation is:
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.

[End]

But when I connect the target direct to the PC or to another USB-port I get the same errors