- flashrom - mail.coreboot.org

Support and configuration
by Goran Metlic 27 Dec '15

27 Dec '15

Hi I have used Flashrom and raspberry pie to flash spi bios chips in past. I need now to flash a parallel flash chip. Is there any way to acomplish this using raspberry pie? Flah memory in question is am29lv800bttc-90. Kind regards Goran Metlic

1 0

Re: [flashrom] HP XW9300 mainboard
by Stefan Tauner 27 Dec '15

27 Dec '15

On Wed, 12 Aug 2015 10:55:06 +0000 Federico Tomasi <federico.tomasi(a)gmail.com> wrote: > Hi, > > I already tried some time ago to flash my hp xw9300 mainboard bios but with > no luck. Then I realized that I was using Ubuntu on a VirtualBox so it > maybe could not access the mainborad chip... > > I retried in these days using an Ubuntu live-cd, and I also read this old > forum thread > > http://forums.bit-tech.net/showpost.php?s=c0347634d93e911f8254f28ec1a83fc1&… > > where a guy tells to have succesfully written a Tyan original bios on the > HP branded version of the same mainboard (the Tyan K8WE S2895) that is the > HP XW9300 mainboard. > (I didn't connect pins as he edit it wasn't necessary to do that but to > enable the jumper of boot block) > Hi Federico, it seems like different versions of the firmware engage different write protection mechanisms and your version requires either a small piece of code in flashrom to disable the write protection or the ugly hack of connection the respective pins to VDD. The problem is that deriving the right commands for the board is not straight forward and no one bothered to find them yet (it requires reverse engineering the firmware files). -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] [PATCH 1/3] Add support for libftdi1.
by Stefan Tauner 25 Dec '15

25 Dec '15

On Sun, 15 Nov 2015 16:40:45 +0100 Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> wrote: > Many distros no longer provide libftdi 0.2, and as a result, > programmers that depend on libftdi must be disabled. This means that > popular programmers, such as ft2232_spi are now disabled in modern > distros. Luckily the libftdi API did not change significantly, so > for our purposes, we can simply use the newer headers and link to the > newer library. > > Signed-off-by: Alexandru Gagniuc <mr.nuke.me(a)gmail.com> > Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Self-acked and committed in r1904. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

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

25 Dec '15

Author: stefanct Date: Fri Dec 25 23:42:45 2015 New Revision: 1904 URL: http://flashrom.org/trac/flashrom/changeset/1904 Log: Add support for libftdi1. Many distros no longer provide libftdi 0.2, and as a result, programmers that depend on libftdi must be disabled to compile flashrom. Luckily the libftdi API did not change significantly, so for our purposes, we can simply use the newer headers and link to the newer library if it is available. Signed-off-by: Alexandru Gagniuc <mr.nuke.me(a)gmail.com> Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Modified: trunk/Makefile Modified: trunk/Makefile ============================================================================== --- trunk/Makefile Fri Dec 25 23:13:15 2015 (r1903) +++ trunk/Makefile Fri Dec 25 23:42:45 2015 (r1904) @@ -634,8 +634,10 @@ endif ifeq ($(NEED_FTDI), yes) -FTDILIBS := $(shell ([ -n "$(PKG_CONFIG_LIBDIR)" ] && export PKG_CONFIG_LIBDIR="$(PKG_CONFIG_LIBDIR)" ); pkg-config --libs libftdi || printf "%s" "-lftdi -lusb") +FTDILIBS := $(shell ([ -n "$(PKG_CONFIG_LIBDIR)" ] && export PKG_CONFIG_LIBDIR="$(PKG_CONFIG_LIBDIR)" ); pkg-config --libs libftdi1 || pkg-config --libs libftdi || printf "%s" "-lftdi -lusb") FEATURE_CFLAGS += $(shell LC_ALL=C grep -q "FT232H := yes" .features && printf "%s" "-D'HAVE_FT232H=1'") +FTDI_INCLUDES := $(shell ([ -n "$(PKG_CONFIG_LIBDIR)" ] && export PKG_CONFIG_LIBDIR="$(PKG_CONFIG_LIBDIR)" ); pkg-config --cflags-only-I libftdi1) +FEATURE_CFLAGS += $(FTDI_INCLUDES) FEATURE_LIBS += $(shell LC_ALL=C grep -q "FTDISUPPORT := yes" .features && printf "%s" "$(FTDILIBS)") # We can't set NEED_USB here because that would transform libftdi auto-enabling # into a hard requirement for libusb, defeating the purpose of auto-enabling. @@ -759,7 +761,7 @@ ifeq ($(NEED_USB), yes) CHECK_LIBUSB0 = yes FEATURE_CFLAGS += -D'NEED_USB=1' -USBLIBS := $(shell ([ -n "$(PKG_CONFIG_LIBDIR)" ] && export PKG_CONFIG_LIBDIR="$(PKG_CONFIG_LIBDIR)" ); pkg-config --libs libusb || printf "%s" "-lusb") +USBLIBS := $(shell ([ -n "$(PKG_CONFIG_LIBDIR)" ] && export PKG_CONFIG_LIBDIR="$(PKG_CONFIG_LIBDIR)" ); pkg-config --libs libusb || printf "%s" "-lusb") endif ifeq ($(CONFIG_PRINT_WIKI), yes) @@ -1023,12 +1025,12 @@ ifeq ($(NEED_FTDI), yes) @printf "Checking for FTDI support... " @echo "$$FTDI_TEST" > .featuretest.c - @$(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) .featuretest.c -o .featuretest$(EXEC_SUFFIX) $(FTDILIBS) $(LIBS) >/dev/null 2>&1 && \ + @$(CC) $(CPPFLAGS) $(CFLAGS) $(FTDI_INCLUDES) $(LDFLAGS) .featuretest.c -o .featuretest$(EXEC_SUFFIX) $(FTDILIBS) $(LIBS) >/dev/null 2>&1 && \ ( echo "found."; echo "FTDISUPPORT := yes" >> .features.tmp ) || \ ( echo "not found."; echo "FTDISUPPORT := no" >> .features.tmp ) @printf "Checking for FT232H support in libftdi... " @echo "$$FTDI_232H_TEST" >> .featuretest.c - @$(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) .featuretest.c -o .featuretest$(EXEC_SUFFIX) $(FTDILIBS) $(LIBS) >/dev/null 2>&1 && \ + @$(CC) $(CPPFLAGS) $(CFLAGS) $(FTDI_INCLUDES) $(LDFLAGS) .featuretest.c -o .featuretest$(EXEC_SUFFIX) $(FTDILIBS) $(LIBS) >/dev/null 2>&1 && \ ( echo "found."; echo "FT232H := yes" >> .features.tmp ) || \ ( echo "not found."; echo "FT232H := no" >> .features.tmp ) endif

1 0

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

25 Dec '15

Author: stefanct Date: Fri Dec 25 23:13:15 2015 New Revision: 1903 URL: http://flashrom.org/trac/flashrom/changeset/1903 Log: Add support for Sanyo LE25FU406C/LE25U40CMC. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Tested-by: Jose Luis León <zenky1(a)gmail.com> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Modified: trunk/flashchips.c trunk/flashchips.h Modified: trunk/flashchips.c ============================================================================== --- trunk/flashchips.c Fri Dec 25 22:59:45 2015 (r1902) +++ trunk/flashchips.c Fri Dec 25 23:13:15 2015 (r1903) @@ -10675,6 +10675,43 @@ { .vendor = "Sanyo", + .name = "LE25FU406C/LE25U40CMC", + .bustype = BUS_SPI, + .manufacture_id = SANYO_ID, + .model_id = SANYO_LE25FU406C, + .total_size = 512, + .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, 128} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {4 * 1024, 128} }, + .block_erase = spi_block_erase_d7, + }, { + .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_bp2_srwd, + .unlock = spi_disable_blockprotect_bp2_srwd, + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B), dual read (0x3B) and dual I/O (0xBB) supported */ + .voltage = {2300, 3600}, + }, + + { + .vendor = "Sanyo", .name = "LE25FW203A", .bustype = BUS_SPI, .manufacture_id = SANYO_ID, Modified: trunk/flashchips.h ============================================================================== --- trunk/flashchips.h Fri Dec 25 22:59:45 2015 (r1902) +++ trunk/flashchips.h Fri Dec 25 23:13:15 2015 (r1903) @@ -595,6 +595,7 @@ #define SANYO_LE25FW418A 0x10 /* RES2 and some weird 1 byte RDID variant */ #define SANYO_LE25FW406A 0x1A /* RES2, no datasheet */ #define SANYO_LE25FU406B 0x1E /* LE25FW418A without HD_READ mode option variant */ +#define SANYO_LE25FU406C 0x0613 /* Also known as LE25U40CMC apparently */ #define SANYO_LE25FW806 0x26 /* RES2 and some weird 1 byte RDID variant */ #define SANYO_LE25FW808 0x20 /* RES2 and some weird 1 byte RDID variant */

1 0

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

Re: [flashrom] SST49LF016C: Supermicro X7DWT successfully reflashed
by Stefan Tauner 25 Dec '15

25 Dec '15

On Thu, 10 Sep 2015 05:56:54 +0000 Steven Stremciuc <steven(a)stremciuc.net> wrote: > The Supermicro X7DWT motherboard is not listed on the flashrom supported > hardware page, and the SST49LF016C chip has an "?" for erase and write > status. I successfully reflashed the chip using flashrom, and thought I > would send you a note so you can update the supported hardware list, if you > would like. > This board(s) was in a Dell C6100 XS23-SB. Hello Steven, thanks for your report! I have added your board to our list of supported hardware and marked the flash chip as fully tested. Also, I have marked the "Multi-system" chassis type as non-laptop type so that the additional parameter is no longer necessary. I will commit all that later together with other small changes. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Support for Rangely Chips with Winboad W25Q64.V tested
by Jeremy Porter 24 Dec '15

24 Dec '15

I noticed that both the chip and the chipset show as untested on the wiki. I can confirm that these work, as we use flashrom extensively on our, Netgate RCC-VE 2440, 4860, 8860, and our DFF-2220. systems. (The boards just have differing amounts of Ram/ethernet ports and CPUs) These are based on the Intel Rangely Chipset PCI ID 8086:1f38. So if you want to update the wiki, those can be marked as tested and working. (We've flashed hundreds of systems). ./flashrom -p internal -V flashrom v0.9.8-r1896 on FreeBSD 10.2-RELEASE (amd64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.3.1, LLVM Clang 3.4.1 (tags/RELEASE_34/dot1-final 208032), little endian Command line (3 args): ./flashrom -p internal -V Calibrating delay loop... OS timer resolution is 1 usecs, 600M loops per second, 10 myus = 10 us, 100 myus = 101 us, 1000 myus = 1018 us, 10000 myus = 10066 us, 4 myus = 4 us, OK. Initializing internal programmer Found candidate at: 00000500-00000510 Found coreboot table at 0x00000500. Found candidate at: 00000c00-00000da4 Found coreboot table at 0x00000c00. coreboot table found at 0x7fbf0c00. coreboot header(24) checksum: 913c table(420) checksum: db66 entries: 11 Vendor ID: Intel, part ID: Mohon Peak Using Internal DMI decoder. DMI string chassis-type: "Desktop" DMI string system-manufacturer: "ADI Engineering" DMI string system-product-name: "RCC-VE" DMI string system-version: "1.0" DMI string baseboard-manufacturer: "ADI Engineering" DMI string baseboard-product-name: "RCC-VE" DMI string baseboard-version: "1.0" Found chipset "Intel Avoton/Rangeley" with PCI ID 8086:1f38. 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... Root Complex Register Block address = 0xfed1c000 GCS = 0x40000c01: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) Top Swap: not enabled 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 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 enabled 0xffc80000/0xff880000 FWH decode enabled 0xffc00000/0xff800000 FWH decode enabled 0xff700000/0xff300000 FWH decode enabled 0xff600000/0xff200000 FWH decode enabled 0xff500000/0xff100000 FWH decode enabled 0xff400000/0xff000000 FWH decode enabled Maximum FWH chip size: 0x100000 bytes SPI_BASE_ADDRESS = 0xfed01000 SPI Read Configuration: prefetching enabled, caching enabled, BIOS_CNTL = 0x09: BIOS Lock Enable: disabled, BIOS Write Enable: enabled 0x04: 0x6000 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=0, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=0 Programming OPCODES... done 0x06: 0x0000 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=0, SME=0 0x50: 0x00001f1f (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0x1f, BRRA 0x1f 0x54: 0x000f0000 FREG0: Flash Descriptor region (0x00000000-0x0000ffff) is read-write. 0x58: 0x07ff0010 FREG1: BIOS region (0x00010000-0x007fffff) is read-write. 0x90: 0x00 (SSFS) SSFS: SCIP=0, FDONE=0, FCERR=0, AEL=0 0x91: 0xf84900 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=0, DBC=9, SME=0, SCF=0 0x94: 0x5006 (PREOP) 0x96: 0x463b (OPTYPE) 0x98: 0x05d80302 (OPMENU) 0x9C: 0xc79f0190 (OPMENU+4) 0xC4: 0x00800000 (LVSCC) LVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x0, VCL=1 0xC8: 0x00000000 (UVSCC) UVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x0 0xD0: 0x00000000 (FPB) OK. The following protocols are supported: FWH, SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB321E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25P64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25LQ40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25LQ80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25LQ64(B), 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25LQ128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L3273E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L6405D, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L12805D, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25U12835F, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix MX25L6495F, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 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 0xef, id2 0x4017 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 0xef, id2 0x4017 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 0xef, id2 0x4017 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 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LQ020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LQ040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LQ080, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LQ016, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LQ032C, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL132K, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL164K, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL127S-64kB, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL127S-256kB, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL128P......0, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL128P......1, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL128S......1, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL129P......0, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Spansion S25FL129P......1, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0xef, id2 0x16 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x16, id2 0x16 Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0xef, id2 0x16 Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0xef, id2 0x16 Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0xef, id2 0x16 Probing for SST SST25VF020B, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xef, id2 0x16 Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xef, id2 0x16 Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST SST25WF080, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q40.V, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0x00000000ff800000. Chip status register is 0x00. Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q40.W, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q80.W, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Unknown SFDP-capable chip, 0 kB: Parsing JEDEC flash parameter table... done. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xef, id2 0x4017 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xef, id2 0x16 Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x8b, id2 0xcf, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0x8b, id2 0xcf, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x8b, id2 0xcf, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x69, id2 0x6c, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x8b, id2 0xcf, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x8b, id2 0xcf, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, 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 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Found Winbond flash chip "W25Q64.V" (8192 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 0x8007bb09c Restoring MMIO space at 0x8007bb098 Restoring MMIO space at 0x8007bb096 Restoring MMIO space at 0x8007bb094 root@4gtest:~/flashrom #

2 2

Succesfull update on untested hardware
by Bernard Grymonpon 24 Dec '15

24 Dec '15

Hi, included a log on a SuperMicro A1SAi board (Intel Atom). The log said it was untested. Thanks for the nice tool, Rgds, Bernard

2 1

Re: [flashrom] Report on Flashing chip
by Stefan Tauner 24 Dec '15

24 Dec '15

On Thu, 24 Dec 2015 10:29:31 +0800 Евгений Черкашин <eugeneai(a)irnok.net> wrote: > Hi! > > 2015-12-24 9:24 GMT+08:00 Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at>: > > > On Mon, 24 Aug 2015 02:42:56 +0000 > > Евгений Черкашин <eugeneai(a)irnok.net> wrote: > > > > > Hi! > > > I saw Your notification when flashing my Motherboard BIOS. > > > > > > It said that flashing is successful > > > > > > Base Board Information > > > Manufacturer: ASUSTeK Computer INC. > > > Product Name: P5GD1-VM > > > Version: Rev 1.xx > > > Serial Number: MB-1234567890 > > > > > > > > > Reboot was successful too. > > > > > > > > > CHIP ID: W39V040FA > > > > Hi Евгений, > > > > thanks for your report! I wonder if you had to enable the untested > > board enable to make it work (because I would expect that but you did > > not mention anything about that)? > > > No special enablings were performed. If it were so I'd not be risky. OK, then we could probably mark the -VM version as tested too. Could you please send me the file logfile.txt created by flashrom -p internal -o logfile.txt to verify my theory? -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] [PATCH] Fix compilation with only one enabled programmer.
by Carl-Daniel Hailfinger 24 Dec '15

24 Dec '15

On 21.11.2015 00:43, Stefan Tauner wrote: > Compilers are free to use an unsigned data type for enumerations without > negative elements. Our enumeration of all programmers is one such > instance. Also, compilers will warn about comparisons of unsigned enum > expressions < 0. > > If we enable only a single programmer then PROGRAMMER_INVALID will be 1. > We do some run-time checks of loop counters of an unsigned enumaration > type against PROGRAMMER_INVALID in the form of > if (p < PROGRAMMER_INVALID - 1) > which get optimized to > if (p < 0) > This makes the check always false and the compiler warnings compulsory. Which gcc version is this? > This patch adds #ifdefs guarding these checks if there is only one programmer > enabled. > > --- > One can enable a single programmer by running > grep CONFIG_ Makefile |fgrep '?= yes'|grep -vi serprog |sed "s/ .*/=no/"|xargs make CONFIG_SERPROG=yes > > Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> > --- > flashrom.c | 9 ++++++++- > 1 file changed, 8 insertions(+), 1 deletion(-) > > diff --git a/flashrom.c b/flashrom.c > index c9c7e31..abb917b 100644 > --- a/flashrom.c > +++ b/flashrom.c > @@ -1633,10 +1633,13 @@ void list_programmers(const char *delim) > enum programmer p; > for (p = 0; p < PROGRAMMER_INVALID; p++) { > msg_ginfo("%s", programmer_table[p].name); > + > +#if PROGRAMMER_INVALID > 1 > if (p < PROGRAMMER_INVALID - 1) Does the warning also disappear if you write if ((PROGRAMMER_INVALID > 1) && (p < PROGRAMMER_INVALID - 1) ) instead? AFAICS that should placate gcc (since this is a constant false expression for PROGRAMMER_INVALID==1) even with warnings switched on. > msg_ginfo("%s", delim); > +#endif > } > - msg_ginfo("\n"); > + msg_ginfo("\n"); > } > > void list_programmers_linebreak(int startcol, int cols, int paren) > @@ -1668,6 +1671,7 @@ void list_programmers_linebreak(int startcol, int cols, int paren) > } > msg_ginfo("%s", pname); > remaining -= pnamelen; > +#if PROGRAMMER_INVALID > 1 > if (p < PROGRAMMER_INVALID - 1) { > msg_ginfo(","); > remaining--; > @@ -1675,6 +1679,9 @@ void list_programmers_linebreak(int startcol, int cols, int paren) > if (paren) > msg_ginfo(")"); > } > +#else > + msg_ginfo(")"); Please drop the complete #else block. It adds a ")" where none should be. It doesn't just look strange in the code, I also verified the output. > +#endif > } > } > Regards, Carl-Daniel

2 3

Re: [flashrom] Report on Flashing chip
by Stefan Tauner 24 Dec '15

24 Dec '15

On Mon, 24 Aug 2015 02:42:56 +0000 Евгений Черкашин <eugeneai(a)irnok.net> wrote: > Hi! > I saw Your notification when flashing my Motherboard BIOS. > > It said that flashing is successful > > Base Board Information > Manufacturer: ASUSTeK Computer INC. > Product Name: P5GD1-VM > Version: Rev 1.xx > Serial Number: MB-1234567890 > > > Reboot was successful too. > > > CHIP ID: W39V040FA Hi Евгений, thanks for your report! I wonder if you had to enable the untested board enable to make it work (because I would expect that but you did not mention anything about that)? Also, which flashrom version did you use? In any case I have marked the flash chip as fully tested and will commit that later together with other small changes. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

SST49LF040B: ASUS M2N-E-SLI successfully reflashed
by Александр Трубицын 24 Dec '15

24 Dec '15

Hello, Stefan! With best regards, Alexander V. Trubitsyn

2 1

MX25L8006E: Gigabyte EP31-DS3L rev 1.0 sucessfully reflashed
by Александр Трубицын 24 Dec '15

24 Dec '15

Hi, Stefan! -- With best regards, Alexander V. Trubitsyn

2 1

HP Probook 6450b: programmer initialization failed
by Александр Трубицын 24 Dec '15

24 Dec '15

Hi! I try to read flash from friends of mine notebook HP Probook 6450b and have no sucess on it. -- With best regards, Alexander V. Trubitsyn

2 1

W25X80: ASUS P5K SE sucessfully reflashed
by Александр Трубицын 24 Dec '15

24 Dec '15

Hi! -- With best regards, Alexander V. Trubitsyn

2 1

W25Q64.V: flashrom can't read flash on ASUS P8H77-V LE
by Александр Трубицын 24 Dec '15

24 Dec '15

Hi! -- With best regards, Alexander V. Trubitsyn

2 1

Re: [flashrom] Problems flashing N25Q064A13ESE40E SPI chip
by Stefan Tauner 24 Dec '15

24 Dec '15

On Fri, 11 Dec 2015 10:52:38 +0100 Ruben Van de Put <rubenvandeput(a)gmail.com> wrote: > Hello, > > I'm having some problems flashing a SPI chip with the BusPirate V3. Writing > the image is successful but verification is not successful. > > First try with chip on breadboard and long leads (20-25cm): > http://paste.flashrom.org/view.php?id=2841 > > Then I shortened the signal leads and soldered them directly on the > BusPirate: > http://paste.flashrom.org/view.php?id=2842 > > Then I soldered all leads directly on the chip (with an adapter) instead of > using a breadboard: > http://paste.flashrom.org/view.php?id=2844 > > I also tried lowering the SPI speed to 1 MHz: > http://paste.flashrom.org/view.php?id=2845 > > Current set-up > [image: Inline afbeelding 1] > [image: Inline afbeelding 2] > > Chip datasheet: http://www.farnell.com/datasheets/1674442.pdf > Flash connected in this way: http://flashrom.org/Bus_Pirate > > Is there anything else I can try or should I try replacing the flash chip? Hi Ruben, if you did not give up yet: looks like your changes constantly improved the situation and you would probably succeed if you just continued to write the same image a few more times. One thing that could further improve the communication between the BP and the flash chip: adding line termination resistors or capacitors as well as a decoupling capacitor between VCC and GND as near as possible to the flash chip. See also https://www.flashrom.org/ISP with some more details even though the site is directed at other use cases. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] FAILED: Lenovo X1 (2015)
by Rui Paulo 24 Dec '15

24 Dec '15

On Thu, 2015-12-17 at 13:08 +0300, Антон Кочков wrote: > Hello! > Mainstream flashrom currently not yet merged patches, adding support > of reading layout. Because ME region usually not readable not from ME > itself, > it should be skipped, so using layout file, in your case: > # flashrom layout v2 > 0x00000000:0x00000fff descr > 0x00500000:0x00ffffff BIOS > 0x00003000:0x004fffff ME > 0x00001000:0x00002fff GbE > > And using flashrom with my patches should help: > https://github.com/XVilka/flashrom/tree/layout_descriptor > > Some of the patches are still 'dirty' but should work - I've checked > them on a bunch of hardware. > you need to run it like: > > flashrom -V -p internal -l this_file.layout -i BIOS -r bios_dump.bin > I got: Layout files are currently supported for write operations only. I thought you mean the read operation would work. -- Rui Paulo

2 1

Re: [flashrom] [PATCH] Detect Android target OS.
by Stefan Tauner 24 Dec '15

24 Dec '15

On Wed, 16 Dec 2015 01:00:15 +0100 Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> wrote: > No other changes are required to build flashrom (excluding programmers > with NEED_PCI) on Android. > > Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> > --- > os.h | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/os.h b/os.h > index 2e6dbaa..e5f72e4 100644 > --- a/os.h > +++ b/os.h > @@ -58,6 +58,11 @@ > #define __FLASHROM_OS__ "libpayload" > // Linux > #elif defined(__linux__) > -#define __FLASHROM_OS__ "Linux" > + // There are various flags in use on Android apparently. __ANDROID__ seems to be the most trustworthy. > + #if defined(__ANDROID__) > + #define __FLASHROM_OS__ "Android" > + #else > + #define __FLASHROM_OS__ "Linux" > + #endif > #endif > __FLASHROM_OS__ I'll add this change to my tested stuff branch to be committed within two weeks. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

S25FL128S - erase fails
by Jim Houston 23 Dec '15

23 Dec '15

Hi I'm playing with a Spansion S25FL128SAGMF1000 and running flashrom on a raspberrypi. I started with a new chip and was successful writing and reading back a random image. It fails when I try to erase the part. Probing this part gives several possible chip names and I picked "S25FL128S......0". I'm assuming that the 0 vs. 1 suffix is selecting 64k vs. 256k sector size. I may put some effort into chasing the erase problem. Is there anyone currently working on this? Jim Houston

3 3

Successful write report S25FL016A
by Márton Miklós 23 Dec '15

23 Dec '15

Hello all, I have successfully flashed a Dell D830 notebook (with discrete NVIDIA VGA) using flashrom from A14 BIOS revision to A17. This means two things: the notebook itself is supported, and the S25FL016A could be marked as verified for probe, read, erase, write. For the later one I have created a patch. I have forgotten to run lspci -vvvv, but I will do that and create a board enable patch soon. -- Regards, Miklos Marton

2 2

N25Q128..1E flashed successfully
by Márton Miklós 23 Dec '15

23 Dec '15

Hello all, I have successfully flashed a N25Q128..1E SPI flash using flashrom with a 16MB image. The programmer was an external one: NI USB-8452. This is not supported in the mainline yet, but patch is coming soon. /Flashing output (I have forgotten to //run with -V//):// //flashrom v0.9.7-unknown on Linux 3.13.0-70-generic (x86_64)// //flashrom is free software, get the source code at http://www.flashrom.org// // //Calibrating delay loop... OK.// //Found USB device (3923:7514).// //USB-8452 IO voltage set to: 1.8 V// //USB-8452 SCK frequency set to: 50.00 MHz// //Found Micron/Numonyx/ST flash chip "N25Q128..1E" (16384 kB, SPI) on usb8451_spi.// //===// //This flash part has status UNTESTED 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 part. Please include the flashrom// //output with the additional -V option for all operations you tested (-V, -Vr,// //-VE, -Vw), and mention which mainboard or programmer you tested.// //Please mention your board in the subject line. Thanks for your help!// //Reading old flash chip contents... done.// //Erasing and writing flash chip... // //Erase/write done.// //Verifying flash... VERIFIED. /Patch attached./ / -- Regards, Miklos Marton

2 1

W836xx: Lenovo B50-70: flashrom -V
by Bernhard Reiter 23 Dec '15

23 Dec '15

flashrom v0.9.7-r1852 on Linux 4.2.0-22-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.1, little endian Command line (3 args): flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 2684M loops per second, 10 myus = 10 us, 100 myus = 124 us, 1000 myus = 1021 us, 10000 myus = 10128 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: "80EU" DMI string system-version: "Lenovo B50-70" DMI string baseboard-manufacturer: "LENOVO" DMI string baseboard-product-name: "Lenovo B50-70" DMI string baseboard-version: "00000000NO DPK" 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 -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.

1 0

Re: [flashrom] BIOS on my PC. Need a little help or advise.
by Benjamin Bellec 22 Dec '15

22 Dec '15

Hello Alan, Did you tried to do clear CMOS to see if it fixes your issue to boot on the CD/DVD ? Anyway, if you want to upgrade your BIOS, you will first need a valid BIOS image of your computer/motherboard. Do you have it ? Regards. 2015-12-19 5:27 GMT+01:00 Alan Bruce <alandbruce(a)gmail.com>: > I did go to the FAQ on your website and clicked on "How Do I Use > Flashrom". The attached screenshot is what I got. So, how do I use this > program. I would not mind paying someone a few bucks to remotely re > configure my BIOS. I think that it has been hacked and modified. > > On Fri, Dec 18, 2015 at 6:32 PM, Alan Bruce <alandbruce(a)gmail.com> wrote: > >> Name is Alan. I am running an older Compaq Presario Desktop PC the model >> number is SR2264WM. it is an AMD 64 Athlion model. The operating system >> is Ubuntu 10.04. I just loved this OS and failed to upgrade before it was >> too late as it is now unsupported. So I downloaded Ubuntu 15.04 and was >> preparing to install it. All of a sudden my BIOS will not go to the boot >> menu when I press the ESC key upon startup, like it used to do. Although I >> downloaded flashrom from the Ubuntu Software Center, I am unable to find it >> on my PC and access the program to reset my BIOS. So how do I access this >> program? Your suggestions and advise will be greatly appreciated. >> > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom >

1 0

W836xx:ThinkPad Edge E130:335852G
by Всеволод Балашов 21 Dec '15

21 Dec '15

1 0

W836xx: Dell Inc.0RRH3K: flashrom -V
by Christophe CHAMOT 21 Dec '15

21 Dec '15

Hello, I know it is a laptop :-( I'm not waiting for a fix, it is just to feed the database of boards… ---------------------------------------------------------------------------------------------------------------- flashrom v0.9.7-r1782 on Linux 3.16.0-4-amd64 (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.8.2, little endian Command line (3 args): flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 1651M loops per second, 10 myus = 11 us, 100 myus = 107 us, 1000 myus = 967 us, 10000 myus = 9641 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Laptop" Laptop detected via DMI. DMI string system-manufacturer: "Dell Inc." DMI string system-product-name: "Precision M4500" DMI string system-version: "0001" DMI string baseboard-manufacturer: "Dell Inc." DMI string baseboard-product-name: "0RRH3K" DMI string baseboard-version: "A03" ======================================================================== 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. ----------------------------------------------------------------------------------------------------------------------------- Thx for all you're doing guys, Christophe

1 0

Re: [flashrom] BIOS on my PC. Need a little help or advise.
by Alan Bruce 19 Dec '15

19 Dec '15

I did go to the FAQ on your website and clicked on "How Do I Use Flashrom". The attached screenshot is what I got. So, how do I use this program. I would not mind paying someone a few bucks to remotely re configure my BIOS. I think that it has been hacked and modified. On Fri, Dec 18, 2015 at 6:32 PM, Alan Bruce <alandbruce(a)gmail.com> wrote: > Name is Alan. I am running an older Compaq Presario Desktop PC the model > number is SR2264WM. it is an AMD 64 Athlion model. The operating system > is Ubuntu 10.04. I just loved this OS and failed to upgrade before it was > too late as it is now unsupported. So I downloaded Ubuntu 15.04 and was > preparing to install it. All of a sudden my BIOS will not go to the boot > menu when I press the ESC key upon startup, like it used to do. Although I > downloaded flashrom from the Ubuntu Software Center, I am unable to find it > on my PC and access the program to reset my BIOS. So how do I access this > program? Your suggestions and advise will be greatly appreciated. >

1 0

BIOS on my PC. Need a little help or advise.
by Alan Bruce 19 Dec '15

19 Dec '15

Name is Alan. I am running an older Compaq Presario Desktop PC the model number is SR2264WM. it is an AMD 64 Athlion model. The operating system is Ubuntu 10.04. I just loved this OS and failed to upgrade before it was too late as it is now unsupported. So I downloaded Ubuntu 15.04 and was preparing to install it. All of a sudden my BIOS will not go to the boot menu when I press the ESC key upon startup, like it used to do. Although I downloaded flashrom from the Ubuntu Software Center, I am unable to find it on my PC and access the program to reset my BIOS. So how do I access this program? Your suggestions and advise will be greatly appreciated.

1 0

flashrom can successfully read the BIOS image of my Amilo Xi3650 laptop
by Elmar Stellnberger 17 Dec '15

17 Dec '15

Lately I have tried > flashrom -p internal:laptop=force_I_want_a_brick --read Xi3650.rom on my Fujitsu Siemens Amilo Xi 3650 laptop and it has worked quite well. ... Found chipset "Intel ICH9M-E". Found Winbond flash chip "W25X16" (2048 kB, SPI) at physical address 0xffe00000. > sha256sum Xi3650.rom 8c5095d38bffe9b87d481ba8da395e48d9dcfadd43176979fd69e5da249b3763 Xi3650.rom BIOS (according to dmidecode) is Vendor: Phoenix Version: 1.0H-1646-0024 Release Date: 04/15/2010 I would love to see it under 'supported boards' in the future. More information can be found in the attachements.

1 1

Re: [flashrom] FAILED: Lenovo X1 (2015)
by Stefan Tauner 17 Dec '15

17 Dec '15

On Thu, 17 Dec 2015 13:08:56 +0300 Антон Кочков <anton.kochkov(a)gmail.com> wrote: > Hello! > Mainstream flashrom currently not yet merged patches, adding support > of reading layout. Because ME region usually not readable not from ME > itself, > it should be skipped, so using layout file, in your case: > # flashrom layout v2 > 0x00000000:0x00000fff descr > 0x00500000:0x00ffffff BIOS > 0x00003000:0x004fffff ME > 0x00001000:0x00002fff GbE > > And using flashrom with my patches should help: > https://github.com/XVilka/flashrom/tree/layout_descriptor > > Some of the patches are still 'dirty' but should work - I've checked > them on a bunch of hardware. > you need to run it like: > > flashrom -V -p internal -l this_file.layout -i BIOS -r bios_dump.bin And, most importantly: they will not help you in writing anything because there are a number of other restrictions in your configuration. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

FAILED: Lenovo X1 (2015)
by Rui Paulo 17 Dec '15

17 Dec '15

Hi, I tried to dump the BIOS on my Lenovo X1 using flashrom and it didn't work. I'm using flashrom from svn trunk. Any ideas? flashrom v0.9.8-r1901 on Linux 4.2.0-1-amd64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.o rg flashrom was built with libpci 3.3.1, GCC 5.2.1 20151028, little endian Command line (6 args): ./flashrom -VVp internal -c MX25L12805D --read a.rom Calibrating delay loop... OS timer resolution is 1 usecs, 2883M loops per second, 10 myus = 10 us, 100 myus = 122 us, 1000 myus = 1018 us, 10000 myus = 10335 us, 4 myus = 15 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. No DMI table found. 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: 00. 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 chipset "Intel Broadwell U Premium" with PCI ID 8086:9cc3. 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... Root Complex Register Block address = 0xfed1c000 GCS = 0x21: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x0 (LPC) Top Swap: not enabled 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 enabled 0xffc80000/0xff880000 FWH decode enabled 0xffc00000/0xff800000 FWH decode enabled 0xff700000/0xff300000 FWH decode enabled 0xff600000/0xff200000 FWH decode enabled 0xff500000/0xff100000 FWH decode enabled 0xff400000/0xff000000 FWH decode enabled Maximum FWH chip size: 0x100000 bytes SPI Read Configuration: prefetching enabled, caching enabled, BIOS_CNTL = 0x2a: BIOS Lock Enable: enabled, BIOS Write Enable: disabled Warning: BIOS region SMM protection is enabled! Warning: Setting Bios Control at 0xdc from 0x2a to 0x09 failed. New value is 0x2a. SPIBAR = 0x00007f030f57a000 + 0x3800 0x04: 0xe008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=1 Warning: SPI Configuration Lockdown activated. Reading OPCODES... done OP Type Pre-OP op[0]: 0x5a, read w/o addr, none op[1]: 0x9f, read w/o addr, none op[2]: 0x05, read w/o addr, none op[3]: 0x01, write w/o addr, none op[4]: 0x03, read w/ addr, none op[5]: 0x15, read w/o addr, none op[6]: 0xff, read w/o addr, none op[7]: 0xff, read w/o addr, none Pre-OP 0: 0x06, Pre-OP 1: 0x06 0x06: 0x0004 (HSFC) HSFC: FGO=0, FCYCLE=2, FDBC=0, SME=0 0x08: 0x00003000 (FADDR) 0x50: 0x00004a4b (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0x4a, BRRA 0x4b 0x54: 0x00000000 FREG0: Warning: Flash Descriptor region (0x00000000- 0x00000fff) is read-only. 0x58: 0x0fff0500 FREG1: BIOS region (0x00500000-0x00ffffff) is read- write. 0x5C: 0x04ff0003 FREG2: Warning: Management Engine region (0x00003000- 0x004fffff) is locked. 0x60: 0x00020001 FREG3: Gigabit Ethernet region (0x00001000-0x00002fff) is read-write. 0x64: 0x00007fff FREG4: Platform Data region is unused. Not all flash regions are freely accessible by flashrom. This is most likely due to an active ME. Please see http://flashrom.org/ME for details. 0x74: 0x00000000 (PR0 is unused) 0x78: 0x8fff0eb0 PR1: Warning: 0x00eb0000-0x00ffffff is read-only. 0x7C: 0x8e2f0df1 PR2: Warning: 0x00df1000-0x00e2ffff is read-only. 0x80: 0x8df00df0 PR3: Warning: 0x00df0000-0x00df0fff is read-only. 0x84: 0x8def0a00 PR4: Warning: 0x00a00000-0x00deffff is read-only. Writes have been disabled for safety reasons. You can enforce write support with the ich_spi_force programmer option, but you will most likely harm your hardware! If you force flashrom you will get no support if something breaks. On a few mainboards it is possible to enable write access by setting a jumper (see its documentation or the board itself). 0x90: 0xc4 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xfc0000 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=0, DBC=0, SME=0, SCF=4 0x94: 0x0606 (PREOP) 0x96: 0x0240 (OPTYPE) 0x98: 0x01059f5a (OPMENU) 0x9C: 0xffff1503 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x80802045 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 0xC8: 0x00002045 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20 0xD0: 0x50444653 (FPB) Reading flash descriptors mapped by the chipset via FDOC/FDOD... done. === Content Section === FLVALSIG 0x0ff0a55a FLMAP0 0x03040003 FLMAP1 0x15100206 FLMAP2 0x00210120 --- Details --- NR (Number of Regions): 4 FRBA (Flash Region Base Address): 0x040 NC (Number of Components): 1 FCBA (Flash Component Base Address): 0x030 ISL (ICH/PCH Strap Length): 21 FISBA/FPSBA (Flash ICH/PCH Strap Base Address): 0x100 NM (Number of Masters): 3 FMBA (Flash Master Base Address): 0x060 MSL/PSL (MCH/PROC Strap Length): 1 FMSBA (Flash MCH/PROC Strap Base Address): 0x200 === Component Section === FLCOMP 0x49900045 FLILL 0xad604221 --- Details --- Component 1 density: 16 MB Component 2 is not used. Read Clock Frequency: 20 MHz Read ID and Status Clock Freq.: 33 MHz Write and Erase Clock Freq.: 33 MHz Fast Read is supported. Fast Read Clock Frequency: 50 MHz Dual Output Fast Read Support: disabled Invalid instruction 0: 0x21 Invalid instruction 1: 0x42 Invalid instruction 2: 0x60 Invalid instruction 3: 0xad === Region Section === FLREG0 0x00000000 FLREG1 0x0fff0500 FLREG2 0x04ff0003 FLREG3 0x00020001 FLREG4 0x00007fff --- Details --- Region 0 (Descr.) 0x00000000 - 0x00000fff Region 1 (BIOS ) 0x00500000 - 0x00ffffff Region 2 (ME ) 0x00003000 - 0x004fffff Region 3 (GbE ) 0x00001000 - 0x00002fff Region 4 (Platf.) is unused. === Master Section === FLMSTR1 0x0a0b0000 FLMSTR2 0x0c0d0000 FLMSTR3 0x08080118 --- Details --- Descr. BIOS ME GbE Platf. BIOS r rw rw ME r rw rw GbE rw PROBLEMS, continuing anyway The following protocols are supported: FWH, SPI. Probing for Macronix MX25L12805D, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2018 Found Macronix flash chip "MX25L12805D" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Chip status register is 0x40. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set Chip status register: Bit 6 is set Chip status register: Block Protect 3 (BP3) is not set Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). Block protection is disabled. Reading flash... Transaction error! SSFS: SCIP=0, FDONE=1, FCERR=1, AEL=0 SSFC: SCGO=0, ACS=0, SPOP=0, COP=4, DBC=63, SME=0, SCF=4 Running OPCODE 0x03 failed at address 0x003000 (payload length was 64). Read operation failed! FAILED. Restoring MMIO space at 0x7f030f57d8a0 Restoring PCI config space for 00:1f:0 reg 0xdc -- Rui Paulo

2 1

[PATCH] Detect Android target OS.
by Stefan Tauner 16 Dec '15

16 Dec '15

No other changes are required to build flashrom (excluding programmers with NEED_PCI) on Android. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> --- os.h | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/os.h b/os.h index 2e6dbaa..e5f72e4 100644 --- a/os.h +++ b/os.h @@ -58,6 +58,11 @@ #define __FLASHROM_OS__ "libpayload" // Linux #elif defined(__linux__) -#define __FLASHROM_OS__ "Linux" + // There are various flags in use on Android apparently. __ANDROID__ seems to be the most trustworthy. + #if defined(__ANDROID__) + #define __FLASHROM_OS__ "Android" + #else + #define __FLASHROM_OS__ "Linux" + #endif #endif __FLASHROM_OS__ -- Kind regards, Stefan Tauner

1 0

Fwd: Your stand proposal for FOSDEM 2016 has been accepted
by Carl-Daniel Hailfinger 15 Dec '15

15 Dec '15

Hello everyone, let's make this our best FOSDEM stand presence ever! https://www.coreboot.org/FOSDEM_2016 Please fill in https://www.coreboot.org/Talk:FOSDEM_2016 if you're coming. Regards, Carl-Daniel -------- Forwarded Message -------- From: FOSDEM Stands Team <stands(a)fosdem.org> To: Carl-Daniel <c-d.hailfinger.devel.2006(a)gmx.net> Subject: Your stand proposal for FOSDEM 2016 has been accepted Message-Id: <20151214195515.C04A3CB582(a)mailhost.gletsjer.net> Date: Mon, 14 Dec 2015 20:54:56 +0100 (CET) Hi Carl-Daniel, The FOSDEM stands team is glad to be able to inform you that your request for a stand for 'coreboot_flashrom' has been accepted. There will be two tables reserved for you. Like most years, we received roughly twice as many requests for stands as we have tables available. We have aimed to grant as many requests as feasible and to increase the diversity of the accepted stands. Because of this, we have unfortunately had to reduce the space available for a number of regular attendees, as well as reject some projects that have been present in previous years years. You will receive further information about what's expected of you closer to the event date. Looking forward to seeing you at FOSDEM 2016! Kind regards, Wynke Stulemeijer FOSDEM stands team

1 0

Re: [flashrom] Add option to disable the reading back of the flash contents at write operation
by Márton Miklós 12 Dec '15

12 Dec '15

Hello David, Thank you for your response! Your answer makes sense for me. In this case it would be useful to refactor the "backupless" writes to read sectors only until a non 0xFF portion found, and then mark that sector erasable or erase immediately. In the case if the flash has non blank region this could speed up the programming, worst case (programming a fully erased chip) it is going to be equal in time. I have not been aware of Nico's patch. Is it already merged to the mainline? If not could you please give me a link to that? Thank you! Regards, Miklos Marton 2015-12-11 21:52 keltezéssel, David Hendricks írta: > Hi Marton, > I respectfully disagree with this approach. Reading the old contents > is not just used for backup. It's used so that flashrom can > selectively erase and write blocks which usually saves time because > erase and write operations are orders of magnitude slower than reads > on NOR flash. > > So, it's not a bad thing to support this option, but I think there is > little benefit and can actually make the process slower in most cases. > (Your case might be different, of course) > > Nico Huber's unbounded read patch should help reduce the initial read > time by a large factor (~90% reduction). Try marking your chip as > tested for unbounded reads. You might find that the read and selective > erase/write is faster than unconditional erase/write. > > > On Fri, Dec 11, 2015 at 12:01 PM, Márton Miklós > <martonmiklosqdev(a)gmail.com <mailto:martonmiklosqdev@gmail.com>> wrote: > > Hello all, > > I am using the flashrom with an external programmer to flash > various SPI flashes a lot. > In most cases I do not care about the old flash contents when > flashing, so the "/Reading old flash chip contents/" step does not > have any added value in my use cases. The code also has a FIXME > note where this is hardcoded to make it configurable in the > future. I would like to patch it if possible. > > Please propose me command line arguments for disabling it. My > proposal: > /-N | --nobackup skip reading back old flash contents before write/ > > I know -N could be confused with -n but the same applies to the -v > (verify) and -V (verbose). > I also could live without the short argument, but that would break > the "standard". > > Thanks in advance for your feedback! > > -- > Regards, > Miklos Marton > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org <mailto:flashrom@flashrom.org> > http://www.flashrom.org/mailman/listinfo/flashrom > > > > > -- > David Hendricks (dhendrix) > Systems Software Engineer, Google Inc.

1 0

Add option to disable the reading back of the flash contents at write operation
by Márton Miklós 11 Dec '15

11 Dec '15

Hello all, I am using the flashrom with an external programmer to flash various SPI flashes a lot. In most cases I do not care about the old flash contents when flashing, so the "/Reading old flash chip contents/" step does not have any added value in my use cases. The code also has a FIXME note where this is hardcoded to make it configurable in the future. I would like to patch it if possible. Please propose me command line arguments for disabling it. My proposal: /-N | --nobackup skip reading back old flash contents before write/ I know -N could be confused with -n but the same applies to the -v (verify) and -V (verbose). I also could live without the short argument, but that would break the "standard". Thanks in advance for your feedback! -- Regards, Miklos Marton

2 1

Problems flashing N25Q064A13ESE40E SPI chip
by Ruben Van de Put 11 Dec '15

11 Dec '15

Hello, I'm having some problems flashing a SPI chip with the BusPirate V3. Writing the image is successful but verification is not successful. First try with chip on breadboard and long leads (20-25cm): http://paste.flashrom.org/view.php?id=2841 Then I shortened the signal leads and soldered them directly on the BusPirate: http://paste.flashrom.org/view.php?id=2842 Then I soldered all leads directly on the chip (with an adapter) instead of using a breadboard: http://paste.flashrom.org/view.php?id=2844 I also tried lowering the SPI speed to 1 MHz: http://paste.flashrom.org/view.php?id=2845 Current set-up [image: Inline afbeelding 1] [image: Inline afbeelding 2] Chip datasheet: http://www.farnell.com/datasheets/1674442.pdf Flash connected in this way: http://flashrom.org/Bus_Pirate Is there anything else I can try or should I try replacing the flash chip? Kind regards, Ruben Van de Put

1 0

W836xx:HP DL145 G3
by Jeff 09 Dec '15

09 Dec '15

I'm not sure if you still need this input but the program requested it. Hope it helps!

1 0

W836xx: ??????????: flashrom -V
by Alexis BRENON 06 Dec '15

06 Dec '15

# sudo flashrom -V -p internal flashrom v0.9.8-r1888 on Linux 4.2.5-1-ARCH (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 (3 args): flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 2658M loops per second, 10 myus = 10 us, 100 myus = 125 us, 1000 myus = 1012 us, 10000 myus = 9948 us, 4 myus = 15 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Portable" Laptop detected via DMI. DMI string system-manufacturer: "Dell Inc. " DMI string system-product-name: "Inspiron 7437" DMI string system-version: "Not Specified" DMI string baseboard-manufacturer: "Dell Inc. " DMI string baseboard-product-name: " " 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: fc. 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. ======================================================================== 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

Re: [flashrom] Question - Help
by Jim Houston 06 Dec '15

06 Dec '15

On 12/05/2015 03:01 PM, Neb Radojkovic wrote: > > I joined flashrom in hope that it will help me. I have an older HP > small-factor desktop computer where the BIOS > is somewhat limited for any adjusting/ changes. It takes forever to > boot to any OS I load and I was hoping that > by flashing and getting an open BIOS things will get faster and better. > Now, I have no real knowledge for doing so - I am an old guy who would > like to think that I can find enough info > to do so. Is this the place that can help me for my task? > Hi Neb, Yes this probably the wrong list for this discussion. There are much easier ways to save time. There is the obvious risk of installing a BIOS which doesn't work and turning your PC into a brick. It sounds like you are hoping for a script to follow - it isn't that easy. I'm new to this list too and planning to use flashrom to backup the prom in a router before trying an open source firmware. Flashrom might be part of the process but you should start by looking at the firmware you plan to use. One project doing a BIOS replacement is coreboot.org. They have lists of supported hardware. It is important to understand that hardware vendors may use the same name for different hardware. Close isn't good enough. Jim Houston

1 0

Question - Help
by Neb Radojkovic 05 Dec '15

05 Dec '15

Hello, This could be a totally wrong place for what I am trying to accomplish but it doesn't hurt to ask. I joined flashrom in hope that it will help me. I have an older HP small-factor desktop computer where the BIOS is somewhat limited for any adjusting/ changes. It takes forever to boot to any OS I load and I was hoping that by flashing and getting an open BIOS things will get faster and better. Now, I have no real knowledge for doing so - I am an old guy who would like to think that I can find enough info to do so. Is this the place that can help me for my task? If so (or not) can you point me in the right direction. I can totally understand instruction of type: open this, download that, extract and boot with to execute...etc. Too many technical terms will confuse me... I also understand if you don't have time to waste on an old guy and in that case just tell me to bug off... Thank you in advance. Cheers! Neb

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom