flashrom

flashrom@flashrom.org

5 participants
9161 discussions

Re: [flashrom] [PATCH] Rigorously check integrity of I/O stream data.
by Stefan Tauner 25 Dec '15

25 Dec '15

On Fri, 25 Dec 2015 23:17:49 +0200 Urja Rannikko <urjaman(a)gmail.com> wrote: > Hi, > > A small nitpick here: > + struct stat image_stat; > + if (fstat(fileno(image), &image_stat) != 0) { > + msg_gerr("Error: getting metadata of file \"%s\" failed: > %s\n", filename, strerror(errno)); > + ret = 1; > + goto out; > + } > + // Try to fsync() only regular files if that function is > available at all (e.g. not provided by MinGW). > +#if defined(_POSIX_FSYNC) && (_POSIX_FSYNC != -1) > + if (S_ISREG(image_stat.st_mode)) { > + if (fsync(fileno(image))) { > + msg_gerr("Error: fsyncing file \"%s\" failed: %s\n", > filename, strerror(errno)); > + ret = 1; > + } > + } > +#endif > > Do we want to fstat if we're not using the results (on mingw), meaning > i suggest move the ifdef above struct stat definition. > Atleast with that moved, > Acked-by: Urja Rannikko <urjaman(a)gmail.com> > True! Thanks. Committed in r1902. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

[commit] r1902 - trunk
by repository service 25 Dec '15

25 Dec '15

Author: stefanct Date: Fri Dec 25 22:59:45 2015 New Revision: 1902 URL: http://flashrom.org/trac/flashrom/changeset/1902 Log: Rigorously check integrity of I/O stream data. Even if fwrite() succeeds the data is not necessarily out of the clib's buffers and writing it eventually could fail. Even if the data is flushed out (explicitly by fflush() or implicitly by fclose()) the kernel might still hold a buffer. Previously we have ignored this to a large extent - even in important cases like writing the flash contents to a file. The results can be truncated images that would brick the respective machine if written back as is (though flashrom would not allow that due to a size mismatch). flashrom would not indicate the problem in any output - so far we only check the return value of fwrite() that is not conclusive. This patch checks the return values of all related system calls like fclose() unless we only read the file and are not really interested in output errors. In the latter case the return value is casted to void to document this fact. Additionally, this patch explicitly calls fflush() and fsync() (on regular files only) to do the best we can to guarantee the read image reaches the disk safely and at least inform the user if it did not work. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: Urja Rannikko <urjaman(a)gmail.com> Modified: trunk/flashrom.c trunk/layout.c trunk/processor_enable.c Modified: trunk/flashrom.c ============================================================================== --- trunk/flashrom.c Sun Nov 22 03:23:31 2015 (r1901) +++ trunk/flashrom.c Fri Dec 25 22:59:45 2015 (r1902) @@ -28,6 +28,7 @@ #include <sys/stat.h> #endif #include <string.h> +#include <unistd.h> #include <stdlib.h> #include <errno.h> #include <ctype.h> @@ -1255,36 +1256,36 @@ msg_gerr("Error: No file I/O support in libpayload\n"); return 1; #else - unsigned long numbytes; - FILE *image; - struct stat image_stat; + int ret = 0; + FILE *image; if ((image = fopen(filename, "rb")) == NULL) { msg_gerr("Error: opening file \"%s\" failed: %s\n", filename, strerror(errno)); return 1; } + + struct stat image_stat; if (fstat(fileno(image), &image_stat) != 0) { msg_gerr("Error: getting metadata of file \"%s\" failed: %s\n", filename, strerror(errno)); - fclose(image); - return 1; + ret = 1; + goto out; } if (image_stat.st_size != size) { msg_gerr("Error: Image size (%jd B) doesn't match the flash chip's size (%lu B)!\n", (intmax_t)image_stat.st_size, size); - fclose(image); - return 1; - } - numbytes = fread(buf, 1, size, image); - if (fclose(image)) { - msg_gerr("Error: closing file \"%s\" failed: %s\n", filename, strerror(errno)); - return 1; + ret = 1; + goto out; } + + unsigned long numbytes = fread(buf, 1, size, image); if (numbytes != size) { msg_gerr("Error: Failed to read complete file. Got %ld bytes, " "wanted %ld!\n", numbytes, size); - return 1; + ret = 1; } - return 0; +out: + (void)fclose(image); + return ret; #endif } @@ -1294,8 +1295,8 @@ msg_gerr("Error: No file I/O support in libpayload\n"); return 1; #else - unsigned long numbytes; FILE *image; + int ret = 0; if (!filename) { msg_gerr("No filename specified.\n"); @@ -1306,14 +1307,37 @@ return 1; } - numbytes = fwrite(buf, 1, size, image); - fclose(image); + unsigned long numbytes = fwrite(buf, 1, size, image); if (numbytes != size) { - msg_gerr("File %s could not be written completely.\n", - filename); - return 1; + msg_gerr("Error: file %s could not be written completely.\n", filename); + ret = 1; + goto out; + } + if (fflush(image)) { + msg_gerr("Error: flushing file \"%s\" failed: %s\n", filename, strerror(errno)); + ret = 1; } - return 0; + // Try to fsync() only regular files and if that function is available at all (e.g. not on MinGW). +#if defined(_POSIX_FSYNC) && (_POSIX_FSYNC != -1) + struct stat image_stat; + if (fstat(fileno(image), &image_stat) != 0) { + msg_gerr("Error: getting metadata of file \"%s\" failed: %s\n", filename, strerror(errno)); + ret = 1; + goto out; + } + if (S_ISREG(image_stat.st_mode)) { + if (fsync(fileno(image))) { + msg_gerr("Error: fsyncing file \"%s\" failed: %s\n", filename, strerror(errno)); + ret = 1; + } + } +#endif +out: + if (fclose(image)) { + msg_gerr("Error: closing file \"%s\" failed: %s\n", filename, strerror(errno)); + ret = 1; + } + return ret; #endif } Modified: trunk/layout.c ============================================================================== --- trunk/layout.c Sun Nov 22 03:23:31 2015 (r1901) +++ trunk/layout.c Fri Dec 25 22:59:45 2015 (r1902) @@ -65,7 +65,7 @@ if (num_rom_entries >= MAX_ROMLAYOUT) { msg_gerr("Maximum number of ROM images (%i) in layout " "file reached.\n", MAX_ROMLAYOUT); - fclose(romlayout); + (void)fclose(romlayout); return 1; } if (2 != fscanf(romlayout, "%s %s\n", tempstr, rom_entries[num_rom_entries].name)) @@ -80,7 +80,7 @@ tstr2 = strtok(NULL, ":"); if (!tstr1 || !tstr2) { msg_gerr("Error parsing layout file. Offending string: \"%s\"\n", tempstr); - fclose(romlayout); + (void)fclose(romlayout); return 1; } rom_entries[num_rom_entries].start = strtol(tstr1, (char **)NULL, 16); @@ -95,7 +95,7 @@ rom_entries[i].end, rom_entries[i].name); } - fclose(romlayout); + (void)fclose(romlayout); return 0; } Modified: trunk/processor_enable.c ============================================================================== --- trunk/processor_enable.c Sun Nov 22 03:23:31 2015 (r1901) +++ trunk/processor_enable.c Fri Dec 25 22:59:45 2015 (r1902) @@ -57,11 +57,11 @@ ptr++; while (*ptr && isspace((unsigned char)*ptr)) ptr++; - fclose(cpuinfo); + (void)fclose(cpuinfo); return (strncmp(ptr, "ICT Loongson-2 V0.3", strlen("ICT Loongson-2 V0.3")) == 0) || (strncmp(ptr, "Godson2 V0.3 FPU V0.1", strlen("Godson2 V0.3 FPU V0.1")) == 0); } - fclose(cpuinfo); + (void)fclose(cpuinfo); return 0; } #endif

