• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 3464 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

problem to connect CCSv5 with xds100v3

Jay Hong
Intellectual 865 points

 

Hi.

I'm trying to connect CCSv5 and xds100v3. The target is dm365EVM from spectrum digital.

I set with the default configuration.

target configuration is as below.

Connect : Texas Instruments XDS 100v3 USB Emulator.

Board or Devide : EVMDM365.

 

After set like above, and click the Test Connection, some error messages come out.

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag.exe -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 'jioserdesusbv3.dll'.
The library build date was 'Oct 27 2011'.
The library build time was '17:12:35'.
The library package version is '5.0.520.0'.
The library component version is '35.34.38.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).

An error occurred while hard opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-501' (0xfffffe0b).
The title is 'SC_ERR_TEST_MEASURE'.

The explanation is:
The built-in scan-path length measurement failed.
The built-in scan-path reliability tests cannot be
performed without knowledge of the scan-path length.
Try specifying the scan-path lengths in the command-line
options or board configuration file of this utility or debugger.

Do I need to another setup?

Thanks.

Jay.

  • 0
    TI__Guru**** 159725 points

    Jay,

    Generally we only see people use XDS100v3 with cJTAG (1149.7) based devices.  Are you sure you have a v3 and not a v2?

    If it is a v3 you need to make sure it is set to operate in v2 mode.  If you go to your .ccxml file and click on the Advanced tab at the bottom you will see more details for your configuration.  Select the XDS100v3 in the tree on the left.  Now on the right you will see the properties for it.  Depending on which CCSv5 you are using the properties may look different but for me there is one called "The Converter Usage".  Make sure this is set to "Its bypassed, use 1149.1, mimic XDS100v2".  The option may be a bit different in your version.  

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 865 points

    Thank you John.

    It works now.

    I changed as you recommanded but it wasn't work.

    After set like you said, connection is fine but memory reference occur.

    so I change the clock 1Mhz to 7Mhz. It works!!!

    anyway I don't understand why it works.

    Jay.