Error connecting to the target (custom board with C5505) :(Error -1063 @ 0x0)Device ID is not recognized or is not supported by driver

Dr.Abhishek Sen

Other Parts Discussed in Thread: TMS320C5505, TMS320VC5505, TMS320VC5402

I am trying to connect a custom board (based on the schematics of EVM5505) with TMS320C5505 with an XDS100v1 emulator.

After starting CCSv4.1.1 , while trying to connect to the target board , i get the following error:

"Error connecting to the target:(Error -1063 @ 0x0)Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver.(Release 5.0.333.0)"

The same emulator works fine with a different EVM5505 , manufactured by Spectrum Digital with an onboard TMS320VC5505, so the drivers for the XDS100v1 emulator are definitely working fine.

1. The error message is written above.

2. CCS version is 4.1.1.

3. CCS Installation directiory is C:\ccs4

4. .ccxml file found in "C:\Users\Abhishek\Desktop\Targetconfig\Newtargetconfiguration.ccxml"

5. I am using the evm5505.gel file, found in the documentation of spectrum digital. http://support.spectrumdigital.com/boards/evm5505/revd/

6. Emulator used XDS100v1

7. It is a custom board designed with reference to EVM5505. The difference being that the EVM5505 used for prototyping had a VC5505 , while the custom board has a C5505. Appropriate changes have been made accordingly in the hardware based on documentation on migration from VC5505 to C5505.

8. Target connector is a 14 pin JTAG.

9. Please find below schematic snapshot of JTAG connections, the pins are connected to appropriate pins of C5505.

10. Host operating system : Windows 7, 64 bit

11. A JTAG diagnostic was run using the dbgjtag.exe GUI. All tests viz. Scan Path Length, Broken Path and Integrity test passed successfully. please find log below.

12. I am using the on chip RTC oscillator, and SPI(Atmel25256) and I2C EEPROMs(24W256) for memory.

Since, the dbgjtag diagnostics went fine,it makes me think that the hardware is probably fine. Is the problem the gel and pll settings, maybe the difference is that the EVM5505 with which the emulator works fine has a VC5505 on board, where as our custom board has a C5505? If yes, can i get the appropriate gel file ?

Please correct me if i am wrong!

A quick response would be VERY helpful, as i am on a deadline!

Thanks Abhishek

Log of dbgjtag test:

-----[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 'Feb 28 2011'.

The library build time was '22:16:13'.

The library package version is '5.0.333.0'.

The library component version is '35.34.29.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 now 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).

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

-----[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 'Feb 28 2011'.

The library build time was '22:16:13'.

The library package version is '5.0.333.0'.

The library component version is '35.34.29.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 now 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).

-----[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 38 bits.

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

The JTAG DR bypass path-length is 1 bits.

-----[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 'Feb 28 2011'.

The library build time was '22:16:13'.

The library package version is '5.0.333.0'.

The library component version is '35.34.29.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 now 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).

-----[Perform the Broken Path 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

All of the values were scanned correctly.

The JTAG IR Broken Path scan-test has succeeded.

-----[Perform the Broken Path 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

All of the values were scanned correctly.

The JTAG DR Broken Path scan-test has succeeded.

-----[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 'Feb 28 2011'.

The library build time was '22:16:13'.

The library package version is '5.0.333.0'.

The library component version is '35.34.29.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 now 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).

-----[Perform the Given Data scan-test on the JTAG IR]-----------------------

This test will use blocks of 512 32-bit words.

This test will be applied just once.

It uses the first 1 of the 10 different test-cases.

Do a test using 0x5533CCAA.

Scan tests: 1, skipped: 0, failed: 0

All of the values were scanned correctly.

The JTAG IR Given Data scan-test has succeeded.

-----[Perform the Given Data scan-test on the JTAG DR]-----------------------

This test will use blocks of 512 32-bit words.

This test will be applied just once.

It uses the first 1 of the 10 different test-cases.

Do a test using 0x5533CCAA.

Scan tests: 1, skipped: 0, failed: 0

All of the values were scanned correctly.

The JTAG DR Given Data scan-test has succeeded.

over 14 years ago

0 Steve Tsang over 14 years ago

TI__Mastermind 23785 points

Can you quickly try updating your CCS?

regards.

0 Dr.Abhishek Sen over 14 years ago in reply to Steve Tsang

Prodigy 220 points

Steve,

I'll quickly update ccs and see if it is working.

Regards

Abhishek

0 Anand CV over 14 years ago in reply to Dr.Abhishek Sen

Prodigy 220 points

Hi Abhishek,

If updating ccs is not helping, try doing the following.

Fullscreen 5327.XDS100v1.txt Download

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">




<configuration XML_version="1.2" id="Texas Instruments XDS100v1 USB Emulator_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS100v1 USB Emulator_0" href="connections\TIXDS100usb_Connection.xml" id="Texas Instruments XDS100v1 USB Emulator_0" xml="TIXDS100usb_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS100v1 USB Emulator_0">
            <instance XML_version="1.2" href="drivers\tixds100c55x.xml" id="drivers" xml="tixds100c55x.xml" xmlpath="drivers"/>
            <property Type="choicelist" Value="0" id="The JTAG TCLK Frequency (MHz)"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="EVM5505_0" href="boards\evm5505.xml" id="EVM5505_0" xml="evm5505.xml" xmlpath="boards"/>
            </platform>
        </connection>
    </configuration>
</configurations>

can you upload the content of the ccxml file. (open it in a text editor and copy paste).

Also try the attached ccxml configuration file.(please rename it to XDS100v1.ccxml before using)

0 Dr.Abhishek Sen over 14 years ago in reply to Anand CV

Prodigy 220 points

Hi Anand and Steve,

I tried updating the drivers as well as the above ccxml config. The problem persists. To reiterate the problem, the XDS100v1 when used with EVM5505 works fine, but gives an error when connected to a custom target board.

I am using the ccxml below

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<configurations XML_version="1.2" id="configurations_0">

<configuration XML_version="1.2" id="Texas Instruments XDS100v1 USB Emulator_0">

<connection XML_version="1.2" id="Texas Instruments XDS100v1 USB Emulator_0">

<instance XML_version="1.2" href="drivers\tixds100c55x.xml" id="drivers" xml="tixds100c55x.xml" xmlpath="drivers"/>

<property Type="choicelist" Value="1" id="The JTAG nTRST Boot-Mode"/>

<property Type="choicelist" Value="1" id="The Power-On-Reset Boot-Mode"/>

<platform XML_version="1.2" id="platform_0">

<instance XML_version="1.2" desc="TMS320C5505_0" href="Devices\c5505.xml" id="TMS320C5505_0" xml="c5505.xml" xmlpath="Devices"/>

</platform>

</connection>

</configuration>

</configurations>

0 Steve Tsang over 14 years ago in reply to Dr.Abhishek Sen

TI__Mastermind 23785 points

i want to get 2 things clear:

What version of CCS4 you are running now after the update?

You have 2 boards, one is a Spectrum Digital EVM with an onboard TMS320VC5505 chip which works; the 2nd is your custom EVM with TMS320C5505 chip that cannot connect. Right?

The evm5505.gel file found in the documentation of spectrum digital http://support.spectrumdigital.com/boards/evm5505/revd/ works for TMS320C5505.

Regards.

0 Dr.Abhishek Sen over 14 years ago in reply to Steve Tsang

Prodigy 220 points

Steve,

1. After the update i am using CCSv4.2.4.

2. Yes, that is correct, i have 2 boards, a SD EVM5505 with on board VC5505 which works fine with the XDS100v1 Emulator. The custom board with onboard C5505 is unable to connect and still gives the error in the first post, although the custom board clears all the dbgjtag tests.

I am using the same gel file for both boards.

Am still clueless of the problem.

Thanks

0 Steve Tsang over 14 years ago in reply to Dr.Abhishek Sen

TI__Mastermind 23785 points

Thanks. Now we are sure both CCS and Gel are good. And it connects with SD EVM but not the custom board.

Is the error message still about the driver?

Regards.

0 Dr.Abhishek Sen over 14 years ago in reply to Steve Tsang

Prodigy 220 points

Steve,

The error is still the same.

These are the following things i tried:

1. Different JTAG TCLK frequencies( in the Advanced target config settings)

2. Reinstalling CCS.

3. Checking all the voltage supplies and JTAG pins on the custom board using an oscilloscope.

There are two questions:

1. The TDO (Pin7 of 14 pin jtag) Pin voltage on the SD EVM board is high(3.3V) where as the custom board TDO Pin voltage is low (0V), Is this something significant ?

2. Could a faulty reset sequence be the cause of the custom board passing the dbgjtag tests but not connecting to CCS ?( I have not checked the resets yet )

Do let me know.

Thanks !

Abhishek

0 Steve Tsang over 14 years ago in reply to Dr.Abhishek Sen

TI__Mastermind 23785 points

TDO low is fishy. JTAG spec states a pull-up; and C5505 I/O for TDO has internal pull-up. Your board is pulling it low somehow.

Regards.

0 Dr.Abhishek Sen over 14 years ago in reply to Steve Tsang

Prodigy 220 points

Steve,

There was problem with the reset initialization on the hardware, after a manual reset, the above error message goes away. But, the controller is still not able to connect, the error message showing up now is

""C55xx: Error connecting to the target: (Error -1023 @ 0x5F) Requested JTAG operation failed. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Release 5.0.333.0) "

I tried setting the TCLK settings to lower values, but it does not seem to work.

Any ideas would be very helpful!

Abhishek

0 Dr.Abhishek Sen over 14 years ago in reply to Dr.Abhishek Sen

Prodigy 220 points

Steve, Anand,

The problem is solved ! All the errors were due to an improper reset signal.

My hardware had an error where the reset IC was monitoring 3.3V instead of the V Core (1.3V). As a result the reset was asserted high before the core got powered up.

A manual reset, with the reset pin grounded at start-up followed by the reset pin in Hi-Z solves all the error messages.

Thanks for the help !

Abhishek

0 Wang Guangcong over 12 years ago in reply to Dr.Abhishek Sen

Prodigy 20 points

Hello

Abhishek,

My board(vc5402) has the same problem as yours,but I still can't solve the problem by reading "with the reset pin grounded at start-up followed by the reset pin in Hi-Z solves".Can you explain it more detailly,thank you!

Guangcong

0 Steve Tsang over 12 years ago in reply to Wang Guangcong

TI__Mastermind 23785 points

Are you using the Spectrum Digital EVM320VC5402 EVM? Are you not able to connect CCS? Have you configurated CCS correctly?

Regards.

0 Wang Guangcong over 12 years ago in reply to Steve Tsang

Prodigy 20 points

Steve

Thanks for your answer,my board is tms320vc5402,and I can't connect ccsv4 or ccsv5 .The error :

0 Steve Tsang over 12 years ago in reply to Wang Guangcong

TI__Mastermind 23785 points

Can you post your target configuration? Are you using the SD's EVM320VC5402 EVM's onboard 14-pins JTAG interface?

Regards.

Processors

Processors forum

Error connecting to the target (custom board with C5505) :(Error -1063 @ 0x0)Device ID is not recognized or is not supported by driver