flashrom May 2012

flashrom@flashrom.org

42 participants
127 discussions

Output of Flashrom for Asus M2N68-VM
by juergen.bullinger＠gmx.de 16 Jul '12

16 Jul '12

Hi, thank you for the great tool it saved me from messing ouround with DOS boot dics etc on a system which is purely running on Linux. I updated the bios of this board and in case the diagnostic output of this board is interesting for you, here is it: juergen@media:/scratch/software/bios$ sudo flashrom [sudo] password for juergen: flashrom v0.9.5.2-r1517 on Linux 3.2.0-25-generic (x86_64), built with libpci 3.1.8, GCC 4.6.3, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "NVIDIA MCP67". Enabling flash write... This chipset is not really supported yet. Guesswork... SPI on this chipset is WIP. Please report any success or failure by mailing us the verbose output to flashrom(a)flashrom.org, thanks! Mapping NVIDIA MCP6x SPI at 0xfec80000, unaligned size 0x544. Please send the output of "flashrom -V" to flashrom(a)flashrom.org with your board name: flashrom -V as the subject to help us finish support for your chipset. Thanks. OK. Found Macronix flash chip "MX25L8005" (1024 kB, SPI) at physical address 0xfff00000. No operations were specified. -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a

2 1

Re: [flashrom] Marvell 9120 SATA Controller/Macronix MX25L4005 EEPROM on ASUS P7p55D-E LX
by Stefan Tauner 18 Jun '12

18 Jun '12

please always reply to the mailing list. some stuff about in-system programming that might be partially relevant to you: http://flashrom.org/ISP a special flashrom version for the chip is not needed at all, you seem to be way too focused on that. normally flashrom will detect that chip by itself. if not then the communication does not work reliable. there is also an option to look for a specific chip only instead of all compatible chips (-c MX25L4005). Begin forwarded message: Date: Fri, 25 May 2012 18:19:27 -0400 From: "Richard R. Blum" <rrblum(a)gmail.com> To: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Subject: Re: [flashrom] Marvell 9120 SATA Controller/Macronix MX25L4005 EEPROM on ASUS P7p55D-E LX Stefan Tauner: Thanks for your reply. I bricked the onboard Marvell 9120 SATA controller by flashing the sata controller itself using the marvell flash tool with firmware for another controller model (stupidly). When I try to force a flash I now get a "Adapter Not Found" message. I'm sure the sata controller firmware is on a Macronix MX25L4005 EEPROM located adjacent to the Marvell onboard sata controller according to information for the Marvell 9120 SATA controller and from reading about the experience of others with similar problems and hardware. Flashing the mainboard bios has no effect. Besides, the Macronix MX25L4005 has 512k memory and the mainboard bios files are 2048k. I'm considering using a buspirate and flashrom to flash the MX25L4005. I'll probably try to flash the MX25L4005 while it is still soldered onto the mainboard but not powered by the mainboard, and supply power to the MX25L4005 separately from the board, although I have read where others have had to either lift their MX25L4005 vcc leg from it's mainboard or remove the MX25L4005 entirely for a successful flash. I believe I have a good full copy of the firmware that I overwrote, I just need to purchase a buspirate and set of probes or a clamp and use the correctly compiled flashrom. At this point having a version of flashrom complied to specifically flash a MX25L4005 would be a great help along with any other advice you might have for me. R. Blum On 25 May 2012 at 21:26, Stefan Tauner wrote: On Thu, 24 May 2012 16:02:47 -0400 "Richard R. Blum" <rrblum(a)gmail.com> wrote: > Dear Flashrom Support: > > I recently bricked the Marvell 9120 SATA Controller on an ASUS > P7P55D-E LX mainboard. oh. onboard sata chip. obviously i was the one confused, sorry. how did you brick it? if the firmware is stored in the normal flash as flashrom sees it (which is likely), flashing the normal mainboard updates should fix it. what about the flashing tools from asus... did you try recovering with them? -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

[PATCH] Bus Pirate buffer management revamp
by Carl-Daniel Hailfinger 08 Jun '12

08 Jun '12

