flashrom

flashrom@flashrom.org

9164 discussions

AT45DB011D / Spartan-3AN SPI flash
by Aidan Thornton 17 Aug '12

17 Aug '12

Hi, So I've got access to a board with an AT45DB011D (or more accurately a XC3S50AN FPGA with integrated SPI flash that's identical to an AT45DB011D down to the ID bytes) hooked up to an FT4232H-based programmer. I've chatted to stefanct in IRC and apparently this is unlikely to be supported by flashrom in the near future, but if at some point someone does want to add support and I still have access to this board I might be able to test it. For anyone that isn't familiar with the AT45DB011D, it's an oddball Atmel DataFlash chip with a non-power-of-two page size (264 bytes per page) and a slightly interesting address space as a result of that. It's also available in a 256-byte page variant that has the same ID and which can only be distinguished by a bit in the status register. One of the read commands supported is mostly standard aside from some weirdness resulting from the odd page size, writing and erasing is probably less so. Aidan

1 0

CHIPSET: AMD CS5536
by Sven Neumann 17 Aug '12

17 Aug '12

Hi, I am trying to flash a new coreboot image to our hardware, which is a "PC Engines ALIX 2C.2" board, see http://pcengines.ch/alix2c2.htm Latest version of flashrom gives me following output, so I am reporting this to you as requested: flashrom v0.9.6.1-r1564 on Linux 3.5.2 (i586) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. coreboot table found at 0xf7c1c00. Found chipset "AMD CS5536". Enabling flash write... OK. WARNING: unexpected second chipset match: "AMD CS5536" ignoring, please report lspci and board URL to flashrom(a)flashrom.org with 'CHIPSET: your board name' in the subject line. No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. And here's the output from "lspci -v": 00:01.0 Class 0600: Device 1022:2080 (rev 33) Subsystem: Device 1022:2080 Flags: bus master, 66MHz, medium devsel, latency 64 I/O ports at ac1c [size=4] 00:01.2 Class 1010: Device 1022:2082 Subsystem: Device 1022:2082 Flags: 66MHz, medium devsel, IRQ 11 Memory at fe020000 (32-bit, non-prefetchable) [size=16K] 00:09.0 Class 0200: Device 1106:3053 (rev 96) Subsystem: Device 1106:0106 Flags: bus master, stepping, medium devsel, latency 64, IRQ 10 I/O ports at 1000 [size=256] Memory at fe029000 (32-bit, non-prefetchable) [size=256] Capabilities: [40] Power Management version 2 Kernel driver in use: via-rhine 00:0b.0 Class 0200: Device 1106:3053 (rev 96) Subsystem: Device 1106:0106 Flags: bus master, stepping, medium devsel, latency 64, IRQ 9 I/O ports at 1400 [size=256] Memory at fe029100 (32-bit, non-prefetchable) [size=256] Capabilities: [40] Power Management version 2 Kernel driver in use: via-rhine 00:0c.0 Class 0200: Device 168c:001b (rev 01) Subsystem: Device 185f:1600 Flags: bus master, medium devsel, latency 168, IRQ 11 Memory at fe000000 (32-bit, non-prefetchable) [size=64K] Capabilities: [44] Power Management version 2 Kernel driver in use: ath5k Kernel modules: ath5k 00:0f.0 Class 0601: Device 1022:2090 (rev 03) Subsystem: Device 1022:2090 Flags: 66MHz, medium devsel I/O ports at 20b0 [size=8] I/O ports at 1800 [size=256] I/O ports at 2000 [size=64] I/O ports at 2080 [size=32] I/O ports at 1c00 [size=128] I/O ports at 2040 [size=64] Kernel driver in use: cs5535-mfd 00:0f.2 Class 0101: Device 1022:209a (rev 01) (prog-if 80 [Master]) Subsystem: Device 1022:209a Flags: bus master, 66MHz, medium devsel, latency 248 [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 000003f0 (type 3, non-prefetchable) [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 00000370 (type 3, non-prefetchable) I/O ports at 20a0 [size=16] Kernel driver in use: cs5536 00:0f.4 Class 0c03: Device 1022:2094 (rev 02) (prog-if 10) Subsystem: Device 1022:2094 Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 9 Memory at fe026000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel driver in use: ohci_hcd 00:0f.5 Class 0c03: Device 1022:2095 (rev 02) (prog-if 20) Subsystem: Device 1022:2095 Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 9 Memory at fe027000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel driver in use: ehci_hcd As flashrom does not appear to find the flash chip, I am now somewhat stuck. Any help would be much appreciated. Regards, Sven -- Sven Neumann Head of RAUMFELD Software Development Lautsprecher Teufel GmbH Gewerbehof Bülowbogen - Aufgang D1 Bülowstr. 66 - 10783 Berlin - Germany Registernummer HRB 20271 beim Amtsgericht Berlin-Charlottenburg Geschäftsführer: Thorsten Reuber, Thomas Stiegler Tel. +49 (0)30 - 300 930 - 0, Direkt -153 neumann(a)teufel.de www.teufel.de www.teufelaudio.com http://blog.teufel.de

