[flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?

[Anders Nelson]

Hi again,

I don't see details on what image file formats are supported - does
Flashrom use only binary files?

I see the ROM layout file explanation so I guess I can use that but it
would be nice to use an Intel HEX format if possible.

=]

--
Anders Nelson

+1 (517) 775-6129

www.erogear.com

On Sat, Nov 11, 2017 at 4:16 PM, Anders Nelson <anders.k.nelson at gmail.com>
wrote:

> We (you mostly) nailed it!:
>
> ===
>
> chrx at chrx:~/Github/flashrom$ ./flashrom -p ft2232_spi:type=2232H,port=A,
> divisor=4
> flashrom v0.9.9-86-ge1a960e on Linux 4.9.4-galliumos-braswell (x86_64)
> flashrom is free software, get the source code at https://flashrom.org
>
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Found Micron/Numonyx/ST flash chip "N25Q128..3E" (16384 kB, SPI) on
> ft2232_spi.
> No operations were specified.
>
> ===
>
> Thanks!
>
> --
> Anders Nelson
>
> +1 (517) 775-6129
>
> www.erogear.com
>
> On Wed, Nov 8, 2017 at 3:50 PM, Anders Nelson <anders.k.nelson at gmail.com>
> wrote:
>
>> Woooo looks like that did it! I don't have a flash device connected yet
>> but Flashrom certainly found the 2232.
>>
>> Thanks for the help, I hope I can contribute definitions for the flash
>> chips I use (Cypress/Spansion 128/256Mbit) if I find they aren't in the
>> database already.
>>
>> =]
>>
>> --
>> Anders Nelson
>>
>> +1 (517) 775-6129
>>
>> www.erogear.com
>>
>> On Wed, Nov 8, 2017 at 3:31 PM, Nico Huber <nico.h at gmx.de> wrote:
>>
>>> On 08.11.2017 16:11, Anders Nelson wrote:
>>> > Ohhh my god you're right - when I call the program as ./flashrom it
>>> runs
>>> > now!
>>> >
>>> > I am still getting an error though it's new:
>>> >
>>> > ===
>>> >
>>> > chrx at chrx:~/Github/flashrom$ ./flashrom -p ft2232_spi
>>> > flashrom v0.9.9-86-ge1a960e on Linux 4.9.4-galliumos-braswell (x86_64)
>>> > flashrom is free software, get the source code at https://flashrom.org
>>> >
>>> > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
>>> > Unable to open FTDI device: -3 (device not found).
>>> > Error: Programmer initialization failed.
>>>
>>> I guess, you have to specify the model (likely 2232H in your case). See
>>> the manpage `man ./flashrom.8`. If that doesn't work, you can check the
>>> output of `lsusb` if your board uses a special USB device id that we
>>> might have to add to flashrom.
>>>
>>> >
>>> > ===
>>> >
>>> > The FTDI device enumerates as /dev/ttyUSB0 and /dev/ttyUSB1... Is it
>>> > necessary to add a rule to udev or something to get Flashrom to find
>>> it?
>>>
>>> Unlikely.
>>>
>>> Nico
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.coreboot.org/pipermail/flashrom/attachments/20171111/b1ea8c7e/attachment.html>