- flashrom - mail.coreboot.org

Re: [flashrom] [PATCH] add support for Pm25LQ032
by Stefan Tauner 04 Apr '15

04 Apr '15

On Sat, 14 Mar 2015 15:00:10 +0000 Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: > I found this in a Chinese router, read tested (twice, successful) but > not yet write/erase tested. > Based on information from the datasheet at > http://www.chingistek.com/img/Product_Files/Pm25LQ032C%20datasheet%20v1.6.1… > > Signed-off-by: Steven Honeyman <stevenhoneyman(a)gmail.com> Hi Steven, thanks for your patch. There are a number of similar chips (Pm25LQ020, Pm25LQ040, Pm25LQ080, Pm25LQ016). Do you want to add support for them too? > Index: flashchips.c > =================================================================== > --- flashchips.c (revision 1888) > +++ flashchips.c (working copy) > @@ -9708,8 +9708,46 @@ > .voltage = {2700, 3600}, /* 2.3-3.6V for Pm25LD040 */ > }, > > -{ > + { > .vendor = "PMC", > + .name = "Pm25LQ032", Have you found any traces of a Pm25LQ032 without a C suffix? I don't and would rather add the C suffix here (and in the ID macro) until we have proof they really exist. > + .bustype = BUS_SPI, > + .manufacture_id = PMC_ID, > + .model_id = PMC_PM25LQ032, > + .total_size = 4096, > + .page_size = 256, > + .feature_bits = FEATURE_WRSR_WREN, Missing OTP flag and information. > + .tested = TEST_OK_PR, > + .probe = probe_spi_rdid, > + .probe_timing = TIMING_ZERO, > + .block_erasers = > + { > + { > + .eraseblocks = { {4 * 1024, 1024} }, > + .block_erase = spi_block_erase_20, /* sector erase */ All these comments are redundant. Experienced flashrom hacker will instantly deduce that from the erase block size(s). > + }, { > + .eraseblocks = { {4 * 1024, 1024} }, > + .block_erase = spi_block_erase_d7, /* sector erase */ > + }, { > + .eraseblocks = { {64 * 1024, 64} }, > + .block_erase = spi_block_erase_d8, /* block erase */ > + }, { > + .eraseblocks = { {4096 * 1024, 1} }, > + .block_erase = spi_block_erase_60, /* chip erase */ > + }, { > + .eraseblocks = { {4096 * 1024, 1} }, > + .block_erase = spi_block_erase_c7, /* chip erase */ > + } > + }, > + .printlock = spi_prettyprint_status_register_bp3_srwd, bit 6 is quad enable > + .unlock = spi_disable_blockprotect_bp3_srwd, > + .write = spi_chip_write_256, > + .read = spi_chip_read, /* Fast read (0x0B), dual I/O > supported */ Actually it supports even multi I/O > + .voltage = {2700, 3600}, /* 2.7-3.6V for Pm25Q032 */ The comment there is redundant (and contains a typo). We only comment the cases where multiple chips share the same ID but have different voltage ranges. The smaller range goes into the code, the broader one gets commented. > + }, > + > + { > + .vendor = "PMC", > .name = "Pm25LV512(A)", > .bustype = BUS_SPI, > .manufacture_id = PMC_ID_NOPREFIX, > Index: flashchips.h > =================================================================== > --- flashchips.h (revision 1888) > +++ flashchips.h (working copy) > @@ -560,6 +560,7 @@ > #define PMC_PM25LD512 0x20 /* Same as Pm25LD512C, but the > latter has more locking options. */ > #define PMC_PM25LD010 0x21 /* Same as Pm25LD010C, but the > latter has more locking options. */ > #define PMC_PM25LD020 0x22 /* Same as Pm25LD020C, but the > latter has more locking options. */ > +#define PMC_PM25LQ032 0x46 > #define PMC_PM25LV512 0x7B /* Same as Pm25LV512A */ > #define PMC_PM25LV010 0x7C /* Same as Pm25LV010A, but the > former does not support RDID but RES3 only. */ > #define PMC_PM25LV020 0x7D The important parts are all correct and I think erase/write should just work, thank you. If you plan to add the other members of this chip's family please supersede this patch with the new one and include the corrections mentioned above. If you do not want to add them please say so and I'll correct it myself before committing. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Results for "AT45DB321D"
by The Raven 04 Apr '15

04 Apr '15

Hi All Operations work fine! Chip can be marked as tested.

2 1

Re: [flashrom] Intel 28F001BN/BX-T erase/write operation verified on 3C905B-TXNM
by Stefan Tauner 04 Apr '15

04 Apr '15

On Sun, 4 Jan 2015 01:36:53 +0800 Lu Xie <lxie1(a)andrew.cmu.edu> wrote: > Hi, > > I performed another erase and 5 write operations on that chip with the same > network adapter. Hopefully it has some useful data here. > I flashed the chip with different BIOS's and they work on their desired > boards. Hello Lu, thanks for your effort! I just wanted to make sure everything is fine, hence my question. I have marked the flash chip as fully tested and will commit that later together with other small changes. Sorry for the delay. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

my new motherboard
by Big Valley Radio 04 Apr '15

04 Apr '15

so new it does not work! I need sound for Rivendell. Everything else seems to function. Attached file should have what you need to know. ASROCK H81M-DGS R2.0 Intel CPU thanks for being there! I spent a few days on this regards Robert Jeffares

1 0

Re: [flashrom] [PATCH] New GigaDevice chips
by Stefan Tauner 03 Apr '15

03 Apr '15

On Mon, 9 Mar 2015 10:18:36 +1000 Roman Titov <titovroman(a)gmail.com> wrote: Hello Roman! > Well, I think this could be the result of my inexperience with svn > (and git-svn). > > So, here's my steps: > 1. git svn clone -rHEAD (r1887, to be exact) flashrom-trunk (I have an > error, when I'm trying to make full git svn clone, looks like git bug > :/) > 2. *code* > 3. make 2 local commits > 4. git format-patch, and it throw me 2 patches for 2 latest commits > not over current origin (and I think thats is the reason) > 5. send patches to mailing list That's perfectly fine and how I work too (well, I use git send-email for 4 and 5). > My suggestions would be: > 1. shallow copying broke smth (idea, that git svn could bond git stuff > to full svn history stuff came to me just right now) > 2. formating 2 patches broke smth > 3. both? The problem is/was the last hunk. I guess you have opened the patch file in an editor that removes white space at the end of lines. The patch application does not seem to care but git-am does. Anyway, here is a list of things I have noticed in the patch. > From 3612049b7f6b2283ae4e593e66f369144b9e997b Mon Sep 17 00:00:00 2001 > From: Roman Titov <titovroman(a)gmail.com> > Date: Fri, 6 Mar 2015 17:18:43 +1000 > Subject: [PATCH 1/2] flashchips: new GigaDevice chips (GD25LQ40, GD25LQ80, > GD25LQ16, GD25LQ64(B), GD25LQ128) > > Signed-off-by: Roman Titov <titovroman(a)gmail.com> > > --- > flashchips.c | 197 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++- > 1 file changed, 196 insertions(+), 1 deletion(-) > > diff --git a/flashchips.c b/flashchips.c > index 8b5d1ec..31541ea 100644 > --- a/flashchips.c > +++ b/flashchips.c > @@ -5466,6 +5466,123 @@ const struct flashchip flashchips[] = { > > { > .vendor = "GigaDevice", > + .name = "GD25LQ40", > + .bustype = BUS_SPI, > + .manufacture_id = GIGADEVICE_ID, > + .model_id = GIGADEVICE_GD25LQ40, > + .total_size = 512, > + .page_size = 256, > + /* OTP: 1024B total, 256B reserved; read 0x48; write 0x42, erase 0x44 */ > + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, > + .tested = TEST_OK_PREW, According to the line above and the respective ones later, you had all that hardware at hand and tested it successfully. Correct me if I am wrong, but I don't think that's the case ;) > + .probe = probe_spi_rdid, > + .probe_timing = TIMING_ZERO, > + .block_erasers = > + { > + { > + .eraseblocks = { {4 * 1024, 128} }, > + .block_erase = spi_block_erase_20, > + }, { > + .eraseblocks = { {32 * 1024, 16} }, > + .block_erase = spi_block_erase_52, > + }, { > + .eraseblocks = { {64 * 1024, 8} }, > + .block_erase = spi_block_erase_d8, > + }, { > + .eraseblocks = { {512 * 1024, 1} }, > + .block_erase = spi_block_erase_60, > + }, { > + .eraseblocks = { {512 * 1024, 1} }, > + .block_erase = spi_block_erase_c7, > + } > + }, > + .printlock = spi_prettyprint_status_register_bp4_srwd, > + .unlock = spi_disable_blockprotect_bp4_srwd, /* TODO: 2nd status reg (read with 0x35) */ > + .write = spi_chip_write_256, > + .read = spi_chip_read, The chips support multiple read and opcodes (unlike flashrom yet!). We note that at least for new chips by adding a comment like this: /* Fast read (0x0B) and multi I/O supported */ (cf. with similar comments throughout the file). > + .voltage = {1700, 1950}, It should actually be 1695, 1950 instead. This is also an error in the existing definition of the GD25LQ32. Apart from these repeated copy & paste errors it looks good. Please fix them so that I can commit your first flashrom contribution, thanks! Have you noticed any differences between the GD25LQ64 and its B revision? -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 2