Use separate functions for managing the Bus Pirate command/data buffer. Open-coding the buffer management was the first step, now the goal is to make it readable. This is the buffer management part of "Re: [flashrom] [PATCH] Make Bus Pirate init more robust, speed up flashing" The buffer management of the Bus Pirate driver has been revamped to use grow-only buffers with a reasonable initial default size so realloc() will not have to be called in normal operation. A side effect is the ability to switch to a static buffer without major hassle. Handle OOM gracefully. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-buspirate_buffermanagement/flash.h =================================================================== --- flashrom-buspirate_buffermanagement/flash.h (Revision 1184) +++ flashrom-buspirate_buffermanagement/flash.h (Arbeitskopie) @@ -35,6 +35,9 @@ #define ERROR_PTR ((void*)-1) +/* Error codes */ +#define OOM_ERROR -100 + typedef unsigned long chipaddr; int register_shutdown(void (*function) (void *data), void *data); Index: flashrom-buspirate_buffermanagement/buspirate_spi.c =================================================================== --- flashrom-buspirate_buffermanagement/buspirate_spi.c (Revision 1184) +++ flashrom-buspirate_buffermanagement/buspirate_spi.c (Arbeitskopie) @@ -46,6 +46,55 @@ #define sp_flush_incoming(...) 0 #endif +static unsigned char *bp_commbuf = NULL; +static int bp_commbufsize = 0; + +static int buspirate_commbuf_resize(int bufsize) +{ + unsigned char *tmpbuf; + + /* Never shrink. realloc() calls are expensive. */ + if (bufsize <= bp_commbufsize) + return 0; + + tmpbuf = realloc(bp_commbuf, bufsize); + if (!tmpbuf) { + /* This is debatable. Do we really want to free the existing + * buffer or do we want to keep it around, especially if memory + * is already tight? + */ + free(bp_commbuf); + bp_commbuf = NULL; + bp_commbufsize = 0; + msg_perr("Out of memory!\n"); + return OOM_ERROR; + } + + bp_commbuf = tmpbuf; + bp_commbufsize = bufsize; + return 0; +} + +static int buspirate_commbuf_init(int bufsize) +{ + bp_commbuf = malloc(bufsize); + if (!bp_commbuf) { + bp_commbufsize = 0; + msg_perr("Out of memory!\n"); + return OOM_ERROR; + } + + bp_commbufsize = bufsize; + return 0; +} + +static void buspirate_commbuf_shutdown(void) +{ + free(bp_commbuf); + bp_commbuf = NULL; + bp_commbufsize = 0; +} + static int buspirate_sendrecv(unsigned char *buf, unsigned int writecnt, unsigned int readcnt) { int i, ret = 0; @@ -231,6 +280,10 @@ return 1; } + /* Sensible default buffer size. */ + if (buspirate_commbuf_init(16 + 3)) + return OOM_ERROR; + buses_supported = CHIP_BUSTYPE_SPI; spi_controller = SPI_CONTROLLER_BUSPIRATE; @@ -267,6 +320,9 @@ ret = serialport_shutdown(); if (ret) return ret; + + buspirate_commbuf_shutdown(); + msg_pdbg("Bus Pirate shutdown completed.\n"); return 0; @@ -275,55 +331,51 @@ int buspirate_spi_send_command(unsigned int writecnt, unsigned int readcnt, const unsigned char *writearr, unsigned char *readarr) { - static unsigned char *buf = NULL; int i = 0, ret = 0; if (writecnt > 16 || readcnt > 16 || (readcnt + writecnt) > 16) return SPI_INVALID_LENGTH; /* 3 bytes extra for CS#, len, CS#. */ - buf = realloc(buf, writecnt + readcnt + 3); - if (!buf) { - msg_perr("Out of memory!\n"); - exit(1); // -1 - } + if (buspirate_commbuf_resize(writecnt + readcnt + 3)) + return OOM_ERROR; /* Assert CS# */ - buf[i++] = 0x02; + bp_commbuf[i++] = 0x02; - buf[i++] = 0x10 | (writecnt + readcnt - 1); - memcpy(buf + i, writearr, writecnt); + bp_commbuf[i++] = 0x10 | (writecnt + readcnt - 1); + memcpy(bp_commbuf + i, writearr, writecnt); i += writecnt; - memset(buf + i, 0, readcnt); + memset(bp_commbuf + i, 0, readcnt); i += readcnt; /* De-assert CS# */ - buf[i++] = 0x03; + bp_commbuf[i++] = 0x03; - ret = buspirate_sendrecv(buf, i, i); + ret = buspirate_sendrecv(bp_commbuf, i, i); if (ret) { msg_perr("Bus Pirate communication error!\n"); return SPI_GENERIC_ERROR; } - if (buf[0] != 0x01) { + if (bp_commbuf[0] != 0x01) { msg_perr("Protocol error while lowering CS#!\n"); return SPI_GENERIC_ERROR; } - if (buf[1] != 0x01) { + if (bp_commbuf[1] != 0x01) { msg_perr("Protocol error while reading/writing SPI!\n"); return SPI_GENERIC_ERROR; } - if (buf[i - 1] != 0x01) { + if (bp_commbuf[i - 1] != 0x01) { msg_perr("Protocol error while raising CS#!\n"); return SPI_GENERIC_ERROR; } /* Skip CS#, length, writearr. */ - memcpy(readarr, buf + 2 + writecnt, readcnt); + memcpy(readarr, bp_commbuf + 2 + writecnt, readcnt); return ret; } -- http://www.hailfinger.org/