1 1

[PATCH] Allow specifying CPPFLAGS
by Carl-Daniel Hailfinger 16 Aug '12

16 Aug '12

The user may know better which CFLAGS/CPPFLAGS are appropriate. Use FLASHROM_CFLAGS for flags which flashrom definitely needs to build. Note: With this patch, automatic Ubuntu Launchpad builds should work again. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-makefile_allow_cppflags/Makefile =================================================================== --- flashrom-makefile_allow_cppflags/Makefile (Revision 1574) +++ flashrom-makefile_allow_cppflags/Makefile (Arbeitskopie) @@ -122,7 +122,7 @@ ifeq ($(TARGET_OS), MinGW) EXEC_SUFFIX := .exe # MinGW doesn't have the ffs() function, but we can use gcc's __builtin_ffs(). -CPPFLAGS += -Dffs=__builtin_ffs +FLASHROM_CFLAGS += -Dffs=__builtin_ffs # libusb-win32/libftdi stuff is usually installed in /usr/local. CPPFLAGS += -I/usr/local/include LDFLAGS += -L/usr/local/lib @@ -201,7 +201,7 @@ endif ifeq ($(TARGET_OS), libpayload) -CPPFLAGS += -DSTANDALONE +FLASHROM_CFLAGS += -DSTANDALONE ifeq ($(CONFIG_DUMMY), yes) UNSUPPORTED_FEATURES += CONFIG_DUMMY=yes else @@ -603,7 +603,7 @@ TAROPTIONS = $(shell LC_ALL=C tar --version|grep -q GNU && echo "--owner=root --group=root") %.o: %.c .features - $(CC) -MMD $(CFLAGS) $(CPPFLAGS) $(FEATURE_CFLAGS) $(SVNDEF) -o $@ -c $< + $(CC) -MMD $(CFLAGS) $(CPPFLAGS) $(FLASHROM_CFLAGS) $(FEATURE_CFLAGS) $(SVNDEF) -o $@ -c $< # Make sure to add all names of generated binaries here. # This includes all frontends and libflashrom. Index: flashrom-makefile_allow_cppflags/util/ich_descriptors_tool/Makefile =================================================================== --- flashrom-makefile_allow_cppflags/util/ich_descriptors_tool/Makefile (Revision 1574) +++ flashrom-makefile_allow_cppflags/util/ich_descriptors_tool/Makefile (Arbeitskopie) @@ -30,10 +30,10 @@ endif -CPPFLAGS += -MMD -MP -MF $(DEPPATH)/$((a)F).d +FLASHROM_CFLAGS += -MMD -MP -MF $(DEPPATH)/$((a)F).d # enables functions that populate the descriptor structs from plain binary dumps -CPPFLAGS += -D ICH_DESCRIPTORS_FROM_DUMP -CPPFLAGS += $(patsubst %,-I%,$(EXTRAINCDIRS)) +FLASHROM_CFLAGS += -D ICH_DESCRIPTORS_FROM_DUMP +FLASHROM_CFLAGS += $(patsubst %,-I%,$(EXTRAINCDIRS)) OBJ = $(OBJATH)/$(SRC:%.c=%.o) @@ -42,15 +42,15 @@ all:$(PROGRAM)$(EXEC_SUFFIX) $(OBJ): $(OBJATH)/%.o : %.c - $(CC) $(CFLAGS) $(CPPFLAGS) -o $@ -c $< + $(CC) $(CFLAGS) $(CPPFLAGS) $(FLASHROM_CFLAGS) -o $@ -c $< # this enables us to share source files without simultaneously sharing .o files # with flashrom, which would lead to unexpected results (w/o running make clean) $(SHAREDOBJ): $(OBJATH)/%.o : $(SHAREDSRCDIR)/%.c - $(CC) $(CFLAGS) $(CPPFLAGS) -o $@ -c $< + $(CC) $(CFLAGS) $(CPPFLAGS) $(FLASHROM_CFLAGS) -o $@ -c $< $(PROGRAM)$(EXEC_SUFFIX): $(OBJ) $(SHAREDOBJ) - $(CC) -o $(PROGRAM)$(EXEC_SUFFIX) $(OBJ) $(SHAREDOBJ) + $(CC) $(LDFLAGS) -o $(PROGRAM)$(EXEC_SUFFIX) $(OBJ) $(SHAREDOBJ) clean: rm -f $(PROGRAM) $(PROGRAM).exe -- http://www.hailfinger.org/