[commit] r1889 - trunk
by repository service 03 Apr '15

03 Apr '15

Author: stefanct Date: Fri Apr 3 23:29:04 2015 New Revision: 1889 URL: http://flashrom.org/trac/flashrom/changeset/1889 Log: Add support for more GigaDevice GD25LQ chips. Namely GD25LQ40, GD25LQ80, GD25LQ16, GD25LQ64(B), GD25LQ128. Signed-off-by: Roman Titov <titovroman(a)gmail.com> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Modified: trunk/flashchips.c Modified: trunk/flashchips.c ============================================================================== --- trunk/flashchips.c Sun Mar 1 23:12:16 2015 (r1888) +++ trunk/flashchips.c Fri Apr 3 23:29:04 2015 (r1889) @@ -5466,6 +5466,123 @@ { .vendor = "GigaDevice", + .name = "GD25LQ40", + .bustype = BUS_SPI, + .manufacture_id = GIGADEVICE_ID, + .model_id = GIGADEVICE_GD25LQ40, + .total_size = 512, + .page_size = 256, + /* OTP: 1024B total, 256B reserved; read 0x48; write 0x42, erase 0x44 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 128} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 16} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 8} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {512 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {512 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_bp4_srwd, + .unlock = spi_disable_blockprotect_bp4_srwd, /* TODO: 2nd status reg (read with 0x35) */ + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {1695, 1950}, + }, + + { + .vendor = "GigaDevice", + .name = "GD25LQ80", + .bustype = BUS_SPI, + .manufacture_id = GIGADEVICE_ID, + .model_id = GIGADEVICE_GD25LQ80, + .total_size = 1024, + .page_size = 256, + /* OTP: 1024B total, 256B reserved; read 0x48; write 0x42, erase 0x44 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 256} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 32} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 16} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {1 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {1 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_bp4_srwd, + .unlock = spi_disable_blockprotect_bp4_srwd, /* TODO: 2nd status reg (read with 0x35) */ + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {1695, 1950}, + }, + + { + .vendor = "GigaDevice", + .name = "GD25LQ16", + .bustype = BUS_SPI, + .manufacture_id = GIGADEVICE_ID, + .model_id = GIGADEVICE_GD25LQ16, + .total_size = 2048, + .page_size = 256, + /* OTP: 1024B total, 256B reserved; read 0x48; write 0x42, erase 0x44 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 512} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 64} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 32} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {2 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {2 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_bp4_srwd, + .unlock = spi_disable_blockprotect_bp4_srwd, /* TODO: 2nd status reg (read with 0x35) */ + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {1695, 1950}, + }, + + { + .vendor = "GigaDevice", .name = "GD25LQ32", .bustype = BUS_SPI, .manufacture_id = GIGADEVICE_ID, @@ -5499,8 +5616,86 @@ .printlock = spi_prettyprint_status_register_bp4_srwd, .unlock = spi_disable_blockprotect_bp4_srwd, /* TODO: 2nd status reg (read with 0x35) */ .write = spi_chip_write_256, - .read = spi_chip_read, - .voltage = {1700, 1950}, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {1695, 1950}, + }, + + { + .vendor = "GigaDevice", + .name = "GD25LQ64(B)", + .bustype = BUS_SPI, + .manufacture_id = GIGADEVICE_ID, + .model_id = GIGADEVICE_GD25LQ64, + .total_size = 8192, + .page_size = 256, + /* OTP: 1024B total, 256B reserved; read 0x48; write 0x42, erase 0x44 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 2048} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 256} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 128} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {8 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {8 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_bp4_srwd, + .unlock = spi_disable_blockprotect_bp4_srwd, /* TODO: 2nd status reg (read with 0x35) */ + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {1695, 1950}, + }, + + { + .vendor = "GigaDevice", + .name = "GD25LQ128", + .bustype = BUS_SPI, + .manufacture_id = GIGADEVICE_ID, + .model_id = GIGADEVICE_GD25LQ128, + .total_size = 16384, + .page_size = 256, + /* OTP: 1024B total, 256B reserved; read 0x48; write 0x42, erase 0x44 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 4096} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 512} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 256} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {16 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {16 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_bp4_srwd, + .unlock = spi_disable_blockprotect_bp4_srwd, /* TODO: 2nd status reg (read with 0x35) */ + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {1695, 1950}, }, {

1 0

Re: [flashrom] Macronix MX23L6454 probe/read success (buspirate_spi)
by Stefan Tauner 03 Apr '15

03 Apr '15

On Sat, 14 Mar 2015 14:40:37 +0000 Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: > On 8 March 2015 at 04:48, Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: > > On 8 March 2015 at 00:46, Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: > > > > ...ok definitely a false positive on the "works OK" status! > > 3rd resolder, 8th read attempt now. I haven't got two matching files > > yet. It keeps missing chunks out, at regular intervals, but different > > positions each time. > > > > I'm happy to upload/send the files & logs somewhere if they'd be useful to you? > > > > Tomorrow I'll try and find something else that will recognise & read > > this. The chip came from a working board so I know the ROM is good. > > OK, I finally got chance to make a little adapter board for > buspirate->soic16 spi... success! > It would seem that a set of ~20cm BP wires are too long for this to > work reliably, because with the adapter it worked first/every time: > > (the two other identical files came from a 'universal programmer' and > its own software) > […] > Found Macronix flash chip "MX23L6454" (8192 kB, SPI). > This chip's main memory can not be erased/written by design. > === > This flash part has status UNTESTED for operations: PROBE READ > The test status of this chip may have been updated in the latest development > version of flashrom. If you are running the latest development version, > please email a report to flashrom(a)flashrom.org if any of the above operations > work correctly for you with this flash chip. Please include the flashrom log > file for all operations you tested (see the man page for details), and mention > which mainboard or programmer you tested in the subject line. > Thanks for your help! > Reading flash... done. > Raw bitbang mode version 1 > Bus Pirate shutdown completed. > > > $ md5sum *.bin* > 6d7cf06448bd5ea941a4b458b6067e5f 25l6445.bin > 6d7cf06448bd5ea941a4b458b6067e5f 25l6465.bin > 6d7cf06448bd5ea941a4b458b6067e5f flashrom_mx23l6454.bin > 6d7cf06448bd5ea941a4b458b6067e5f flashrom_mx23l6454.bin2 Thanks for the update. I have marked the flash chip as tested and will commit that later together with other small changes. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] Support for AT25080
by Roy Krikke 03 Apr '15

03 Apr '15

I know C coding and I also know some thing or two about hardware. But tip on how to add this specific device to flashrom are welcome. On 18-3-2015 22:42, Idwer Vollering wrote: > 2015-03-18 22:24 GMT+01:00 Roy Krikke <roykrikke(a)gmail.com>: >> Hello, >> >> I have compiled the latest version of flashrom (flashrom v0.9.8-r1887) and >> hoped to flash my AT25080. But without suc6. > flashrom does not (yet) support this chip. We like patches :) > >> I have connected a new AT25080 to a Raspberry Pi and hoped to flash the >> device with in system programming (ISP) mode. >> >> First erasing the device with sudo flashrom -E -V -p >> linux_spi:dev=/dev/spidev0.0 > The command line command looks just fine, but flashrom doesn't support > this particular flash chip, > >> No luke :( >> >> snapshot of flashrom below: >> Probing for Generic unknown SPI chip (RDID), 0 kB: RDID byte 0 parity >> violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 >> Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on linux_spi. >> Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, >> id2 0x0 >> Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). >> === >> This flash part has status NOT WORKING for operations: PROBE READ ERASE >> WRITE >> The test status of this chip may have been updated in the latest development >> version of flashrom. If you are running the latest development version, >> please email a report to flashrom(a)flashrom.org if any of the above >> operations >> work correctly for you with this flash chip. Please include the flashrom log >> file for all operations you tested (see the man page for details), and >> mention >> which mainboard or programmer you tested in the subject line. >> Thanks for your help! >> Read is not working on this chip. Aborting. >> >> Any kind of help is welcome, tips on how best to proceed! >> >> >> Thank you very much, >> >> Roy >> >> >> >> My previous post >> -------------------------------------------------------------------------------- >> Hello, >> >> Is there support for the AT25080B device from ATMEL? It is not in the >> supported device list. >> >> http://www.atmel.com/Images/Atmel-5228-SEEPROM-AT25080B-160B-Datasheet.pdf >> >> Need to flash the AT25080B which is connected to a 82574L from intel. There >> are two 82574L with two AT25080B on my board. If I read from the first >> AT25080B the data is fine and I can also flash is. But the second one is not >> working at all. >> >> I compared/checked the SPI communication of the first one with the second >> one. This looks the same. So I thought maybe the second AT25080B is broken. >> After replacing it, still the same result. >> >> I hope to get is to work if I could flash is not by the SPI interface of the >> 82574L, but by an in system programming (ISP). Example shown in >> http://satxhackers.org/wp/hack-content/uploads/2013/04/rPI_flashrom.pdf >> >> Any kind of help is welcome. >> >> Thanks, >> >> Roy >> >> >> >> >> _______________________________________________ >> flashrom mailing list >> flashrom(a)flashrom.org >> http://www.flashrom.org/mailman/listinfo/flashrom > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

3 4

Re: [flashrom] Flashrom not finding BIOS flash on HP DL585 G2
by Stefan Tauner 03 Apr '15

03 Apr '15

