On Fri, 25 Dec 2020, 14:27 Gerhard Sittig, <gerhard.sit...@gmx.net> wrote:
> On Thu, 2020-11-26 at 22:22 +0200, Christo Crause wrote: > > > > As discussed previously [1] there may be the odd FTDI based board with a > > corrupt EEPROM leading to sigrok not listing a working device because > > ftdi_usb_get_strings returns an error when retrieving the device > descriptor > > strings. > > > > The attached patch assigns default descriptor strings for vendor and > model > > if ftdi_usb_get_strings fails to retrieve a descriptor. > > > > [1] https://sourceforge.net/p/sigrok/mailman/message/37133778/ > > Have picked up that patch of yours, and slightly massaged it. > See libsigrok aa8e4959e24a. Thank you for reporting and addressing > the issue! > > Who's got FTDI based setups where scans failed before, and can test? > > > virtually yours > Gerhard Sittig > -- Gerhard, Thanks for fixing up and incorporating this patch. I can't seem to revert my board's eeprom to the original messed up state so unfortunately can't test this. Best regards, Christo
_______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