1 1

[commit] r1575 - in trunk: . util/ich_descriptors_tool
by repository service 16 Aug '12

16 Aug '12

Author: hailfinger Date: Thu Aug 16 01:06:32 2012 New Revision: 1575 URL: http://flashrom.org/trac/flashrom/changeset/1575 Log: Allow specifying CPPFLAGS The user may know better which CFLAGS/CPPFLAGS are appropriate. Use FLASHROM_CFLAGS for flags which flashrom definitely needs to build. Thanks to Stefan Tauner for pointing out the flaw in r1574. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Modified: trunk/Makefile trunk/util/ich_descriptors_tool/Makefile Modified: trunk/Makefile ============================================================================== --- trunk/Makefile Tue Aug 14 23:36:11 2012 (r1574) +++ trunk/Makefile Thu Aug 16 01:06:32 2012 (r1575) @@ -122,7 +122,7 @@ ifeq ($(TARGET_OS), MinGW) EXEC_SUFFIX := .exe # MinGW doesn't have the ffs() function, but we can use gcc's __builtin_ffs(). -CPPFLAGS += -Dffs=__builtin_ffs +FLASHROM_CFLAGS += -Dffs=__builtin_ffs # libusb-win32/libftdi stuff is usually installed in /usr/local. CPPFLAGS += -I/usr/local/include LDFLAGS += -L/usr/local/lib @@ -201,7 +201,7 @@ endif ifeq ($(TARGET_OS), libpayload) -CPPFLAGS += -DSTANDALONE +FLASHROM_CFLAGS += -DSTANDALONE ifeq ($(CONFIG_DUMMY), yes) UNSUPPORTED_FEATURES += CONFIG_DUMMY=yes else @@ -603,7 +603,7 @@ TAROPTIONS = $(shell LC_ALL=C tar --version|grep -q GNU && echo "--owner=root --group=root") %.o: %.c .features - $(CC) -MMD $(CFLAGS) $(CPPFLAGS) $(FEATURE_CFLAGS) $(SVNDEF) -o $@ -c $< + $(CC) -MMD $(CFLAGS) $(CPPFLAGS) $(FLASHROM_CFLAGS) $(FEATURE_CFLAGS) $(SVNDEF) -o $@ -c $< # Make sure to add all names of generated binaries here. # This includes all frontends and libflashrom. Modified: trunk/util/ich_descriptors_tool/Makefile ============================================================================== --- trunk/util/ich_descriptors_tool/Makefile Tue Aug 14 23:36:11 2012 (r1574) +++ trunk/util/ich_descriptors_tool/Makefile Thu Aug 16 01:06:32 2012 (r1575) @@ -30,10 +30,10 @@ endif -CPPFLAGS += -MMD -MP -MF $(DEPPATH)/$((a)F).d +FLASHROM_CFLAGS += -MMD -MP -MF $(DEPPATH)/$((a)F).d # enables functions that populate the descriptor structs from plain binary dumps -CPPFLAGS += -D ICH_DESCRIPTORS_FROM_DUMP -CPPFLAGS += $(patsubst %,-I%,$(EXTRAINCDIRS)) +FLASHROM_CFLAGS += -D ICH_DESCRIPTORS_FROM_DUMP +FLASHROM_CFLAGS += $(patsubst %,-I%,$(EXTRAINCDIRS)) OBJ = $(OBJATH)/$(SRC:%.c=%.o) @@ -42,15 +42,15 @@ all:$(PROGRAM)$(EXEC_SUFFIX) $(OBJ): $(OBJATH)/%.o : %.c - $(CC) $(CFLAGS) $(CPPFLAGS) -o $@ -c $< + $(CC) $(CFLAGS) $(CPPFLAGS) $(FLASHROM_CFLAGS) -o $@ -c $< # this enables us to share source files without simultaneously sharing .o files # with flashrom, which would lead to unexpected results (w/o running make clean) $(SHAREDOBJ): $(OBJATH)/%.o : $(SHAREDSRCDIR)/%.c - $(CC) $(CFLAGS) $(CPPFLAGS) -o $@ -c $< + $(CC) $(CFLAGS) $(CPPFLAGS) $(FLASHROM_CFLAGS) -o $@ -c $< $(PROGRAM)$(EXEC_SUFFIX): $(OBJ) $(SHAREDOBJ) - $(CC) -o $(PROGRAM)$(EXEC_SUFFIX) $(OBJ) $(SHAREDOBJ) + $(CC) $(LDFLAGS) -o $(PROGRAM)$(EXEC_SUFFIX) $(OBJ) $(SHAREDOBJ) clean: rm -f $(PROGRAM) $(PROGRAM).exe

