I can not connect xds100v2 to DM365EVM w/ CCSv5.1.1.

Hello,

Did you run dbgjtag utility to validate your connection? If not, could you run it and post the results if it failed?

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

Thanks

ki

I am having the same issue with a DM368 design.

CCS Version: 5.1.1.00031

Blackhawk XDS100USBv2

DBGJTAG runs without an issue.  Here is the listing.  Any ideas where to look next?

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

-----[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 'Dec 19 2011'.
The library build time was '21:32:12'.
The library package version is '5.0.569.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 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).

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

Here is some additional info:

I have tried to access the system using an XDS510USB emulator from SD and SDConfigEx seems to run just fine.

Verify, Reset,and Emulator Test all run and produce good results.  Diagnostics Scan Verify both pass with 100 loops and no errors.

What follows is the responses from SDConfigEx:

<SNIP>

** Using emulation application from directory c:\ti\ccsv5\ccs_base\emulation\drivers
 **Emulator is reset

** Using emulation application from directory c:\ti\ccsv5\ccs_base\emulation\drivers
** Checking for a valid emulator/eZdsp

  $$ You are connected to:
  $$ EmuProductName=XDS510USB
  $$ EmuPortAddr=0x510
  $$ EmuPortMode=USB
  $$ ProductId=510
  $$ ProductVersion=84

** Checking emulator/eZdsp scan connection

** Emulator Test **

 $$ EmuProductName=XDS510USB

 $$ EmuPortAddr=0x510

 $$ EmuPortMode=USB

 $$ ProductId=510

 $$ ProductVersion=84

 ** Emulator Scan Test

   -- Found JTAG IR length of 6

   -- Found 1 JTAG device(s) in the scan chain

** Checking for a valid emulator/eZdsp
** Running diagnostic scan on EmuProductName=XDS510USB

** Checking emulator/eZdsp scan connection

Performed 100 test loops with 0 errors.

</SNIP>

Inside CCS 5.1 I get the following error when I try to use the Test Connection facility in the target configuration:

[Start]

Execute the command:

%ccs_base%/emulation/drivers/sdjtag.exe -f %boarddatafile% -v -X reset -X scantest

[Result]

** BoardFilePath: C:\Users\jcrist\AppData\Local\.TI\213602635\0\0\BrdDat\testBoard.dat
** Resetting Emulator
 -- Emulator is Reset
** Emulator Scan Test
     ERROR -- XDS510-USB Emulator not connected/enumerated

[End]

When I can get the emulator to run in debug I get the following error:

ARM9: GEL Output:

DM368 EVM ARM Startup Sequence

ARM9: GEL: Error while executing OnTargetConnect(): execution state prevented access at (*((unsigned int *) 0x01C408E4)&3) [evmdm368.gel:87] at OnTargetConnect() .

Any input that can help me narrow things down would be appreciated.

Thanks in advance!

Hi j-breeze, justin,

There are a lot of variables here. First thing to take into account is what boot mode your target is in. If uboot/xloader/linux is running on power up, it can impact your ability to debug with CCS. You would not want to use a gel file if trying to connect to the target and debug in those cases. Be aware of if you are booting from the SD card or flash, etc. Make sure you are in the right debug boot mode (check the documentation for your target on how to change the boot modes).

j-breeze - there are several known issues with DM365 and XDS100. I am trying to find out more on what exactly these issues are.

ki

Hi Ki-san,

I apologize for the delay.

I could connect xds100v2(Rev. B) to DM365EVM(Rev. E) & DM368EVM(Rev. G) after turning on adaptive clocking.
But, it took about "1-hour".

Though I changed the boot mode by selecting ONE NAND for not running UBL/U-Boot/Linux on power up, the connection still took about 1-hour.   

CCSv5 Test Connection button run without an issue.
 I also tried to connect xds510usb(Rev. B) to the EVMs.  It was no problem.
So, I decided not to use xds100v2 for ARM9 core.

Could you please refer information related my settings below? I hope it's useful.

- Emulator: xds100v2 Rev. B  (It has the latest CPLD code)
- CCS: v5.1.100031
- CCS Installed Software - TI Emulators: v5.0.623.0
- Target Configuration:
  - Basic
    - Connection        : Texas Instruments XDS100v2 USB Emulator
    - Board or Device: EVMDM365
  - Advanced
    - Connection Properties
      - Board Data File                                     : auto generate
      - Emulator Selection                               : Only one XDS100 installed
      - The JTAG nTRST Boot-Mode              : Disable - Both EMU pins remain Hi-z
      - The Power-On-Reset Boot-Mode       : Disable - Both EMU pins remain Hi-z
      - The JTAG TCLK Frequency (MHz)      : Adaptive with user specified limit
      - Enter a value from 488Hz to 30.0MHz: 1.0MHz
  - CPU Properties
    - initilization scripts     : evmdm368.gel  (v0.0.1, downloaded from SD web site)
    - Endianess                 : Little Endian
    - ARM Fast Download: On
    - Advanced Debug      : On
    - Arm9 Core                 : Auto-detect
    - Target Timeouts       : Very Slow

Best regards,
j-breeze