[flashrom] Fwd: Re: Problem with flashrom and FT2232 Port B

[Zak]

I got it to work

it was the dll, the problem happens when you use libftdi 0.18 or 0.20, 
other channels don't work. i used the latest libftdi1 1.3 & libusb 
1.0.20 (libftdi1-1.3git_devkit_mingw32_13Dec2015) from here: 
https://sourceforge.net/projects/picusb/files/, using the link provided 
on flashrom windows compile page 
(https://code.google.com/archive/p/picusb/downloads), if i take libftdi1 
1.0 i get an error with the file ftdi.h when i compile flashrom but 
libftdi1-1.3 works perfectly
Simply extract the folders bin, include & lib into you mingw and msys 
and compile should work fine

As for the drivers, you don't need anymore libusb-win32 wizard and also 
you don't need unsigned driver installation option enabled on your windows,
Just download zadig from the libusb driver installation part on: 
https://github.com/libusb/libusb/wiki/Windows, plug you ftdi board to 
the computer, run zadig, go to options "show all devices", then select 
your ftdi rs232 interface and chose WinUSB (not libusb!) as target 
driver and repeate for all of the interface you have depending how to 
amout of channels the ftdi has.

Voila everything should work fine

Maybe you want to update that in the instructions for to compile 
flashrom for windows,

Thanks for pointing the right direction nico


Regards


Le 23/03/2017 à 23:12, Nico Huber a écrit :
> Hi Zak,
>
> please always keep the mailing list in CC, you will get less attention
> otherwise.
>
> On 23.03.2017 12:16, Nico Huber wrote:
>> -------- Forwarded Message --------
>> Subject: Re: [flashrom] Problem with flashrom and FT2232 Port B
>> Date: Wed, 22 Mar 2017 18:01:18 +0100
>> From: Zak <zackwarrior at gmail.com>
>> To: Nico Huber <nico.huber at secunet.com>
>>
>> Yeah of course if another program is trying to access the device it can
>> explain the error but i would not be able to get the port a either,
>> since the device is used with another app, and i tryed it on few
>> different computers and still get the same error
> I was just guessing. The FT2232H has two separate USB interfaces, but
> maybe it's impossible to block one interface without the other, idk.
>
>> It's only on the port B, I already submitted this error a year aggo or
>> more but wasn't patched
> It's working fine on ArchLinux here (see attached log). I don't have
> access to a Windows installation and no intend to fix anything there.
> It's possible that you ask for something that only you are interested
> in. I guess you have to fix it by yourself then.
>
> Nico