1 0

Re: [flashrom] IBM SurePOS 700 4800-783 support
by Stefan Tauner 15 Aug '12

15 Aug '12

On Wed, 15 Aug 2012 08:56:34 -0400 Jason_Vannest(a)abercrombie.com wrote: Hi Jason! > Sorry Stefan, > > I've been busy and our test lab is being used to do a regression right now > so I've not had time to try and compile and test the patch you provided. NP, i just wanted to get sure you have received my last mail and nothing momentous happened, because your replies were within days or even hours before. > I do intend to do so, give me a little more time and I'll see what I can > do. We have received your other message containing the read out bios image. It sits in the moderation queue at the moment, because we can't publish it (it is copyrighted). Thanks for taking the time to test! What we actually wanted to see is the output that flashrom prints to screen (or saves to a file when one specifies the log file option -o "logfilename"). But since you were able to read the BIOS file correctly the patch seems to have worked at least to some extend. This is great news! Nevertheless please send the verbose output of flashrom too. > On the topic of IBM and help, I have been in discussion with IBM about the > firmware updates and they have been very adamant that we need to insure > that we update all the devices not just the BIOS itself. From looking at > a handful of their update packages, I can see that they frequently include > updates for riser cards, service processors and possibly other devices > with the BIOS updates. So before we implement something with flashrom we > would want to make sure we're not missing something that could later cause > us issues even if the issues are only that IBM is unhappy because we > didn't follow their update procedures. The latter would be the last thing i would worry about, but especially the service processors might interact with the BIOS and if an update changes the protocol that they talk with each other, then this may lead to unbootable machines... It is probably possible to add support for the other device to flashrom as well, but that would certainly not be a single line change and take way more time to implement, even if IBM provides some documentation. Without documentation it would probably be pretty much infeasible. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] IBM SurePOS 700 4800-783 support
by Stefan Tauner 15 Aug '12

15 Aug '12