On Thu, 19 Mar 2015 21:27:18 +0000 Paul Lalonde <Paul.Lalonde(a)telecomcomputer.com> wrote: > Unless there is another way to perform a BIOS flash backup of an HP ProLiant DL585 G2 server, I'd like to use flashrom for this. > > Results of flashrom -V -p internal, lspci, and superiotool are attached. Hi, I think you have found an old but still unsupported flash chip in that server. From some lines in the log output I think it is plausible that it is a Macronix MX29LV320DT or MX29LV321DT. It would be great if you could verify that visually if that's possible. I can probably add support for the chip without too much problems... but I am not sure if you would want to test it on that hardware if it is somewhat important to you...? :) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] Nec/Renesas 78k0s flash programming?
by Stefan Tauner 03 Apr '15

03 Apr '15

On Mon, 30 Mar 2015 15:56:06 +0000 Riccardo Delpopolo Carciopolo <rdelpopolo(a)gmail.com> wrote: > Hi, > I've used flashrom with pickit2 in past. > I'm a newbie but I'd like to add support for this MCUs by myself. > On Internet exist some parallel programmer but I want to program a 78k0s > flash my with the uart protocol. > We're can I start from? > It requires some vpp pulses to enable the uart programming mode. I don't think that flashrom is the right tool for the job of writing the flash memory of a microcontroller. Usually there are dedicated tools for this... but I guess the 78k0s are not really popular? You can of course use flashrom or at least its serial.c as a base for your tool. The protocol seems to be documented in a public application note: http://documentation.renesas.com/doc/DocumentServer/U17739EJ3V0AN00.pdf I am not sure about pulses thing. AFAICT the flash mode is enabled if FLMD0 is high when reset is released. I am however unsure if the following pulses on the same pin (FLMD0) are to be output by the programmer or are a way for the chip to indicate how it needs to be accessed... the language in the AN is abysmal. I would apply VCC to FLMD0 on reset release with a pull-up resistor and measure if the chip outputs anything on the port... Anyway this is rather off-topic... good luck with your project! -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] Linux Raspberry PI B - Spansion FL256S
by Stefan Tauner 02 Apr '15

02 Apr '15

On Thu, 2 Apr 2015 16:16:38 +0200 Pascal de Marichalar <pascal.demarichalar(a)gmail.com> wrote: > Hi, > > I use the latest version of flashrom from github: "flashrom v0.9.8-r1887 on > Linux 3.18.10+ (armv6l)" that I had built on a Raspberry PI B. When I run > the command line "flashrom -p linux_spi:dev=/dev/spidev0.0" to probe a SPI > Flash memory chip soldered on a board (I use a a clip test probe) I get the > message: 'Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on > linux_spi.' > The Flash chip is a 32 MB Spansion memory. On the chip is written « > FL256SAIF00 SPANSION ». I have attached the output log from flashrom. Flash chips >16MB are not supported yet, but there are some patches you might want to look at, see http://patchwork.coreboot.org/project/flashrom/list/ -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Linux Raspberry PI B - Spansion FL256S
by Pascal de Marichalar 02 Apr '15

02 Apr '15

Hi, I use the latest version of flashrom from github: "flashrom v0.9.8-r1887 on Linux 3.18.10+ (armv6l)" that I had built on a Raspberry PI B. When I run the command line "flashrom -p linux_spi:dev=/dev/spidev0.0" to probe a SPI Flash memory chip soldered on a board (I use a a clip test probe) I get the message: 'Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on linux_spi.' The Flash chip is a 32 MB Spansion memory. On the chip is written « FL256SAIF00 SPANSION ». I have attached the output log from flashrom. Thanks, Best regards, Pascal de Marichalar

1 0

Nec/Renesas 78k0s flash programming?
by Riccardo Delpopolo Carciopolo 30 Mar '15

30 Mar '15

Hi, I've used flashrom with pickit2 in past. I'm a newbie but I'd like to add support for this MCUs by myself. On Internet exist some parallel programmer but I want to program a 78k0s flash my with the uart protocol. We're can I start from? It requires some vpp pulses to enable the uart programming mode. Thabk you for help

1 0

W836xx: Lancer 5A2: flashrom -V
by Henrik Stokseth 29 Mar '15

29 Mar '15

if you want me to run additional tests on this new lenovo g50-70 laptop mail me privately. got some developer experience. HTH === flashrom v0.9.8-r1887 on Linux 3.19.0-10-generic (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.1, GCC 4.9.2, little endian Command line (3 args): ./flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 3072M loops per second, 10 myus = 10 us, 100 myus = 107 us, 1000 myus = 1000 us, 10000 myus = 10406 us, 4 myus = 6 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Notebook" Laptop detected via DMI. DMI string system-manufacturer: "LENOVO" DMI string system-product-name: "20351" DMI string system-version: "Lenovo G50-70" DMI string baseboard-manufacturer: "LENOVO" DMI string baseboard-product-name: "Lancer 5A2" DMI string baseboard-version: "31900058STD" W836xx enter config mode worked or we were already in config mode. W836xx leave config mode had no effect. Active config mode, unknown reg 0x20 ID: 85. Please send the output of "flashrom -V -p internal" to flashrom(a)flashrom.org with W836xx: your board name: flashrom -V as the subject to help us finish support for your Super I/O. Thanks. Found ITE EC, ID 0x8586, Rev 0x06 on port 0x4e. ====

1 0

W836xx: To be filled by O.E.M.: flashrom -V
by Florian Schroeter 29 Mar '15

29 Mar '15

Dear flashrom Developers, I am writing you because I want to set up a proper Linux on my Laptop, which I imported from china. It's clearly an imitation of some Acer Aspire One Model. When I got it, the packaging was labeled as "Spire One"... W-Lan and Bluetooth, sound, battery state and brightness controls as well as function keys seem to work under windows but not under Linux. I guess the ACPI tables provided by the hardware do poorly support any OS different from Microsoft Windows. I had hoped that a BIOS update could maybe fix the buggy ACPI tables but wasn't able to update the bios using flashrom. As suggested by your tool I'll put the verbose output of flashrom into the attachment. Kind regards Florian Schröter

3 2

Support for programming device on SPI via USB bridge?
by Robert Selby 26 Mar '15

26 Mar '15

Hi, just found FlashRom and looks to be a good base to start from for my needs. I have a USB->SPI bridge device (MCP2210) and on it's SPI bus is a "S25FL128S" device. It looks as though there is no direct support for accessing via the MCP2210. I assume that I would need to write a "programmer" to get this to work ??? I have a MCP2210 access library that seems to work well via "/dev/hidraw". Any advice/recommendations very welcome. It may be that someone has already done this ... Regards, Bob _____ Bob Selby Senior Engineer, Software - LTV Newbury Snell a Quantel Company Innovation in the Multi-Screen World T +44 (0) 1635 48222 Extn 3753 Turnpike Road, Newbury, Berkshire, RG14 2NX, UK Routing <http://www.snellgroup.com/products/routing/> | Modular Infrastructure <http://www.snellgroup.com/products/modular-infrastructure/> | Conversion & Restoration <http://www.snellgroup.com/products/conversion-and-restoration/> | Live Production <http://www.snellgroup.com/products/production-and-master-control-switch ing/> | Automation & Media Management <http://www.snellgroup.com/products/automation-and-media-management/> | Control & Monitoring <http://www.snellgroup.com/products/control-and-monitoring/> This email and any attachments are confidential, may be legally privileged and are intended for the use of the addressee only. If you are not the intended recipient, please note that any use, disclosure, printing or copying of this email is strictly prohibited and may be unlawful. If received in error, please delete this email and any attachments and confirm this to the sender. Snell Limited, registered number 1160119 Registered in England, registered office at 31 Turnpike Road, Newbury, Berkshire, RG14 2NX, U.K.

3 3

W836xx: To be filled by O.E.M.: flashrom -V
by Florian Schroeter 22 Mar '15

22 Mar '15

Dear flashrom Developers, I am writing you because I want to set up a proper Linux on my Laptop, which I imported from china. It's clearly an imitation of some Acer Aspire One Model. When I got it, the packaging was labeled as "Spire One"... W-Lan and Bluetooth, sound, battery state and brightness controls as well as function keys seem to work under windows but not under Linux. I guess the ACPI tables provided by the hardware do poorly support any OS different from Microsoft Windows. I had hoped that a BIOS update could maybe fix the buggy ACPI tables but wasn't able to update the bios using flashrom. As suggested by your tool I'll put the verbose output of flashrom into the attachment. Kind regards Florian Schröter

1 0

(no subject)
by Djamel Kalala 22 Mar '15

22 Mar '15

HelloI have a problem in flash rom program Use Program spipgm Windows XP Sweet 5.1 [SP3 v5.1.2600](C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Administrateur>flashrom -p rayer_spiflashrom v0.9.6.1-r1705 on MS-DOS 5 (i686)flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK.No EEPROM/flash device found.Note: flashrom can never write if the flash chip isn't found automatically. C:\DOCUME~1\ADMINI~1>

1 1

lenovo thinkpad edge 11
by Jens Thiele 20 Mar '15

20 Mar '15

# flashrom -V -p internal flashrom v0.9.7-r1852 on Linux 3.2.0-4-amd64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.9, GCC 4.7.2, little endian Command line (3 args): flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 521M loops per second, delay more than 10% too short (got 74% of expected delay), recalculating... 218M loops per second, delay more than 10% too short (got 31% of expected delay), recalculating... 206M loops per second, delay more than 10% too short (got 30% of expected delay), recalculating... 203M loops per second, delay more than 10% too short (got 29% of expected delay), recalculating... 206M loops per second, delay loop is unreliable, trying to continue 10 myus = 11 us, 100 myus = 104 us, 1000 myus = 1032 us, 10000 myus = 3578 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Notebook" Laptop detected via DMI. DMI string system-manufacturer: "LENOVO" DMI string system-product-name: "2545A26" DMI string system-version: "ThinkPad Edge" DMI string baseboard-manufacturer: "LENOVO" DMI string baseboard-product-name: "2545A26" DMI string baseboard-version: "Not Available" W836xx enter config mode worked or we were already in config mode. W836xx leave config mode had no effect. Active config mode, unknown reg 0x20 ID: 85. Please send the output of "flashrom -V -p internal" to flashrom(a)flashrom.org with W836xx: your board name: flashrom -V as the subject to help us finish support for your Super I/O. Thanks. Found ITE EC, ID 0x8502, Rev 0x60 on port 0x2e. ======================================================================== WARNING! You seem to be running flashrom on an unsupported laptop. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and http://www.flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== Aborting. Error: Programmer initialization failed.

1 0

Rangeley platform flashrom 0.9.8 update fail
by james_lee 20 Mar '15

20 Mar '15

Dear Sir, I use flashrom0.9.8 to update Coreboot BIOS on Rangeley platform, Flash result its fail, could you help teach me how to fix this issue? Thanks. Attach file is log file. Best Regards James Lee / 李清正 BIOS Engineer james_lee(a)lannerinc.com <mailto:allan_su@lannerinc.com> 立端科技股份有限公司 Lanner Electronics www.lannerinc.com <http://www.lannerinc.com/> (886) <Tel:(886)> 286926060 # 553 5F, 173, section 2 Datong road, Sijhih City, Taipei 221, Taiwan.

2 2

Flashrom not finding BIOS flash on HP DL585 G2
by Paul Lalonde 19 Mar '15

19 Mar '15

Unless there is another way to perform a BIOS flash backup of an HP ProLiant DL585 G2 server, I'd like to use flashrom for this. Results of flashrom -V -p internal, lspci, and superiotool are attached. Regards, Paul

1 0

Re: [flashrom] Support for AT25080
by Idwer Vollering 18 Mar '15

18 Mar '15

2015-03-18 22:24 GMT+01:00 Roy Krikke <roykrikke(a)gmail.com>: > > Hello, > > I have compiled the latest version of flashrom (flashrom v0.9.8-r1887) and > hoped to flash my AT25080. But without suc6. flashrom does not (yet) support this chip. We like patches :) > > I have connected a new AT25080 to a Raspberry Pi and hoped to flash the > device with in system programming (ISP) mode. > > First erasing the device with sudo flashrom -E -V -p > linux_spi:dev=/dev/spidev0.0 The command line command looks just fine, but flashrom doesn't support this particular flash chip, > > No luke :( > > snapshot of flashrom below: > Probing for Generic unknown SPI chip (RDID), 0 kB: RDID byte 0 parity > violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 > Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on linux_spi. > Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, > id2 0x0 > Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). > === > This flash part has status NOT WORKING for operations: PROBE READ ERASE > WRITE > The test status of this chip may have been updated in the latest development > version of flashrom. If you are running the latest development version, > please email a report to flashrom(a)flashrom.org if any of the above > operations > work correctly for you with this flash chip. Please include the flashrom log > file for all operations you tested (see the man page for details), and > mention > which mainboard or programmer you tested in the subject line. > Thanks for your help! > Read is not working on this chip. Aborting. > > Any kind of help is welcome, tips on how best to proceed! > > > Thank you very much, > > Roy > > > > My previous post > -------------------------------------------------------------------------------- > Hello, > > Is there support for the AT25080B device from ATMEL? It is not in the > supported device list. > > http://www.atmel.com/Images/Atmel-5228-SEEPROM-AT25080B-160B-Datasheet.pdf > > Need to flash the AT25080B which is connected to a 82574L from intel. There > are two 82574L with two AT25080B on my board. If I read from the first > AT25080B the data is fine and I can also flash is. But the second one is not > working at all. > > I compared/checked the SPI communication of the first one with the second > one. This looks the same. So I thought maybe the second AT25080B is broken. > After replacing it, still the same result. > > I hope to get is to work if I could flash is not by the SPI interface of the > 82574L, but by an in system programming (ISP). Example shown in > http://satxhackers.org/wp/hack-content/uploads/2013/04/rPI_flashrom.pdf > > Any kind of help is welcome. > > Thanks, > > Roy > > > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

Support for AT25080
by Roy Krikke 18 Mar '15

18 Mar '15

Hello, I have compiled the latest version of flashrom (flashrom v0.9.8-r1887) and hoped to flash my AT25080. But without suc6. I have connected a new AT25080 to a Raspberry Pi and hoped to flash the device with in system programming (ISP) mode. First erasing the device with *sudo flashrom -E -V -p linux_spi:dev=/dev/spidev0.0* No luke :( snapshot of flashrom below: *Probing for Generic unknown SPI chip (RDID), 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on linux_spi.Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, id2 0x0Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI).===This flash part has status NOT WORKING 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 <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!Read is not working on this chip. Aborting.* Any kind of help is welcome, tips on how best to proceed! Thank you very much, Roy *My previous post* *--------------------------------------------------------------------------------* Hello, Is there support for the AT25080B device from ATMEL? It is not in the supported device list. http://www.atmel.com/Images/Atmel-5228-SEEPROM-AT25080B-160B-Datasheet.pdf Need to flash the AT25080B which is connected to a 82574L from intel. There are two 82574L with two AT25080B on my board. If I read from the first AT25080B the data is fine and I can also flash is. But the second one is not working at all. I compared/checked the SPI communication of the first one with the second one. This looks the same. So I thought maybe the second AT25080B is broken. After replacing it, still the same result. I hope to get is to work if I could flash is not by the SPI interface of the 82574L, but by an in system programming (ISP). Example shown in http://satxhackers.org/wp/hack-content/uploads/2013/04/rPI_flashrom.pdf Any kind of help is welcome. Thanks, Roy

1 0

Re: [flashrom] flahsrom
by David Hendricks 18 Mar '15

18 Mar '15

On Tue, Mar 17, 2015 at 9:47 PM, bobby deyton <wikkidhalo(a)gmail.com> wrote: > I hope this isn't too silly of a question, but it is the first time I've > used this program. I have an acer t180, which is on the supported hardware > list. The link to the board describes a socket 772 and the board I have has > an AM2 socket board. I tried using the .bin supplied from the website. I > haven't tried using the one from the vendor. But the difference in socket > made me nervous. Thank you for your time and your awesome work. > Well, the good news is that your chipset is supported and flashrom found the flash chip successfully. I'd recommend reading your ROM twice to two different files and diff'ing them just to make sure they are consistent. -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

Support for AT25080
by Roy Krikke 18 Mar '15

18 Mar '15

Hello, Is there support for the AT25080B device from ATMEL? It is not in the supported device list. http://www.atmel.com/Images/Atmel-5228-SEEPROM-AT25080B-160B-Datasheet.pdf Need to flash the AT25080B which is connected to a 82574L from intel. There are two 82574L with two AT25080B on my board. If I read from the first AT25080B the data is fine and I can also flash is. But the second one is not working at all. I compared/checked the SPI communication of the first one with the second one. This looks the same. So I thought maybe the second AT25080B is broken. After replacing it, still the same result. I hope to get is to work if I could flash is not by the SPI interface of the 82574L, but by an in systerm programming (ISP). Example shown in http://satxhackers.org/wp/hack-content/uploads/2013/04/rPI_flashrom.pdf Any kind of help is welcome. Thanks, Roy

1 0

flahsrom
by bobby deyton 18 Mar '15

18 Mar '15

I hope this isn't too silly of a question, but it is the first time I've used this program. I have an acer t180, which is on the supported hardware list. The link to the board describes a socket 772 and the board I have has an AM2 socket board. I tried using the .bin supplied from the website. I haven't tried using the one from the vendor. But the difference in socket made me nervous. Thank you for your time and your awesome work. WH

1 0

Resolved M25P128 erase/write failed on raspberry pi
by wangmengk＠digitalchina.com 18 Mar '15

18 Mar '15

Hi all, I have encountered unstable failed when rewrite M25P128 via raspberry pi, sometimes cannot read out chip id(0x00), sometimes failed @ erase/write process, at beginning I'm confused because another chip(MX25L128) can work fine on the same platform, I found similar issue at maillist(attached below), but in my scenario the unconnected pin is HOLD(low is enable), after connected HOLD pin to VCC(3.3Volt), M25P128 can work fine. >[flashrom] MX25L128 Support >Brian Rak brak at gameservers.com >Thu Feb 6 02:19:00 CET 2014 >Previous message: [flashrom] MX25L128 Support >Next message: [flashrom] status report (write works!) >Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] >So, I connected WP to ground (instead of leaving it unconnected), and >reduced the speed (spispeed=8000). Looking at a binary comparison of >the original file versus what was actually written, it seems that it was >writing parts of it successfully, but corrupting data every few bytes. > >I'm guessing either the raspberry pi can't handle the higher speeds, or >I'm getting interference from something. > >Either way, I've done a couple erase, write, read cycles and it's been >working fine. > >On 2/4/2014 8:16 PM, Brian Rak wrote: >> So, after realizing that the MX25L256 was the wrong chip, I've >> obtained a few of the correct chips (MX25L12845EMI-10G). These are >> detected by flashrom, but writes are failing. >> >> Erase/write done. >> Verifying flash... FAILED at 0x00000002! Expected=0x55, Found=0x75, >> failed byte count from 0x00000000-0x00ffffff: 0x3e5cb3 >> Your flash chip is in an unknown state. >> Please report this on IRC at chat.freenode.net (channel #flashrom) or >> mail flashrom at flashrom.org, thanks! >> >> This is using a raspberry pi as a programmer, and: >> >> ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=32000 -w >> ../flashrom/ipmi/SMT_313.bin -o debug1 >> >> -rw-r--r-- 1 root root 16777216 Jan 2 19:10 ../flashrom/ipmi/SMT_313.bin >> >> >> Any suggestions here? -o debug1 is attached >> >> >> _______________________________________________ >> flashrom mailing list >> flashrom at flashrom.org >> http://www.flashrom.org/mailman/listinfo/flashrom ------------------------------------------------------------------------------------------------------------------- 免责声明(Disclaimer) 1.此电子邮件包含来自神州数码的信息，而且是机密的或者专用的信息。这些信息是供所有以上列出的个人或者团体使用的。如果您不是此邮件的预期收件人，请勿阅读、复制、转发或存储此邮件。如果已误收此邮件，请通知发件人。 This e-mail may contain confidential and/or privileged information from Digital China and is intended solely for the attention and use of the person(s) named above. If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this email is strictly forbidden. 2.本公司不担保本电子邮件中信息的准确性、适当性或完整性，并且对此产生的任何错误或疏忽不承担任何责任。 The content provided in this e-mail can not be guaranteed and assured to be accurate, appropriate for all, and complete by Digital China, and Digital China can not be held responsible for any error or negligence derived therefrom. 3.接收方应在接收电子邮件或任何附件时检查有无病毒。本公司对由于转载本电子邮件而引发病毒产生的任何损坏不承担任何责任。 The internet communications through this e-mail can not be guaranteed or assured to be error or virus-free, and the sender do not accept liability for any errors, omissions or damages arising therefrom.

1 0

Re: [flashrom] Flashrom patch for Dediprog sf100?
by Stefan Tauner 16 Mar '15

16 Mar '15

On Sun, 15 Mar 2015 12:49:24 -0400 Adam Duncan <adam.duncan(a)gmail.com> wrote: > Thanks! > > Is there a specific flashrom version I need to use with the patch? Well, you need to make it compile with the version you want to use As you can see from the patch, it is against flashrom r1846. But it should not be hard to port it to the current version. > Do you know if there is specific dediprog firmware I need to use to make it > work? The patched flashrom should still work with older firmwares but also the currently newest ones AFAIK. At least I am not aware of any additional changes required. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Compile under MinGW32, how?
by Topolinux 15 Mar '15

15 Mar '15

Hi guys, sorry to disturb you. Based on instructions I saw here: http://flashrom.org/Windows I installed MinGW32 on my Windows XP machine in order to try to compile the latest flashrom release which I need. Sadly I'm unable to compile anything because I get the errors as follow: ************************************************************************************** $ make Files don't seem to be under version control. Replacing all version templates wi th 0.9.8-r1888. Package libftdi was not found in the pkg-config search path. Perhaps you should add the directory containing `libftdi.pc' to the PKG_CONFIG_PATH environment variable No package 'libftdi' found Package libusb was not found in the pkg-config search path. Perhaps you should add the directory containing `libusb.pc' to the PKG_CONFIG_PATH environment variable No package 'libusb' found Checking for a C compiler... found. Target arch is x86 Target OS is MinGW Checking for libusb-0.1/libusb-compat headers... .test.c:3:23: fatal error: lusb 0_usb.h: No such file or directory #include <lusb0_usb.h> ^ compilation terminated. not found. Please install libusb-0.1 headers or libusb-compat headers. See README for more information. make: *** [hwlibs] Error 1 ************************************************************************************** A weird thing is that I had to manually install the pkg-config package, that isn't listed in the instructions. Anyway I'm pretty sure I have all the files in the right places and I guess my fault is due the fact I'm not able to figure how and where edit the PKG_CONFIG_PATH that indeed I haven't in nowhere. I wonder where I can see an example of PKG_CONFIG_PATH, any suggestions? Thanks. I need compile flashrom for Bus Pirate, so is there any mandatory flag that have to be set? Honestly I didn't know it was so complicated to compile for Windows, by read of the instructions it seemed to me pretty easy, but it isn't. Is perhaps there any documentations that explain clearly how do the job? I think that a description of the folders and the files inside them can be enough in order to understand, sadly I have seen nothing like that. Last but not least. Maybe I'm wrong, though seems to me that the way as MinGW is installed allows to move the installation easily, almost like an portable application. Am I wrong? If I'm not wrong this means that should be possible achieve a running environment if someone would provide one. Anyway I'm pretty sure that being be able to see a working installation would help to settle the matter. Thanks for reading! Regards, ~Topolinux

2 1

Re: [flashrom] Flashrom patch for Dediprog sf100?
by Stefan Tauner 15 Mar '15

15 Mar '15

On Sun, 15 Mar 2015 08:12:13 -0400 Adam Duncan <adam.duncan(a)gmail.com> wrote: > Hi, > > I'm having a problem getting my dediprog sf100 working with flashrom. I've > tried flashrom building versions 0.9.6, 0.9.7, 0.9.8 with the > 'configure_dediprog' flag and can see dediprog listed as programmer option. > However when I go to read a chip, flashrom detects the correct dediprog > firmware (5.5.02) but finds " unknown flash chip of 0kb. > > I can use the same setup with the windows dediprog sw and it can read and > write the chip fine. I can also use a buspirate with flashrom and the same > chip and it can read and write fine ( but really slowly). > > My question is if there is a specific flashrom version and patch I need to > use my dediprog with flashrom? Is there something else I may be doing wrong > here? Yes, you do need an unmerged patch: http://patchwork.coreboot.org/patch/4240/ -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Flashrom patch for Dediprog sf100?
by Adam Duncan 15 Mar '15

15 Mar '15

Hi, I'm having a problem getting my dediprog sf100 working with flashrom. I've tried flashrom building versions 0.9.6, 0.9.7, 0.9.8 with the 'configure_dediprog' flag and can see dediprog listed as programmer option. However when I go to read a chip, flashrom detects the correct dediprog firmware (5.5.02) but finds " unknown flash chip of 0kb. I can use the same setup with the windows dediprog sw and it can read and write the chip fine. I can also use a buspirate with flashrom and the same chip and it can read and write fine ( but really slowly). My question is if there is a specific flashrom version and patch I need to use my dediprog with flashrom? Is there something else I may be doing wrong here? Thanks!

1 0

Re: [flashrom] flashrom Digest, Vol 70, Issue 26
by Márton Miklós 15 Mar '15

15 Mar '15

Hey Alex, No worries, the board is functioning, I have been able to update BIOS with the vendor's DOS based utility. Usually when I need to update a BIOS on a board which is not in the flashrom supported list I try out the flashing with flashrom first, to be able to send an unsuccess/success report. Üdvözlettel, Márton Miklós +36-70-39-60-009 2015-03-15 12:00 keltezéssel, flashrom-request(a)flashrom.org írta: > Hi, > > There might be a solution if you want to update to the latest firmware. In > section 2.1.4 of the board manual you have an option to recover bios after > a failed update or corruption. You need an usb stick and the bios file > renamed per instructions in the manual. You need to put that file on the > usb and insert the usb prior to powering the PC. They do not specify this > in the manual for this board but in manuals for similar boards, also from > Asus, they uncover it. > > Try this last thing even if the board doesn't POST. I had success in the > past with this method. > > Good luck > > Alex.

1 0

Re: [flashrom] ASUS M2N-MX board enable needed? (M?rton Mikl?s)
by nicolae788 . 14 Mar '15

14 Mar '15

Hi, There might be a solution if you want to update to the latest firmware. In section 2.1.4 of the board manual you have an option to recover bios after a failed update or corruption. You need an usb stick and the bios file renamed per instructions in the manual. You need to put that file on the usb and insert the usb prior to powering the PC. They do not specify this in the manual for this board but in manuals for similar boards, also from Asus, they uncover it. Try this last thing even if the board doesn't POST. I had success in the past with this method. Good luck Alex.

1 0

[PATCH] add support for Pm25LQ032
by Steven Honeyman 14 Mar '15

14 Mar '15

I found this in a Chinese router, read tested (twice, successful) but not yet write/erase tested. Based on information from the datasheet at http://www.chingistek.com/img/Product_Files/Pm25LQ032C%20datasheet%20v1.6.1… Signed-off-by: Steven Honeyman <stevenhoneyman(a)gmail.com> Index: flashchips.c =================================================================== --- flashchips.c (revision 1888) +++ flashchips.c (working copy) @@ -9708,8 +9708,46 @@ .voltage = {2700, 3600}, /* 2.3-3.6V for Pm25LD040 */ }, -{ + { .vendor = "PMC", + .name = "Pm25LQ032", + .bustype = BUS_SPI, + .manufacture_id = PMC_ID, + .model_id = PMC_PM25LQ032, + .total_size = 4096, + .page_size = 256, + .feature_bits = FEATURE_WRSR_WREN, + .tested = TEST_OK_PR, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 1024} }, + .block_erase = spi_block_erase_20, /* sector erase */ + }, { + .eraseblocks = { {4 * 1024, 1024} }, + .block_erase = spi_block_erase_d7, /* sector erase */ + }, { + .eraseblocks = { {64 * 1024, 64} }, + .block_erase = spi_block_erase_d8, /* block erase */ + }, { + .eraseblocks = { {4096 * 1024, 1} }, + .block_erase = spi_block_erase_60, /* chip erase */ + }, { + .eraseblocks = { {4096 * 1024, 1} }, + .block_erase = spi_block_erase_c7, /* chip erase */ + } + }, + .printlock = spi_prettyprint_status_register_bp3_srwd, + .unlock = spi_disable_blockprotect_bp3_srwd, + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B), dual I/O supported */ + .voltage = {2700, 3600}, /* 2.7-3.6V for Pm25Q032 */ + }, + + { + .vendor = "PMC", .name = "Pm25LV512(A)", .bustype = BUS_SPI, .manufacture_id = PMC_ID_NOPREFIX, Index: flashchips.h =================================================================== --- flashchips.h (revision 1888) +++ flashchips.h (working copy) @@ -560,6 +560,7 @@ #define PMC_PM25LD512 0x20 /* Same as Pm25LD512C, but the latter has more locking options. */ #define PMC_PM25LD010 0x21 /* Same as Pm25LD010C, but the latter has more locking options. */ #define PMC_PM25LD020 0x22 /* Same as Pm25LD020C, but the latter has more locking options. */ +#define PMC_PM25LQ032 0x46 #define PMC_PM25LV512 0x7B /* Same as Pm25LV512A */ #define PMC_PM25LV010 0x7C /* Same as Pm25LV010A, but the former does not support RDID but RES3 only. */ #define PMC_PM25LV020 0x7D

1 0

Re: [flashrom] Macronix MX23L6454 probe/read success (buspirate_spi)
by Steven Honeyman 14 Mar '15

14 Mar '15

On 8 March 2015 at 04:48, Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: > On 8 March 2015 at 00:46, Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: >> On 8 March 2015 at 00:24, Stefan Tauner >> <stefan.tauner(a)alumni.tuwien.ac.at> wrote: >>> On Sat, 7 Mar 2015 02:24:49 +0000 >>> Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: >>> >>>> Probe and Read both worked, no problems >>>> >>>> Log: >>>> >>>> […] >>>> Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 >>>> 0xc2, id2 0x517 >>>> Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 >>>> 0xc2, id2 0x517 >>>> Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 >>>> 0xc2, id2 0x517 >>>> Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 >>>> 0xc2, id2 0x517 >>>> Found Macronix flash chip "MX23L6454" (8192 kB, SPI) on buspirate_spi. >>>> Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 >>>> 0xc2, id2 0x517 >>>> Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: >>>> probe_spi_rdid_generic: id1 0xc2, id2 0x517 >>>> Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: >>>> probe_spi_rdid_generic: id1 0xc2, id2 0x517 >>>> Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: >>>> probe_spi_rdid_generic: id1 0xc2, id2 0x517 >>>> Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: RDID byte 0 >>>> parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 >>>> Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 >>>> kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, >>>> id2 0x00 >>>> Probing for Macronix MX25L1605, 2048 kB: RDID byte 0 parity violation. >>>> probe_spi_rdid_generic: id1 0x00, id2 0x00 >>>> […] >>> >>> Hello Steven, >>> >>> thanks for your report! >>> The log looks quite suspicious in terms of reproducibility. The excerpt >>> above shows that the chip replied two different things when queried with >>> probe_spi_rdid_generic: all zeros and the correct ID (0xc2517) >>> respectively. This is usually an indication for wiring problems. If it >>> was that inconsistent all the time you would probably not be able to >>> read a good image. Did you read the chip multiple times and compared >>> the results? >> >> Hmmm, I didn't (because it was so slow), but I can do if you think >> there were issues. >> >> I only had a quick look through the image but it looked to be what I >> was expecting. >> I'll dump the image using some other software/hardware and make sure >> that matches too. > > ...ok definitely a false positive on the "works OK" status! > 3rd resolder, 8th read attempt now. I haven't got two matching files > yet. It keeps missing chunks out, at regular intervals, but different > positions each time. > > I'm happy to upload/send the files & logs somewhere if they'd be useful to you? > > Tomorrow I'll try and find something else that will recognise & read > this. The chip came from a working board so I know the ROM is good. OK, I finally got chance to make a little adapter board for buspirate->soic16 spi... success! It would seem that a set of ~20cm BP wires are too long for this to work reliably, because with the adapter it worked first/every time: (the two other identical files came from a 'universal programmer' and its own software) $ flashrom -V -p buspirate_spi:dev=/dev/ttyUSB0 -r flashrom_mx23l6454.bin flashrom v0.9.8-r1887 on Linux 3.19.1-e6540 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.3.0, GCC 4.9.2 20150204 (prerelease), little endian Command line (5 args): flashrom -V -p buspirate_spi:dev=/dev/ttyUSB0 -r flashrom_mx23l6454.bin Calibrating delay loop... OS timer resolution is 1 usecs, 3255M loops per second, 10 myus = 10 us, 100 myus = 120 us, 1000 myus = 1009 us, 10000 myus = 10163 us, 4 myus = 14 us, OK. Initializing buspirate_spi programmer Baud rate is 115200 now. Detected Bus Pirate hardware v3.5 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 AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB321E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Found Macronix flash chip "MX23L6454" (8192 kB, SPI) on buspirate_spi. Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L3273E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L6405D, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L12805D, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25U12835F, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L6495F, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL132K, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL164K, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL127S-64kB, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL127S-256kB, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL128P......0, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL128P......1, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL128S......1, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL129P......0, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL129P......1, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF020B, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF080, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q40.V, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q40.W, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q80.W, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Unknown SFDP-capable chip, 0 kB: No SFDP signature found. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, id2 0x0 Found Macronix flash chip "MX23L6454" (8192 kB, SPI). This chip's main memory can not be erased/written by design. === This flash part has status UNTESTED for operations: PROBE READ The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Reading flash... done. Raw bitbang mode version 1 Bus Pirate shutdown completed. $ md5sum *.bin 6d7cf06448bd5ea941a4b458b6067e5f 25l6445.bin 6d7cf06448bd5ea941a4b458b6067e5f 25l6465.bin 6d7cf06448bd5ea941a4b458b6067e5f flashrom_mx23l6454.bin $ flashrom -V -p buspirate_spi:dev=/dev/ttyUSB0 -r flashrom_mx23l6454.bin2 flashrom v0.9.8-r1887 on Linux 3.19.1-e6540 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.3.0, GCC 4.9.2 20150204 (prerelease), little endian Command line (5 args): flashrom -V -p buspirate_spi:dev=/dev/ttyUSB0 -r flashrom_mx23l6454.bin2 Calibrating delay loop... OS timer resolution is 1 usecs, 3249M loops per second, 10 myus = 10 us, 100 myus = 120 us, 1000 myus = 1008 us, 10000 myus = 10005 us, 4 myus = 5 us, OK. Initializing buspirate_spi programmer Baud rate is 115200 now. Detected Bus Pirate hardware v3.5 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 AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB321E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Found Macronix flash chip "MX23L6454" (8192 kB, SPI) on buspirate_spi. Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L3273E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L6405D, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L12805D, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25U12835F, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L6495F, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL132K, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL164K, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL127S-64kB, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL127S-256kB, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL128P......0, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL128P......1, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL128S......1, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL129P......0, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL129P......1, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF020B, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF080, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q40.V, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q40.W, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q80.W, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Unknown SFDP-capable chip, 0 kB: No SFDP signature found. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, id2 0x0 Found Macronix flash chip "MX23L6454" (8192 kB, SPI). This chip's main memory can not be erased/written by design. === This flash part has status UNTESTED for operations: PROBE READ The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Reading flash... done. Raw bitbang mode version 1 Bus Pirate shutdown completed. $ md5sum *.bin* 6d7cf06448bd5ea941a4b458b6067e5f 25l6445.bin 6d7cf06448bd5ea941a4b458b6067e5f 25l6465.bin 6d7cf06448bd5ea941a4b458b6067e5f flashrom_mx23l6454.bin 6d7cf06448bd5ea941a4b458b6067e5f flashrom_mx23l6454.bin2

1 0

Re: [flashrom] [coreboot] New flashrom logo
by Stefan Tauner 14 Mar '15

14 Mar '15

On Wed, 25 Feb 2015 03:38:01 +0100 Peter Stuge <peter(a)stuge.se> wrote: > Carl-Daniel Hailfinger wrote: > > two logos > > I'd recommend avoiding that. It becomes confusing for people. Not necessarily... the facebook "f" or linkedin "in" are examples where parts of the lettering are reused in icons. Based on that idea I have created a lettering containing the SOIC chip and bolt. I doubt this would produce any confusion :) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

4 13

ASUS M2N-MX board enable needed?
by Márton Miklós 13 Mar '15

13 Mar '15

Hello all, I have tried to flash an Asus M2N-MX board, and it failed (if I think it well it needs board enable patch). The chip is a SST49LF040B as the flashrom detected. (Checked physically) Product page can be found here: http://www.asus.com/Motherboards/M2NMX/ Latest BIOS can be found here: http://dlcdnet.asus.com/pub/ASUS/mb/socketAM2/M2N-MX/M2NX1004.zip I have forgotten to save lspci and superiotool logs, let me know if it needed. Thank you for your help in advance! -- Regards, Miklós Márton

2 2

unsupportted borad report
by Michael Cheung 13 Mar '15

13 Mar '15

Hi, my motherboard is asrock H61M Here is the verbose output. best regards; michael # flashrom -V flashrom v0.9.5.2-r1530 on Linux 2.6.32-504.8.1.el6.i686 (i686), built with libpci 3.1.4, GCC 4.4.6 20110731 (Red Hat 4.4.6-3), little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OS timer resolution is 1 usecs, 1293M loops per second, 10 myus = 11 us, 100 myus = 100 us, 1000 myus = 1021 us, 10000 myus = 10056 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "To Be Filled By O.E.M." DMI string system-product-name: "To Be Filled By O.E.M." DMI string system-version: "To Be Filled By O.E.M." DMI string baseboard-manufacturer: "ASRock" DMI string baseboard-product-name: "H61M" DMI string baseboard-version: " " DMI string chassis-type: "Desktop" Found chipset "Intel H61" with PCI ID 8086:1c5c. Enabling flash write... 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode enabled 0xffe00000/0xffa00000 FWH decode enabled 0xffd80000/0xff980000 FWH decode enabled 0xffd00000/0xff900000 FWH decode disabled 0xffc80000/0xff880000 FWH decode disabled 0xffc00000/0xff800000 FWH decode disabled 0xff700000/0xff300000 FWH decode disabled 0xff600000/0xff200000 FWH decode disabled 0xff500000/0xff100000 FWH decode disabled 0xff400000/0xff000000 FWH decode disabled Maximum FWH chip size: 0x100000 bytes BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x0 Root Complex Register Block address = 0xfed1c000 GCS = 0xc24: BIOS Interface Lock-Down: disabled, Boot BIOS Straps: 0x3 (SPI) Top Swap : not enabled SPIBAR = 0xfed1c000 + 0x3800 0x04: 0x6008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=0 Programming OPCODES... program_opcodes: preop=5006 optype=463b opmenu=05d80302c79f0190 done 0x06: 0x0000 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=0, SME=0 0x08: 0x00000000 (FADDR) 0x50: 0x00000a0b (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0x0a, BRRA 0x0b 0x54: 0x00000000 FREG0: WARNING: Flash Descriptor region (0x00000000-0x00000fff) is read-only. 0x58: 0x03ff0180 FREG1: BIOS region (0x00180000-0x003fffff) is read-write. 0x5C: 0x017f0001 FREG2: WARNING: Management Engine region (0x00001000-0x0017ffff) is locked. Please send a verbose log to flashrom(a)flashrom.org if this board is not listed on http://flashrom.org/Supported_hardware#Supported_mainboards yet. Writes have been disabled. You can enforce write support with the ich_spi_force programmer option, but it will most likely harm your hardware! If you force flashrom you will get no support if something breaks. 0x90: 0xc4 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xf84140 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=4, DBC=1, SME=0, SCF=0 0x94: 0x5006 (PREOP) 0x96: 0x463b (OPTYPE) 0x98: 0x05d80302 (OPMENU) 0x9C: 0xc79f0190 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x00002005 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0 0xC8: 0x00002005 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0 0xD0: 0x00000000 (FPB) SPI Read Configuration: prefetching disabled, caching enabled, OK. The following protocols are supported: FWH, SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for AMIC A25LQ032, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for EMST F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for GigaDevice GD25Q20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for GigaDevice GD25Q40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for GigaDevice GD25Q80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for GigaDevice GD25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for GigaDevice GD25Q32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for GigaDevice GD25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for GigaDevice GD25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Macronix MX25L512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Macronix MX25L1005, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Macronix MX25L2005, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Macronix MX25L4005, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Macronix MX25L8005, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Macronix MX25L3205, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Macronix MX25L12805, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Numonyx M25PE10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Numonyx M25PE20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Numonyx M25PE40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Numonyx M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Numonyx M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Numonyx N25Q064, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for PMC Pm25LV010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for PMC Pm25LV512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Sanyo LF25FW203A, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Spansion S25FL032A, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Spansion S25FL064A, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for SST SST25LF040A, 512 kB: program_opcodes: preop=5006 optype=462b opmenu=05ab0302c79f0190 on-the-fly OPCODE (0xAB) re-programmed, op-pos=2 probe_spi_res2: id1 0x15, id2 0x15 Probing for SST SST25LF080A, 1024 kB: probe_spi_res2: id1 0x15, id2 0x15 Probing for SST SST25VF010, 128 kB: probe_spi_rems: id1 0xef, id2 0x15 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xef, id2 0x15 Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xef, id2 0x15 Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Winbond W25Q80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Winbond W25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Winbond W25Q32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Chip status register is 00 Found Winbond flash chip "W25Q32" (4096 kB, SPI) at physical address 0xffc00000. Probing for Winbond W25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Winbond W25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Unknown SFDP-capable chip, 0 kB: program_opcodes: preop=5006 optype=462b opmenu=055a0302c79f0190 on-the-fly OPCODE (0x5A) re-programmed, op-pos=2 Parsing JEDEC flash parameter table... done. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4016 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xef, id2 0x15 Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x14, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xa6, id2 0x80, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0x14, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xa6, id2 0x80, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x14, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xa6, id2 0x80, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xa6, id2 0x80, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xd7, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xa6, id2 0x80, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xa6, id2 0x80, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x14, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xd7, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xa6, id2 0x80, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x14, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xa6, id2 0x80, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Found Winbond flash chip "W25Q32" (4096 kB, SPI). 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). No operations were specified. Restoring MMIO space at 0xb77e38a0 Restoring MMIO space at 0xb77e389c Restoring MMIO space at 0xb77e3898 Restoring MMIO space at 0xb77e3896 Restoring MMIO space at 0xb77e3894 Restoring PCI config space for 00:1f:0 reg 0xdc

1 0

RFC: changes in the development of flashrom
by Stefan Tauner 10 Mar '15

10 Mar '15

Hello folks, hello Carl-Daniel! I am (again) trying to fix our development process. The development of 0.9.8 was an improvement already to what we did previously (since about the 0.9.4 release) although my own resources where quite limited in the second third of the cycle. But obviously it is not enough and we still have some huge problems (e.g. probing, 4B addressing) and I don't see how this is possible with the resources we currently have and use. I have set out my plans already in the wiki: http://flashrom.org/Development_Guidelines The summary is an additional branch named staging where patches are committed to allow for testing them by a broader audience without tainting trunk. Patches will be moved to trunk rather slowly, either after "enough" testing (and an additionally ack) or by the known reviewing process. This kind of mirrors what I do locally already but makes it more publicly. The idea behind this is to still maintain the (at least) four-eyes principle but support it by provoking testing (and superficial reviewing) by non-regulars. My hope is that this helps to keep up our high quality standards with less reviewing strain on the regulars that can not invest as much time as they want to while allowing for faster integrating of changes. I am happy to discuss changes to my proposal until the eventual release of 0.9.8, or the end of February, whatever comes first. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 2

W836xx: Packard Bell Easynote MH45 laptop : flashrom -V
by Tom Meades 10 Mar '15

10 Mar '15

Trying to read the flashrom on this laptop, but is not supported. Want to read out the bios and rewrite the file to an identical laptop motherboard which had a bad flash, and has no known recovery method, so trying to flash in circuit. flashrom v0.9.8-r1887 on Linux 3.13.0-46-generic (i686) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.1, GCC 4.8.2, little endian Command line (3 args): flashrom -p internal -V Calibrating delay loop... OS timer resolution is 1 usecs, 830M loops per second, 10 myus = 12 us, 100 myus = 101 us, 1000 myus = 999 us, 10000 myus = 10018 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Other" DMI chassis-type is not specific enough. DMI string system-manufacturer: "PACKARD BELL BV" DMI string system-product-name: "EasyNote MH45 " DMI string system-version: "PE2 " DMI string baseboard-manufacturer: "PACKARD BELL BV" DMI string baseboard-product-name: "EasyNote MH45 " DMI string baseboard-version: " " W836xx enter config mode worked or we were already in config mode. W836xx leave config mode had no effect. Active config mode, unknown reg 0x20 ID: 85. Please send the output of "flashrom -V -p internal" to flashrom(a)flashrom.org with W836xx: your board name: flashrom -V as the subject to help us finish support for your Super I/O. Thanks. Found ITE EC, ID 0x8512, Rev 0x60 on port 0x2e. ======================================================================== WARNING! You may be running flashrom on an unsupported laptop. We could not detect this for sure because your vendor has not setup the SMBIOS tables correctly. You can enforce execution by adding '-p internal:laptop=this_is_not_a_laptop' to the command line, but please read the following warning if you are not sure. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and http://www.flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== Aborting. Error: Programmer initialization failed. Thanks Tom Meades tomead(a)btopenworld.com

1 0

Re: [flashrom] ASUS M2N-MX board enable needed?
by nicolae788 . 10 Mar '15

10 Mar '15

Hi hi regarding the board enable problem you might not have permission to write the boot block. You can check this by checking if there are 3.3 V on the no.8 pin of the PLCC. If you do not have then you must enable a Gpio to pull this high ( +3.3 V) . I have the same problem but haven't got the time to solve it... Any feedback, if you succeed would be appreciated. Good luck

1 0

FAILED: Gigabyte Z87-D3HP
by Jeroen Vermeulen 10 Mar '15

10 Mar '15

Help! The flashrom tool instructed me to send this email. It also told me not to reboot the machine, but small power outages happen very frequently here... I was trying to upgrade my BIOS on an Ubuntu 14.04 system with a Gigabyte z87-d3hp motherboard, by running: $ sudo flashrom -p internal -w /tmp/Z87D3HP.F7 -o ~/Desktop/flash.log Reading and verifying did work, but writing did not. Log is attached, as is the output of "flashrom -p internal -V". I guess my ROM is hosed at this point. Verifying with the -v option shows that it's different from both my backup and the file I was trying to flash, with output like: $ sudo flashrom -p internal -v /tmp/Z87D3HP.F7 flashrom v0.9.6.1-r1563 on Linux 3.13.0-46-generic (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "Intel Lynx Point". This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... enable_flash_ich_dc_spi: unknown ICH generation. Please report! WARNING: SPI Configuration Lockdown activated. OK. Found Macronix flash chip "MX25L6405" (8192 kB, SPI) at physical address 0xff800000. Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. Reading old flash chip contents... done. Verifying flash... VERIFY FAILED at 0x00000010! Expected=0x5a, Read=0xff, failed byte count from 0x00000000-0x007fffff: 0x664753 (The difference is the same and happens at the same place. Only the byte count differs depending on which file I try to verify against.) Any ideas about what I could do to save my system? Thanks in advance, Jeroen

1 0

Re: [flashrom] Regarding FPGA-based flash chip emulator project
by Stefan Tauner 09 Mar '15

09 Mar '15

On Sat, 7 Mar 2015 18:52:19 +0530 vin ben <vinben94(a)gmail.com> wrote: > Hi Flashrom, > > I am Vinamra. I want to contribute to the FPGA-based flash chip > emulator project in the summer of code program. I have good experience > with digital design and VHDL . Can you please get me started. > Hello Vinamra, having VHDL experience is very important for that project, but you also need to know the communication interface(s) of flash chips to design the emulator. A profitable way to start with that is adding support for yet unknown chips to flashrom by studying their datasheets and the information needed by flashrom to support new chips. Please see http://flashrom.org/Easy_projects#Add_new_flash_chip_definitions on how to do that. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

[PATCH] New GigaDevice chips and tiny pastebug fix
by Роман Титов 09 Mar '15

09 Mar '15

Few days ago stefanct, gave me a bunch of datasheets for GigaDevice chips, so I could get me way into flashrom. Here is 2 pathces. One with GigaDevice chips support and one with a fix to *PROBABLE* pastebug in AMIC A25LQ64 chip definition, which I found earlier. I never used mailing lists and not sure about mime64 attachments, so archive with datasheets can be found here: https://www.dropbox.com/s/sk5mecwj7e4z4t3/GIGADEVICE_GD25LQ.tar.bz2?dl=0

3 3

flashrom + bus pirate + winbond w25q64bv laptop ISP
by typr75s-rog＠yahoo.com 09 Mar '15

09 Mar '15

Hi All - Been trying to dump out the bios on my asus G750JW laptop using flashrom + bus pirate. The bios chip is Winbond w25q64bv. No success until reading the ISP page and tried disconnecting Vcc, using laptop power and holding power button down on laptop. Unfortunately the bios dump is good in the beginning but ends up being corrupted in the end with dummy data FF FF FF .... Does anyone have any suggestions on getting a good bios dump? Thank you!Marc

2 2

Question about flashrom
by Omar Khaled 08 Mar '15

08 Mar '15

Hi. I am Omar from Egypt and i have a question : i have a Raspberry Pi and a spi flash memory (25q128fvsg)i have also a binary file and must be written at exact address 0x80060000 openwrt-ar71xx-generic-linino-u-boot.bin how i can write this file at this address ( just need the command ) Thank's

2 1

Re: [flashrom] Macronix MX23L6454 probe/read success (buspirate_spi)
by Stefan Tauner 08 Mar '15

08 Mar '15

On Sun, 8 Mar 2015 16:57:02 +0000 Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: > On 8 March 2015 at 16:46, Stefan Tauner > <stefan.tauner(a)alumni.tuwien.ac.at> wrote: > > On Sun, 8 Mar 2015 04:48:57 +0000 > > Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: > > > > Your logs show > >> Detected Bus Pirate firmware 6.2 > > I am not sure but I think the latest firmware is a beta firmware that > > shows up as «6.2 ("v6.2-beta1")». Have you looked at that as a possible > > option? > > That's the firmware I'm using. The latest from their google code > downloads page, dated August 2012 - "BPv3-firmware-v6.2-r1981.hex" I don't think so, because your log does not include the text in parentheses. Maybe something has changed in flashrom (I don't think so), but compare your log with this one for example: http://www.flashrom.org/pipermail/flashrom/2014-March/012069.html -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] Macronix MX23L6454 probe/read success (buspirate_spi)
by Stefan Tauner 08 Mar '15