2 5

Using flashrom with Intel Ibex Peak (PCH 3420) amd M25P64 flash works
by Gary Hannon 08 Jun '12

08 Jun '12

Great tool. I found this after lunch and had it working and verified by 3:30. Attached are the Verbose output dumps that you were hoping to get on new arch's. I was able to read, erase, program and verify the flash. We will soon have a board that uses 2 flashes, each 64Mb. I will also send feedback of what that looks like. Can this tool specify which chip select to use when writing, or do I need to create a map? We will have the descriptors in each flash calling the other flash as the Platform Data region. Our board has a way to steer which chip gets CS0 and which gets CS1 for having a failover incase a BIOS setting makes the board unbootable. Thanks much Gary Hannon Sr. Software Engineer CSP Inc. 43 Manning Road Billerica, MA 01821 978-663-7598 x1509 ghannon(a)cspi.com

2 3

Re: [flashrom] [PATCH] Add logfile support to flashrom
by Carl-Daniel Hailfinger 05 Jun '12

05 Jun '12

Am 08.05.2012 19:48 schrieb Idwer Vollering: > 2012/5/3 Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net>: >> I have decided to discard most of the logging code and rewrite it to be >> more readable. It even worked in preliminary tests. >> TODO: >> - Should "-o -" be a no-op which just redirects stderr to stdout? Right >> now "-" is treated as regular file name, but most Unix utilities are >> unable to handle a file with that name (try "less -" for amusement). > Is this a part of your long-term plan? Some people might want all messages (even error messages) to end up on stdout, but the more I think about it, the less I believe supporting - as placeholder for stdout makes sense. One of the biggest problems with that idea is that most messages would appear twice on screen, and that's just stupid. Unless someone objects, I'll remove this point from the TODO list. >> - Add man page entry >> - Is the log level difference for screen/logfile a good thing, and >> should we default the logfile level to dbg2 instead of dbg? >> >> Add log file support to flashrom. >> >> If you use cli_classic, the log file will always contain messages at >> a level which is one higher than the one specified. That way we get >> all verbose messages in the log even if the user doesn't specify -V. > This handles -VV and -VVV too, correct? Yes. If a user specifies -VV, the log file will get -VVV output, but the on-screen info will stay manageable. Not sure how we should handle it when the user specifies -VVV... for now, that would set msglevel to 5 (outside the defined range of the enum, but handled implicitly by the code like msglevel 4). We could make the log file always store logs at least at level -VV (to get all dbg2 output) regardless of whether -V was specified or not, and only if -VV or greater was specified, add 1 to the loglevel. What do you think? >> Convert all printf() after start of logging to msg_*(). >> >> Allow separate control of log level for screen and logfile in case >> other frontends (e.g. GUI, cli_mfg) want that. >> >> Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> >> >> Index: flashrom-logfile/flash.h >> =================================================================== >> --- flashrom-logfile/flash.h (Revision 1528) >> +++ flashrom-logfile/flash.h (Arbeitskopie) >> @@ -268,13 +269,20 @@ >> #define ERROR_FLASHROM_LIMIT -201 >> >> /* cli_output.c */ >> +#ifndef STANDALONE >> +int open_logfile(const char * const filename); >> +int close_logfile(void); >> +void start_logging(void); >> +#endif >> /* Let gcc and clang check for correct printf-style format strings. */ >> -int print(int type, const char *fmt, ...) __attribute__((format(printf, 2, 3))); >> -#define MSG_ERROR 0 >> -#define MSG_INFO 1 >> -#define MSG_DEBUG 2 >> -#define MSG_DEBUG2 3 > http://review.coreboot.org/gitweb?p=coreboot.git;a=blob;f=src/include/conso… I think the coreboot loglevels have nice names, but coreboot has too many loglevels for an application like flashrom. > #define MSG_NOTICE 2 > #define MSG_DEBUG 3 > >> -#define MSG_BARF 4 > #define MSG_SPEW 4 BARF->SPEW changed everywhere. >> +enum msglevel { >> + MSG_ERROR = 0, >> + MSG_INFO = 1, >> + MSG_DEBUG = 2, >> + MSG_DEBUG2 = 3, >> + MSG_BARF = 4, >> +}; >> +int print(enum msglevel level, const char *fmt, ...) __attribute__((format(printf, 2, 3))); >> #define msg_gerr(...) print(MSG_ERROR, __VA_ARGS__) /* general errors */ >> #define msg_perr(...) print(MSG_ERROR, __VA_ARGS__) /* programmer errors */ >> #define msg_cerr(...) print(MSG_ERROR, __VA_ARGS__) /* chip errors */ >> Index: flashrom-logfile/cli_output.c >> =================================================================== >> --- flashrom-logfile/cli_output.c (Revision 1528) >> +++ flashrom-logfile/cli_output.c (Arbeitskopie) >> @@ -20,36 +21,80 @@ >> >> #include <stdio.h> >> #include <stdarg.h> >> +#include <string.h> >> +#include <errno.h> >> #include "flash.h" >> >> -int print(int type, const char *fmt, ...) >> +static FILE *logfile = NULL; >> + >> +#ifndef STANDALONE >> +int close_logfile(void) >> { >> + if (logfile && fclose(logfile)) { > No sync() / fsync() ? > From http://linux.die.net/man/3/fclose "Note that fclose() only > flushes the user space buffers provided by the C library. To ensure > that the data is physically stored on disk the kernel buffers must be > flushed too, for example, with sync(2) or fsync(2)." Good point, will do. I'll probably have to change the file open mode as well... Uwe mentioned that "wb" is needed for Windows to behave sanely. >> + /* fclose returned an error. Stop writing to be safe. */ >> + logfile = NULL; >> + msg_perr("Closing the log file returned error %s\n", >> + strerror(errno)); >> + return 1; >> + } >> + logfile = NULL; >> + return 0; >> +} >> + >> Index: flashrom-logfile/cli_classic.c >> =================================================================== >> --- flashrom-logfile/cli_classic.c (Revision 1528) >> +++ flashrom-logfile/cli_classic.c (Arbeitskopie) >> @@ -377,20 +394,40 @@ >> cli_classic_abort_usage(); >> } >> >> - /* FIXME: Print the actions flashrom will take. */ >> - >> - if (list_supported) { >> - print_supported(); >> - exit(0); >> + if ((read_it | write_it | verify_it) && !filename) { >> + fprintf(stderr, "Error: No filename specified.\n"); > "No log filename specified.\n" ? No, if anything, it should be "No image filename specified". Thoughts? >> + cli_classic_abort_usage(); >> } >> + if (filename && (filename[0] == '\0')) { >> + fprintf(stderr, "Error: No filename specified.\n"); > dito dito. >> + cli_classic_abort_usage(); >> + } >> + if (filename && (filename[0] == '-')) >> + fprintf(stderr, "Warning: Supplied file name starts with -\n"); >> >> +#ifndef STANDALONE >> + if (log_name && (log_name[0] == '-')) >> + fprintf(stderr, "Warning: Supplied file name starts with -\n"); >> + if (log_name && open_logfile(log_name)) > WARNING or Warning? Maybe add a line that says that this will change > in the future? I'd say "Warning" it totally OK... it's an indicator that the user did something unintended, but it's not an error per se. >> + return 1; >> +#endif /* !STANDALONE */ >> + >> Regards, Carl-Daniel -- http://www.hailfinger.org/

3 7

Re: [flashrom] external programmer
by Bicks Factory 01 Jun '12

01 Jun '12

Hey thanks for taking time to help out. So I went and got a copy of debian os to try. I installed it but had too many problems with network cards not being detected and getting root privlages etc. That was a waste of a cd. So I went to ubuntu 12.04. Installed on hard drive and couldnt get flashrom to install at all. Changed the server location were ubuntu was looking for flashrom from CAN site to default server. Worked. So now I have ubuntu installed with flashrom. I checked and libftdi is installed aswell. Unfortunately I get the same problem. Cant detect/see my external programmer. I am hoping someone that has got this thing to work can add some usefull instructions on how they got this to work. Thanks again. I hope Im responding in the right manner. Not sure if this is going to a personal email or if this is going to the mailing list. Sent From Android Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> wrote: On Thu, 24 May 2012 22:04:50 -0400 Bicks Factory <newforest333(a)hotmail.ca> wrote: > > > Trying to use an external programmer, specifically the > TIAO/DIYGADGET USB Multi-Protocol Adapter (TUMPA). > Running from a live cd of parted magic. Using flashrom v0.9.5.2-r1515. > Run command: flashrom -p ft2232_spi:type=tumpa > get back: unknown programmer ft2232_spi:type=tumpa. > Motherboard is a MSI G41M-F. > Flashrom can see the flash chip on the board. Intel ich7 > Not really used to using command prompt or linux. > I'm assuming I'm missing some usb drivers. > > > Any help would be greatly appreciated. hello! that's not your fault (and admittedly the error message could be a bit better). the problem seems to be that flashrom was compiled without support for the ft2232_spi programmer in parted magic to safe space. so you need to get another live cd or build flashrom yourself (not really recommended when you dont know linux and the command line :) i am not aware of any live cd that ships a full build of flashrom (i was not aware yet, that they actually strip them down. it is not the default to do so, so they did it on consciously). the livecds of the bigger distributions such as ubuntu should be able to install packages after boot, which is necessary because flashrom is not added to the cds themselves and they should be the complete version. this requires either internet access after boot or some manual preparation though... hth -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 3

[PATCH] remove exit call from show_id
by Niklas Söderlund 30 May '12

30 May '12

The only caller is able to check the return code and handle it correctly --- flashrom.c | 5 ++++- layout.c | 2 +- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/flashrom.c b/flashrom.c index ec8137b..f6597e5 100644 --- a/flashrom.c +++ b/flashrom.c @@ -1781,7 +1781,10 @@ int doit(struct flashctx *flash, int force, const char *filename, int read_it, #if CONFIG_INTERNAL == 1 if (programmer == PROGRAMMER_INTERNAL) - show_id(newcontents, size, force); + if (show_id(newcontents, size, force)) { + ret = 1; + goto out; + } #endif } diff --git a/layout.c b/layout.c index 379ee8c..0512638 100644 --- a/layout.c +++ b/layout.c @@ -137,7 +137,7 @@ int show_id(uint8_t *bios, int size, int force) "\n\n", mainboard_vendor, mainboard_part, lb_vendor, lb_part); - exit(1); + return 1; } } -- 1.7.10.2

2 2

[PATCH] remove exit call from internal_init
by Niklas Söderlund 30 May '12

30 May '12

Replace with a return instead, all other plumbing is already in place Signed-off-by: Niklas Söderlund <niso(a)kth.se> --- internal.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/internal.c b/internal.c index 5b24577..75e526b 100644 --- a/internal.c +++ b/internal.c @@ -298,7 +298,7 @@ int internal_init(void) msg_perr("Proceeding anyway because user forced us to.\n"); } else { msg_perr("Aborting.\n"); - exit(1); + return 1; } } -- 1.7.10.2

