• State Resolved
  • Locked Locked
  • Replies 13 replies
  • Subscribers 54 subscribers
  • Views 5663 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.

Error connecting my TMS320

Dru Steeby
Intellectual 410 points

Hi,

I'm new to CC and TI chips and I'm having an error that I cannot figure out.

I'm using CC v5 and windows 7 64 bit. I get this error message everytime I try to test the connection over USB to my board.

[Start]

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\JRM\AppData\Local\.TI\213602635\
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 'jioserdesusbv3.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 '-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 one or more of: invalid emulator serial number,
blank emulator EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the emulator can be located.

[End]

Any help is appreciated. Thanks!

 

  • 0
    Intellectual 410 points

    Here is what I get when I run xds100serial.exe, seems that it can't find any emulators. 

  • 0
    TI__Guru**** 171104 points

    Hi,

    This error indicates that your OS does not have the device drivers installed for the XDS100 or is not being properly recognized. Check some tips at the page below:

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

    Also, if you are using BeagleBone, please check this thorough discussion where several issues may be applicable to your system as well.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 410 points

    First issue I see is that these items are not showing up in my device manager after installing CC v5.2:

     

    and the note they give about it is "Check your Windows System Devices. When properly installed, the XDS100 should look like the below image. If the XDS100 does not show up in the Windows device manager, then it is likely that the XDS100 was not programmed properly (contact manufacturer) or that there is a conflict with another FTDI based USB device (see FAQ below for details)."

  • 0 in reply to Dru Steeby
    TI__Guru**** 171104 points

    Hi,

    The installation of the first driver (XDS560) is disabled by default in a CCSv5.1+ install, therefore it should only show if it was explictly installed (CCSv4 and v5 pre-release versions always installed this driver, therefore the warning).

    The installation of the XDS100 driver is checked by default, but the fact that the XDS100 ports are not showing may indicate two scenarios: either the drivers were not properly installed or your system is somehow not able to recognize and install the device drivers for the emulator.

    CCSv5 keeps a copy of the XDS100 device drivers in the directory below; you can try to re-run the installer (DPInst32 or DPInst64, depending on your system), disconnect and re-connect the board to see if the drivers were picked up.

    C:\ti\ccsv5\ccs_base\emulation\windows\xds100_drivers\ftdi

    If you still see an unrecognized device (or see two devices named USB Serial Converter A and USB Serial Converter B) listed on the device manager, it is possible that your emulator is somehow configured for the standard FTDI VID/PID. You then need to configure it back to the TI VID/PID (check section 5.2 of the XDS100 wiki page) and see if the drivers are installed. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 410 points

    Hi,

    I made sure that when I installed CCS v5.2 that I checked every single option that I could and installed everything. 

    I went to "C:\ti\ccsv5\ccs_base\emulation\windows\xds100_drivers\ftdi" and ran DPInst64, it tells me that the drivers are installed and ready to go. 

    Below is a screenshot of my device manager, I don't see any device, not any that are "unrecognized" or "USB Serial Converter A or B"

  • 0 in reply to desouza
    Intellectual 410 points

    Here are some more screenshots: 

  • 0 in reply to desouza
    Intellectual 410 points

    and a few more:

  • 0 in reply to Dru Steeby
    TI__Guru**** 171104 points

    Hi,

    What device and board are you using? The reason of my question is because the screenshot below indicates you are using a F28x eZdsp kit, which sports a XDS510USB emulator from Spectrum Digital, and not a XDS100.

    If that is your case, then from inside the target configuration editor, set the Connection to Spectrum Digital DSK-EVM-eZdsp onboard USB Emulator and select the device of your kit.

    Dru Steeby said:

    Below is a screenshot of my device manager, I don't see any device, not any that are "unrecognized" or "USB Serial Converter A or B"

    Hope this helps,
    Rafael

  • 0 in reply to desouza
    Intellectual 410 points

    Yeah that's correct. In the target manager I switched the emulator and this is what I get when I run a test connection:

    My USB is connected, my board is powered up and I made sure that I installed all of the emulators that came with CC. Still not sure what the problem is.

  • 0 in reply to Dru Steeby
    TI__Guru**** 171104 points

    Are you sure you selected the connection I mentioned before? The reason is the Test Connection button is greyed out when I select it.

    When you launch the debugger, the box below appears at the bottom right of the screen, indicating the emulator is being initialized:

    If everything is correctly setup and no box is shown, at this point I would start inspecting the USB connections or even the Control Panel to see if the device driver initialized properly.Try to disconnect/reconnect the emulator, preferrably to another USB port on your PC and to one that is not part of a hub (if you have one).

    At last, if you are using a Virtual Machine (VMware or Virtualbox) additional steps may be required to connect the emulator to the guest OS. Not sure if that is your case, though.

    I am running out of ideas on what may be happening in your system, but I will reply here if I think of anything else that may be happening in your case.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 410 points

    Got it working, thanks. Was just using the wrong emulator. 

  • 0 in reply to desouza
    Prodigy 30 points

    i use XDS100 and i have same problem