Hi Christo, I have an FT232HQ here and it works perfectly with the command you used. sigrok-cli is version 0.7.0 from an Ubuntu 18.04. I attached my eeprom file, maybe you can flash it in your device to see if that helps. $ sudo ftdi_eeprom --flash-eeprom ftdi.conf should do the trick. Have you thought about that the chip may be a fake one? Those tend to have some strange behaviour and do not work as expected sometimes.
Best regards, Fabian Am 21.10.20 um 09:21 schrieb Christo Crause: > Hi Gerhard, > > Thanks for the lead. Poking around in fdti_la/api.c shows that the > error number printed with the ""Failed to get the FTDI strings"" message > seems to come from the ftdi_usb_get_strings call. Some further > searching revealed a seemingly related problem in libftdi: > http://libftdi.141977.n3.nabble.com/ftdi-usb-get-strings-failed-td4026147.html > which points to missing descriptor strings in a board similar to mine. > lsusb does report errors for some of the descriptors (iManufacturer 1 > (error), iProduct 2 (error), iSerial 3 (error)). I will try to edit the > onboard eeprom as suggested in the libftdi post to see if it solves the > issue (not sure what is expected by sigrok though). > > Best regards, > Christo > > On Wed, Oct 21, 2020 at 7:33 AM Gerhard Sittig <gerhard.sit...@gmx.net > <mailto:gerhard.sit...@gmx.net>> wrote: > > Error code -7 translates to SR_ERR_DEV_CLOSED, a device is > expected to be opened for an activity but isn't. > > A quick look at the scan related parts of > src/hardware/ftdi-la/api.c suggests that neither the scan() > routine nor its descendents open the device at this time. > Only for later use after the scan has completed. > > Can somebody who has access to the hardware take a look? > > > > _______________________________________________ > sigrok-devel mailing list > sigrok-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sigrok-devel >
eeprom.bin
Description: Binary data
# The Vendor ID and Product ID seem to identify a particular chipset # to target. I used the libftdi utilities and OS X USB Prober app to # poke around and figure out what numbers to use. vendor_id=0x403 product_id=0x6014 # The rest of the fields are settings which can be written to the # FT2xx with the --flash-eeprom option. # Max. power consumption: value * 2 mA. Use 0 if self_powered = true. #max_power=500 ########### # Strings # ########### #manufacturer="YOUR MANUFACTURER ID HERE" #product="YOUR PRODUCT NAME HERE" #serial="YOUR SERIAL NUMBER HERE" ########### # Options # ########### #self_powered=false # Turn this off for bus powered #remote_wakeup=false # Turn this on for remote wakeup feature #use_serial=true # Use the serial number string # Normally out don't have to change one of these flags #in_is_isochronous=false # In Endpoint is Isochronous #out_is_isochronous=false # Out Endpoint is Isochronous #suspend_pull_downs=false # Enable suspend pull downs for lower power #change_usb_version=false # Change USB Version #usb_version=0x0200 # Only used when change_usb_version is enabled #cha_vcp=false #cha_type=FIFO #chb_type=UART #eeprom_type=0x46 ######## # Misc # ######## # This is the relative filename that EEPROM contents will either be # read from or written to, depending on whether ftdi_eeprom is run # with the --read-eeprom or --flash-eeprom option. filename="eeprom.bin"
_______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
