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> 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