2 1

Gigabyte 8iPE1000 rev 1.x
by Darío García Martos 26 May '12

26 May '12

Dear developers, I have this motherboard: GA-8IPE1000 (rev. 1.x) <http://www.gigabyte.com/products/product-page.aspx?pid=1647&dl=1#bios> with version FB of the BIOS, and tried to upgrade BIOS firmware with your software, and here is the results: usuario@pentium4ht:~/temporal$ sudo /usr/sbin/flashrom -w 8ipe1000.f12 flashrom v0.9.5.2-r1517 on Linux 3.2.0-24-generic-pae (i686), built with libpci 3.1.8, GCC 4.6.3, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "Intel ICH5/ICH5R". Enabling flash write... OK. Found SST flash chip "SST49LF002A/B" (256 kB, FWH) at physical address 0xfffc0000. Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. Reading old flash chip contents... done. Erasing and writing flash chip... ERASE FAILED at 0x00000000! Expected=0xff, Read=0x23, failed byte count from 0x00000000-0x00000fff: 0xff0 ERASE FAILED! Reading current flash chip contents... done. ERASE FAILED at 0x00000000! Expected=0xff, Read=0x23, failed byte count from 0x00000000-0x00003fff: 0x3fb9 ERASE FAILED! FAILED! Uh oh. Erase/write failed. Checking if anything changed. Good. It seems nothing was changed. Writing to the flash chip apparently didn't do anything. This means we have to add special support for your board, programmer or flash chip. Please report this on IRC at irc.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org! ------------------------------------------------------------------------------- You may now reboot or simply leave the machine running. usuario@pentium4ht:~/temporal$ I attached the output of lshw. Thanks a lot.

2 3

Re: [flashrom] Intel Q67 read failed
by Stefan Tauner 25 May '12

25 May '12

On Tue, 22 May 2012 08:15:04 +0000 Schollerer Michael <MichaelSchollerer(a)kuka-roboter.de> wrote: > It would be great to get it working, because I really need a bios update! Thanks for your support. hello michael, locked down intel-based boards wont be supported in the foreseeable future, sorry. please use the vendor tool if possible. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

← Newer
1
2
3
4
5
6
7
8
...
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom May 2012