TMS320 DC/DC LED Dev Kit F28035 control card is not programmed and TI workaround to flash the micro does not work in CCS v5.5.0 or v4 that came with the kit.

Hi Robert,

Which version of XDS100 emulator have you selected in Target Configuration?

Regards,
Gautam

v1, but when that didn't work I tried v2 also.

Secondly, are the drivers installed properly? Did you check the device manager?

Hi Gautam,

Yes, the drivers were properly installed and according to Device Manager, there were no more recent versions available.

Drivers installed correctly and proper target configuration should be enough on debugger side. Check this wiki article:
processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems

Well,

I reviewed the wiki article and verified that the drivers were installed correctly and determined that the emulator is TDS100 v1. I deleted all the drivers and configuration files and re installed everything from scratch. No improvement. Here is the exact connection error:

Error connecting to the target:
(Error -1135 @ 0x0)
The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.
(Emulation package 5.1.232.0)

Here is the target configuration error report from the test connection utility. It shows the output stuck at all ones.

[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\RSTEPH~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 failed.
The JTAG IR instruction scan-path is stuck-at-ones.

The test for the JTAG DR bypass path-length failed.
The JTAG DR bypass scan-path is stuck-at-ones.

-----[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.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.

The JTAG IR Integrity scan-test has failed.

-----[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.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.

The JTAG DR Integrity scan-test has failed.

[End]

Can you try flashing a sample .out file through SCI instead?
C:\ti\controlSUITE\device_support\~Utilities\serial_flash_programmer

By this atleast we'll get to know whether the controller is functional or not.

Regards,
Gautam

Hi Gautam,

I found the original user's guide from the OEM, Crosshairs Embedded, and found that the TI Quickstart guide has the wrong jumper settings identified. They say for example "Remove any jumpers placed on [Main]-J6. This is exactly wrong as this jumper enables the JTAG chain. So, I was able to program the micro with the precompiled .out file. The problem now is that the GUI can't connect to the board. The ports show up in the "Setup Connection" window, but it won't connect.

thanks

Update:

I purchased a second kit from a different distributor and it worked fine right out of the box. So, I am able to move forward on the project, but now I'm stuck with the original non-functioning kit. Mouser won't accept it as RMA until someone from TI acknowledges that it is defective. I started a ticket with TI support but haven't heard anything back. Does anyone from TI check these support forums?

thanks,

Bob

Ohh.... Quick Progress within a day :)
So you need to wait for a TIers response.
All the best for that!

Goodluck & Regards,
Gautam

Well,

I contacted TI Support 2 weeks ago and just got this:

Thank you for your interest in Texas Instruments’ semiconductor products.  We value your support request.  We apologize for the delay in correspondence.

To serve you in a timely and efficient manner, TI is migrating support to our E2E™ (Engineer to Engineer) Community Forums.  This community is home to thousands of discussions in which you can search for answers, post questions, and collaborate with fellow engineers and TI experts.

Please direct your current and future questions to the E2E forums through the following link: http://e2e.ti.com.  

We appreciate your business and look forward to collaborating with you in the E2E forum.

So, here I am back in this forum. As I mentioned to Brett, I purchased a second kit from a different distributor which worked perfectly right out of the box. So now I have met my technical need and have a usable test bed, but am still out 350 bucks or so for the defective one and the distributor won't issue an RMA until a TI representative acknowledges that there is a problem with it.

Any help?