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

FTDI Drivers for ICE3359v2

Garth Jackson
Prodigy 200 points
Other Parts Discussed in Thread: AM3359

When beginning to use the ICE3359v2 development board, I am encountering errors regarding the FTDI drivers when I try to connect the Tex Inst XDS100v2 emulator. I have connected to the ICE3359v1 boards without issue, but now I see the following error when attempting to connect to either of the development boards.

From "Test Connection":

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

D:\Users\204038~1\AppData\Local\.TI\693494126\     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 '-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.

 

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

And from the "Connect to Target" command:

IcePick_D_0: Error connecting to the target: (Error -151 @ 0x0) 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. (Emulation package 5.1.73.0)

 

(The xds100serial command line utility detects no emulators, and device manager detects ICE3359 boards, but fails on driver install)

Thanks

  • 0
    TI__Guru**** 441781 points

    Hi Garth,

    Garth Jackson said:

    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.

     

    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

    And from the "Connect to Target" command:

    IcePick_D_0: Error connecting to the target: (Error -151 @ 0x0) 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. (Emulation package 5.1.73.0)

    Check that the EEPROM is programmed correctly:

    http://processors.wiki.ti.com/index.php/XDS100#Q:_I_was_following_Debugging_JTAG_Connectivity_Problems_and_I_a_-151_SC_ERR_POD_OPEN_error_with_Dbgjtag.

    I use MProg.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 200 points

    Using Windows 7 x64, neither the ICE3359v1 or ICE3359v2 show a vendor ID, (VID), and product ID, (PID).

    The ICE3359v1 board appears in device manager as a USB device titled TI XDS100 Channel A & TI XDS100 Channel B. The details pane carries the same name with no VID/PID.

    The ICE3359v2 board appears under the "Other Devices" heading in Device Manager. It is titled ICE-EVM_V2\XDS100V2 for both channels with no VID/PID listed in the details pane.

    I can try updating the EEPROM as an experiment, but the does not appear to be a likely scenario.

  • 0 in reply to Garth Jackson
    Prodigy 200 points

    Loading latest FTDI drivers from here appear to have resolved the issue to some degree.

    http://www.ftdichip.com/Drivers/D2XX.htm

    Not sure why the ICEv1 board did not encounter the same connectivity issue, and flashing to SPI seems to be a little buggy. So I am running images from the SD card instead.

  • 0 in reply to Garth Jackson
    TI__Guru**** 169234 points

    Hi,

    Thanks for reporting your findings. The difference in the descriptions and VID/PID explain the difference in behaviour. The VID/PID is probably listed somewhere else, as they are mandatory for all USB devices. From inside the Device Manager, right-click on the board, select properties, then tab Details and select Hardware IDs on the drop down. You should see something on the value field that goes USB\VID_nnnn&PID_mmmm.

    The device drivers installed by CCS recognize FTDI-based XDS100 emulators, but some development boards rely on the standard FTDI device drivers and therefore require them to be installed separately. Unfortunately we at the CCS team do not have control on this.

    I apologize for the inconvenience,

    Rafael

     

  • 0 in reply to desouza
    Prodigy 200 points

    Thank you for the additional explanation Rafael! I do like to understand the root cause for a solution.

  • 0 in reply to Garth Jackson
    Prodigy 200 points

    Additionally, the .CCXML target configuration file will fail to connect to the target if "ICE_AM3359" is selected. Instead select "AM3359" to successfully connect to the CortexA8 target.