08 Mar '15

On Sun, 8 Mar 2015 04:48:57 +0000 Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: > ...ok definitely a false positive on the "works OK" status! > 3rd resolder, 8th read attempt now. I haven't got two matching files > yet. It keeps missing chunks out, at regular intervals, but different > positions each time. > > I'm happy to upload/send the files & logs somewhere if they'd be useful to you? > > Tomorrow I'll try and find something else that will recognise & read > this. The chip came from a working board so I know the ROM is good. Is the chip still soldered to the board? I guess not because of your wording, but I really don't have any idea where these symptoms could come from if not. Your logs show > Detected Bus Pirate firmware 6.2 I am not sure but I think the latest firmware is a beta firmware that shows up as «6.2 ("v6.2-beta1")». Have you looked at that as a possible option? -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

W836xx: LENOVO 36852BG: flashrom -V
by BW 08 Mar '15

08 Mar '15

# flashrom -V -p internal flashrom v0.9.6.1-r1563 on Linux 3.13.0-46-lowlatency (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.9, GCC 4.7.1, little endian Command line (3 args): flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 476M loops per second, 10 myus = 10 us, 100 myus = 96 us, 1000 myus = 981 us, 10000 myus = 9864 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "LENOVO" DMI string system-product-name: "36852BG" DMI string system-version: "Lenovo B575e" DMI string baseboard-manufacturer: "LENOVO" DMI string baseboard-product-name: "36852BG" DMI string baseboard-version: "Not Available" DMI string chassis-type: "Notebook" Laptop detected via DMI. W836xx enter config mode worked or we were already in config mode. W836xx leave config mode had no effect. Active config mode, unknown reg 0x20 ID: fc. Please send the output of "flashrom -V" to flashrom(a)flashrom.org with W836xx: your board name: flashrom -V as the subject to help us finish support for your Super I/O. Thanks.

1 0

Re: [flashrom] Macronix MX23L6454 probe/read success (buspirate_spi)
by Steven Honeyman 08 Mar '15

08 Mar '15

On 8 March 2015 at 00:46, Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: > On 8 March 2015 at 00:24, Stefan Tauner > <stefan.tauner(a)alumni.tuwien.ac.at> wrote: >> On Sat, 7 Mar 2015 02:24:49 +0000 >> Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: >> >>> Probe and Read both worked, no problems >>> >>> Log: >>> >>> […] >>> Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 >>> 0xc2, id2 0x517 >>> Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 >>> 0xc2, id2 0x517 >>> Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 >>> 0xc2, id2 0x517 >>> Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 >>> 0xc2, id2 0x517 >>> Found Macronix flash chip "MX23L6454" (8192 kB, SPI) on buspirate_spi. >>> Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 >>> 0xc2, id2 0x517 >>> Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: >>> probe_spi_rdid_generic: id1 0xc2, id2 0x517 >>> Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: >>> probe_spi_rdid_generic: id1 0xc2, id2 0x517 >>> Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: >>> probe_spi_rdid_generic: id1 0xc2, id2 0x517 >>> Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: RDID byte 0 >>> parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 >>> Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 >>> kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, >>> id2 0x00 >>> Probing for Macronix MX25L1605, 2048 kB: RDID byte 0 parity violation. >>> probe_spi_rdid_generic: id1 0x00, id2 0x00 >>> […] >> >> Hello Steven, >> >> thanks for your report! >> The log looks quite suspicious in terms of reproducibility. The excerpt >> above shows that the chip replied two different things when queried with >> probe_spi_rdid_generic: all zeros and the correct ID (0xc2517) >> respectively. This is usually an indication for wiring problems. If it >> was that inconsistent all the time you would probably not be able to >> read a good image. Did you read the chip multiple times and compared >> the results? > > Hmmm, I didn't (because it was so slow), but I can do if you think > there were issues. > > I only had a quick look through the image but it looked to be what I > was expecting. > I'll dump the image using some other software/hardware and make sure > that matches too. ...ok definitely a false positive on the "works OK" status! 3rd resolder, 8th read attempt now. I haven't got two matching files yet. It keeps missing chunks out, at regular intervals, but different positions each time. I'm happy to upload/send the files & logs somewhere if they'd be useful to you? Tomorrow I'll try and find something else that will recognise & read this. The chip came from a working board so I know the ROM is good.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom