- flashrom - mail.coreboot.org

Re: [flashrom] [PATCH 2/3] Make make errors more less flashily.
by Carl-Daniel Hailfinger 07 Jan '16

07 Jan '16

On 15.11.2015 16:40, Stefan Tauner wrote: > Previously we have hid almost all error messages from called tools like > pkg-config or the compiler in the "configure" step. Only exceptions were > the library checks because Carl-Daniel felt it improved usability in > case of missing headers etc. > > However, this makes the output of the makefile less readable and in the > case of pkg-config fallbacks the error messages are actually expected. > Instead of throwing a part of the detailed stderr outputs of the tools into the > face of the users and completely hiding others, write all of them into > a separate log file instead. Agreed. Should we eventually move to "make config; make" to simplify the makefile? > Also, disable implicit rules because we don't need them and they just > make the build slower. Good idea. > Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Comments inline. > diff --git a/Makefile b/Makefile > index e68b106..3f96a15 100644 > --- a/Makefile > +++ b/Makefile > @@ -37,6 +37,8 @@ MANDIR ?= $(PREFIX)/share/man > CFLAGS ?= -Os -Wall -Wshadow > EXPORTDIR ?= . > RANLIB ?= ranlib > +PKG_CONFIG ?= pkg-config > +BUILD_DETAILS_FILE ?= build_details.txt > > # The following parameter changes the default programmer that will be used if there is no -p/--programmer > # argument given when running flashrom. The predefined setting does not enable any default so that every > @@ -70,6 +72,8 @@ LDFLAGS += -L$(LIBS_BASE)/lib -Wl,-rpath -Wl,$(LIBS_BASE)/lib > PKG_CONFIG_LIBDIR ?= $(LIBS_BASE)/lib/pkgconfig > endif > > +dummy_for_make_3_80:=$(shell printf "Build started on " >$(BUILD_DETAILS_FILE) ; date >>$(BUILD_DETAILS_FILE) ; echo >>$(BUILD_DETAILS_FILE)) What's the oldest make version where the new makefile works reliably? Do we have to document that somewhere or test+abort? > +debug_shell = $(shell export LC_ALL=C ; { echo 'exec: export LC_ALL=C ; { $(1) ; }' >&2; { $(1) ; } | tee -a $(BUILD_DETAILS_FILE) ; echo >&2 ; } 2>>$(BUILD_DETAILS_FILE)) I'd love to learn how this works. Do you have any pointers? > ############################################################################### > # General OS-specific settings. > # 1. Prepare for later by gathering information about host and target OS > @@ -90,7 +94,7 @@ endif > # IMPORTANT: The following line must be placed before TARGET_OS is ever used > # (of course), but should come after any lines setting CC because the line > # below uses CC itself. > -override TARGET_OS := $(strip $(shell LC_ALL=C $(CC) $(CPPFLAGS) -E os.h 2>/dev/null | grep -v '^\#' | grep '"' | cut -f 2 -d'"')) > +override TARGET_OS := $(strip $(call debug_shell,$(CC) $(CPPFLAGS) -E os.h 2>/dev/null | grep -v '^\#' | grep '"' | cut -f 2 -d'"')) > > ifeq ($(TARGET_OS), Darwin) > CPPFLAGS += -I/opt/local/include -I/usr/local/include > [...] > @@ -824,11 +834,11 @@ endef > export COMPILER_TEST > > compiler: featuresavailable > - @printf "Checking for a C compiler... " > + @printf "Checking for a C compiler... " | tee -a $(BUILD_DETAILS_FILE) > @echo "$$COMPILER_TEST" > .test.c > - @$(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) .test.c -o .test$(EXEC_SUFFIX) >/dev/null && \ > - echo "found." || ( echo "not found."; \ > - rm -f .test.c .test$(EXEC_SUFFIX); exit 1) > + @{ { { { { $(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) .test.c -o .test$(EXEC_SUFFIX) >&2 && \ > + echo "found." || { echo "not found."; \ > + rm -f .test.c .test$(EXEC_SUFFIX); exit 1; }; } 2>>$(BUILD_DETAILS_FILE); echo $? >&3 ; } | tee -a $(BUILD_DETAILS_FILE) >&4; } 3>&1;} | { read rc ; exit ${rc}; } } 4>&1 > @rm -f .test.c .test$(EXEC_SUFFIX) > @printf "Target arch is " > @# FreeBSD wc will output extraneous whitespace. Hm. Is this compatible with classic sh, or do you introduce a dependency on bash here? Regards, Carl-Daniel

2 3

[commit] r1911 - trunk
by repository service 07 Jan '16

07 Jan '16

Author: stefanct Date: Thu Jan 7 18:45:59 2016 New Revision: 1911 URL: http://flashrom.org/trac/flashrom/changeset/1911 Log: Make make errors more less flashily. Previously we have hid almost all error messages from called tools like pkg-config or the compiler in the "configure" step. Only exceptions were the library checks because Carl-Daniel felt it improved usability in case of missing headers etc. However, this makes the output of the makefile less readable and in the case of pkg-config fallbacks the error messages are actually expected. Instead of throwing a part of the detailed stderr outputs of the tools into the face of the users and completely hiding others, write all of them into a separate log file instead. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Modified: trunk/ (props changed) trunk/Makefile Modified: trunk/Makefile ============================================================================== --- trunk/Makefile Thu Jan 7 10:50:26 2016 (r1910) +++ trunk/Makefile Thu Jan 7 18:45:59 2016 (r1911) @@ -37,6 +37,8 @@ CFLAGS ?= -Os -Wall -Wshadow EXPORTDIR ?= . RANLIB ?= ranlib +PKG_CONFIG ?= pkg-config +BUILD_DETAILS_FILE ?= build_details.txt # The following parameter changes the default programmer that will be used if there is no -p/--programmer # argument given when running flashrom. The predefined setting does not enable any default so that every @@ -70,6 +72,8 @@ PKG_CONFIG_LIBDIR ?= $(LIBS_BASE)/lib/pkgconfig endif +dummy_for_make_3_80:=$(shell printf "Build started on %s\n\n" "$$(date)" >$(BUILD_DETAILS_FILE)) +debug_shell = $(shell export LC_ALL=C ; { echo 'exec: export LC_ALL=C ; { $(1) ; }' >&2; { $(1) ; } | tee -a $(BUILD_DETAILS_FILE) ; echo >&2 ; } 2>>$(BUILD_DETAILS_FILE)) ############################################################################### # General OS-specific settings. # 1. Prepare for later by gathering information about host and target OS @@ -90,7 +94,7 @@ # IMPORTANT: The following line must be placed before TARGET_OS is ever used # (of course), but should come after any lines setting CC because the line # below uses CC itself. -override TARGET_OS := $(strip $(shell LC_ALL=C $(CC) $(CPPFLAGS) -E os.h 2>/dev/null | grep -v '^\#' | grep '"' | cut -f 2 -d'"')) +override TARGET_OS := $(strip $(call debug_shell,$(CC) $(CPPFLAGS) -E os.h 2>/dev/null | grep -v '^\#' | grep '"' | cut -f 2 -d'"')) ifeq ($(TARGET_OS), Darwin) CPPFLAGS += -I/opt/local/include -I/usr/local/include @@ -326,7 +330,7 @@ # IMPORTANT: The following line must be placed before ARCH is ever used # (of course), but should come after any lines setting CC because the line # below uses CC itself. -override ARCH := $(strip $(shell LC_ALL=C $(CC) $(CPPFLAGS) -E archtest.c 2>/dev/null | grep -v '^\#' | grep '"' | cut -f 2 -d'"')) +override ARCH := $(strip $(call debug_shell,$(CC) $(CPPFLAGS) -E archtest.c 2>/dev/null | grep -v '^\#' | grep '"' | cut -f 2 -d'"')) # PCI port I/O support is unimplemented on PPC/MIPS/SPARC and unavailable on ARM. # Right now this means the drivers below only work on x86. @@ -615,14 +619,14 @@ ifeq ($(CONFIG_FT2232_SPI), yes) # This is a totally ugly hack. -FEATURE_CFLAGS += $(shell LC_ALL=C grep -q "FTDISUPPORT := yes" .features && printf "%s" "-D'CONFIG_FT2232_SPI=1'") +FEATURE_CFLAGS += $(call debug_shell,grep -q "FTDISUPPORT := yes" .features && printf "%s" "-D'CONFIG_FT2232_SPI=1'") NEED_FTDI := yes PROGRAMMER_OBJS += ft2232_spi.o endif ifeq ($(CONFIG_USBBLASTER_SPI), yes) # This is a totally ugly hack. -FEATURE_CFLAGS += $(shell LC_ALL=C grep -q "FTDISUPPORT := yes" .features && printf "%s" "-D'CONFIG_USBBLASTER_SPI=1'") +FEATURE_CFLAGS += $(call debug_shell,grep -q "FTDISUPPORT := yes" .features && printf "%s" "-D'CONFIG_USBBLASTER_SPI=1'") NEED_FTDI := yes PROGRAMMER_OBJS += usbblaster_spi.o endif @@ -634,11 +638,11 @@ endif ifeq ($(NEED_FTDI), yes) -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) +FTDILIBS := $(call debug_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 += $(call debug_shell,grep -q "FT232H := yes" .features && printf "%s" "-D'HAVE_FT232H=1'") +FTDI_INCLUDES := $(call debug_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)") +FEATURE_LIBS += $(call debug_shell,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. endif @@ -710,13 +714,13 @@ ifeq ($(CONFIG_LINUX_SPI), yes) # This is a totally ugly hack. -FEATURE_CFLAGS += $(shell LC_ALL=C grep -q "LINUX_SPI_SUPPORT := yes" .features && printf "%s" "-D'CONFIG_LINUX_SPI=1'") +FEATURE_CFLAGS += $(call debug_shell,grep -q "LINUX_SPI_SUPPORT := yes" .features && printf "%s" "-D'CONFIG_LINUX_SPI=1'") PROGRAMMER_OBJS += linux_spi.o endif ifeq ($(CONFIG_MSTARDDC_SPI), yes) # This is a totally ugly hack. -FEATURE_CFLAGS += $(shell LC_ALL=C grep -q "LINUX_I2C_SUPPORT := yes" .features && printf "%s" "-D'CONFIG_MSTARDDC_SPI=1'") +FEATURE_CFLAGS += $(call debug_shell,grep -q "LINUX_I2C_SUPPORT := yes" .features && printf "%s" "-D'CONFIG_MSTARDDC_SPI=1'") NEED_LINUX_I2C := yes PROGRAMMER_OBJS += mstarddc_spi.o endif @@ -734,7 +738,7 @@ ifeq ($(NEED_PCI), yes) CHECK_LIBPCI = yes FEATURE_CFLAGS += -D'NEED_PCI=1' -FEATURE_CFLAGS += $(shell LC_ALL=C grep -q "OLD_PCI_GET_DEV := yes" .libdeps && printf "%s" "-D'OLD_PCI_GET_DEV=1'") +FEATURE_CFLAGS += $(call debug_shell,grep -q "OLD_PCI_GET_DEV := yes" .libdeps && printf "%s" "-D'OLD_PCI_GET_DEV=1'") PROGRAMMER_OBJS += pcidev.o physmap.o hwaccess.o ifeq ($(TARGET_OS), NetBSD) @@ -761,7 +765,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 := $(call debug_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) @@ -769,10 +773,10 @@ CLI_OBJS += print_wiki.o endif -FEATURE_CFLAGS += $(shell LC_ALL=C grep -q "UTSNAME := yes" .features && printf "%s" "-D'HAVE_UTSNAME=1'") +FEATURE_CFLAGS += $(call debug_shell,grep -q "UTSNAME := yes" .features && printf "%s" "-D'HAVE_UTSNAME=1'") # We could use PULLED_IN_LIBS, but that would be ugly. -FEATURE_LIBS += $(shell LC_ALL=C grep -q "NEEDLIBZ := yes" .libdeps && printf "%s" "-lz") +FEATURE_LIBS += $(call debug_shell,grep -q "NEEDLIBZ := yes" .libdeps && printf "%s" "-lz") LIBFLASHROM_OBJS = $(CHIP_OBJS) $(PROGRAMMER_OBJS) $(LIB_OBJS) OBJS = $(CLI_OBJS) $(LIBFLASHROM_OBJS) @@ -801,7 +805,7 @@ # 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 $(BUILD_DETAILS_FILE) @+$(MAKE) -C util/ich_descriptors_tool/ clean distclean: clean @@ -824,11 +828,11 @@ export COMPILER_TEST compiler: featuresavailable - @printf "Checking for a C compiler... " + @printf "Checking for a C compiler... " | tee -a $(BUILD_DETAILS_FILE) @echo "$$COMPILER_TEST" > .test.c - @$(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) .test.c -o .test$(EXEC_SUFFIX) >/dev/null && \ - echo "found." || ( echo "not found."; \ - rm -f .test.c .test$(EXEC_SUFFIX); exit 1) + @{ { { { { $(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) .test.c -o .test$(EXEC_SUFFIX) >&2 && \ + echo "found." || { echo "not found."; \ + rm -f .test.c .test$(EXEC_SUFFIX); exit 1; }; } 2>>$(BUILD_DETAILS_FILE); echo $? >&3 ; } | tee -a $(BUILD_DETAILS_FILE) >&4; } 3>&1;} | { read rc ; exit ${rc}; } } 4>&1 @rm -f .test.c .test$(EXEC_SUFFIX) @printf "Target arch is " @# FreeBSD wc will output extraneous whitespace. @@ -906,43 +910,43 @@ hwlibs: compiler @printf "" > .libdeps ifeq ($(CHECK_LIBPCI), yes) - @printf "Checking for libpci headers... " + @printf "Checking for libpci headers... " | tee -a $(BUILD_DETAILS_FILE) @echo "$$LIBPCI_TEST" > .test.c - @$(CC) -c $(CPPFLAGS) $(CFLAGS) .test.c -o .test.o >/dev/null && \ - echo "found." || ( echo "not found."; echo; \ - echo "Please install libpci headers (package pciutils-devel)."; \ + @{ { { { { $(CC) -c $(CPPFLAGS) $(CFLAGS) .test.c -o .test.o >&2 && \ + echo "found." || { echo "not found."; echo; \ + echo "Please install libpci headers."; \ echo "See README for more information."; echo; \ - rm -f .test.c .test.o; exit 1) - @printf "Checking version of pci_get_dev... " + rm -f .test.c .test.o; exit 1; }; } 2>>$(BUILD_DETAILS_FILE); echo $? >&3 ; } | tee -a $(BUILD_DETAILS_FILE) >&4; } 3>&1;} | { read rc ; exit ${rc}; } } 4>&1 + @printf "Checking version of pci_get_dev... " | tee -a $(BUILD_DETAILS_FILE) @echo "$$PCI_GET_DEV_TEST" > .test.c - @$(CC) -c $(CPPFLAGS) $(CFLAGS) .test.c -o .test.o >/dev/null 2>&1 && \ + @ { $(CC) -c $(CPPFLAGS) $(CFLAGS) .test.c -o .test.o >&2 && \ ( echo "new version (including PCI domain parameter)."; echo "OLD_PCI_GET_DEV := no" >> .libdeps ) || \ - ( echo "old version (without PCI domain parameter)."; echo "OLD_PCI_GET_DEV := yes" >> .libdeps ) - @printf "Checking if libpci is present and sufficient... " - @$(CC) $(LDFLAGS) .test.o -o .test$(EXEC_SUFFIX) $(LIBS) $(PCILIBS) >/dev/null && \ - echo "yes." || ( echo "no."; \ - printf "Checking if libz+libpci are present and sufficient..."; \ - $(CC) $(LDFLAGS) .test.o -o .test$(EXEC_SUFFIX) $(LIBS) $(PCILIBS) -lz >/dev/null && \ - ( echo "yes."; echo "NEEDLIBZ := yes" > .libdeps ) || ( echo "no."; echo; \ + ( echo "old version (without PCI domain parameter)."; echo "OLD_PCI_GET_DEV := yes" >> .libdeps ) } 2>>$(BUILD_DETAILS_FILE) | tee -a $(BUILD_DETAILS_FILE) + @printf "Checking if libpci is present and sufficient... " | tee -a $(BUILD_DETAILS_FILE) + @{ { { { $(CC) $(LDFLAGS) .test.o -o .test$(EXEC_SUFFIX) $(LIBS) $(PCILIBS) 2>>$(BUILD_DETAILS_FILE) >&2 && \ + echo "yes." || { echo "no."; \ + printf "Checking if libz+libpci are present and sufficient..." ; \ + { $(CC) $(LDFLAGS) .test.o -o .test$(EXEC_SUFFIX) $(LIBS) $(PCILIBS) -lz >&2 && \ + echo "yes." && echo "NEEDLIBZ := yes" > .libdeps } || { echo "no."; echo; \ echo "Please install libpci (package pciutils) and/or libz."; \ echo "See README for more information."; echo; \ - rm -f .test.c .test.o .test$(EXEC_SUFFIX); exit 1) ) + rm -f .test.c .test.o .test$(EXEC_SUFFIX); exit 1; }; }; } 2>>$(BUILD_DETAILS_FILE); echo $? >&3 ; } | tee -a $(BUILD_DETAILS_FILE) >&4; } 3>&1;} | { read rc ; exit ${rc}; } } 4>&1 @rm -f .test.c .test.o .test$(EXEC_SUFFIX) endif ifeq ($(CHECK_LIBUSB0), yes) - @printf "Checking for libusb-0.1/libusb-compat headers... " + @printf "Checking for libusb-0.1/libusb-compat headers... " | tee -a $(BUILD_DETAILS_FILE) @echo "$$LIBUSB0_TEST" > .test.c - @$(CC) -c $(CPPFLAGS) $(CFLAGS) .test.c -o .test.o >/dev/null && \ - echo "found." || ( echo "not found."; echo; \ + @{ { { { { $(CC) -c $(CPPFLAGS) $(CFLAGS) .test.c -o .test.o >&2 && \ + echo "found." || { echo "not found."; echo; \ echo "Please install libusb-0.1 headers or libusb-compat headers."; \ echo "See README for more information."; echo; \ - rm -f .test.c .test.o; exit 1) - @printf "Checking if libusb-0.1 is usable... " - @$(CC) $(LDFLAGS) .test.o -o .test$(EXEC_SUFFIX) $(LIBS) $(USBLIBS) >/dev/null && \ - echo "yes." || ( echo "no."; \ + rm -f .test.c .test.o; exit 1; }; } 2>>$(BUILD_DETAILS_FILE); echo $? >&3 ; } | tee -a $(BUILD_DETAILS_FILE) >&4; } 3>&1;} | { read rc ; exit ${rc}; } } 4>&1 + @printf "Checking if libusb-0.1 is usable... " | tee -a $(BUILD_DETAILS_FILE) + @{ { { { { $(CC) $(LDFLAGS) .test.o -o .test$(EXEC_SUFFIX) $(LIBS) $(USBLIBS) >&2 && \ + echo "yes." || { echo "no."; \ echo "Please install libusb-0.1 or libusb-compat."; \ echo "See README for more information."; echo; \ - rm -f .test.c .test.o .test$(EXEC_SUFFIX); exit 1) + rm -f .test.c .test.o .test$(EXEC_SUFFIX); exit 1; }; } 2>>$(BUILD_DETAILS_FILE); echo $? >&3 ; } | tee -a $(BUILD_DETAILS_FILE) >&4; } 3>&1;} | { read rc ; exit ${rc}; } } 4>&1 @rm -f .test.c .test.o .test$(EXEC_SUFFIX) endif @@ -1023,36 +1027,40 @@ features: compiler @echo "FEATURES := yes" > .features.tmp ifeq ($(NEED_FTDI), yes) - @printf "Checking for FTDI support... " + @printf "Checking for FTDI support... " | tee -a $(BUILD_DETAILS_FILE) @echo "$$FTDI_TEST" > .featuretest.c - @$(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) $(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 ) + @ { $(CC) $(CPPFLAGS) $(CFLAGS) $(FTDI_INCLUDES) $(LDFLAGS) .featuretest.c -o .featuretest$(EXEC_SUFFIX) $(FTDILIBS) $(LIBS) >&2 && \ + ( echo "found."; echo "FTDISUPPORT := yes" >> .features.tmp ; \ + printf "Checking for FT232H support in libftdi... " ; \ + echo "$$FTDI_232H_TEST" >> .featuretest.c ; \ + { $(CC) $(CPPFLAGS) $(CFLAGS) $(FTDI_INCLUDES) $(LDFLAGS) .featuretest.c -o .featuretest$(EXEC_SUFFIX) $(FTDILIBS) $(LIBS) >&2 && \ + ( echo "found."; echo "FT232H := yes" >> .features.tmp ) || \ + ( echo "not found."; echo "FT232H := no" >> .features.tmp ) } \ + ) || \ + ( echo "not found."; echo "FTDISUPPORT := no" >> .features.tmp ) } \ + 2>>$(BUILD_DETAILS_FILE) | tee -a $(BUILD_DETAILS_FILE) endif ifeq ($(CONFIG_LINUX_SPI), yes) - @printf "Checking if Linux SPI headers are present... " + @printf "Checking if Linux SPI headers are present... " | tee -a $(BUILD_DETAILS_FILE) @echo "$$LINUX_SPI_TEST" > .featuretest.c - @$(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) .featuretest.c -o .featuretest$(EXEC_SUFFIX) >/dev/null 2>&1 && \ + @ { $(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) .featuretest.c -o .featuretest$(EXEC_SUFFIX) >&2 && \ ( echo "yes."; echo "LINUX_SPI_SUPPORT := yes" >> .features.tmp ) || \ - ( echo "no."; echo "LINUX_SPI_SUPPORT := no" >> .features.tmp ) + ( echo "no."; echo "LINUX_SPI_SUPPORT := no" >> .features.tmp ) } \ + 2>>$(BUILD_DETAILS_FILE) | tee -a $(BUILD_DETAILS_FILE) endif ifeq ($(NEED_LINUX_I2C), yes) - @printf "Checking if Linux I2C headers are present... " + @printf "Checking if Linux I2C headers are present... " | tee -a $(BUILD_DETAILS_FILE) @echo "$$LINUX_I2C_TEST" > .featuretest.c - @$(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) .featuretest.c -o .featuretest$(EXEC_SUFFIX) >/dev/null 2>&1 && \ + @ { $(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) .featuretest.c -o .featuretest$(EXEC_SUFFIX) >&2 && \ ( echo "yes."; echo "LINUX_I2C_SUPPORT := yes" >> .features.tmp ) || \ - ( echo "no."; echo "LINUX_I2C_SUPPORT := no" >> .features.tmp ) + ( echo "no."; echo "LINUX_I2C_SUPPORT := no" >> .features.tmp ) } \ + 2>>$(BUILD_DETAILS_FILE) | tee -a $(BUILD_DETAILS_FILE) endif - @printf "Checking for utsname support... " + @printf "Checking for utsname support... " | tee -a $(BUILD_DETAILS_FILE) @echo "$$UTSNAME_TEST" > .featuretest.c - @$(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) .featuretest.c -o .featuretest$(EXEC_SUFFIX) >/dev/null 2>&1 && \ + @ { $(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) .featuretest.c -o .featuretest$(EXEC_SUFFIX) >&2 && \ ( echo "found."; echo "UTSNAME := yes" >> .features.tmp ) || \ - ( echo "not found."; echo "UTSNAME := no" >> .features.tmp ) + ( echo "not found."; echo "UTSNAME := no" >> .features.tmp ) } 2>>$(BUILD_DETAILS_FILE) | tee -a $(BUILD_DETAILS_FILE) @$(DIFF) -q .features.tmp .features >/dev/null 2>&1 && rm .features.tmp || mv .features.tmp .features @rm -f .featuretest.c .featuretest$(EXEC_SUFFIX)

1 0

[commit] r1910 - trunk
by repository service 07 Jan '16

07 Jan '16

Author: stefanct Date: Thu Jan 7 10:50:26 2016 New Revision: 1910 URL: http://flashrom.org/trac/flashrom/changeset/1910 Log: makefile: fix exports of PKG_CONFIG_LIBDIR for pkg-config calls. The parenthesis pushed the exports into a subshell thus made them useless. 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 Mon Jan 4 06:08:40 2016 (r1909) +++ trunk/Makefile Thu Jan 7 10:50:26 2016 (r1910) @@ -634,9 +634,9 @@ endif ifeq ($(NEED_FTDI), yes) -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") +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) +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 @@ -761,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)

1 0

Re: [flashrom] Proposed changes to flashrom hosting and workflow
by Stefan Tauner 07 Jan '16

07 Jan '16

(I am replying to various messages of the thread within this single email. Hence the quotes below are of different people.) > For those who missed it on IRC, Stefan (Reinauer) has proposed retiring SVN > and patch work in favor of Git and (likely) Gerrit + Jenkins. Maintaining > SVN and Patchwork represents a surprisingly large maintenance burden on top > of Git and Gerrit that coreboot uses. Additionally, many in the community > work around SVN's limitations by mirroring the project at places like > Github anyway. My counterproposal is to use gitub instead of Gerrit. - I really can't stand gerrit's interface. - We (relatively) often get patches from one-time contributors which is way easier on github because "everybody" has an account there and knows how to work with it (and if not it is straight forward compared to gerrit). - We don't really need jenkins. I am not a big fan of CI although I am a fan of build testing (hence flashrom is build tested for over 30 architecture/OS combinations manually). Depending on how it would be to interface my build bot with jenkins it would however be an improvement (not sure if it is worth it though). - The only reason to avoid github for me would be due to its proprietary nature and related problems (lock-in etc). Please give me other reasons if you prefer coreboot.org-hosted gerrit over github. > Though I know stefanct often makes small corrections/modifications to > patches before submitting them (because our code review process makes even > small amounts of back-and-forth comments so cumbersome). At least this way > such changes can be tracked trivially on-line by diffing the N and N-1 > patch revisions in gerrit. The reason is not because the back-and-forth is cumbersome but because I am a perfectionist who does not want to bother others with my annoying views of details and I don't expect anybody to care about these changes like me (this does not always hold). The same goes for commit messages. With Carl-Daniel I do exchange my views about these kind of things *if* there is any exchange that is ;) > If there really is a large demand for a non-svn hosting, I would be open > to using mercurial (as master) because it at least has some sort of > usability and can provide (conceptually limited) version numbers. I have > worked for a few years with mercurial and the version numbers are > extremely helpful even if they are per-branch and only semi-stable. Just to make things clear here: I won't even discuss this option - it is none. If you want to use another VCS management tool/interface then you are free to do so, but you are the only person known to prefer something else than git so you have to take on the burden and not force everybody else to as it has been up to now - this has to and will end. > The auto-tag of every commit sounds like an option I could agree with. > It would preserve the convenience of the global strong svn commit ID > even for git. > However, I don't know if this would be acceptable for Stefan (especially > from a merging perspective). We have the infrastructure for using this kind of version strings since about 2,5 years and there is a patch that would make flashrom use them in prints which is lingering uncommented in the mailing list since August 2013. It might not be exactly what we want eventually, but if there are no comments I'll have to decide on something... My current plan is to do a 0.9.9 release in January 2016 and switch to git afterwards. I'd like to keep patchwork at least for a while and figure out a way to keep the patches. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

5 6

Supported hardware
by Jan van Roessel 05 Jan '16

05 Jan '16

Tried to read the bios of 2 Intel NUC units with flashrom, getting these messages (see below). Verbose log files are attached to this mail. Hope this inputs helps to extend support of flashrom Base Board Information: Manufacturer: Intel Corporation Product Name: NUC5CPYB Found chipset "Intel Braswell" with PCI ID 8086:229c. 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! Base Board Information: Manufacturer: Intel Corporation Product Name: NUC5i3RYB 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! Met vriendelijke groet, JWM (Jan) van Roessel Consultant Techfox (member of the Foxi Group) =================================== Ringbaan Oost 102-037 5013 CD Tilburg Tel: (+31).13.5425551 The Netherlands =================================== http://www.foxi.nl =========================================== De in dit email-bericht verstrekte informatie is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Het kopiëren van of verstrekken aan en gebruik door derden van deze informatie is niet toegestaan. Door de elektronische verzending van dit bericht kunnen er geen rechten worden ontleend aan de informatie. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Copyright (c) 2016 Foxi Group All world wide rights reserved. ===========================================

1 0

Re: [flashrom] Support...can read BIOS but cannot flash
by David Hendricks 05 Jan '16

05 Jan '16

It looks like EWSR (opcode 0x50) is missing from OPMENU and OPMENU+4. Perhaps a BIOS bug (or bad design)? On Mon, Jan 4, 2016 at 5:30 PM, Mike Keryeski <mike(a)oerinet.net> wrote: > Intel D945GCLF2 motherboard with flash chip SST25LF040A. flashrom seems > to be able to read the BIOS fine, but refuses to flash or erase. > > Here is my output: http://paste.flashrom.org/view.php?id=2856 > > Any ideas would be appreciated > > Thank you, > Mike > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom > -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

ERROR IN GE PRO-M2
by Jose Herrera J.E Suministros y Mas, C.A. 05 Jan '16

05 Jan '16

No how to operate ----------------------------- flashrom v0.9.5.2-r1546 on Linux 3.11.10.10-canaima+ (i686) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.9, GCC 4.7.1, little endian Command line (1 args): flashrom -V Calibrating delay loop... OS timer resolution is 1 usecs, 1369M loops per second, delay more than 10% too short (got 80% of expected delay), recalculating... 1663M loops per second, 10 myus = 10 us, 100 myus = 129 us, 1000 myus = 961 us, 10000 myus = 14003 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: " " DMI string system-product-name: "GE PRO-M2." DMI string system-version: "3.0X" DMI string baseboard-manufacturer: " " DMI string baseboard-product-name: "GE PRO-M2." DMI string baseboard-version: "3.0X" DMI string chassis-type: "Desktop" W836xx hardware monitor busy, ignoring it. Probably not a Winbond Super I/O Found chipset "SiS 650" with PCI ID 1039:0650. 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... Found southbridge 1039:0962 at 00:02:0 OK. The following protocols are supported: Non-SPI. Probing for AMD Am29F010A/B, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F002(N)BB, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F002(N)BT, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F016D, 2048 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F080B, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV001BB, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV001BT, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BB, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BT, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BB, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BT, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BB, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BT, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV081B, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002T, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C512, 64 kB: probe_jedec_common: id1 0x1e, id2 0xf4, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C010A, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C040A, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49BV512, 64 kB: probe_jedec_common: id1 0x1e, id2 0xf4, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F002(N), 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F002(N)T, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Catalyst CAT28F512, 64 kB: probe_jedec_common: id1 0x1e, id2 0xf4, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Bright BM29F040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for EMST F49B002UA, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F010, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F002(A)(N)B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F002(A)(N)T, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29LV640B, 8192 kB: probe_en29lv640b: id1 0xffff, id2 0x00ff Probing for Fujitsu MBM29F004BC, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F004TC, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F400BC, 512 kB: probe_m29f400bt: id1 0xff, id2 0xff Probing for Fujitsu MBM29F400TC, 512 kB: probe_m29f400bt: id1 0xff, id2 0xff Probing for Hyundai HY29F002T, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Hyundai HY29F002B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Hyundai HY29F040A, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F001BN/BX-B, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F001BN/BX-T, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F002BC/BL/BV/BX-T, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F008S3/S5/SC, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-T, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-T, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F001B, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F001T, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F002(N)B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F002(N)T, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29LV040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51000B, 64 kB: probe_jedec_common: id1 0x1e, id2 0xf4, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51000T, 64 kB: probe_jedec_common: id1 0x1e, id2 0xf4, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51400B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51400T, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29LC51000, 64 kB: probe_jedec_common: id1 0x1e, id2 0xf4, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29LC51001, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29LC51002, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm29F002T, 256 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm29F002B, 256 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV010, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV512, 64 kB: probe_jedec_common: id1 0x1e, id2 0xf4, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sharp LH28F008BJT-BTLZ1, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST28SF040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29EE010, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29LE010, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29EE020A, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29LE020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF512, 64 kB: probe_jedec_common: id1 0x1e, id2 0xf4, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF010A, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF020A, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF512, 64 kB: probe_jedec_common: id1 0x1e, id2 0xf4, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF010, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF080, 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 SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 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 SST SST49LF020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002T/NT, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F400BB, 512 kB: probe_m29f400bt: id1 0xff, id2 0xff Probing for ST M29F400BT, 512 kB: probe_m29f400bt: id1 0xff, id2 0xff Probing for ST M29W010B, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29W040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29W512B, 64 kB: probe_jedec_common: id1 0x1e, id2 0xf4, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 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 0xff, id2 0xff, 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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51001B, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51001T, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51002B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51004B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51004T, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {S,V}29C31004B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {S,V}29C31004T, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for TI TMS29F002RB, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for TI TMS29F002RT, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012-old, 128 kB: Old Winbond W29* probe method disabled because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29C010(M)/W29C011A/W29EE011/W29EE012-old' if you have a board with such a chip. Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 kB: probe_jedec_common: id1 0x6a, id2 0x34, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C020(C)/W29C022, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C040/P, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39L040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080A, 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 W49F002U/N, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49F020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. Restoring PCI config space for 00:02:0 reg 0x45 Restoring PCI config space for 00:02:0 reg 0x40 ----------------------------- -- *----* *José Herrera* Operaciones Comerciales J.E Suministros y Mas, C.A. www.jesuministrosymas.com.ve Telefonos de Contacto: +58 243 6721452 +58 414 1448515 +58 426 8326367 @JESYMCA <https://twitter.com/JESYMCA> -- -- -- -- -- -- -- -- ESTIMADO USUARIO, ESTE CORREO NO ES GENERADO POR UNA MAQUINA. CONSIDERE LO SIGUIENTE: SI USTED NO ES CLIENTE DE J.E SUMINISTROS Y MAS, C.A. TOME EN CUENTA QUE ESTE PUEDE RESPONDER A UNOS DE LOS SERVICIOS DE ENVÍO DE CORREO GRATUITO PARA CLIENTES PRESTADO POR J.E SUMINISTROS Y MAS, C.A. DE SER ESTE EL CASO ESTE CORREO DEBE INDICAR EL MOTIVO EN EL ASUNTO Y EN EL CONTENIDO DEBE IR CONTENIDO EL NOMBRE DE LA PERSONA QUE ESTA SOLICITANDO REMITIR EL MISMO. NO EN NECESARIO QUE RESPONDA ESTE CORREO A MENOS QUE USTED CONSIDERE QUE HA RECIBIDO EL MISMO POR EQUIVOCACIÓN FAVOR RESPONDA DE INMEDIATO NOTIFICANDONOS AL RESPECTO PARA QUE VERIFIQUEMOS A LA BREVEDAD. J.E SUMINISTROS Y MAS, C.A. GENTE EN LA QUE USTED PUEDE CONFIAR. -- -- -- -- -- -- -- -- *Antes de imprimir este mensaje, asegúrese de que sea realmente necesario. Proteger el medio ambiente está también en su manos.* -- -- -- -- -- -- -- --

1 0

Support...can read BIOS but cannot flash
by Mike Keryeski 05 Jan '16

05 Jan '16

Intel D945GCLF2 motherboard with flash chip SST25LF040A. flashrom seems to be able to read the BIOS fine, but refuses to flash or erase. Here is my output: http://paste.flashrom.org/view.php?id=2856 Any ideas would be appreciated Thank you, Mike

1 0

[PATCH] Modify strnlen() check for old OSes to check its presence directly
by Andrey Korolyov 04 Jan '16

04 Jan '16

Adding generic check against the function in addition to check for a problematic compiler. Fixes: r1878: Make strnlen() visible in old versions of glibc. Signed-off-by: Andrey Korolyov <andrey(a)xdel.ru> --- flash.h | 2 +- helpers.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/flash.h b/flash.h index 24861ba..3af4c43 100644 --- a/flash.h +++ b/flash.h @@ -260,7 +260,7 @@ void tolower_string(char *str); #ifdef __MINGW32__ char* strtok_r(char *str, const char *delim, char **nextp); #endif -#if defined(__DJGPP__) +#if defined(__DJGPP__) || ! defined(HAVE_STRNLEN) size_t strnlen(const char *str, size_t n); #endif diff --git a/helpers.c b/helpers.c index 7a146c3..cdc87e0 100644 --- a/helpers.c +++ b/helpers.c @@ -92,7 +92,7 @@ char* strtok_r(char *str, const char *delim, char **nextp) #endif /* There is no strnlen in DJGPP */ -#if defined(__DJGPP__) +#if defined(__DJGPP__) || ! defined(HAVE_STRNLEN) size_t strnlen(const char *str, size_t n) { size_t i; -- 1.8.4.5

2 2

[commit] r1909 - trunk
by repository service 04 Jan '16

04 Jan '16

Author: stefanct Date: Mon Jan 4 06:08:40 2016 New Revision: 1909 URL: http://flashrom.org/trac/flashrom/changeset/1909 Log: serial: support arbitrary baud rates on Windows. Available baud rates obviously depend on driver support, but the CBR_ defines used so far are basically only for backwards source compatibility with Win16, so dont bother with them. Signed-off-by: Urja Rannikko <urjaman(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/serial.c Modified: trunk/serial.c ============================================================================== --- trunk/serial.c Mon Jan 4 04:05:23 2016 (r1908) +++ trunk/serial.c Mon Jan 4 06:08:40 2016 (r1909) @@ -43,74 +43,77 @@ fdtype sp_fd = SER_INV_FD; -#if IS_WINDOWS -struct baudentry { - DWORD flag; - unsigned int baud; -}; -#define BAUDENTRY(baud) { CBR_##baud, baud }, -#else +/* There is no way defined by POSIX to use arbitrary baud rates. It only defines some macros that can be used to + * specify respective baud rates and many implementations extend this list with further macros, cf. TERMIOS(3) + * and http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=inclu… + * The code below creates a mapping in sp_baudtable between these macros and the numerical baud rates to deal + * with numerical user input. + * + * On Linux there is a non-standard way to use arbitrary baud rates that flashrom does not support (yet), cf. + * http://www.downtowndougbrown.com/2013/11/linux-custom-serial-baud-rates/ + * + * On Windows there exist similar macros (starting with CBR_ instead of B) but they are only defined for + * backwards compatibility and the API supports arbitrary baud rates in the same manner as the macros, see + * http://msdn.microsoft.com/en-us/library/windows/desktop/aa363214(v=vs.85).a… + */ +#if !IS_WINDOWS struct baudentry { int flag; unsigned int baud; }; #define BAUDENTRY(baud) { B##baud, baud }, -#endif -/* I'd like if the C preprocessor could have directives in macros. - * See TERMIOS(3) and http://msdn.microsoft.com/en-us/library/windows/desktop/aa363214(v=vs.85).a… and - * http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=inclu… */ static const struct baudentry sp_baudtable[] = { BAUDENTRY(9600) /* unconditional default */ -#if defined(B19200) || defined(CBR_19200) +#ifdef B19200 BAUDENTRY(19200) #endif -#if defined(B38400) || defined(CBR_38400) +#ifdef B38400 BAUDENTRY(38400) #endif -#if defined(B57600) || defined(CBR_57600) +#ifdef B57600 BAUDENTRY(57600) #endif -#if defined(B115200) || defined(CBR_115200) +#ifdef B115200 BAUDENTRY(115200) #endif -#if defined(B230400) || defined(CBR_230400) +#ifdef B230400 BAUDENTRY(230400) #endif -#if defined(B460800) || defined(CBR_460800) +#ifdef B460800 BAUDENTRY(460800) #endif -#if defined(B500000) || defined(CBR_500000) +#ifdef B500000 BAUDENTRY(500000) #endif -#if defined(B576000) || defined(CBR_576000) +#ifdef B576000 BAUDENTRY(576000) #endif -#if defined(B921600) || defined(CBR_921600) +#ifdef B921600 BAUDENTRY(921600) #endif -#if defined(B1000000) || defined(CBR_1000000) +#ifdef B1000000 BAUDENTRY(1000000) #endif -#if defined(B1152000) || defined(CBR_1152000) +#ifdef B1152000 BAUDENTRY(1152000) #endif -#if defined(B1500000) || defined(CBR_1500000) +#ifdef B1500000 BAUDENTRY(1500000) #endif -#if defined(B2000000) || defined(CBR_2000000) +#ifdef B2000000 BAUDENTRY(2000000) #endif -#if defined(B2500000) || defined(CBR_2500000) +#ifdef B2500000 BAUDENTRY(2500000) #endif -#if defined(B3000000) || defined(CBR_3000000) +#ifdef B3000000 BAUDENTRY(3000000) #endif -#if defined(B3500000) || defined(CBR_3500000) +#ifdef B3500000 BAUDENTRY(3500000) #endif -#if defined(B4000000) || defined(CBR_4000000) +#ifdef B4000000 BAUDENTRY(4000000) #endif {0, 0} /* Terminator */ @@ -133,6 +136,7 @@ msg_pinfo("Using slowest possible baudrate: %d.\n", sp_baudtable[0].baud); return &sp_baudtable[0]; } +#endif /* Uses msg_perr to print the last system error. * Prints "Error: " followed first by \c msg and then by the description of the last error retrieved via @@ -169,8 +173,7 @@ return 1; } if (baud >= 0) { - const struct baudentry *entry = round_baud(baud); - dcb.BaudRate = entry->flag; + dcb.BaudRate = baud; } dcb.ByteSize = 8; dcb.Parity = NOPARITY; @@ -233,6 +236,7 @@ msg_pdbg("Actual baud flags are: ispeed: 0x%08lX, ospeed: 0x%08lX\n", (long)cfgetispeed(&observed), (long)cfgetospeed(&observed)); } + // FIXME: display actual baud rate - at least if none was specified by the user. #endif return 0; }

1 0

[commit] r1908 - trunk
by repository service 04 Jan '16

04 Jan '16

Author: stefanct Date: Mon Jan 4 04:05:23 2016 New Revision: 1908 URL: http://flashrom.org/trac/flashrom/changeset/1908 Log: serprog: fix missing device parameter error message on Windows. Previously, flashrom -p serprog didnt notice a completely missing dev= string on Windows. Also, the error message shown if no device name followed contained a misleading "/dev/...". Signed-off-by: Urja Rannikko <urjaman(a)gmail.com> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Modified: trunk/serprog.c Modified: trunk/serprog.c ============================================================================== --- trunk/serprog.c Mon Jan 4 04:05:15 2016 (r1907) +++ trunk/serprog.c Mon Jan 4 04:05:23 2016 (r1908) @@ -371,6 +371,8 @@ have_device++; } } + +#if !IS_WINDOWS if (device && !strlen(device)) { msg_perr("Error: No device specified.\n" "Use flashrom -p serprog:dev=/dev/device[:baud]\n"); @@ -379,7 +381,6 @@ } free(device); -#if !IS_WINDOWS device = extract_programmer_param("ip"); if (have_device && device) { msg_perr("Error: Both host and device specified.\n" @@ -415,15 +416,20 @@ free(device); return 1; } +#endif free(device); if (!have_device) { +#if IS_WINDOWS + msg_perr("Error: No device specified.\n" + "Use flashrom -p serprog:dev=comN[:baud]\n"); +#else msg_perr("Error: Neither host nor device specified.\n" "Use flashrom -p serprog:dev=/dev/device:baud or " "flashrom -p serprog:ip=ipaddr:port\n"); +#endif return 1; } -#endif if (register_shutdown(serprog_shutdown, NULL)) return 1;

1 0

[commit] r1907 - trunk
by repository service 04 Jan '16

04 Jan '16

Author: stefanct Date: Mon Jan 4 04:05:15 2016 New Revision: 1907 URL: http://flashrom.org/trac/flashrom/changeset/1907 Log: serprog: allow to omit specifying a baud rate. On USB-based serial connections (VCP) the requested baud rate usually does not matter (much). Remove the arbitrary restriction and use whatever default values the OS/hardware provides. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: Urja Rannikko <urjaman(a)gmail.com> Modified: trunk/flashrom.8.tmpl trunk/programmer.h trunk/serial.c trunk/serprog.c Modified: trunk/flashrom.8.tmpl ============================================================================== --- trunk/flashrom.8.tmpl Mon Jan 4 04:05:06 2016 (r1906) +++ trunk/flashrom.8.tmpl Mon Jan 4 04:05:15 2016 (r1907) @@ -203,10 +203,9 @@ Olimex ARM-USB-TINY/-H, Olimex ARM-USB-OCD/-H, TIAO/DIYGADGET USB Multi-Protocol Adapter (TUMPA), TUMPA Lite, and GOEPEL PicoTAP. .sp -.BR "* serprog" " (for flash ROMs attached to a programmer speaking serprog), \ -including AVR flasher by Urja Rannikko, AVR flasher by eightdot, \ -Arduino Mega flasher by fritz, InSystemFlasher by Juhana Helovuo, and \ -atmegaXXu2-flasher by Stefan Tauner." +.BR "* serprog" " (for flash ROMs attached to a programmer speaking serprog, \ +including Arduino-based devices as well as various programmers by Urja Rannikko, \ +Juhana Helovuo, Stefan Tauner and others)." .sp .BR "* buspirate_spi" " (for SPI flash ROMs attached to a Bus Pirate)" .sp @@ -683,19 +682,22 @@ syntax. .SS .BR "serprog " programmer -A mandatory parameter specifies either a serial -device/baud combination or an IP/port combination for communication with the -programmer. In the device/baud combination, the device has to start with a -slash. For serial, you have to use the +A mandatory parameter specifies either a serial device (and baud rate) or an IP/port combination for +communicating with the programmer. +The device/baud combination has to start with +.B dev= +and separate the optional baud rate with a colon. +For example .sp -.B " flashrom \-p serprog:dev=/dev/device:baud" +.B " flashrom \-p serprog:dev=/dev/ttyS0:115200" .sp -syntax and for IP, you have to use +If no baud rate is given the default values by the operating system/hardware will be used. +For IP connections you have to use the .sp .B " flashrom \-p serprog:ip=ipaddr:port" .sp -instead. In case the device supports it, you can set the SPI clock frequency -with the optional +syntax. +In case the device supports it, you can set the SPI clock frequency with the optional .B spispeed parameter. The frequency is parsed as hertz, unless an .BR M ", or " k Modified: trunk/programmer.h ============================================================================== --- trunk/programmer.h Mon Jan 4 04:05:06 2016 (r1906) +++ trunk/programmer.h Mon Jan 4 04:05:15 2016 (r1907) @@ -719,10 +719,8 @@ #endif void sp_flush_incoming(void); -fdtype sp_openserport(char *dev, unsigned int baud); -int serialport_config(fdtype fd, unsigned int baud); +fdtype sp_openserport(char *dev, int baud); extern fdtype sp_fd; -/* expose serialport_shutdown as it's currently used by buspirate */ int serialport_shutdown(void *data); int serialport_write(const unsigned char *buf, unsigned int writecnt); int serialport_write_nonblock(const unsigned char *buf, unsigned int writecnt, unsigned int timeout, unsigned int *really_wrote); Modified: trunk/serial.c ============================================================================== --- trunk/serial.c Mon Jan 4 04:05:06 2016 (r1906) +++ trunk/serial.c Mon Jan 4 04:05:15 2016 (r1907) @@ -116,7 +116,7 @@ {0, 0} /* Terminator */ }; -const struct baudentry *round_baud(unsigned int baud) +static const struct baudentry *round_baud(unsigned int baud) { int i; /* Round baud rate to next lower entry in sp_baudtable if it exists, else use the lowest entry. */ @@ -125,11 +125,12 @@ return &sp_baudtable[i]; if (sp_baudtable[i].baud < baud) { - msg_pinfo("Warning: given baudrate %d rounded down to %d.\n", + msg_pwarn("Warning: given baudrate %d rounded down to %d.\n", baud, sp_baudtable[i].baud); return &sp_baudtable[i]; } } + msg_pinfo("Using slowest possible baudrate: %d.\n", sp_baudtable[0].baud); return &sp_baudtable[0]; } @@ -154,7 +155,7 @@ #endif } -int serialport_config(fdtype fd, unsigned int baud) +int serialport_config(fdtype fd, int baud) { if (fd == SER_INV_FD) { msg_perr("%s: File descriptor is invalid.\n", __func__); @@ -167,8 +168,10 @@ msg_perr_strerror("Could not fetch original serial port configuration: "); return 1; } - const struct baudentry *entry = round_baud(baud); - dcb.BaudRate = entry->flag; + if (baud >= 0) { + const struct baudentry *entry = round_baud(baud); + dcb.BaudRate = entry->flag; + } dcb.ByteSize = 8; dcb.Parity = NOPARITY; dcb.StopBits = ONESTOPBIT; @@ -188,10 +191,12 @@ return 1; } wanted = observed; - const struct baudentry *entry = round_baud(baud); - if (cfsetispeed(&wanted, entry->flag) != 0 || cfsetospeed(&wanted, entry->flag) != 0) { - msg_perr_strerror("Could not set serial baud rate: "); - return 1; + if (baud >= 0) { + const struct baudentry *entry = round_baud(baud); + if (cfsetispeed(&wanted, entry->flag) != 0 || cfsetospeed(&wanted, entry->flag) != 0) { + msg_perr_strerror("Could not set serial baud rate: "); + return 1; + } } wanted.c_cflag &= ~(PARENB | CSTOPB | CSIZE | CRTSCTS); wanted.c_cflag |= (CS8 | CLOCAL | CREAD); @@ -232,7 +237,7 @@ return 0; } -fdtype sp_openserport(char *dev, unsigned int baud) +fdtype sp_openserport(char *dev, int baud) { fdtype fd; #if IS_WINDOWS Modified: trunk/serprog.c ============================================================================== --- trunk/serprog.c Mon Jan 4 04:05:06 2016 (r1906) +++ trunk/serprog.c Mon Jan 4 04:05:15 2016 (r1907) @@ -342,26 +342,28 @@ unsigned char rbuf[3]; unsigned char c; char *device; - char *baudport; int have_device = 0; - /* the parameter is either of format "dev=/dev/device:baud" or "ip=ip:port" */ + /* the parameter is either of format "dev=/dev/device[:baud]" or "ip=ip:port" */ device = extract_programmer_param("dev"); if (device && strlen(device)) { - baudport = strstr(device, ":"); - if (baudport) { + char *baud_str = strstr(device, ":"); + if (baud_str != NULL) { /* Split device from baudrate. */ - *baudport = '\0'; - baudport++; + *baud_str = '\0'; + baud_str++; } - if (!baudport || !strlen(baudport)) { - msg_perr("Error: No baudrate specified.\n" - "Use flashrom -p serprog:dev=/dev/device:baud\n"); - free(device); - return 1; - } - if (strlen(device)) { - sp_fd = sp_openserport(device, atoi(baudport)); + int baud; + /* Convert baud string to value. + * baud_str is either NULL (if strstr can't find the colon), points to the \0 after the colon + * if no characters where given after the colon, or a string to convert... */ + if (baud_str == NULL || *baud_str == '\0') { + baud = -1; + msg_pdbg("No baudrate specified, using the hardware's defaults.\n"); + } else + baud = atoi(baud_str); // FIXME: replace atoi with strtoul + if (strlen(device) > 0) { + sp_fd = sp_openserport(device, baud); if (sp_fd == SER_INV_FD) { free(device); return 1; @@ -371,7 +373,7 @@ } if (device && !strlen(device)) { msg_perr("Error: No device specified.\n" - "Use flashrom -p serprog:dev=/dev/device:baud\n"); + "Use flashrom -p serprog:dev=/dev/device[:baud]\n"); free(device); return 1; } @@ -386,20 +388,20 @@ return 1; } if (device && strlen(device)) { - baudport = strstr(device, ":"); - if (baudport) { + char *port = strstr(device, ":"); + if (port != NULL) { /* Split host from port. */ - *baudport = '\0'; - baudport++; + *port = '\0'; + port++; } - if (!baudport || !strlen(baudport)) { + if (!port || !strlen(port)) { msg_perr("Error: No port specified.\n" "Use flashrom -p serprog:ip=ipaddr:port\n"); free(device); return 1; } if (strlen(device)) { - sp_fd = sp_opensocket(device, atoi(baudport)); + sp_fd = sp_opensocket(device, atoi(port)); // FIXME: replace atoi with strtoul if (sp_fd < 0) { free(device); return 1;

1 0

[commit] r1906 - trunk
by repository service 04 Jan '16

04 Jan '16

Author: stefanct Date: Mon Jan 4 04:05:06 2016 New Revision: 1906 URL: http://flashrom.org/trac/flashrom/changeset/1906 Log: serprog: ignore failures when setting serial port options. There is no good reason to abort earlier just because some options did not stick. This should improve compatibility without negative effects. If communication is affected by the missing flag(s) then we abort later anyway. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: Urja Rannikko <urjaman(a)gmail.com> Modified: trunk/serial.c Modified: trunk/serial.c ============================================================================== --- trunk/serial.c Mon Jan 4 04:04:36 2016 (r1905) +++ trunk/serial.c Mon Jan 4 04:05:06 2016 (r1906) @@ -209,12 +209,25 @@ if (observed.c_cflag != wanted.c_cflag || observed.c_lflag != wanted.c_lflag || observed.c_iflag != wanted.c_iflag || - observed.c_oflag != wanted.c_oflag || - cfgetispeed(&observed) != cfgetispeed(&wanted)) { - msg_perr("%s: Some requested options did not stick.\n", __func__); - return 1; + observed.c_oflag != wanted.c_oflag) { + msg_pwarn("Some requested serial options did not stick, continuing anyway.\n"); + msg_pdbg(" observed wanted\n" + "c_cflag: 0x%08lX 0x%08lX\n" + "c_lflag: 0x%08lX 0x%08lX\n" + "c_iflag: 0x%08lX 0x%08lX\n" + "c_oflag: 0x%08lX 0x%08lX\n", + (long)observed.c_cflag, (long)wanted.c_cflag, + (long)observed.c_lflag, (long)wanted.c_lflag, + (long)observed.c_iflag, (long)wanted.c_iflag, + (long)observed.c_oflag, (long)wanted.c_oflag + ); + } + if (cfgetispeed(&observed) != cfgetispeed(&wanted) || + cfgetospeed(&observed) != cfgetospeed(&wanted)) { + msg_pwarn("Could not set baud rates exactly.\n"); + msg_pdbg("Actual baud flags are: ispeed: 0x%08lX, ospeed: 0x%08lX\n", + (long)cfgetispeed(&observed), (long)cfgetospeed(&observed)); } - msg_pdbg("Baud rate is %d now.\n", entry->baud); #endif return 0; }

1 0

[commit] r1905 - trunk
by repository service 04 Jan '16

04 Jan '16

Author: stefanct Date: Mon Jan 4 04:04:36 2016 New Revision: 1905 URL: http://flashrom.org/trac/flashrom/changeset/1905 Log: serprog: clear NDELAY flag only once after opening the port. Change sp_openserport() to directly clear the O_NONBLOCK flag that is potentially set by opening the device with O_NDELAY instead of clearing ALL flags in serialport_config() unconditionally. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: Urja Rannikko <urjaman(a)gmail.com> Modified: trunk/serial.c Modified: trunk/serial.c ============================================================================== --- trunk/serial.c Fri Dec 25 23:42:45 2015 (r1904) +++ trunk/serial.c Mon Jan 4 04:04:36 2016 (r1905) @@ -183,10 +183,6 @@ msg_pdbg("Baud rate is %ld.\n", dcb.BaudRate); #else struct termios wanted, observed; - if (fcntl(fd, F_SETFL, 0) != 0) { - msg_perr_strerror("Could not clear serial port mode: "); - return 1; - } if (tcgetattr(fd, &observed) != 0) { msg_perr_strerror("Could not fetch original serial port configuration: "); return 1; @@ -254,11 +250,23 @@ } return fd; #else - fd = open(dev, O_RDWR | O_NOCTTY | O_NDELAY); + fd = open(dev, O_RDWR | O_NOCTTY | O_NDELAY); // Use O_NDELAY to ignore DCD state if (fd < 0) { msg_perr_strerror("Cannot open serial port: "); return SER_INV_FD; } + + /* Ensure that we use blocking I/O */ + const int flags = fcntl(fd, F_GETFL); + if (flags == -1) { + msg_perr_strerror("Could not get serial port mode: "); + return SER_INV_FD; + } + if (fcntl(fd, F_SETFL, flags & ~O_NONBLOCK) != 0) { + msg_perr_strerror("Could not set serial port mode to blocking: "); + return SER_INV_FD; + } + if (serialport_config(fd, baud) != 0) { close(fd); return SER_INV_FD;

1 0

Re: [flashrom] Issue with internal access to the W39V040FB
by Stefan Tauner 03 Jan '16

03 Jan '16

On Fri, 1 Jan 2016 16:18:17 +0300 Andrey Korolyov <andrey(a)xdel.ru> wrote: > Hello and Happy New Year, > > a couple of days ago I acquired an old GeodeLX-based thin client > TONK-1202/ТОНК-1202 (cyr) for a purpose to put coreboot on it, because > board is very simular to existing ones in the coreboot tree and there > should be no big deal to make a port. Aside from very funny issue that > I am not able to boot modern 2.6.18+ i386 Linux kernel on it (ALIX > Geode board said to have same issue [0], but it has been reportedly > fixed by a vendor bios update), all other Linux variants (2.4.xx and > 2.6.13) and NetBSD 7.0 are somehow messing with the internal > interface, with no positive outcome as a result: > > ./flashrom -p internal:laptop=this_is_not_a_laptop -c W39V040FB -r bios.bin -V > .... > Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x25, > id2 0x6b, id1 is normal flash content, id2 is normal flash content > No EEPROM/flash device found > ... > > > NetBSD 5.1 with same flashrom version working just well, I was able to > read the chip contents and write them back without any issues. This is > not a blocker, as I would stick to the external programmer anyway, but > probably worth investigating as a regression - monolithic nature of > NetBSD releases and very limited board performance would not allow to > bisect this easily, so it`s better to narrow a debug field, if > possible, in advance. Hi Andrey, please post complete logs of a working and non-working probe as well as the exact flashrom version you are using. The output of lspci -nnv might become handy as well. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] Successful flashing of a Dell Latitude D630
by Stefan Tauner 03 Jan '16

03 Jan '16

On Mon, 28 Dec 2015 14:47:15 +0100 Márton Miklós <martonmiklosqdev(a)gmail.com> wrote: > Hello all, > > My "try to flash all old stuff at home with flashrom" project continued. > Today's victim was a Dell Latitude D630 with discrete VGA and BIOS version > A07. > > I have successfully updated to the A17 BIOS version with the latest flasrom > from svn. > > Now I have not forgotten to log the write so here it is: > http://paste.flashrom.org/view.php?id=2853 > > I have also created a board enable patch to whitelist this notebook: > http://paste.flashrom.org/view.php?id=2854 > > I have added the PCIe root hub's VID:PID without SSID and the SMBUS > controller with SSID to the whitelisting PCI devices. > Hi, thanks for your report and patch. The latter is not quite right. Have you tested it? Quote from the comment above the board_enable table: > * When a board is matched through DMI, the first and second main PCI IDs > * and the first subsystem PCI ID have to match as well. If you specify the > * first subsystem ID as 0x0:0x0, the DMI matching code expects that the > * subsystem ID of that device is indeed zero. So the two PCI device should be swapped (or the first one should be completed). I have implemented the swap locally. Also, the right function to call is p2_whitelist_laptop because that Dell thing is really a laptop (and not misdetected as one). Finally, the system should also be added to the laptop table in print.c I have done all that and will commit it later together with other small changes. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

SST25VF080B: Gigabyte GA-G33M-S2 successfully reflashed
by Александр Трубицын 03 Jan '16

03 Jan '16

Hi, Stefan! With best regards, Alexander Trubitsyn

2 1

MX25L4006E: Gigabyte GA-P31DS3L successfully reflashed
by Александр Трубицын 03 Jan '16

03 Jan '16

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

2 3

Issue with internal access to the W39V040FB
by Andrey Korolyov 01 Jan '16

01 Jan '16

Hello and Happy New Year, a couple of days ago I acquired an old GeodeLX-based thin client TONK-1202/ТОНК-1202 (cyr) for a purpose to put coreboot on it, because board is very simular to existing ones in the coreboot tree and there should be no big deal to make a port. Aside from very funny issue that I am not able to boot modern 2.6.18+ i386 Linux kernel on it (ALIX Geode board said to have same issue [0], but it has been reportedly fixed by a vendor bios update), all other Linux variants (2.4.xx and 2.6.13) and NetBSD 7.0 are somehow messing with the internal interface, with no positive outcome as a result: ./flashrom -p internal:laptop=this_is_not_a_laptop -c W39V040FB -r bios.bin -V .... Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x25, id2 0x6b, id1 is normal flash content, id2 is normal flash content No EEPROM/flash device found ... NetBSD 5.1 with same flashrom version working just well, I was able to read the chip contents and write them back without any issues. This is not a blocker, as I would stick to the external programmer anyway, but probably worth investigating as a regression - monolithic nature of NetBSD releases and very limited board performance would not allow to bisect this easily, so it`s better to narrow a debug field, if possible, in advance. Thanks! 0. http://www.twam.info/software/linux/gentoo/updating-bios-on-alix3d3-within-…

