flashrom>flashrom -V -p buspirate_spi:dev=com19 -c "MX25L6
445E" -w 4flash.bin
flashrom v0.9.7-r1781 on Windows 6.1 (x86)
flashrom is free software, get the source code at http://www.flashrom.org
flashrom was built with GCC 4.8.2, little endian
Command line (7 args): flashrom -V -p buspirate_spi:dev=com19 -c MX25L6445E
-w 4
flash.bin
Calibrating delay loop... OS timer resolution is 1000 usecs, 1629M loops
per sec
ond, 10 myus = 0 us, 100 myus = 0 us, 1000 myus = 1000 us, 10000 myus =
10001 us
, 4000 myus = 4000 us, OK.
Initializing buspirate_spi programmer
Baud rate is 115200.
Detected Bus Pirate hardware v4
Detected Bus Pirate firmware 6.2
Using SPI command set v2.
SPI speed is 8MHz
Raw bitbang mode version 1
Raw SPI mode version 1
The following protocols are supported: SPI.
Probing for Macronix MX25L6445E, 8192 kB: probe_spi_rdid_generic: id1 0xc2,
id2
0x2017
Found Macronix flash chip "MX25L6445E" (8192 kB, SPI) on buspirate_spi.
Chip status register is 0x40.
Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not
set
Chip status register: Bit 6 is set
Chip status register: Block Protect 3 (BP3) is not set
Chip status register: Block Protect 2 (BP2) is not set
Chip status register: Block Protect 1 (BP1) is not set
Chip status register: Block Protect 0 (BP0) is not set
Chip status register: Write Enable Latch (WEL) is not set
Chip status register: Write In Progress (WIP/BUSY) is not set
This chip may contain one-time programmable memory. flashrom cannot read
and may never be able to write it, hence it may not be able to completely
clone the contents of this chip (see man page for details).
Reading old flash chip contents... done.
Erasing and writing flash chip... Trying erase function 0...
0x000000-0x000fff:E
FAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from
0x000000
00-0x00000fff: 0x92
ERASE FAILED!
Bonjour everybody,
May I get your advices ?
I tried to flash my mb but got an error message, here are the infos you may need :
flashrom v0.9.9-r1954 on Linux 4.9.0-3-amd64 (x86_64)
flashrom was built with libpci 3.5.2, GCC 6.3.0 20170221, little endian
Command line (6 args): flashrom -w P5B-ASUS-Deluxe-1238.ROM -p internal -o test.txt
Calibrating delay loop... OS timer resolution is 1 usecs, 1599M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1000 us, 10000 myus = 10005 us, 4 myus = 4 us, OK.
Initializing internal programmer
No coreboot table found.
Using Internal DMI decoder.
DMI string chassis-type: "Desktop"
DMI string system-manufacturer: "System manufacturer"
DMI string system-product-name: "System Product Name"
DMI string system-version: "System Version"
DMI string baseboard-manufacturer: "ASUSTeK Computer INC."
DMI string baseboard-product-name: "P5B-Deluxe"
DMI string baseboard-version: "Rev 1.xx"
Found chipset "Intel ICH8/ICH8R" with PCI ID 8086:2810.
Enabling flash write... Root Complex Register Block address = 0xfed1c000
Error accessing ICH RCRB, 0x4000 bytes at 0x00000000fed1c000
/dev/mem mmap failed: Operation not permitted
FAILED!
FATAL ERROR!
Error: Programmer initialization failed.
I have bios 0506 and want to write the 1238.
ONLY EMAIL COMMUNICATION PLEASE.
Thanks for your attention.
Gégé
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(a)gmail.com>
wrote:
> We (you mostly) nailed it!:
>
> ===
>
> chrx@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(a)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(a)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@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
>>>
>>>
>>
>
We (you mostly) nailed it!:
===
chrx@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(a)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(a)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@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
>>
>>
>
Attached are more log files that the Board Testing HOWTO wiki entry asks for.
The board name from dmidecode seems to just be the chipset name, sis
630, rather then the actual board name. Hopefully there is still
something to identify the board with autodetect.
Just to be complete, the board is also marked as Rev: 1.0.
Running on the latest Debian package.I checked https://www.flashrom.org/Supported_hardwareand looked @ git log a bit ... didn't find anything about testing this chip .... SO
root@black:/data/MTD_Images# time flashrom -p ch341a_spi -c GD25Q128C -w NB-PR2.imgflashrom v0.9.9-r1954 on Linux 4.9.0-4-amd64 (x86_64)flashrom is free software, get the source code at https://flashrom.org
Calibrating delay loop... OK.Found GigaDevice flash chip "GD25Q128C" (16384 kB, SPI) on ch341a_spi.===This flash part has status UNTESTED for operations: PROBE READ ERASE WRITEThe test status of this chip may have been updated in the latest developmentversion of flashrom. If you are running the latest development version,please email a report to flashrom(a)flashrom.org if any of the above operationswork correctly for you with this flash chip. Please include the flashrom logfile for all operations you tested (see the man page for details), and mentionwhich mainboard or programmer you tested in the subject line.Thanks for your help!Reading old flash chip contents... done.Erasing and writing flash chip... Erase/write done.Verifying flash... VERIFIED.
real 5m49.633suser 0m17.820ssys 0m38.380s
This chip is installed on a prototype wireless router.It seems to work OK.[ 0.537541] m25p80 spi0.0: gd25q128 (16384 Kbytes)
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@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
Hi Anders,
On 07.11.2017 23:44, Anders Nelson wrote:
> root@chrx:/home/chrx/Github/flashrom# make clean
Doing such things as root is very discouraged.
> Replacing all version templates with v0.9.9-86-ge1a960e.
> rm -f flashrom flashrom.exe libflashrom.a *.o *.d flashrom.8
> flashrom.8.html build_details.txt
> make[1]: Entering directory
> '/home/chrx/Github/flashrom/util/ich_descriptors_tool'
> rm -f ich_descriptors_tool ich_descriptors_tool.exe
> rm -rf .dep .obj
> make[1]: Leaving directory
> '/home/chrx/Github/flashrom/util/ich_descriptors_tool'
>
> ===
>
> [...build completes without error...]
Well, like Stefan said, this is the part that could have told me
that libftdi is already installed.
>
> ===
> root@chrx:/home/chrx/Github/flashrom# flashrom -p ft2232_spi
> flashrom v0.9.9-rc1-r1942 on Linux 4.9.4-galliumos-braswell (x86_64)
> flashrom is free software, get the source code at https://flashrom.org
>
> Error: Unknown programmer "ft2232_spi". Valid choices are:
> internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia,
> it8212, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel,
> nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, pickit2_spi,
> ch341a_spi.
> Please run "flashrom --help" for usage info.
I could have seen this earlier... you are not calling your self-built
flashrom at all. You call the one pre-installed by GalliumOS. If you
want to run a binary that is not in a directory in your $PATH envi-
ronment variable, you have to prefix it with a path, e.g. `./flashrom
-p ft2232_spi` if you want to run the flashrom in the current directory.
Nico