• Resolved

TMDSHVMTRINSPIN: Cannot Connect or Identify USB Serial Port

Prodigy 110 points

Replies: 15

Views: 262

Part Number: TMDSHVMTRINSPIN

Hello,

I recently purchased a TMDSHVMTRINSPIN kit on Oct 16 2019 and I am just now setting up the device for the first time. I am attempting to get an initial run going with the GUI Composer InstaSPIN program that came with the included USB drive in the kit. I have followed the "Quick Start Guide: Evaluating InstaSPIN-MOTION (F2806xM) using the Graphical User Interface" document up to the point where I connect a USB port to my computer and launch the GUI. When I connect the USB, I cannot find the device in my Device Manager and when I launch the GUI, I get the error:

"ScriptingException: Error connecting to the target: emulation failure occurred"

I have a TMDSCNCD28069MISO control card installed with  SW1: UP-UP, SW2: DOWN-DOWN, SW3: UP-UP. I have verified that Jumpers J3, J4, J5, J7, J8, M3-J5, and J2 are properly configured. I have a brushless DC motor connected to ports U, V, and W. I have a banana cable from BS5 to BS1 connected. I have the 15 VDC power supply connected and the USB cable connected to J1 on the control card. When I plug in the 15 VDC power supply, M6-LD1 turns green as well as LD1 on the control card. When I connect the USB to J1, M3-LD1 turns green, however, my computer does not recognize any USB connected  (no recognition in the Device Manager). I did try connecting the AC plug after following these steps, but still no USB recognition.

How can I resolve this problem?

  • Can you try taking a look at this application report? It has some debug tips for common connectivity issues.

    www.ti.com/lit/spracf0

    Are you able to connect to the device in CCS?

    Thanks,

    Whitney

  • In reply to Whitney Dewey:

    When trying to connect in CCS, I set the connection to "Texas Instruments XDS100v2 USB Debug Probe", the Board/Device to "TMS320F28069", saved the configuration, then clicked the button to test the connection. This lead to the following output:

    [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)]------------------------------------
    C:\Users\username001\AppData\Local\TEXASI~1\CCS\
        ccs920\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'.
    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 '-716' (0xfffffd34).
    The title is 'SC_ERR_LIB_LOAD_SERDES_DRV'.
    The explanation is:
    Required dynamic library jscserdes could not be located.
    The library isn't on the search path.
    [End: Texas Instruments XDS100v2 USB Debug Probe_0]
     I have tried re-installing controlSuite, CCS, and MotorWare with the same output.
    In regards to the www.ti.com/lit/spracf0 document, Section 3.3 puts me on a path to "Reprogram Emulation Controller". That document then points to https://e2e.ti.com/support/microcontrollers/c2000/f/171/p/252873/889381#889381, but I am unsure how to exactly execute that reprogramming... Do I need to disconnect my TMDSCNCD28069MISO controlCard from the HVMTR kit and use one of the on-card usb connections? And how do I execute a reprogramming session? Or should I focus on resolving the suspected driver problem mentioned above?
    Any help would be appreciated
  • In reply to John Easum:

    jioserdesusb.dll should be in your CCS installation under \ccs\ccs_base\common\uscif. It should be included when you download CCS. Is it present and accessible?

    Whitney

  • In reply to Whitney Dewey:

    I can see the jioserdesusb.dll file in the \ccs\ccs_base\common\uscif directory. Interestingly, I see the same error message whether or not I have the USB cable connected to the HVMTR Kit

    John

  • In reply to John Easum:

    In an effort to further troubleshoot, I installed CCS on Ubuntu 18.04 and tried to connect. This time, I see the following error 

    [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/username001/.ti/ccs920/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'.

    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 '-151' (0xffffff69).
    The title is 'SC_ERR_FTDI_OPEN'.

    The explanation is:
    One of the FTDI driver functions used during the connect
    returned bad status or an error. The cause may be one or
    more of: no XDS100 is plugged in, invalid XDS100 serial number,
    blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
    Use the xds100serial command-line utility in the 'common/uscif'
    folder to verify the XDS100 can be located.

    [End: Texas Instruments XDS100v2 USB Debug Probe_0]

    This seems to point to what the www.ti.com/lit/spracf0 guide mentioned for reprogramming the emulation controller. What is the detailed procedure for reprogramming the FTDI FT2232 on the TMDSCNCDF28069MISO control card?

  • In reply to John Easum:

    One final follow up. I tried two different USB cables and ran the xds100serial command line utility in the common/uscif directory. Both times I had the following output in the command line:

    $ ./xds100serial
    Scanning for XDS100 emulators...

    No XDS100 emulators were found on the system.

  • In reply to John Easum:

    Have you tired connecting without being docked to the TMDSHVMTRINSPIN? You should be able to power the controlCARD through the micro USB while you connect over the mini USB.

    I'll look for more info on how to reprogram the FTDI chip. You can try looking at this page. I'm not sure how stale the information is...

    Whitney

  • In reply to Whitney Dewey:

    I am planning to pick up the needed USB cables today. I will follow up on that connectivity soon.

    John

  • In reply to John Easum:

    Okay after getting the proper USB cables, I removed the TMDSCNCD28069MISO controlCard from the TMDSHVMTRINSPIN kit. I connected both USBs to my Windows machine and tested the connection in CCS. It appears that I can connect to the card when it is isolated from the HVMTR kit. Here is my output:

    How can I now proceed?

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

    C:\Users\username001\AppData\Local\TEXASI~1\CCS\
    ccs920\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 'Aug 26 2019'.
    The library build time was '13:34:49'.
    The library package version is '8.3.0.00003'.
    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 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 64 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 64 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 XDS100v2 USB Debug Probe_0]

  • In reply to John Easum:

    I tried the link for  this page as you mentioned earlier. I was able to scan to find my device on the TMDSCNCD28069MISO controlCard, successfully erase the device (as prescribed), but it was not able to program the device. There is an error message stating "No devices found" when I click to program the FT2232 chip. However, I can perform a scan and it states

    Number Of Blank Devices = 1
    Number Of Programmed Devices = 0

    If i disconnect my card from the USB ports and re-scan, I see

    Number Of Blank Devices = 0
    Number Of Programmed Devices = 0

    Clearly it is seeing the device, but I cannot program it. One possible concern is that  this page is providing software for a FT2232C, while the part number on my TMDSCNCD28069MISO controlCard states FT2232HL.

    What else can I try?

    John