flashrom

flashrom@flashrom.org

1 participants
9168 discussions

Re: [flashrom] ASUS C60M1-I Write Success
by Stefan Tauner 15 Mar '13

15 Mar '13

On Mon, 25 Feb 2013 17:42:18 -0500 Justin Chevrier <jchevrier(a)gmail.com> wrote: > Hey Guys, > > Another report; this one successful going from BIOS 0205 to 0305. > Executed an erase before writing the new BIOS. Original MAC address of > the onboard LAN adapter was lost after upgrade. > > Justin Hello Justin, thanks for your report! I have added your board to our list of supported hardware and will commit that later together with other small changes. Do you … [View More]

1 0

P8Z68-V LE log
by blondquirk 15 Mar '13

15 Mar '13

2 1

Re: [flashrom] M29W512B write operation verified on 3C905C/TX
by Stefan Tauner 14 Mar '13

14 Mar '13

On Fri, 15 Mar 2013 03:24:17 +0800 Lu Xie <lxie1(a)andrew.cmu.edu> wrote: > Dear Stefan, > > I did another flash and this time there is no "S" after the address range. OK, thanks. The status page will be updated in a few weeks/months depending on how many other reports we get. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] M29W512B write operation verified on 3C905C/TX
by Stefan Tauner 14 Mar '13

14 Mar '13

On Tue, 5 Mar 2013 08:36:41 +0800 Lu Xie <lxie1(a)andrew.cmu.edu> wrote: > I am pretty sure my customized image was written into the rom. I flashed > the same image again after I saw the request of using "-v" parameter and > decided to pipe the output to a file. We have added an --output option to write output directly to a file BTW. > The adapter was shipped with MBA/PXE boot rom and I have flashed it with > plop boot manager. The manager is now fully functional so I … [View More]

2 1

Re: [flashrom] [coreboot] IMC on persimmon (was: Flashrom erase failure)
by Stefan Tauner 14 Mar '13

14 Mar '13

On Mon, 4 Mar 2013 09:42:43 +0100 Wolfgang Kamp - datakamp <wmkamp(a)datakamp.de> wrote: > Hi, > > recently I had the same problems to get Flashrom working on an embedded platform with AMD G-series processor similar to Persimmon. > I did all the patches to get Flashrom working but actually I'm not able to commit to flashrom.org. > If there is interest I would send the necessary files to someone who can do that for me. Hello Wolfgang, you can/should send any flashrom-… [View More]

2 2

Re: [flashrom] [PATCH 2/4] Add granularity handling for AT45DB series.
by Carl-Daniel Hailfinger 14 Mar '13

14 Mar '13

Am 03.03.2013 23:57 schrieb Stefan Tauner: > Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> > --- > flash.h | 2 ++ > flashrom.c | 38 +++++++++++++++++++++++--------------- > 2 files changed, 25 insertions(+), 15 deletions(-) > > diff --git a/flash.h b/flash.h > index 7dd9d9f..1df43c4 100644 > --- a/flash.h > +++ b/flash.h > @@ -66,11 +66,13 @@ enum chipbustype { > * - 128 bytes: If less than 128 bytes are written, the … [View More]rest will be erased. Each write to a 128-byte region > * will trigger an automatic erase before anything is written. Very uncommon behaviour. > * - 256 bytes: If less than 256 bytes are written, the contents of the unwritten bytes are undefined. > + * - 264 bytes: FIXME Just copy the comment from 256 bytes. If that isn't completely correct, maybe this would fit: "If less than 264 bytes are written, the contents of all bytes of the write operation are undefined." AFAICS my text is inaccurate for Dataflash, though. > */ > enum write_granularity { > write_gran_256bytes = 0, /* We assume 256 byte granularity on default. */ > write_gran_1bit, > write_gran_1byte, > + write_gran_264bytes, Should we reverse the order of the values in that enum to have an ordering by size? > }; > > /* > diff --git a/flashrom.c b/flashrom.c > index 225b6f0..fc5e34a 100644 > --- a/flashrom.c > +++ b/flashrom.c > @@ -676,6 +676,21 @@ out_free: > return ret; > } > > +static int need_erase_n_byte(uint8_t *have, uint8_t *want, unsigned int len, unsigned int n) Different name for the function maybe? Not sure, it doesn't sound too bad. > +{ > + unsigned int i, j, limit; > + for (j = 0; j < len / n; j++) { > + limit = min (n, len - j * n); > + /* Are 'have' and 'want' identical? */ > + if (!memcmp(have + j * n, want + j * n, limit)) > + continue; > + /* have needs to be in erased state. */ > + for (i = 0; i < limit; i++) > + if (have[j * n + i] != 0xff) > + return 1; > + } > + return 0; > +} > /* > * Check if the buffer @have can be programmed to the content of @want without > * erasing. This is only possible if all chunks of size @gran are either kept > @@ -693,7 +708,7 @@ out_free: > int need_erase(uint8_t *have, uint8_t *want, unsigned int len, enum write_granularity gran) > { > int result = 0; > - unsigned int i, j, limit; > + unsigned int i; > > switch (gran) { > case write_gran_1bit: > @@ -711,20 +726,10 @@ int need_erase(uint8_t *have, uint8_t *want, unsigned int len, enum write_granul > } > break; > case write_gran_256bytes: > - for (j = 0; j < len / 256; j++) { > - limit = min (256, len - j * 256); > - /* Are 'have' and 'want' identical? */ > - if (!memcmp(have + j * 256, want + j * 256, limit)) > - continue; > - /* have needs to be in erased state. */ > - for (i = 0; i < limit; i++) > - if (have[j * 256 + i] != 0xff) { > - result = 1; > - break; > - } > - if (result) > - break; > - } > + result = need_erase_n_byte(have, want, len, 256); > + break; > + case write_gran_264bytes: > + result = need_erase_n_byte(have, want, len, 264); The refactoring of that code is a really good idea. > break; > default: > msg_cerr("%s: Unsupported granularity! Please report a bug at " > @@ -772,6 +777,9 @@ static unsigned int get_next_write(uint8_t *have, uint8_t *want, unsigned int le > case write_gran_256bytes: > stride = 256; > break; > + case write_gran_264bytes: > + stride = 264; > + break; > default: > msg_cerr("%s: Unsupported granularity! Please report a bug at " > "flashrom(a)flashrom.org\n", __func__); Overall, I like it. Regards, Carl-Daniel -- http://www.hailfinger.org/ [View Less]

2 1

Re: [flashrom] Intel C602 support
by Stefan Tauner 13 Mar '13

13 Mar '13

On Wed, 13 Mar 2013 13:15:32 +0000 Greg Schardt <gschardt(a)ddn.com> wrote: > I have modified the flashrom code to allow reads and writes to unprotected regions to occur, but am still blocked by having the ME region locked. Do you have any idea how the AFUDOS utility is able to modify the Management Engine region even though it should be locked? I would have thought that the Region Access Control settings would be in effect once the BIOS finished booting, before DOS could start. … [View More]

2 1

testing DELL Dimension 4100
by Bertho Grandpied 13 Mar '13

13 Mar '13

Testing Dell Dimension 4100 : Pentium III and Intel 815 (82815 + 82801BA, ICH2) based desktop machine from ca yr 2000. This chipset should be supported IIUC, but flash chip is not detected :( Flashrom was run under MS-DOS (log appended) - notice how I had to specify the "not-a-laptop" override because of insufficient DMI tables. Please notice also the "warning" about being unable to set Bios Control at 0x4e : thus the question arises, is that Intel chipset variant supported or is it not ? … [View More]Additionally I ran 'Linux/sensors-detct' FWIW : "probing for Super-I/O at 0x2e/2f", "SMSC LPC47M10x/112/13x" fan sensors were found. Any further software probe I can try before opening up the box in the hope of finding what BIOS chip was used by visual inspection ? Regards... __________________________________________________________________ flashrom v0.9.6.1-r1624 on MS-DOS 7 (i686) flashrom was built with libpci 3.1.5, GCC 4.4.4, little endian Command line (7 args): c:/flashrom/flashrom.exe -p internal:laptop=this_is_not_a_laptop -V -r DELL.BIN -o READ.LOG Calibrating delay loop... OS timer resolution is 50000 usecs, 486M loops per second, 10 myus = 0 us, 100 myus = 0 us, 1000 myus = 0 us, 10000 myus = 0 us, 200000 myus = 270000 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "Dell Computer Corporation " DMI string system-product-name: "XPS-Z " DMI string system-version: " " DMI string baseboard-manufacturer: "Intel Corporation " DMI string baseboard-product-name: "D815EEA " DMI string baseboard-version: "AAA10383-402 " DMI string chassis-type: "Unknown" DMI chassis-type is not specific enough. ======================================================================== WARNING! You may be running flashrom on an unsupported laptop.(....) You have been warned. ======================================================================== Proceeding anyway because user forced us to. Found chipset "Intel ICH2" with PCI ID 8086:2440. Enabling flash write... BIOS_CNTL = 0x02: BIOS Lock Enable: enabled, BIOS Write Enable: disabled WARNING: Setting Bios Control at 0x4e from 0x02 to 0x03 on ICH2 failed. New value is 0x02. FAILED! The following protocols are supported: FWH. Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x93, id2 0x26, 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 PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0x93, id2 0x26, 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 LHF00L04, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x93, id2 0x26, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xb2, id2 0xf1, 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 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 0x93, id2 0x26, 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 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 W49V002FA, 256 kB: probe_jedec_common: id1 0x93, id2 0x26, 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:1f:0 reg 0x4e _________________________________________________________________ -- Czerno [View Less]

3 11

Re: [flashrom] Hello ! ERASE FAILED ASUS P5VD2-MX SE
by Idwer Vollering 13 Mar '13

13 Mar '13

2013/3/13 Rémi charest <remicharest(a)gmail.com>: > Hello it seems my motherboard isn't really supported... Can you add > support for my board please ? Certainly.. run and attach the output of 'lspci -nnvvvxxx' (as root). Beware that writing, when a board enable is applied, trashes the LOM MAC address: http://www.flashrom.org/pipermail/flashrom/2012-March/009017.html > I'm wiLling to help if i can (linux noob here). > > Thanks ! > > I DID: flashrom -p internal -w … [View More]

1 0

Re: [flashrom] Intel C602 support
by Stefan Tauner 13 Mar '13

13 Mar '13

On Mon, 6 Aug 2012 12:07:47 -0700 Greg Schardt <gschardt(a)ddn.com> wrote: > Can you explain why doing a read operation failed? I expected that reads would work and writes would fail. each region can have 4 different access states: read/write, read-only, write-only (never seen in practice), locked (neither read nor write allowed) (see FREG in the public datasheets for any newer intel southbridge >ICH8). flashrom disables writes by default if it detects locked or read-only regions … [View More]

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom