TMS320F28035 Experimenter Kit and CCS V6 - communication problem

Leo, the reason I asked you to go through the infosheet is because of the Boot switch configuration. You need to check the switch configuration on the controlCard.

Also, is your docking station based debugger getting detected by your PC?

Hi Gautam,

I tried all 8 positions of Switches SW1 and SW2 - without success.

The Docking Station appears in the device Manager as USB Serial Port (COM24) and with USB-Controller as: TI XDS100 Channel A and TI XDS100 Channel B.

If I connect only my Spectrum Digital XDS100v2 zu the PC I don't get the COM-Port but the USB-Controllers also appear as TI XDS100 Channel A and TI XDS100 Channel B.

Best regards,
Leo

leopold rohrecker said:

Could there be a Driver Problem with experimenter kit FTDI chip?

Can be the issue. You can try re-programming the EEPROM and also go through the troubleshooting:

Hi Leopold,

This issue comes up rarely and its reason is not completely understood.  My best understanding is that it means that Windows is finding the driver, but the driver isn't working well with CCS.

1) I'm aware of some instances where this comes up as a result of using a Virtual Machine
(hypothetically, delays between the driver and the hardware may be causing an issue)
2) The following describes a resolution that, in at least two instances, has resolved the issue:
http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems#Generic_FTDI_failure


If you find that either resolves the issue - please let us know.  We can then report that this is a potential resolution with more confidence - and may enable the CCS team to better characterize the problem and potentially resolve it directly in the driver at some point in the future.

(the emulator built into the Docking Station is a xds100v1, as Gautam has mentioned)


Thank you,
Brett

Hi Brett and Gautam,

without exactly knowing what I did (:-) I deleted the "-rv" from the following instruction (guessing that this removes some Kind of reset) and than executed the modified instruction from a bat-File in dir uscif

dbgjtag -f testBoard.dat -rv -o -F inform,logfile=yes -S pathlength -S integrity

This might have helped at least a bit because now from "Test Connection" I get the answer below that I like better. I can also load and run a LED test blink program.

Regards,
Leo

[Start: Texas Instruments XDS100v1 USB Debug Probe_0]

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\ROHREC~1.LEO\AppData\Local\TEXASI~1\
    CCS\ti\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 'Feb 18 2015'.
The library build time was '23:56:50'.
The library package version is '5.1.641.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 38 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: Texas Instruments XDS100v1 USB Debug Probe_0]