Can Not Connect To F28069 with xds100v2 using CCS 4.2.4

Hi Jerry,

What are the results when you press the 'Test Connection' button in the ccxml file for you target?

Thanks

ki

Hi ki,

   It looks like the 'Test Connection' button is in CCS5.  I'm running CCS4.2.4.  I tried running the bdgjtag.exe and a dos screen flashes up then disappears.

   I have tried installing CCS5, however, I ran into a licensing problem where I could only get a 90 day license.  When I install CCS4 I get the option of the bundle license so I went back to CCS4

Thanks,  Jerry

Sorry, you are right. It is only for v5. 

gerald garland said:

I tried running the bdgjtag.exe and a dos screen flashes up then disappears.

You need to run it from the DOS command window with some parameters. See the below wiki for more details:

http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

Thanks

ki

Ki, 

 Here's what I got:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

Z:\>"C:\Program Files\Texas Instruments\ccsv4\common\uscif\dbgjtag.exe" -f "C:\D
ocuments and Settings\garlage\Local Settings\Application Data\.TI\2067366409\0\B
rdDat\ccBoard0.dat" -rv -S pathlength

-----[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 'Jun 14 2011'.
The library build time was '22:23:33'.
The library package version is '5.0.429.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 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.

Z:\>

Thanks, Jerry

gerald garland said:

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.

The JTAG scan connection is not working. Do you have another target to try the same emulator and CCS configuration with?

Ki,

   This is the only target board built.

  I can see the TDI, TCK, and TDO toggling on a scope.

   Is there an incompatability with the TMS vs the TMX versions?  I had a problem a few years ago with flashing a TMX28335 that worked on a TMS28335.

  I'm going to have the TMX swapped with a TMS. 

Thanks, Jerry

gerald garland said:

Is there an incompatability with the TMS vs the TMX versions? 

I don't think it is even getting that far enough to actually read the device on the scan chain but I am not an expert with regards to this.

I will tag the thread to the correct experts however...

Thanks

ki