On Wed, 11 Jul 2012 18:17:19 -0400 Jason_Vannest(a)abercrombie.com wrote: > If I'm reading the flashrom site correctly this is one of the flash chips > that flashrom has support for already. So that might be a plus. Yes, the flash chip itself wont be a problem. There is a service manual for the POS located at ftp://ftp.software.ibm.com/software/retail/pubs/hw/4800_surepos700/btd5_480… and it mentions a "backup bios" in the service processor section. That could complicate things further (or help you out if something fails if you are very lucky, but usually it make things worse for us). The remainder of the document is not very helpful (targeted at users not developers). > > I'd venture a guess that we can do this before IBM can > > even give you a quote. > > What kind of information would you want? I have pretty solid connections > with IBM I may be able to get questions answered about this. A schematic that contains the data path between the southbridge and the flash chip as well as its relation to the Renesas IC would indicate if we have to take care about the Renesas at all. Any additional information regarding the BIOS upgrade process (e.g. if the version of the Renesas' firmware has to be kept in sync with the BIOS) or the service processor's interaction with the flash chip would be very welcome too. Above all we need to work on the support for the VIA chipset (VT8251), but IBM won't be able to help us with that. I have no news regarding that. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

3 6

Re: [flashrom] Issue with flashrom tool
by Carl-Daniel Hailfinger 15 Aug '12

15 Aug '12

Hi Lap Ngo Doan, your flashrom version is very old. Please get a newer flashrom version from https://launchpad.net/~flashrom-developers/+archive/flashrom-daily or compile latest flashrom from source: http://flashrom.org/Downloads Am 15.08.2012 05:14 schrieb Lap Ngo Doan: > We are preparing flash new rom (coreboot.rom) to Persimmon board using > flashrom tool > http://www.coreboot.org/AMD_DB-FT1_PERSIMMON > http://www.amd.com/us/Documents/49286_Embedded_Solutions_Brief_FT1_web.pdf > Before do that, We'd like to make a test of using flashroom tool. > [Envrionment] > Hardware: Persimmon board > OS: Ubuntu 10.10 32bits > Flash rom tool: flashrom > [Testing steps] > 1. Use flashrom tool to capture/read current ROM > file (to make a backup) : ROM_BOARD2.rom > $flashrom -r ROM_BOARD2.rom > 2. Verify captured data (ROM_BOARD2.rom) with > current ROM > $flashrom -v ROM_BOARD2.rom > Unfortunately, the verifiy status is FALIED ==> We are not confident to use > flashrom tool to update new rom file Please retry the test with flashrom 0.9.5 or 0.9.6 or newer in verbose mode: flashrom -p internal -VV -r ROM_BOARD2.rom flashrom -p internal -VV -v ROM_BOARD2.rom Then post the new verbose logs to this mailing list. Regards, Carl-Daniel -- http://www.hailfinger.org/

1 0

Issue with flashrom tool
by Lap Ngo Doan 15 Aug '12

15 Aug '12

Hi all, We are preparing flash new rom (coreboot.rom) to Persimmon board using flashrom tool http://www.coreboot.org/AMD_DB-FT1_PERSIMMON http://www.amd.com/us/Documents/49286_Embedded_Solutions_Brief_FT1_web.pdf Before do that, We'd like to make a test of using flashroom tool. [Envrionment] Hardware: Persimmon board OS: Ubuntu 10.10 32bits Flash rom tool: flashrom [Testing steps] 1. Use flashrom tool to capture/read current ROM file (to make a backup) : ROM_BOARD2.rom $flashrom -r ROM_BOARD2.rom 2. Verify captured data (ROM_BOARD2.rom) with current ROM $flashrom -v ROM_BOARD2.rom Unfortunately, the verifiy status is FALIED ==> We are not confident to use flashrom tool to update new rom file Could you please refer to log file to see the details and give us some advises? Thank you very much!

1 0

Fix for serprog-ardu initialization failure due to unimplemented S_CMD_S_BUSTYPE (0x12)
by Alexander Meyer 15 Aug '12

15 Aug '12

Hi, I had problems making flashrom talk to an Arduino as described in http://www.flashrom.org/index.php?title=Serprog&redirect=no It always failed right after this: Warning: Automatic command availability check failed for cmd 0x12 - won't execute cmd With help from stefanct on the IRC I was able to fix it and successfully write and verify a W25X80 bios chip. The problem was, stefanct implemented a mandatory check for S_CMD_S_BUSTYPE (0x12) in flashrom which isn't yet implemented in the Arduino code. To work around it you can downgrade flashrom to before r1557 or you can make the Arduino code give a satisfactory answer to the check. To do that, you must append "| (1 << (S_CMD_S_BUSTYPE - 16))" to the SUPPORTED_COMMANDS_HIGH define, and send an ACK when asked for S_CMD_S_BUSTYPE (0x12) in the Arduino code. Actually, "<stefanct> the right way would be to test if flashrom tries to set SPI and ack in that case and nak in all other cases". I also had problems with the high baudrate. Setting it to 1000000 instead of 2000000 seems to work reliably and is still fast enough for me. YMMV. Note that the value must be changed in the arguments for flashrom as well as the Arduino code. Thank you guys for your great work and thank you stefanct for helping me out! Cheers, Alexander

1 0

Shuttle Inc FN78S: flashrom -V
by dvrhax 15 Aug '12

15 Aug '12

3 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom