• Locked Locked
  • Replies 8 replies
  • Subscribers 54 subscribers
  • Views 3061 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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 with xds200 on board emulator (TMDSEVM6657LS)

Sam lam
Prodigy 210 points

Other Parts Discussed in Thread: AM1802

Hi,

I ran into this problem when I tried to connect to the XDS200 emulator:

E_RPCENV_IO_ERROR(-6) No connection: DTC_IO_Open::dtc_io
Failed to open i/o connection (xds2xxu:0)

An error occurred while soft 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 '-250' (0xffffff06).
The title is 'SC_ERR_ECOM_EMUNAME'.

So, I followed the instructions on "processors.wiki.ti.com/.../XDS200 to update the firmware on the XDS200 emulator as suggested by "processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems".  And I got this problem during the update:

------------------------------------------------

$ ~/ti/ccsv6/ccs_base/emulation/specdig/xds2xx$ ./xds2xx_conf get xds2xxu 0
boardRev=2
ipAddress=0.0.0.0
ipConfig=dhcp
ipGateway=255.255.255.255
ipNetmask=255.255.255.255
productClass=XDS2XX
productName=XDS200
serialNum=00:0E:99:03:92:31
swRev=1.0.0.5
hostCPU=AM1802
emuCtrlType=Bit bang
extMemType=SDRAM
portUSB=true
portENET=false
portWIFI=false
portRS232=false
EnableUSBSerial=false
CurrentMeasure=false

$ ~/ti/ccsv6/ccs_base/emulation/specdig/xds2xx$ ./update_xds2xx.sh xds200
Updating CPLD
Error : test failed
.
Updating Firmware
ERROR: failed firmware update
Error : test failed
.
Rebooting
.
Reading Configuration
.
Check swRev is 1.0.0.5 or higher
.
Error : Failed to open port connection : xds2xxu : 0
Error : test failed
.
Hit any key to exit
--------------------------------------------------------------------------

The emulator seems to be dead now.  I don't see the device in the "lsusb" list anymore.  How do I go about fixing it?

Thanks,

Sam

  • TI__Guru* 81335 points

    ,

    Welcome to the TI E2E forum. I hope you will find many good answers here and in the TI.com documents and in the TI Wiki Pages (for processor issues). Be sure to search those for helpful information and to browse for the questions others may have asked on similar topics (e2e.ti.com). Please read all the links below my signature.

    We will get back to you on the above query shortly. Thank you for your patience.

  • TI__Guru* 81335 points

    Moving this thread over CCS forum for appropriate response.

    Till then you can work  with the XDS100 onboard emulator on TMDSEVM6657L EVM.

    Thank you.

  • in reply to Raja
    Prodigy 210 points

    Is there a XDS100 onboard emulator on the "TMSEVM320C6657LS" evaluation board?  I thought it only has the integrated "XDS200" emulator which I bricked with the update process?

    Thanks,

    Sam

  • in reply to Sam lam
    TI__Mastermind 43660 points

    Hello Sam,

    I think the XDS200 that you are talking about is a add on mezzanine emulator. Apart from this, there is a XDS100 on board emulator available on TMSEVM320C6657LS board. You can just remove the mezzanine emulator and use on board XDS100.

    Regards,
    Senthil

  • in reply to Sam lam
    TI__Guru* 81335 points
    Yes. Please unmount the xds200 mounted on the JTAG emulation header. Please refer the EVM TRM from the link provided above. Thank you.
  • in reply to Raja
    Prodigy 210 points
    Hi Raja,
    Thanks for the info. Found the XDS100 connection as recommended. However, I am having problem connecting to the board:

    I am using CCSv6 and with the XDS200 mezzanine unmounted. I ran a test connection from CCSv6 and I got the following errors. Did I configure the board incorrectly?

    [Start: Texas Instruments XDS100v2 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)]------------------------------------

    /home/sam/.ti/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 'libjioserdesusb.so'.
    The library build date was 'Sep 4 2015'.
    The library build time was '21:51:07'.
    The library package version is '6.0.14.5'.
    The library component version is '35.35.0.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 64 32-bit words.

    The JTAG IR instruction path-length was not recorded.

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    This test will use blocks of 64 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0

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

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

    The value is '-183' (0xffffff49).
    The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.

    The explanation is:
    The controller has detected a cable break far-from itself.
    The user must connect the cable/pod to the target.

    [End: Texas Instruments XDS100v2 USB Debug Probe_0]
  • in reply to Raja
    Prodigy 210 points
    Hi Raja,
    Thanks for the info. Found the XDS100 connection as recommended. However, I am having problem connecting to the board:

    I am using CCSv6 and with the XDS200 mezzanine unmounted. I ran a test connection from CCSv6 and I got the following errors. Did I somehow mis-configure the board?

    [Start: Texas Instruments XDS100v2 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)]------------------------------------

    /home/sam/.ti/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 'libjioserdesusb.so'.
    The library build date was 'Sep 4 2015'.
    The library build time was '21:51:07'.
    The library package version is '6.0.14.5'.
    The library component version is '35.35.0.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 64 32-bit words.

    The JTAG IR instruction path-length was not recorded.

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    This test will use blocks of 64 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0

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

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

    The value is '-183' (0xffffff49).
    The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.

    The explanation is:
    The controller has detected a cable break far-from itself.
    The user must connect the cable/pod to the target.

    [End: Texas Instruments XDS100v2 USB Debug Probe_0]
  • in reply to Sam lam
    TI__Guru**** 476741 points
    Hello,
    I believe it is an XDS100v1, not an XDS100v2. Try changing the connection type to see if that helps