1 0

tested flash chip EN25QH32 using linux_spi programmer on Himmingboard
by Josua Mayer 31 Dec '15

31 Dec '15

Hi there, just letting you know that I was able to read, write and erase the above mentioned flash chip without any issues. Hardware used: HummingBoard (Freescale i.MX6Q, 4x1GHz armv7l). Chip was attached to the SPI port, and 1 gpio was configured and wired as ChipSelect. Find the logfiles I made attached.

2 1

W836xx: HP Pavilion dv6t-6100 Notebook PC: flashrom -V
by Razzaline Reindell 29 Dec '15

29 Dec '15

Hello Flashrom Developers, As instructed by the flashrom utility, here is my output: flashrom v0.9.8-unknown on Linux 4.3.3-040303-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.8.4, little endian Command line (3 args): flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 2829M loops per second, 10 myus = 10 us, 100 myus = 97 us, 1000 myus = 994 us, 10000 myus = 9866 us, 4 myus = 6 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Notebook" Laptop detected via DMI. DMI string system-manufacturer: "Hewlett-Packard" DMI string system-product-name: "HP Pavilion dv6 Notebook PC" DMI string system-version: "058C110000244720001620100" DMI string baseboard-manufacturer: "Hewlett-Packard" DMI string baseboard-product-name: "1657" DMI string baseboard-version: "10.31" W836xx enter config mode worked or we were already in config mode. W836xx leave config mode had no effect. Active config mode, unknown reg 0x20 ID: 85. Please send the output of "flashrom -V -p internal" to flashrom(a)flashrom.org with W836xx: your board name: flashrom -V as the subject to help us finish support for your Super I/O. Thanks. Found ITE EC, ID 0x8518, Rev 0x02 on port 0x4e. ---------- Thanks, Razzy

1 0

serprog: Pm25LQ032C erase/write working
by Dirk Knop 28 Dec '15

28 Dec '15

Hello dear flashrom developers, the code told me to contact you: flashrom -p serprog:dev=/dev/tty.usbserial-AM0212W4:115200 -w vonets-fullbackup-edited.bin flashrom v0.9.8-unknown on Darwin 15.2.0 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. serprog: Programmer name is "frser-duino" serprog: requested mapping AT45CS1282 is incompatible: 0x1080000 bytes at 0x00000000fef80000. Found PMC flash chip "Pm25LQ032C" (4096 kB, SPI) on serprog. === This flash part has status UNTESTED for operations: ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash… I didn’t make any logs, but use flashrom/HEAD (thus latest development branch) with homebrew on Mac OS X for 5 days and successfully read, erase and write that SPI flash several times already. I hope this helps! Cheers, Dirk

2 2

FS Esprimo E5730: writing rom images seems to work correctly
by Elmar Stellnberger 28 Dec '15

28 Dec '15

Today I was about to try write support for flashrom with the Xi 3650 BIOS and see whether it would work. The two images used for write were not too different (the only difference was a BIOS setting letting you choose between the on-board graphics card and an Nvidia Geforce 9600M GT). Nonetheless it seems to have written (and erased) at least one block of the BIOS ROM correctly. Yours, Elmar P.S. the console screenshot: Proceeding anyway because user forced us to. Found chipset "Intel ICH9M-E". Enabling flash write... OK. Found Winbond flash chip "W25X16" (2048 kB, SPI) at physical address 0xffe00000. Reading flash... done. root@sysresccd /usb/Xi3650-BIOS/flashrom-T6400 % ls intermediate Xi3650-T6400-1.0B-1646-0020.rom Xi3650-T6400-1.0H-1646-0024-IGD-2ndflash.rom root@sysresccd /usb/Xi3650-BIOS/flashrom-T6400 % cmp Xi3650-T6400-1.0H-1646-0024-IGD-2ndflash.rom intermediate/Xi3650-T6400-1.0H-1646-0024-IGD.rom Xi3650-T6400-1.0H-1646-0024-IGD-2ndflash.rom intermediate/Xi3650-T6400-1.0H-1646-0024-IGD.rom differ: char 1575900, line 3706 root@sysresccd /usb/Xi3650-BIOS/flashrom-T6400 % ls intermediate Xi3650-T6400-1.0B-1646-0020.rom Xi3650-T6400-1.0H-1646-0024-IGD-2ndflash.rom root@sysresccd /usb/Xi3650-BIOS/flashrom-T6400 % flashrom -p internal:laptop=force_I_want_a_brick --write intermediate/Xi3650-T6400-1.0H-1646-0024-Nvidia.rom flashrom v0.9.7-r1711 on Linux 3.14.50-std460-amd64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. ======================================================================== 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. ======================================================================== Proceeding anyway because user forced us to. Found chipset "Intel ICH9M-E". Enabling flash write... OK. Found Winbond flash chip "W25X16" (2048 kB, SPI) at physical address 0xffe00000. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED. root@sysresccd /usb/Xi3650-BIOS/flashrom-T6400 % flashrom -p internal:laptop=force_I_want_a_brick --write Xi3650-T6400-1.0H-1646-0024-IGD-2ndflash.rom flashrom v0.9.7-r1711 on Linux 3.14.50-std460-amd64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. ======================================================================== 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. ======================================================================== Proceeding anyway because user forced us to. Found chipset "Intel ICH9M-E". Enabling flash write... OK. Found Winbond flash chip "W25X16" (2048 kB, SPI) at physical address 0xffe00000. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED. root@sysresccd /usb/Xi3650-BIOS/flashrom-T6400 %

2 7

Re: [flashrom] Support and configuration
by Stefan Tauner 28 Dec '15

28 Dec '15

On Sun, 27 Dec 2015 20:02:49 +0100 Goran Metlic <goran.metlic(a)gmail.com> wrote: > 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. Hi Goran, it is possible but AFAIK no one has tried so far. One would need some additional chips to accomplish that IIRC because parallel chips require way more pins than the handful SPI needs and thus shift registered or similar elements would be needed - definitely not a project for one evening. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Successful flashing of a Dell Latitude D630
by Márton Miklós 28 Dec '15

28 Dec '15

Hello all, My "try to flash all old stuff at home with flashrom" project continued. Today's victim was a Dell Latitude D630 with discrete VGA and BIOS version A07. I have successfully updated to the A17 BIOS version with the latest flasrom from svn. Now I have not forgotten to log the write so here it is: http://paste.flashrom.org/view.php?id=2853 I have also created a board enable patch to whitelist this notebook: http://paste.flashrom.org/view.php?id=2854 I have added the PCIe root hub's VID:PID without SSID and the SMBUS controller with SSID to the whitelisting PCI devices. -- Regards, Miklos Marton

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom