flashrom December 2015

flashrom@flashrom.org

32 participants
71 discussions

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

11 Dec '15

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

2 1

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

11 Dec '15

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

1 0

W836xx:HP DL145 G3
by Jeff 09 Dec '15

09 Dec '15

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

1 0

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

06 Dec '15

# sudo flashrom -V -p internal flashrom v0.9.8-r1888 on Linux 4.2.5-1-ARCH (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.3.0, GCC 4.9.2 20150204 (prerelease), little endian Command line (3 args): flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 2658M loops per second, 10 myus = 10 us, 100 myus = 125 us, 1000 myus = 1012 us, 10000 myus = 9948 us, 4 myus = 15 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Portable" Laptop detected via DMI. DMI string system-manufacturer: "Dell Inc. " DMI string system-product-name: "Inspiron 7437" DMI string system-version: "Not Specified" DMI string baseboard-manufacturer: "Dell Inc. " DMI string baseboard-product-name: " " DMI string baseboard-version: " " W836xx enter config mode worked or we were already in config mode. W836xx leave config mode had no effect. Active config mode, unknown reg 0x20 ID: fc. Please send the output of "flashrom -V -p internal" to flashrom(a)flashrom.org with W836xx: your board name: flashrom -V as the subject to help us finish support for your Super I/O. Thanks. ======================================================================== WARNING! You seem to be running flashrom on an unsupported laptop. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and http://www.flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== Aborting. Error: Programmer initialization failed.

1 0

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

06 Dec '15

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

1 0

Question - Help
by Neb Radojkovic 05 Dec '15

05 Dec '15

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

1 0

W836xx: your board name: flashrom -V
by Mohit Keswani 05 Dec '15

05 Dec '15

Output for flashrom attached. Please support my board. I;ve bought the latest lenovo y700.

1 0

Re: [flashrom] Ch431 programmer
by Stefan Tauner 04 Dec '15

04 Dec '15

On Tue, 1 Dec 2015 09:25:46 +0200 Ran Weizman <ranwzmn(a)gmail.com> wrote: > Hi > Thanks a lot, unfortunately my chip model is not supported by Flashrom. And that won't change if you don't tell us what model it is :) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 2

[PATCH 0/1] Add support for reading the current flash contents from a file
by Paul Kocialkowski 04 Dec '15

04 Dec '15

Here is an example script that I'm using to read the flash contents to a file once and update it as I flash newer versions of the software: #!/bin/sh flashrom="flashrom" programmer="ft2232_spi:type=openmoko,divisor=8" contents="~/flash-contents.img" image="$1" if [ -z $image ] then echo "Reading initial flash contents" timeb=$( date +%s ) $flashrom -p $programmer -r $contents timea=$( date +%s ) echo "Time: "$(( $timea - $timeb ))" seconds" else echo "Writing new flash contents" timeb=$( date +%s ) $flashrom -p $programmer -w $image -C $contents --noverify timea=$( date +%s ) cp $image $contents echo "Time: "$(( $timea - $timeb ))" seconds" fi

1 1

[PATCH v3 1/2] Add support for selecting the erased bit value with a flag
by Paul Kocialkowski 03 Dec '15

03 Dec '15

Most flash chips are erased to ones and programmed to zeros. However, some other flash chips, such as the ENE KB9012 internal flash, work the opposite way. Signed-off-by: Paul Kocialkowski <contact(a)paulk.fr> --- flash.h | 5 ++++- flashrom.c | 39 +++++++++++++++++++++------------------ 2 files changed, 25 insertions(+), 19 deletions(-) diff --git a/flash.h b/flash.h index 24861ba..8d557fe 100644 --- a/flash.h +++ b/flash.h @@ -123,6 +123,9 @@ enum write_granularity { #define FEATURE_WRSR_EITHER (FEATURE_WRSR_EWSR | FEATURE_WRSR_WREN) #define FEATURE_OTP (1 << 8) #define FEATURE_QPI (1 << 9) +#define FEATURE_ERASED_ZERO (1 << 10) + +#define ERASED_VALUE(flash) (((flash)->chip->feature_bits & FEATURE_ERASED_ZERO) ? 0x00 : 0xff) enum test_state { OK = 0, @@ -275,7 +278,7 @@ int probe_flash(struct registered_master *mst, int startchip, struct flashctx *f int read_flash_to_file(struct flashctx *flash, const char *filename); char *extract_param(const char *const *haystack, const char *needle, const char *delim); int verify_range(struct flashctx *flash, const uint8_t *cmpbuf, unsigned int start, unsigned int len); -int need_erase(const uint8_t *have, const uint8_t *want, unsigned int len, enum write_granularity gran); +int need_erase(const uint8_t *have, const uint8_t *want, unsigned int len, enum write_granularity gran, const uint8_t erased_value); void print_version(void); void print_buildinfo(void); void print_banner(void); diff --git a/flashrom.c b/flashrom.c index c9c7e31..bd8ef3f 100644 --- a/flashrom.c +++ b/flashrom.c @@ -673,12 +673,13 @@ int check_erased_range(struct flashctx *flash, unsigned int start, { int ret; uint8_t *cmpbuf = malloc(len); + const uint8_t erased_value = ERASED_VALUE(flash); if (!cmpbuf) { msg_gerr("Could not allocate memory!\n"); exit(1); } - memset(cmpbuf, 0xff, len); + memset(cmpbuf, erased_value, len); ret = verify_range(flash, cmpbuf, start, len); free(cmpbuf); return ret; @@ -731,7 +732,7 @@ out_free: } /* Helper function for need_erase() that focuses on granularities of gran bytes. */ -static int need_erase_gran_bytes(const uint8_t *have, const uint8_t *want, unsigned int len, unsigned int gran) +static int need_erase_gran_bytes(const uint8_t *have, const uint8_t *want, unsigned int len, unsigned int gran, const uint8_t erased_value) { unsigned int i, j, limit; for (j = 0; j < len / gran; j++) { @@ -741,7 +742,7 @@ static int need_erase_gran_bytes(const uint8_t *have, const uint8_t *want, unsig continue; /* have needs to be in erased state. */ for (i = 0; i < limit; i++) - if (have[j * gran + i] != 0xff) + if (have[j * gran + i] != erased_value) return 1; } return 0; @@ -761,7 +762,7 @@ static int need_erase_gran_bytes(const uint8_t *have, const uint8_t *want, unsig * @gran write granularity (enum, not count) * @return 0 if no erase is needed, 1 otherwise */ -int need_erase(const uint8_t *have, const uint8_t *want, unsigned int len, enum write_granularity gran) +int need_erase(const uint8_t *have, const uint8_t *want, unsigned int len, enum write_granularity gran, const uint8_t erased_value) { int result = 0; unsigned int i; @@ -776,31 +777,31 @@ int need_erase(const uint8_t *have, const uint8_t *want, unsigned int len, enum break; case write_gran_1byte: for (i = 0; i < len; i++) - if ((have[i] != want[i]) && (have[i] != 0xff)) { + if ((have[i] != want[i]) && (have[i] != erased_value)) { result = 1; break; } break; case write_gran_128bytes: - result = need_erase_gran_bytes(have, want, len, 128); + result = need_erase_gran_bytes(have, want, len, 128, erased_value); break; case write_gran_256bytes: - result = need_erase_gran_bytes(have, want, len, 256); + result = need_erase_gran_bytes(have, want, len, 256, erased_value); break; case write_gran_264bytes: - result = need_erase_gran_bytes(have, want, len, 264); + result = need_erase_gran_bytes(have, want, len, 264, erased_value); break; case write_gran_512bytes: - result = need_erase_gran_bytes(have, want, len, 512); + result = need_erase_gran_bytes(have, want, len, 512, erased_value); break; case write_gran_528bytes: - result = need_erase_gran_bytes(have, want, len, 528); + result = need_erase_gran_bytes(have, want, len, 528, erased_value); break; case write_gran_1024bytes: - result = need_erase_gran_bytes(have, want, len, 1024); + result = need_erase_gran_bytes(have, want, len, 1024, erased_value); break; case write_gran_1056bytes: - result = need_erase_gran_bytes(have, want, len, 1056); + result = need_erase_gran_bytes(have, want, len, 1056, erased_value); break; case write_gran_1byte_implicit_erase: /* Do not erase, handle content changes from anything->0xff by writing 0xff. */ @@ -1424,6 +1425,7 @@ static int erase_and_write_block_helper(struct flashctx *flash, unsigned int starthere = 0, lenhere = 0; int ret = 0, skip = 1, writecount = 0; enum write_granularity gran = flash->chip->gran; + const uint8_t erased_value = ERASED_VALUE(flash); /* curcontents and newcontents are opaque to walk_eraseregions, and * need to be adjusted here to keep the impression of proper abstraction @@ -1431,7 +1433,7 @@ static int erase_and_write_block_helper(struct flashctx *flash, curcontents += start; newcontents += start; msg_cdbg(":"); - if (need_erase(curcontents, newcontents, len, gran)) { + if (need_erase(curcontents, newcontents, len, gran, erased_value)) { msg_cdbg("E"); ret = erasefn(flash, start, len); if (ret) @@ -1441,7 +1443,7 @@ static int erase_and_write_block_helper(struct flashctx *flash, return -1; } /* Erase was successful. Adjust curcontents. */ - memset(curcontents, 0xff, len); + memset(curcontents, erased_value, len); skip = 0; } /* get_next_write() sets starthere to a new value after the call. */ @@ -1938,6 +1940,7 @@ int doit(struct flashctx *flash, int force, const char *filename, int read_it, int ret = 0; unsigned long size = flash->chip->total_size * 1024; int read_all_first = 1; /* FIXME: Make this configurable. */ + const uint8_t erased_value = ERASED_VALUE(flash); if (chip_safety_check(flash, force, read_it, write_it, erase_it, verify_it)) { msg_cerr("Aborting.\n"); @@ -1964,15 +1967,15 @@ int doit(struct flashctx *flash, int force, const char *filename, int read_it, msg_gerr("Out of memory!\n"); exit(1); } - /* Assume worst case: All bits are 0. */ - memset(oldcontents, 0x00, size); + /* Assume worst case: All bits are not erased. */ + memset(oldcontents, ~erased_value, size); newcontents = malloc(size); if (!newcontents) { msg_gerr("Out of memory!\n"); exit(1); } - /* Assume best case: All bits should be 1. */ - memset(newcontents, 0xff, size); + /* Assume best case: All bits should be erased. */ + memset(newcontents, erased_value, size); /* Side effect of the assumptions above: Default write action is erase * because newcontents looks like a completely erased chip, and * oldcontents being completely 0x00 means we have to erase everything -- 1.9.1

2 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom December 2015