1 0

Re: [flashrom] [PATCH] Rigorously check integrity of I/O stream data.
by Stefan Tauner 25 Dec '15

25 Dec '15

On Sun, 29 Nov 2015 17:40:06 +0200 Urja Rannikko <urjaman(a)gmail.com> wrote: > Hi, > > On Sun, Nov 22, 2015 at 7:43 PM, Stefan Tauner > > @@ -1255,36 +1256,39 @@ int read_buf_from_file(unsigned char *buf, unsigned long size, > > […] > > +out: > > + if (fclose(image)) { > > + msg_gerr("Error: closing file \"%s\" failed: %s\n", filename, strerror(errno)); > > + ret = 1; > > + } > > + return ret; > > #endif > > } > Why do this goto stuff and fclose fail reporting to read_buf_from_file? > I'd suggest same handling as below for layout files etc (= (void)fclose()). > > If you fix that (or convince me that you want to print reading fclose > failure), this is acked by me. > Fair enough... I'd rather convert all of them to report errors but I agree that consistency is important, and the checking for errors in that case is highly debatable anyway... so I have void-casted this one and then discovered that fsync is not implemented in MinGW :( I have #if-guarded the respective part in the attached patch. This however does not commit the file as we intend to on Windows. OTOH just fsync()ing on Unix does not provide 100% certainty either so I think this should still get in because it is a clear improvement. It builds fine one the build bot (where expected). -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

[PATCH] Pimp the manpage to create nicer hyperlinks and HTML output.
by Stefan Tauner 25 Dec '15

25 Dec '15

Also, add a target to the makefile to build a flashrom.8.html with groff. FIXME: svn:ignore for the html Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> --- Makefile | 5 ++- flashrom.8.tmpl | 101 ++++++++++++++++++++++++++++++++++++-------------------- 2 files changed, 69 insertions(+), 37 deletions(-) diff --git a/Makefile b/Makefile index c439d8d..6e9dc19 100644 --- a/Makefile +++ b/Makefile @@ -799,7 +799,7 @@ TAROPTIONS = $(shell LC_ALL=C tar --version|grep -q GNU && echo "--owner=root -- # This includes all frontends and libflashrom. # We don't use EXEC_SUFFIX here because we want to clean everything. clean: - rm -f $(PROGRAM) $(PROGRAM).exe libflashrom.a *.o *.d $(PROGRAM).8 + rm -f $(PROGRAM) $(PROGRAM).exe libflashrom.a *.o *.d $(PROGRAM).8 $(PROGRAM).8.html @+$(MAKE) -C util/ich_descriptors_tool/ clean distclean: clean @@ -1054,6 +1054,9 @@ endif @$(DIFF) -q .features.tmp .features >/dev/null 2>&1 && rm .features.tmp || mv .features.tmp .features @rm -f .featuretest.c .featuretest$(EXEC_SUFFIX) +$(PROGRAM).8.html: $(PROGRAM).8 + @groff -mandoc -Thtml $< >$@ + $(PROGRAM).8: $(PROGRAM).8.tmpl @sed -e '1 s#".*".*#"$(shell ./util/getrevision.sh -d $(PROGRAM).8.tmpl 2>/dev/null)" "$(VERSION)"#' <$< >$@ diff --git a/flashrom.8.tmpl b/flashrom.8.tmpl index 8b5f98c..1be8698 100644 --- a/flashrom.8.tmpl +++ b/flashrom.8.tmpl @@ -1,3 +1,38 @@ +.\" Load the www device when using groff; provide a fallback for groff's MTO macro that formats email addresses. +.ie \n[.g] \ +. mso www.tmac +.el \ +. de MTO \\$2 \(la\\$1 \(ra\\$3 +.. +.\" Create wrappers for .MTO and .URL that print only text on systems w/o groff or if not outputting to a HTML +.\" device. To that end we need to distinguish HTML output on groff from other configurations first. +.nr groffhtml 0 +.if \n[.g] \ +. if "\*[.T]"html" \ +. nr groffhtml 1 +.\" For code reuse create a generic wrapper that gets its target macro as first parameter. +.de FKGRF +. ds cmd \\$1 +. shift +. ie (\n[groffhtml]==1) \{\ +. \\*[cmd] \\$@ +. \} +. el \{\ +. ie "\\$2"" \{\ +. BR "\\$1" "\\$3" +. \} +. el \{\ +. RB "\\$2 \(la" "\\$1" "\(ra\\$3" +. \} +. \} +.. +.de URLB +. FKGRF URL \\$@ +.. +.\" Likewise for the MTO macro. FIXME: can these be combined? +.de MTOB +. FKGRF MTO \\$@ +.. .TH FLASHROM 8 "" "" .SH NAME flashrom \- detect, read, write, verify and erase flash chips @@ -160,9 +195,8 @@ if you have proper means to recover from failure! Same as .BR \-\-list\-supported , but outputs the supported hardware in MediaWiki syntax, so that it can be -easily pasted into the wiki page at -.nh -.BR http://www.flashrom.org/ . +easily pasted into the +.URLB https://www.flashrom.org/Supported_hardware "supported hardware wiki page" . Please note that MediaWiki output is not compiled in by default. .TP .B "\-p, \-\-programmer <name>[:parameter[,parameter[,parameter]]]" @@ -453,9 +487,9 @@ unusable (see also the .B BUGS section). The embedded controller (EC) in these machines often interacts badly with flashing. -.nh -.B http://www.flashrom.org/Laptops -has more information. For example the EC firmware sometimes resides on the same +More information is +.URLB http://www.flashrom.org/Laptops "in the wiki" . +For example the EC firmware sometimes resides on the same flash chip as the host firmware. While flashrom tries to change the contents of that memory the EC might need to fetch new instructions or data from it and could stop working correctly. Probing for and reading from the chip may also @@ -628,8 +662,7 @@ syntax where .B addr will be interpreted as usual (leading 0x (0) for hexadecimal (octal) values, or else decimal). For more information please see -.nh -.B http://flashrom.org/VT6421A +.URLB http://flashrom.org/VT6421A "its wiki page" . .SS .BR "nicintel_eeprom " programmer This is the first programmer module in flashrom that does not provide access to NOR flash chips but EEPROMs @@ -733,9 +766,9 @@ where .B state can be .BR on " or " off . -More information about the Bus Pirate pull-up resistors and their purpose is available at -.nh -.BR "http://dangerousprototypes.com/docs/Practical_guide_to_Bus_Pirate_pull-up_r… " . +More information about the Bus Pirate pull-up resistors and their purpose is available +.URLB "http://dangerousprototypes.com/docs/Practical_guide_to_Bus_Pirate_pull-up_r…" \ +"in a guide by dangerousprototypes" . Only the external supply voltage (Vpu) is supported as of this writing. .SS .BR "pickit2_spi " programmer @@ -842,17 +875,13 @@ can be STK200/300, " wiggler " for the Macraigor Wiggler, or " xilinx " for the Xilinx Parallel Cable III (DLC 5)." .sp More information about the RayeR hardware is available at -.nh -.BR "http://rayer.ic.cz/elektro/spipgm.htm " . +.URLB "http://rayer.g6.cz/elektro/spipgm.htm" "RayeR's website" . The Altera ByteBlasterMV datasheet can be obtained from -.nh -.BR "http://www.altera.co.jp/literature/ds/dsbytemv.pdf " . +.URLB "http://www.altera.co.jp/literature/ds/dsbytemv.pdf" Altera . For more information about the Macraigor Wiggler see -.nh -.BR "http://www.macraigor.com/wiggler.htm " . +.URLB "http://www.macraigor.com/wiggler.htm" "their company homepage" . The schematic of the Xilinx DLC 5 was published in -.nh -.BR "http://www.xilinx.com/support/documentation/user_guides/xtp029.pdf " . +.URLB "http://www.xilinx.com/support/documentation/user_guides/xtp029.pdf" "a Xilinx user guide" . .SS .BR "pony_spi " programmer The serial port (like /dev/ttyS0, /dev/ttyUSB0 on Linux or COM3 on windows) is @@ -865,8 +894,7 @@ named "serbang". The optional parameter accepts the values "si_prog" (default) or "serbang". .sp Information about the SI-Prog adapter can be found at -.nh -.BR "http://www.lancos.com/siprogsch.html " . +.URLB "http://www.lancos.com/siprogsch.html" "its website" . .sp An example call to flashrom is .sp @@ -1022,7 +1050,7 @@ needs TCP access to the network or userspace access to a serial port. .B buspirate_spi needs userspace access to a serial port. .sp -.BR dediprog ", " ft2232_spi " and " usbblaster_spi and " pickit2_spi +.BR dediprog ", " ft2232_spi ", " usbblaster_spi " and " pickit2_spi need access to the USB device via libusb. .sp .B dummy @@ -1032,7 +1060,7 @@ needs no access permissions at all. .BR gfxnvidia ", " drkaiser ", " satasii ", " satamv ", " atahpt" and " atavia have to be run as superuser/root, and need additional raw access permission. .sp -.BR serprog ", " buspirate_spi ", " dediprog ", " usbblaster_spi " and " ft2232_spi and " pickit2_spi +.BR serprog ", " buspirate_spi ", " dediprog ", " usbblaster_spi ", " ft2232_spi " and " pickit2_spi can be run as normal user on most operating systems if appropriate device permissions are set. .sp @@ -1045,23 +1073,22 @@ in .B "/etc/rc.securelevel" and rebooting, or rebooting into single user mode. .SH BUGS -Please report any bugs to the flashrom mailing list at -.B "<flashrom(a)flashrom.org>" +Please report any bugs to the +.MTOB "flashrom(a)flashrom.org" "flashrom mailing list" . .sp We recommend to subscribe first at -.sp -.B " http://www.flashrom.org/mailman/listinfo/flashrom" +.URLB "http://www.flashrom.org/mailman/listinfo/flashrom" "" . .sp Many of the developers communicate via the .B "#flashrom" IRC channel on .BR chat.freenode.net . +If you don't have an IRC client, you can use the +.URLB http://webchat.freenode.net/?channels=flashrom "freenode webchat" . You are welcome to join and ask questions, send us bug and success reports there too. Please provide a way to contact you later (e.g.\& a mail address) and be -patient if there is no immediate reaction. Also, we provide a pastebin service -at -.nh -.B http://paste.flashrom.org +patient if there is no immediate reaction. Also, we provide a +.URLB http://paste.flashrom.org "pastebin service" that is very useful when you want to share logs etc.\& without spamming the channel. .SS @@ -1076,8 +1103,8 @@ paragraph in the .B internal programmer subsection of the .B PROGRAMMER-SPECIFIC INFORMATION -section and the information in our wiki at -.BR "http://www.flashrom.org/Laptops " . +section and the information +.URLB "http://www.flashrom.org/Laptops" "in our wiki" . .SS One-time programmable (OTP) memory and unique IDs .sp @@ -1172,8 +1199,10 @@ Yinghai Lu .br some others, please see the flashrom svn changelog for details. .br -All still active authors can be reached via email at <flashrom(a)flashrom.org>. +All still active authors can be reached via +.MTOB "flashrom(a)flashrom.org" "the mailing list" . .PP -This manual page was written by Uwe Hermann <uwe(a)hermann-uwe.de>, -Carl-Daniel Hailfinger and others. +This manual page was written by +.MTOB "uwe(a)hermann-uwe.de" "Uwe Hermann" , +Carl-Daniel Hailfinger, Stefan Tauner and others. It is licensed under the terms of the GNU GPL (version 2 or later). -- Kind regards, Stefan Tauner

1 0

[Laptop read log] HP "Compaq NC6320": Probe: OK, Read: OK
by Denis 'GNUtoo' Carikli 25 Dec '15

25 Dec '15

Hi, Here is a successful read on the HP "Compaq NC6320" laptop (The model seem not to be available trough DMI, however it is written near the screen, on the plastic). flashrom v0.9.6.1-r1563 on Linux 3.13.0-74-generic (x86_64) flashrom was built with libpci 3.1.9, GCC 4.7.1, little endian Command line (7 args): flashrom -VVV -p internal:laptop=force_I_want_a_brick -r BIOS_V.bin -o BIOS_V.log Calibrating delay loop... OS timer resolution is 1 usecs, 1989M loops per second, 10 myus = 11 us, 100 myus = 100 us, 1000 myus = 998 us, 10000 myus = 10011 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "Hewlett-Packard" DMI string system-product-name: " " DMI string system-version: "F.0B" DMI string baseboard-manufacturer: "Hewlett-Packard" DMI string baseboard-product-name: "30AA" DMI string baseboard-version: "KBC Version 58.12" DMI string chassis-type: "Notebook" Laptop detected via DMI. ======================================================================== 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 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. ======================================================================== Proceeding anyway because user forced us to. Found chipset "Intel ICH7M" with PCI ID 8086:27b9. 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 disabled 0xffe00000/0xffa00000 FWH decode disabled 0xffd80000/0xff980000 FWH decode disabled 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 = 0xfed90000 GCS = 0x600460: BIOS Interface Lock-Down: disabled, Boot BIOS Straps: 0x1 (SPI) Top Swap : not enabled SPIBAR = 0xfed90000 + 0x3020 0x00: 0x8004 (SPIS) 0x02: 0x7f10 (SPIC) 0x04: 0x000fffc0 (SPIA) 0x08: 0xffffffff (SPID0) 0x0c: 0xffffffff (SPID0+4) 0x10: 0xffffffff (SPID1) 0x14: 0xffffffff (SPID1+4) 0x18: 0xffffffff (SPID2) 0x1c: 0xffffffff (SPID2+4) 0x20: 0xffffffff (SPID3) 0x24: 0xffffffff (SPID3+4) 0x28: 0xfffeffe0 (SPID4) 0x2c: 0xfff00000 (SPID4+4) 0x30: 0x20054004 (SPID5) 0x34: 0x00000000 (SPID5+4) 0x38: 0x3191f5e9 (SPID6) 0x3c: 0x35312f32 (SPID6+4) 0x40: 0x5936302f (SPID7) 0x44: 0x0d2c4455 (SPID7+4) 0x50: 0x00000000 (BBAR) 0x54: 0x5006 (PREOP) 0x56: 0x7f48 (OPTYPE) 0x58: 0x0405039f (OPMENU) 0x5c: 0x0102d852 (OPMENU+4) 0x60: 0x00000000 (PBR0) 0x64: 0x00000000 (PBR1) 0x68: 0x00000000 (PBR2) WARNING: SPI Configuration Lockdown activated. Reading OPCODES... done OP Type Pre-OP op[0]: 0x9f, read w/o addr, none op[1]: 0x03, read w/ addr, none op[2]: 0x05, read w/o addr, none op[3]: 0x04, write w/o addr, none op[4]: 0x52, write w/ addr, none op[5]: 0xd8, write w/ addr, none op[6]: 0x02, write w/ addr, none op[7]: 0x01, write w/o addr, none Pre-OP 0: 0x06, Pre-OP 1: 0x50 SPI Read Configuration: prefetching disabled, caching enabled, OK. The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: RDID returned 0x20 0x80 0x14 0x00. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L05PU, 64 kB: RDID returned 0x20 0x80 0x14 0x00. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L10PT, 128 kB: RDID returned 0x20 0x80 0x14 0x00. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L10PU, 128 kB: RDID returned 0x20 0x80 0x14 0x00. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L20PT, 256 kB: RDID returned 0x20 0x80 0x14 0x00. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L20PU, 256 kB: RDID returned 0x20 0x80 0x14 0x00. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L40PT, 512 kB: RDID returned 0x20 0x80 0x14 0x00. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L40PU, 512 kB: RDID returned 0x20 0x80 0x14 0x00. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L80P, 1024 kB: RDID returned 0x20 0x80 0x14 0x00. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L16PT, 2048 kB: RDID returned 0x20 0x80 0x14 0x00. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L16PU, 2048 kB: RDID returned 0x20 0x80 0x14 0x00. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L512, 64 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L010, 128 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L020, 256 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L040, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L080, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L016, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25L032, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for AMIC A25LQ032, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF021, 256 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF041A, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF081, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF081A, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF161, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF321, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF321A, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DF641(A), 8192 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25DQ161, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25F512B, 64 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25FS010, 128 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT25FS040, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT26DF041, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT26DF081A, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT26DF161, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT26DF161A, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT26F004, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45CS1282, 16896 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB011D, 128 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB021D, 256 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB041D, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB081D, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB161D, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB321C, 4224 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB321D, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Atmel AT45DB642D, 8192 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for EMST F25L008A, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B05, 64 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B05T, 64 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B10, 128 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B10T, 128 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B20, 256 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B20T, 256 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B40, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B40T, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B80, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B80T, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B16, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B16T, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B32, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B32T, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B64, 8192 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25B64T, 8192 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25F05, 64 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25F10, 128 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25F20, 256 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25F40, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25F80, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25F16, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25F32, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25Q40, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25Q80(A), 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25Q16, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25Q32(A/B), 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25Q64, 8192 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25Q128, 16384 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25QH16, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Eon EN25QH32, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for GigaDevice GD25Q20, 256 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for GigaDevice GD25Q40, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for GigaDevice GD25Q80, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for GigaDevice GD25Q16, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for GigaDevice GD25Q32, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for GigaDevice GD25Q64, 8192 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for GigaDevice GD25Q128, 16384 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L512, 64 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L1005, 128 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L2005, 256 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L4005, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L8005, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L1605, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L1635D, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L1635E, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L3205, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L3235D, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L6405, 8192 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Macronix MX25L12805, 16384 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Numonyx M25PE10, 128 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Numonyx M25PE20, 256 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Numonyx M25PE40, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Numonyx M25PE80, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Chip status register is 00 Found Numonyx flash chip "M25PE80" (1024 kB, SPI) at physical address 0xfff00000. Probing for Numonyx M25PE16, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Numonyx N25Q064, 8192 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for PMC Pm25LV010, 128 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for PMC Pm25LV016B, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for PMC Pm25LV020, 256 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for PMC Pm25LV040, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for PMC Pm25LV080B, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for PMC Pm25LV512, 64 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Sanyo LF25FW203A, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Spansion S25FL004A, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Spansion S25FL008A, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Spansion S25FL016A, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Spansion S25FL032A, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Spansion S25FL064A, 8192 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for SST SST25LF040A, 512 kB: Invalid OPCODE 0xab, will not execute. Probing for SST SST25LF080A, 1024 kB: Invalid OPCODE 0xab, will not execute. Probing for SST SST25VF010, 128 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF016B, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for SST SST25VF032B, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for SST SST25VF064C, 8192 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for SST SST25VF040, 512 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF040B, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for SST SST25VF040B.REMS, 512 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF080B, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P05-A, 64 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P05, 64 kB: RDID returned 0x20 0x80 0x14. Ignoring RES in favour of RDID. Probing for ST M25P10-A, 128 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P10, 128 kB: RDID returned 0x20 0x80 0x14. Ignoring RES in favour of RDID. Probing for ST M25P20, 256 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P40, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P40-old, 512 kB: RDID returned 0x20 0x80 0x14. Ignoring RES in favour of RDID. Probing for ST M25P80, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P16, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P32, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P64, 8192 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25P128, 16384 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25PX16, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25PX32, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for ST M25PX64, 8192 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25Q80, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25Q16, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25Q32, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25Q64, 8192 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25Q128, 16384 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25X10, 128 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25X20, 256 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25X40, 512 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25X80, 1024 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25X16, 2048 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25X32, 4096 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Winbond W25X64, 8192 kB: RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Probing for Unknown SFDP-capable chip, 0 kB: Not mapping flash chip, zero size at 0x00000000. spi_sfdp_read_sfdp_chunk: addr=0x0, len=2, data: Invalid OPCODE 0x5a, will not execute. Receiving SFDP signature failed. Not unmapping zero size at 0xffffffffffffffff Probing for AMIC unknown AMIC SPI chip, 0 kB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0x20 0x80 0x14 0x00. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Not unmapping zero size at 0xffffffffffffffff Probing for Atmel unknown Atmel SPI chip, 0 kB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Not unmapping zero size at 0xffffffffffffffff Probing for Eon unknown Eon SPI chip, 0 kB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Not unmapping zero size at 0xffffffffffffffff Probing for Macronix unknown Macronix SPI chip, 0 kB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Not unmapping zero size at 0xffffffffffffffff Probing for PMC unknown PMC SPI chip, 0 kB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Not unmapping zero size at 0xffffffffffffffff Probing for SST unknown SST SPI chip, 0 kB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Not unmapping zero size at 0xffffffffffffffff Probing for ST unknown ST SPI chip, 0 kB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Not unmapping zero size at 0xffffffffffffffff Probing for Sanyo unknown Sanyo SPI chip, 0 kB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Not unmapping zero size at 0xffffffffffffffff Probing for Generic unknown SPI chip (RDID), 0 kB: Not mapping flash chip, zero size at 0x00000000. RDID returned 0x20 0x80 0x14. probe_spi_rdid_generic: id1 0x20, id2 0x8014 Not unmapping zero size at 0xffffffffffffffff Probing for Generic unknown SPI chip (REMS), 0 kB: Not mapping flash chip, zero size at 0x00000000. Invalid OPCODE 0x90, will not execute. Not unmapping zero size at 0xffffffffffffffff Found Numonyx flash chip "M25PE80" (1024 kB, SPI). Reading flash... done. Restoring MMIO space at 0x7f34c4755070 Restoring PCI config space for 00:1f:0 reg 0xdc Denis.

1 0

External programmers
by Carl-Daniel Hailfinger 25 Dec '15

25 Dec '15

Hi, I'm trying to find out which external programmers should be supported next. 1. There was talk of an AVR-based new programmer using the serprog protocol on IRC by someone with the nick "coldelectrons", but I have no idea if he/she is reading this mail. IMHO more hardware using the serprog protocol is always a good idea. 2. All those Willem/Sivava variants. People regularly request those, but I don't think anyone in here owns the hardware. 3. RayeR's SPIPGM. I have a preliminary patch which could work, but I don't have the hardware. Will send the patch to the list soon. 4. LPC^2, Milksop, CheapLPC and other programmers from the Xbox modding community. 5. Dozens of SPI programmer hardware projects scattered over the net. Too many to count, and I'm not sure which of them has more than one user. In general, it seems creating a new programmer hardware design is like writing IRC clients: A nice way to get started in the field. I have no problems merging flashrom support for all of them, but I won't implement support for all of them myself. Regards, Carl-Daniel -- http://www.hailfinger.org/

8 13

Macronix Erase/Write Problems
by Adam Clarke 25 Dec '15

25 Dec '15

Good morning, I am trying to revive a computer which had a failed BIOS update. I bought a BUS Pirate and started using Flashrom to take a copy of an identical fully working model. Strangely this machine has two chips: MX25L6405D MX25L3205D >From the dump's I have made, I believe the MX25L6405D holds the BIOS and the MX25L3205D possibly holds the ME Firmware. Don't know if this is any use but an output from fptw64 on the working machine shows me the following: C:\FPTw64>fptw64.exe -i Intel (R) Flash Programming Tool. Version: 8.0.10.1464 Copyright (c) 2007 - 2012, Intel Corporation. All rights reserved. Platform: Intel(R) Q77 Express Chipset Reading HSFSTS register... Flash Descriptor: Valid --- Flash Devices Found --- MX25L6405D ID:0xC22017 Size: 8192KB (65536Kb) MX25L3205D ID:0xC22016 Size: 4096KB (32768Kb) --- Flash Image Information -- Signature: VALID Number of Flash Components: 2 Component 1 - 8192KB (65536Kb) Component 2 - 4096KB (32768Kb) Regions: Descriptor - Base: 0x000000, Limit: 0x000FFF BIOS - Base: 0x600000, Limit: 0xBFFFFF ME - Base: 0x005000, Limit: 0x5FFFFF GbE - Base: 0x001000, Limit: 0x004FFF PDR - Not present Master Region Access: CPU/BIOS - ID: 0x0000, Read: 0x0B, Write: 0x0A ME - ID: 0x0000, Read: 0x0D, Write: 0x0C GbE - ID: 0x0118, Read: 0x08, Write: 0x08 Total Accessable SPI Memory: 12288KB, Total Installed SPI Memory : 12288KB I am struggling to properly erase/write to both of these chips so I wondered if you could offer any advise on trying to get this working? These are the errors I am getting on both chips, have tried with both Linux and Windows on each chip and get pretty much the same output: flashrom v0.9.7-r1711 on Linux 3.14.48-std454-amd64 (x86_64) flashrom was built with libpci 3.2.0, GCC 4.8.4, little endian Command line (8 args): flashrom -p buspirate_spi:dev=/dev/ttyUSB0, -c MX25L6405(D) -E -V -o /media/usb/log2.txt Calibrating delay loop... OS timer resolution is 1 usecs, 1456M loops per second, 10 myus = 11 us, 100 myus = 100 us, 1000 myus = 997 us, 10000 myus = 9996 us, 4 myus = 4 us, OK. Initializing buspirate_spi programmer Baud rate is 115200. Detected Bus Pirate hardware v3.a Detected Bus Pirate firmware 6.3 ("v6.3-beta1") Using SPI command set v2. SPI speed is 8MHz Raw bitbang mode version 1 Raw SPI mode version 1 The following protocols are supported: SPI. Probing for Macronix MX25L6405(D), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on buspirate_spi. Chip status register is 0x80. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is set Chip status register: Bit 6 is not set Chip status register: Block Protect 3 (BP3) is not set Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). Block protection is disabled. Erasing and writing flash chip... Trying erase function 0... 0x000000-0x00ffff:EFAILED at 0x00001000! Expected=0xff, Found=0x90, failed byte count from 0x00000000-0x0000ffff: 0x3aa8 ERASE FAILED! Reading current flash chip contents... At one point the above was the same output as below that everything was set but still failed on "unsetting lock bits" but I have forgotten to save that output. flashrom was built with GCC 4.9.2, little endian Command line (6 args): flashrom -p buspirate_spi:dev=COM3 -c MX25L3205D/MX25L3208D -E -V Calibrating delay loop... OS timer resolution is 501 usecs, 1771M loops per second, 10 myus = 0 us, 100 myus = 0 us, 1000 myus = 1000 us, 10000 myus = 10008 us, 2004 myus = 2002 us, OK. Initializing buspirate_spi programmer Baud rate is 115200. Detected Bus Pirate hardware v3.a Detected Bus Pirate firmware 6.3 Using SPI command set v2. SPI speed is 8MHz Raw bitbang mode version 1 Raw SPI mode version 1 The following protocols are supported: SPI. Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2016 Found Macronix flash chip "MX25L3205D/MX25L3208D" (4096 kB, SPI) on buspirate_spi. Chip status register is 0xff. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is set Chip status register: Bit 6 is set Chip status register: Block Protect 3 (BP3) is set Chip status register: Block Protect 2 (BP2) is set Chip status register: Block Protect 1 (BP1) is set Chip status register: Block Protect 0 (BP0) is set Chip status register: Write Enable Latch (WEL) is set Chip status register: Write In Progress (WIP/BUSY) is set This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). Some block protection in effect, disabling... Need to disable the register lock first... Unsetting lock bit(s) failed. Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:EFAILED at 0x00000000! Expected=0xff, Found=0xe8, failed byte count from 0x00000000-0x00000fff: 0x1000 ERASE FAILED! Reading current flash chip contents... ^C This is a link to the datasheet for both chips : http://www.macronix.com/Lists/DataSheet/Attachments/2453/MX25L6405D,%203V,%… It mentions something about having to give 9.5v-10.5v to the WP pin so maybe that is the problem? does this mean i would have to externally source this voltage outside of bus pirate to enable write enable properly? Many Thanks

2 1

Can't probe AT26DF321 on OptiPlex 755
by Patrick 'P. J.' McDermott 25 Dec '15

25 Dec '15

Hi, I have a Dell OptiPlex 755 USFF which has an Atmel AT26DF321 SPI flash chip (which is like an AT25DF321 and has the same device ID except it doesn't have a HOLD# pin). I've used flashrom to read and write the same chip on another board by ISP using a BeagleBone Black, 10-cm jumper cables, a SOIC clip, and an ATX PSU. However, flashrom with the same ISP setup fails to probe the chip on the OptiPlex. I've tried two different known-working BBBs, different cables, two different Pomona SOIC clips, connecting WP# to 3.3 V, connecting what would be HOLD# on the AT25 to 3.3 V, and different spispeed clock frequencies from 1 kHz to 10 MHz. I've tried powering the chip (and the rest of the board's 3.3-V rail) with a 3.3-V line of the ATX PSU, and I've tried instead powering the whole board with the computer's 12-V PSU. I've also tried running flashrom while holding down the power button to keep the system in reset. Following some advice on <http://flashrom.org/ISP> I even tried removing the DIMMs and CPU. Every time I get only bytes of 0xff from the chip, as in the attached log. In my experience that usually means either the programmer isn't properly connected to the chip or the programmer uses a different data voltage than the chip does. But I've checked and rechecked all of the connections, and I know both the BBB and the AT26DF321 use 3.3-V data signals. Unfortunately there don't seem to be any schematics available for this board (Dell model number 0HX555, ODM model number HX533 A00, ODM might be Asustek or MiTAC). This system does have an Intel Management Engine in the northbridge, but even if that was running I should at least be able to probe the chip and read its contents. Does anyone have any ideas of anything else I could try (short of desoldering the chip from the board) or about what the problem may be? Thanks, -- Patrick "P. J." McDermott http://www.pehjota.net/ Lead Developer, ProteanOS http://www.proteanos.com/

3 4

Re: [flashrom] MS7336 (HP Compaq dx2300 Microtower motherboard) successful BIOS update
by Stefan Tauner 25 Dec '15

25 Dec '15

On Tue, 18 Aug 2015 18:53:15 +0200 Benjamin Bellec <b.bellec(a)gmail.com> wrote: > Hello, > > I successfully flashed this motherboard with a Winbond flash chip > "W39V080FA (1024 kB, FWH)" which is currently tagged as UNTESTED for ERASE > and WRITE. > http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=3353051 > > I flashed from BIOS version 1.08 to 1.14 (the last one). > Note that the BIOS included some DMI data (SKU number, Serial number, UUID, > etc.) which have been deleted during the operation. See > dmidecode_before/after log files attached for more information. Hello Benjamin, thanks for your report! I have added your board (as MS-7336 with a note) to our list of supported hardware and will commit that later together with other small changes. The flash chip got already marked as fully tested in the meantime. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] Gigabyte GA-Z97MX Gaming 5
by Stefan Tauner 25 Dec '15

25 Dec '15

On Thu, 20 Aug 2015 16:28:03 +0300 XVilka Haos of System <xvilka(a)gmail.com> wrote: > Hello! Trying to make flashrom working on the Gigabyte GA-Z97MX Gaming > 5 mainboard. > It has ITE IT8620E Super I/O chip, DualBIOS configuration, thus 2 MXIC > MX25L6473E chips. > Attaching some logs: > http://paste.flashrom.org/view.php?id=2779 I don't see anything that looks like it would not work? What was the actual problem? -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom