[flashrom] Problem with flashrom and FT2232 Port B

[Nico Huber]

On 22.03.2017 14:08, Zak wrote:
> Heya
> 
> Thanks for the reply, I'm using the latest version 1.2 for windows and I
> use this programmer with other softwares with that same dll and it works
> fine on both ports
> 
> But in case I tried with the old libftdi 0.18 and it's the same error

Sorry, I'm just poking in the dark. Another idea: Some other driver or
program might have claimed access to port B and is blocking it. flash-
rom doesn't know how to handle that, maybe your "other softwares" do.

Nico

> 
> Regards
> 
> Le 22 mars 2017 12:14, "Nico Huber" <nico.huber at secunet.com> a écrit :
> 
>> Hi Zak,
>>
>> On 21.03.2017 17:28, Zak wrote:
>>> Hello,
>>>
>>> I got flashrom compiled for windows and it works like a charm (has to
>>> tweet the code a little, add data for the chips i want to work with, add
>>> 4BA and fast rading for FT2232), it works perfectly fine but only for
>>> the port A (flashrom -p ft2232_spi:type=2232H,port=A)
>>>
>>> Using default programmer "ft2232_spi" with arguments "type=2232H,port=A".
>>> Calibrating delay loop... OK.
>>> Found Macronix flash chip "flashrom -p
>>> ft2232_spi:type=2232H,port=AMX25L25665E" (32768 kB, SPI)
>>> on ft2232_spi.
>>> Reading flash... (0% to done.)
>>>
>>> If i use the port B (flashrom -p ft2232_spi:type=2232H,port=B), i get
>>> this error
>>>
>>> Calibrating delay loop... OK.
>>> Unable to reset FTDI device (USB device unavailable).
>>> Unable to set latency timer (USB device unavailable).
>>> Unable to set bitmode to SPI (USB device unavailable).
>>> ftdi_write_data: -666, USB device unavailable
>>> Error: Programmer initialization failed.
>>>
>>> I get this error also if i try to compile with make
>>> CONFIG_DEFAULT_PROGRAMMER=PROGRAMMER_FT2232_SPI
>>> CONFIG_DEFAULT_PROGRAMMER_ARGS="type=2232H,port=B" to force port B
>>>
>>> I looked around i didn't find any solution to fix this, anyone could
>>> give me a hand?
>>
>> the problem probably lies within your (windows) version of libftdi. I'd
>> try another OS / libftdi to rule that out.
>>
>> Nico
>>
>>
>