flashrom December 2012

flashrom@flashrom.org

33 participants
119 discussions

Re: [flashrom] [PATCH 1/3] Refactor PCI and USB device status printing.
by Carl-Daniel Hailfinger 12 Dec '12

12 Dec '12

Am 17.11.2012 20:09 schrieb Stefan Tauner: > To be able to get rid of lots of #ifdefs and centralize programmer-specific > data more... > - introduce two new fields to struct programmer_entry, namely > enum type (OTHER, USB, PCI) and union devices (pcidev_status, usbdev_status > or char *note). > - use those fields to generate device listings in print.c and print_wiki.c. > > Bonus: add printing of USB devices to print_wiki.c and count supported PCI > and USB devices. > > Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Good idea. I have a few comments, otherwise it looks OK. Note: I have not checked the wiki output, I only reviewed the code. I trust you have checked the wiki output for changes. > --- > flashrom.c | 48 ++++++++++++++++++- > ft2232_spi.c | 13 ------ > pcidev.c | 13 ------ > print.c | 148 +++++++++++++++++++--------------------------------------- > print_wiki.c | 141 ++++++++++++++++++++++++++++++++++--------------------- > programmer.h | 41 ++++++++++------ > 6 files changed, 211 insertions(+), 193 deletions(-) > > diff --git a/flashrom.c b/flashrom.c > index 2299b06..d873276 100644 > --- a/flashrom.c > +++ b/flashrom.c > @@ -64,6 +64,8 @@ const struct programmer_entry programmer_table[] = { > #if CONFIG_INTERNAL == 1 > { > .name = "internal", > + .type = OTHER, > + .devices.note = NULL, > .init = internal_init, > .map_flash_region = physmap, > .unmap_flash_region = physunmap, > @@ -84,6 +89,8 @@ const struct programmer_entry programmer_table[] = { > #if CONFIG_NIC3COM == 1 > { > .name = "nic3com", > + .type = PCI, > + .devices.pci = nics_3com, If we reference the device list here, can we kill the code in each programmer which mentions the device list explicitly and use pgm->devices->pci there? Otherwise there's a good chance someone will forget one or the other reference and wonder why --list and actual recognized programmer devices differ. > .init = nic3com_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -185,6 +212,9 @@ const struct programmer_entry programmer_table[] = { > #if CONFIG_DEDIPROG == 1 > { > .name = "dediprog", > + .type = OTHER, Regression. The old code lists all devices. > + /* FIXME */ > + .devices.note = "Dediprog SF100\n", > .init = dediprog_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > diff --git a/print.c b/print.c > index d7bdbfe..4b23ca0 100644 > --- a/print.c > +++ b/print.c > @@ -433,8 +433,32 @@ static void print_supported_boards_helper(const struct board_info *boards, > } > #endif > For consistency, we should introduce NEED_USB here. That would need Makefile glue, but I think it's worth it, especially now that there are Dediprog patches which change the libusb-0 dependency to a libusb-1 dependency. > +void print_supported_usbdevs(const struct usbdev_status *devs) > +{ > + int i; > + > + msg_pinfo("USB devices:\n"); > + for (i = 0; devs[i].vendor_name != NULL; i++) { > + msg_pinfo("%s %s [%04x:%04x]%s\n", devs[i].vendor_name, devs[i].device_name, devs[i].vendor_id, > + devs[i].device_id, (devs[i].status == NT) ? " (untested)" : ""); > + } > +} > + > +#if NEED_PCI == 1 > +void print_supported_pcidevs(const struct pcidev_status *devs) > +{ > + int i; > + > + for (i = 0; devs[i].vendor_name != NULL; i++) { > + msg_pinfo("%s %s [%04x:%04x]%s\n", devs[i].vendor_name, devs[i].device_name, devs[i].vendor_id, > + devs[i].device_id, (devs[i].status == NT) ? " (untested)" : ""); > + } > +} > +#endif > + > int print_supported(void) > { > + unsigned int i; > if (print_supported_chips()) > return 1; > > @@ -449,107 +473,31 @@ int print_supported(void) > msg_ginfo("\n"); > print_supported_boards_helper(laptops_known, "laptops"); > #endif > -#if CONFIG_DUMMY == 1 > - msg_ginfo("\nSupported devices for the %s programmer:\n", > - programmer_table[PROGRAMMER_DUMMY].name); > - /* FIXME */ > - msg_ginfo("Dummy device, does nothing and logs all accesses\n"); > -#endif > [...] > -#if CONFIG_LINUX_SPI == 1 > - msg_ginfo("\nSupported devices for the %s programmer:\n", > - programmer_table[PROGRAMMER_LINUX_SPI].name); > - msg_ginfo("Device files /dev/spidev*.*\n"); > + for (i = 0; i < PROGRAMMER_INVALID; i++) { > + const struct programmer_entry prog = programmer_table[i]; > + switch (prog.type) { NEED_USB again. > + case USB: > + msg_ginfo("\nSupported USB devices for the %s programmer:\n", prog.name); > + print_supported_usbdevs(prog.devices.usb); > + break; > +#if NEED_PCI == 1 > + case PCI: > + msg_ginfo("\nSupported PCI devices for the %s programmer:\n", prog.name); > + print_supported_pcidevs(prog.devices.pci); > + break; > #endif > + case OTHER: > + if (prog.devices.note == NULL) > + break; Interesting logic. I'm not saying it is wrong, but it's not immediately obvious that .note=NULL means the programmer won't be listed at all. I fear this might be forgotten by future programmer driver authors, but then again I should update my programmer code generation script and push it to svn so this won't be a problem in the future. > + msg_ginfo("\nSupported devices for the %s programmer:\n", prog.name); > + msg_ginfo("%s", prog.devices.note); > + break; > + default: > + msg_gerr("\n%s: %s: Uninitialized programmer type! Please report a bug at " > + "flashrom(a)flashrom.org\n", __func__, prog.name); > + break; > + } > + } > return 0; > } > > diff --git a/print_wiki.c b/print_wiki.c > index 617053c..17e2e85 100644 > --- a/print_wiki.c > +++ b/print_wiki.c > @@ -302,9 +298,18 @@ static void print_supported_chips_wiki(int cols) > printf("|}\n\n"); > } > > -/* Not needed for CONFIG_INTERNAL, but for all other PCI-based programmers. */ > -#if CONFIG_NIC3COM+CONFIG_NICREALTEK+CONFIG_NICNATSEMI+CONFIG_GFXNVIDIA+CONFIG_DRKAISER+CONFIG_SATASII+CONFIG_ATAHPT+CONFIG_NICINTEL+CONFIG_NICINTEL_SPI+CONFIG_OGP_SPI+CONFIG_SATAMV >= 1 > -static void print_supported_pcidevs_wiki(const struct pcidev_status *devs) > +/* Following functions are not needed when no PCI/USB programmers are compiled in, > + * but since print_wiki code has no size constraints we include it unconditionally. */ Heh. > +static int count_supported_pcidevs_wiki(const struct pcidev_status *devs) > +{ > + unsigned int count = 0; > + unsigned int i = 0; > + for (i = 0; devs[i].vendor_name != NULL; i++) AFAICS this should segfault in case a driver has prog.type=PCI and prog.devices.pci==NULL. Not a problem, but maybe we should catch this case (as well as the USB case) in a selftest function during startup? That would also help during programmer development. > + count++; > + return count; > +} > + > +static void print_supported_pcidevs_wiki_helper(const struct pcidev_status *devs) > { > int i = 0; > static int c = 0; > @@ -313,14 +318,81 @@ static void print_supported_pcidevs_wiki(const struct pcidev_status *devs) > c = !c; > > for (i = 0; devs[i].vendor_name != NULL; i++) { > - printf("|- bgcolor=\"#%s\"\n| %s || %s || " > - "%04x:%04x || {{%s}}\n", (c) ? "eeeeee" : "dddddd", > - devs[i].vendor_name, devs[i].device_name, > - devs[i].vendor_id, devs[i].device_id, > + printf("|- bgcolor=\"#%s\"\n| %s || %s || %04x:%04x || {{%s}}\n", (c) ? "eeeeee" : "dddddd", > + devs[i].vendor_name, devs[i].device_name, devs[i].vendor_id, devs[i].device_id, > (devs[i].status == NT) ? "?3" : "OK"); > } > } > -#endif > + > +static int count_supported_usbdevs_wiki(const struct usbdev_status *devs) > +{ > + unsigned int count = 0; > + unsigned int i = 0; > + for (i = 0; devs[i].vendor_name != NULL; i++) > + count++; > + return count; > +} > + > +static void print_supported_usbdevs_wiki_helper(const struct usbdev_status *devs) > +{ > + int i = 0; > + static int c = 0; > + > + /* Alternate colors if the vendor changes. */ > + c = !c; > + > + for (i = 0; devs[i].vendor_name != NULL; i++) { > + printf("|- bgcolor=\"#%s\"\n| %s || %s || %04x:%04x || {{%s}}\n", (c) ? "eeeeee" : "dddddd", > + devs[i].vendor_name, devs[i].device_name, devs[i].vendor_id, devs[i].device_id, > + (devs[i].status == NT) ? "?3" : "OK"); > + } > +} > + > +static void print_supported_devs_wiki() > +{ > + unsigned int pci_count = 0; > + unsigned int usb_count = 0; > + unsigned int i; > + > + for (i = 0; i < PROGRAMMER_INVALID; i++) { > + const struct programmer_entry prog = programmer_table[i]; > + switch (prog.type) { > + case USB: > + usb_count += count_supported_usbdevs_wiki(prog.devices.usb); > + break; > + case PCI: > + pci_count += count_supported_pcidevs_wiki(prog.devices.pci); > + break; > + case OTHER: > + default: > + break; > + } > + } > + > + printf("\n== PCI Devices ==\n\n" > + "Total amount of supported PCI devices flashrom can use as a programmer: '''%d'''\n\n" > + "{%s%s", pci_count, th_start, programmer_th); > + > + for (i = 0; i < PROGRAMMER_INVALID; i++) { > + const struct programmer_entry prog = programmer_table[i]; > + if (prog.type == PCI) { > + print_supported_pcidevs_wiki_helper(prog.devices.pci); > + } > + } > + printf("\n|}\n\n|}\n"); > + > + printf("\n== USB Devices ==\n\n" > + "Total amount of supported USB devices flashrom can use as a programmer: '''%d'''\n\n" > + "{%s%s", usb_count, th_start, programmer_th); > + > + for (i = 0; i < PROGRAMMER_INVALID; i++) { > + const struct programmer_entry prog = programmer_table[i]; > + if (prog.type == USB) { > + print_supported_usbdevs_wiki_helper(prog.devices.usb); > + } > + } > + printf("\n|}\n\n|}\n"); > +} > > void print_supported_wiki(void) > { > @@ -332,41 +404,6 @@ void print_supported_wiki(void) > print_supported_chipsets_wiki(3); > print_supported_boards_wiki(); > #endif > - printf("%s%s%s", programmer_intro, th_start, programmer_th); > - > -#if CONFIG_NIC3COM == 1 > - print_supported_pcidevs_wiki(nics_3com); > -#endif > -#if CONFIG_NICREALTEK == 1 > - print_supported_pcidevs_wiki(nics_realtek); > -#endif > -#if CONFIG_NICNATSEMI == 1 > - print_supported_pcidevs_wiki(nics_natsemi); > -#endif > -#if CONFIG_GFXNVIDIA == 1 > - print_supported_pcidevs_wiki(gfx_nvidia); > -#endif > -#if CONFIG_DRKAISER == 1 > - print_supported_pcidevs_wiki(drkaiser_pcidev); > -#endif > -#if CONFIG_SATASII == 1 > - print_supported_pcidevs_wiki(satas_sii); > -#endif > -#if CONFIG_ATAHPT == 1 > - print_supported_pcidevs_wiki(ata_hpt); > -#endif > -#if CONFIG_NICINTEL == 1 > - print_supported_pcidevs_wiki(nics_intel); > -#endif > -#if CONFIG_NICINTEL_SPI == 1 > - print_supported_pcidevs_wiki(nics_intel_spi); > -#endif > -#if CONFIG_OGP_SPI == 1 > - print_supported_pcidevs_wiki(ogp_spi); > -#endif > -#if CONFIG_SATAMV == 1 > - print_supported_pcidevs_wiki(satas_mv); > -#endif > - printf("\n|}\n\n|}\n"); > + print_supported_devs_wiki(); > } > > diff --git a/programmer.h b/programmer.h > index dedec67..21fa707 100644 > --- a/programmer.h > +++ b/programmer.h > @@ -90,9 +90,21 @@ enum programmer { > PROGRAMMER_INVALID /* This must always be the last entry. */ > }; > > +enum programmer_type { > + PCI = 1, /* to detect uninitialized values */ > + USB, > + OTHER, > +}; > + > struct programmer_entry { > const char *vendor; > const char *name; > + const enum programmer_type type; > + union { > + const struct pcidev_status *const pci; > + const struct usbdev_status *const usb; > + const char *const note; Neat! > + } devices; > > int (*init) (void); > > @@ -221,13 +233,6 @@ void internal_delay(int usecs); > extern uint32_t io_base_addr; > extern struct pci_access *pacc; > extern struct pci_dev *pcidev_dev; > -struct pcidev_status { > - uint16_t vendor_id; > - uint16_t device_id; > - const enum test_state status; > - const char *vendor_name; > - const char *device_name; > -}; > uintptr_t pcidev_readbar(struct pci_dev *dev, int bar); > uintptr_t pcidev_init(int bar, const struct pcidev_status *devs); > /* rpci_write_* are reversible writes. The original PCI config space register > @@ -244,6 +249,21 @@ int rpci_write_long(struct pci_dev *dev, int reg, uint32_t data); > void print_supported_pcidevs(const struct pcidev_status *devs); > #endif > > +struct usbdev_status { > + uint16_t vendor_id; > + uint16_t device_id; > + const enum test_state status; > + const char *vendor_name; > + const char *device_name; > +}; > +struct pcidev_status { > + uint16_t vendor_id; > + uint16_t device_id; > + const enum test_state status; > + const char *vendor_name; > + const char *device_name; > +}; Hm. You moved the struct pcidev_status and usbdev_status outside the #ifdef protecting it. Given that this has no impact on code generation, I don't have a big problem with it. This is a question we should eventually decide: Do we want unused struct declarations inside #ifdef or not? Such a decision should not hold up merging this code, I just wanted to mention it. > + > #if CONFIG_INTERNAL == 1 > /* board_enable.c */ > int board_parse_parameter(const char *boardstring, const char **vendor, const char **model); > @@ -422,13 +442,6 @@ extern const struct pcidev_status ata_hpt[]; > > /* ft2232_spi.c */ > #if CONFIG_FT2232_SPI == 1 > -struct usbdev_status { > - uint16_t vendor_id; > - uint16_t device_id; > - const enum test_state status; > - const char *vendor_name; > - const char *device_name; > -}; > int ft2232_spi_init(void); > extern const struct usbdev_status devs_ft2232spi[]; > void print_supported_usbdevs(const struct usbdev_status *devs); Regards, Carl-Daniel -- http://www.hailfinger.org/

2 1

Re: [flashrom] Dell Alienware Aurora R2
by Stefan Tauner 12 Dec '12

12 Dec '12

On Mon, 3 Dec 2012 15:32:47 +0100 "Gilles Antonetti / Gmail" <gilles.antonetti(a)gmail.com> wrote: > 0x54: 0x00000000 FREG0: WARNING: Flash Descriptor region (0x00000000-0x00000fff) is read-only. > 0x58: 0x03ff0200 FREG1: BIOS region (0x00200000-0x003fffff) is read-write. > 0x5C: 0x01ff0001 FREG2: WARNING: Management Engine region (0x00001000-0x001fffff) is locked.Hello Gilles, thanks for your report! The problem is the locked ME region as quoted above. We are working on unlocking it or working around it, but intel does not provide us any documentation so please do not expect a solution soon (or ever). I have added the board to our list of (un)supported boards (with an appropriate note) and will commit that later together with other small changes. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] mail archives down?
by Patrick Georgi 11 Dec '12

11 Dec '12

Am 2012-12-10 09:55, schrieb Idwer Vollering: > Works for me. This however looks wrong: > http://www.flashrom.org/pipermail/flashrom/2012-December/000073.html Sorry, misconfiguration on my part. Mails between yesterday evening and 8am this morning (both CET) got lost on their way to the archive. Patrick

2 2

Re: [flashrom] Erase Fails on Winmate I370 Motherboard with PMC Pm49FL004 Flash Chip
by Stefan Tauner 10 Dec '12

10 Dec '12

On Mon, 10 Dec 2012 14:35:54 -0500 sdbarnes(a)rockwellcollins.com wrote: > I think I have verified that there is no issue with flashrom 0.9.3 and the > PMC Pm49FL004 chip. > > I had received some Pm49FL004 chips from a vendor with a WinMate I330 BIOS > load (an I330 message was being displayed briefly on BIOS POST). Am I > correct in assuming that some portion of the BIOS (e.g.,boot block) cannot > be updated with flashrom? that depends on how the boot block (or any other range) is protected, there are various schemes to do this. the most common one is to use a dedicated write protection pin for the whole device or the boot block (or both), which can be changed by a GPIO of the southbridge or super i/o chip (flashrom supports a huge number of mainboards that need this, but each had to be added manually). but there are also some flash chips that can be locked by software which is done by the BIOS before the OS even loads (and there are various other schemes involving the chipset). the log you provided indicated that *if at all* there were only bits changed from 0 to 1 (by erasing whole blocks). this may have been because you rerun flashrom to obtain the log and the actual changes were done in an earlier run. flashrom would then skip every block that is already equal... > I never saw a checksum error after rebooting my > motherboard and I know that my BIOS defaults had been updated from the > factory defaults. > > I have since received some more Pm49FL004 chips from the same vendor with > a WinMate I370 BIOS load and flashing these chips with a different I370 > image works with flashrom-0.9.3 without any issues. this would OTOH indicate that there is no (hardware) write protection in place... i so am a bit puzzled ATM about what's the real issue (if there is any) and what happened exactly. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] Erase Fails on Winmate I370 Motherboard with PMC Pm49FL004 Flash Chip
by Stefan Tauner 10 Dec '12

10 Dec '12

On Mon, 10 Dec 2012 10:44:01 -0500 sdbarnes(a)rockwellcollins.com wrote: > Despite the verification failure, the motherboard appears to function > properly with the new flash image that is written. Below is the flashrom > verbose output: > > > > flashrom v0.9.3-r1250 on Linux 2.6.32.59 (i686), built with libpci 3.1.7, > … > Found chip "PMC Pm49FL004" (512 KB, LPC,FWH) at physical address > 0xfff80000. > … > Erasing and writing flash chip... Looking at blockwise erase function 0... > trying... 0x000000-0x000fff:S, 0x001000-0x001fff:S, 0x002000-0x002fff:S, > 0x003000-0x003fff:S, 0x004000-0x004fff:S, 0x005000-0x005fff:S, > 0x006000-0x006fff:S, 0x007000-0x007fff:S, 0x008000-0x008fff:S, > 0x009000-0x009fff:S, 0x00a000-0x00afff:S, 0x00b000-0x00bfff:S, > 0x00c000-0x00cfff:S, 0x00d000-0x00dfff:S, 0x00e000-0x00efff:S, > 0x00f000-0x00ffff:S, 0x010000-0x010fff:S, 0x011000-0x011fff:S, > 0x012000-0x012fff:S, 0x013000-0x013fff:S, 0x014000-0x014fff:S, > 0x015000-0x015fff:S, 0x016000-0x016fff:S, 0x017000-0x017fff:S, > 0x018000-0x018fff:S, 0x019000-0x019fff:S, 0x01a000-0x01afff:S, > 0x01b000-0x01bfff:S, 0x01c000-0x01cfff:S, 0x01d000-0x01dfff:S, > 0x01e000-0x01efff:S, 0x01f000-0x01ffff:S, 0x020000-0x020fff:S, > 0x021000-0x021fff:S, 0x022000-0x022fff:S, 0x023000-0x023fff:S, > 0x024000-0x024fff:S, 0x025000-0x025fff:S, 0x026000-0x026fff:S, > 0x027000-0x027fff:S, 0x028000-0x028fff:S, 0x029000-0x029fff:S, > 0x02a000-0x02afff:S, 0x02b000-0x02bfff:S, 0x02c000-0x02cfff:S, > 0x02d000-0x02dfff:S, 0x02e000-0x02efff:S, 0x02f000-0x02ffff:S, > 0x030000-0x030fff:S, 0x031000-0x031fff:S, 0x032000-0x032fff:S, > 0x033000-0x033fff:S, 0x034000-0x034fff:S, 0x035000-0x035fff:S, > 0x036000-0x036fff:S, 0x037000-0x037fff:S, 0x038000-0x038fff:S, > 0x039000-0x039fff:S, 0x03a000-0x03afff:S, 0x03b000-0x03bfff:S, > 0x03c000-0x03cfff:S, 0x03d000-0x03dfff:S, 0x03e000-0x03efff:S, > 0x03f000-0x03ffff:S, 0x040000-0x040fff:S, 0x041000-0x041fff:S, > 0x042000-0x042fff:S, 0x043000-0x043fff:S, 0x044000-0x044fff:S, > 0x045000-0x045fff:S, 0x046000-0x046fff:S, 0x047000-0x047fff:S, > 0x048000-0x048fff:S, 0x049000-0x049fff:S, 0x04a000-0x04afff:S, > 0x04b000-0x04bfff:S, 0x04c000-0x04cfff:S, 0x04d000-0x04dfff:S, > 0x04e000-0x04efff:S, 0x04f000-0x04ffff:S, 0x050000-0x050fff:S, > 0x051000-0x051fff:S, 0x052000-0x052fff:S, 0x053000-0x053fff:S, > 0x054000-0x054fff:S, 0x055000-0x055fff:S, 0x056000-0x056fff:S, > 0x057000-0x057fff:S, 0x058000-0x058fff:S, 0x059000-0x059fff:S, > 0x05a000-0x05afff:S, 0x05b000-0x05bfff:S, 0x05c000-0x05cfff:S, > 0x05d000-0x05dfff:S, 0x05e000-0x05efff:S, 0x05f000-0x05ffff:S, > 0x060000-0x060fff:S, 0x061000-0x061fff:S, 0x062000-0x062fff:S, > 0x063000-0x063fff:S, 0x064000-0x064fff:S, 0x065000-0x065fff:S, > 0x066000-0x066fff:S, 0x067000-0x067fff:S, 0x068000-0x068fff:S, > 0x069000-0x069fff:S, 0x06a000-0x06afff:S, 0x06b000-0x06bfff:S, > 0x06c000-0x06cfff:S, 0x06d000-0x06dfff:S, 0x06e000-0x06efff:S, > 0x06f000-0x06ffff:S, 0x070000-0x070fff:EERASE FAILED at 0x00070002! > Expected=0xff, Read=0x00, failed byte count from 0x00070000-0x00070fff: > 0xf70 > ERASE FAILED! > > > Looking at blockwise erase function 1... trying... 0x000000-0x00ffff:S, > 0x010000-0x01ffff:S, 0x020000-0x02ffff:S, 0x030000-0x03ffff:S, > 0x040000-0x04ffff:S, 0x050000-0x05ffff:S, 0x060000-0x06ffff:S, > 0x070000-0x07ffff:EERASE FAILED at 0x00070002! Expected=0xff, Read=0x00, > failed byte count from 0x00070000-0x0007ffff: 0xfd35 > ERASE FAILED! > > > Looking at blockwise erase function 2... trying... > 0x000000-0x07ffff:EERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, > failed byte count from 0x00000000-0x0007ffff: 0x53f0b > ERASE FAILED! > > > Looking at blockwise erase function 3... not defined. trying... > > Done. > Verifying flash... VERIFY FAILED at 0x0007010b! Expected=0x7c, Read=0x70, > failed byte count from 0x00000000-0x0007ffff: 0x9f2 > Your flash chip is in an unknown state. > Get help on IRC at irc.freenode.net (channel #flashrom) or > mail flashrom(a)flashrom.org with FAILED: your board name in the subject > line! > ------------------------------------------------------------------------------- > DO NOT REBOOT OR POWEROFF! > Restoring PCI config space for 00:1f:0 reg 0xdc i am not entirely sure, but i think 0.9.3 can not distinguish between an unknown state and the old, safe state the flash was before flashrom tried to erase. in your case it would be possible then that the whole flash chip is write protected and nothing changed/was deleted at all, which would explain the bootable condition of the system (i.e. you were lucky). if that is true we will need to add a small routine that disables the write protection on that mainboard (if there is no jumper oder bios option to do so). please send us the output of 'lspci -nn', 'lspci -nnvvvxxx', 'superiotool -deV' (run all commands as root), thanks. if not too much of a hassle you should also upgrade flashrom before further attempts. JFYI: your first message was stuck in the moderation queue because it was sent before you subscribed. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Erase Fails on Winmate I370 Motherboard with PMC Pm49FL004 Flash Chip
by sdbarnes＠rockwellcollins.com 10 Dec '12

10 Dec '12

Despite the verification failure, the motherboard appears to function properly with the new flash image that is written. Below is the flashrom verbose output: flashrom v0.9.3-r1250 on Linux 2.6.32.59 (i686), built with libpci 3.1.7, GCC 4.3.4, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OS timer resolution is 1 usecs, 1344M loops per second, 10 myus = 12 us, 100 myus = 109 us, 1000 myus = 1088 us, 10000 myus = 9464 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: " " DMI string system-product-name: " " DMI string system-version: " " DMI string baseboard-manufacturer: " " DMI string baseboard-product-name: "945GM" DMI string baseboard-version: " " DMI string chassis-type: "Desktop" Found chipset "Intel ICH7M", enabling flash write... chipset PCI ID is 8086:27b9, 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode enabled 0xffe00000/0xffa00000 FWH decode enabled 0xffd80000/0xff980000 FWH decode enabled 0xffd00000/0xff900000 FWH decode enabled 0xffc80000/0xff880000 FWH decode enabled 0xffc00000/0xff800000 FWH decode enabled 0xff700000/0xff300000 FWH decode disabled 0xff600000/0xff200000 FWH decode disabled 0xff500000/0xff100000 FWH decode disabled 0xff400000/0xff000000 FWH decode disabled Maximum FWH chip size: 0x100000 bytes BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x0 Root Complex Register Block address = 0xfed1c000 GCS = 0xc64: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x3 (LPC) Top Swap : not enabled OK. This chipset supports the following protocols: FWH. Probing for AMD Am29F010A/B, 128 KB: skipped. Probing for AMD Am29F002(N)BB, 256 KB: skipped. Probing for AMD Am29F002(N)BT, 256 KB: skipped. Probing for AMD Am29F016D, 2048 KB: skipped. Probing for AMD Am29F040B, 512 KB: skipped. Probing for AMD Am29F080B, 1024 KB: skipped. Probing for AMD Am29LV040B, 512 KB: skipped. Probing for AMD Am29LV081B, 1024 KB: skipped. Probing for AMIC A25L05PT, 64 KB: skipped. Probing for AMIC A25L05PU, 64 KB: skipped. Probing for AMIC A25L10PT, 128 KB: skipped. Probing for AMIC A25L10PU, 128 KB: skipped. Probing for AMIC A25L20PT, 256 KB: skipped. Probing for AMIC A25L20PU, 256 KB: skipped. Probing for AMIC A25L40PT, 512 KB: skipped. Probing for AMIC A25L40PU, 512 KB: skipped. Probing for AMIC A25L80P, 1024 KB: skipped. Probing for AMIC A25L16PT, 2048 KB: skipped. Probing for AMIC A25L16PU, 2048 KB: skipped. Probing for AMIC A25L512, 64 KB: skipped. Probing for AMIC A25L010, 128 KB: skipped. Probing for AMIC A25L020, 256 KB: skipped. Probing for AMIC A25L040, 512 KB: skipped. Probing for AMIC A25L080, 1024 KB: skipped. Probing for AMIC A25L016, 2048 KB: skipped. Probing for AMIC A25L032, 4096 KB: skipped. Probing for AMIC A25LQ032, 4096 KB: skipped. Probing for AMIC A29002B, 256 KB: skipped. Probing for AMIC A29002T, 256 KB: skipped. Probing for AMIC A29040B, 512 KB: skipped. Probing for AMIC A49LF040A, 512 KB: skipped. Probing for Atmel AT25DF021, 256 KB: skipped. Probing for Atmel AT25DF041A, 512 KB: skipped. Probing for Atmel AT25DF081, 1024 KB: skipped. Probing for Atmel AT25DF081A, 1024 KB: skipped. Probing for Atmel AT25DF161, 2048 KB: skipped. Probing for Atmel AT25DF321, 4096 KB: skipped. Probing for Atmel AT25DF321A, 4096 KB: skipped. Probing for Atmel AT25DF641, 8192 KB: skipped. Probing for Atmel AT25DQ161, 2048 KB: skipped. Probing for Atmel AT25F512B, 64 KB: skipped. Probing for Atmel AT25FS010, 128 KB: skipped. Probing for Atmel AT25FS040, 512 KB: skipped. Probing for Atmel AT26DF041, 512 KB: skipped. Probing for Atmel AT26DF081A, 1024 KB: skipped. Probing for Atmel AT26DF161, 2048 KB: skipped. Probing for Atmel AT26DF161A, 2048 KB: skipped. Probing for Atmel AT26F004, 512 KB: skipped. Probing for Atmel AT29C512, 64 KB: skipped. Probing for Atmel AT29C010A, 128 KB: skipped. Probing for Atmel AT29C020, 256 KB: skipped. Probing for Atmel AT29C040A, 512 KB: skipped. Probing for Atmel AT45CS1282, 16896 KB: skipped. Probing for Atmel AT45DB011D, 128 KB: skipped. Probing for Atmel AT45DB021D, 256 KB: skipped. Probing for Atmel AT45DB041D, 512 KB: skipped. Probing for Atmel AT45DB081D, 1024 KB: skipped. Probing for Atmel AT45DB161D, 2048 KB: skipped. Probing for Atmel AT45DB321C, 4224 KB: skipped. Probing for Atmel AT45DB321D, 4096 KB: skipped. Probing for Atmel AT45DB642D, 8192 KB: skipped. Probing for Atmel AT49BV512, 64 KB: skipped. Probing for Atmel AT49F020, 256 KB: skipped. Probing for Atmel AT49F002(N), 256 KB: skipped. Probing for Atmel AT49F002(N)T, 256 KB: skipped. Probing for Bright BM29F040, 512 KB: skipped. Probing for EMST F49B002UA, 256 KB: skipped. Probing for EMST F25L008A, 1024 KB: skipped. Probing for Eon EN25B05, 64 KB: skipped. Probing for Eon EN25B05T, 64 KB: skipped. Probing for Eon EN25B10, 128 KB: skipped. Probing for Eon EN25B10T, 128 KB: skipped. Probing for Eon EN25B20, 256 KB: skipped. Probing for Eon EN25B20T, 256 KB: skipped. Probing for Eon EN25B40, 512 KB: skipped. Probing for Eon EN25B40T, 512 KB: skipped. Probing for Eon EN25B80, 1024 KB: skipped. Probing for Eon EN25B80T, 1024 KB: skipped. Probing for Eon EN25B16, 2048 KB: skipped. Probing for Eon EN25B16T, 2048 KB: skipped. Probing for Eon EN25B32, 4096 KB: skipped. Probing for Eon EN25B32T, 4096 KB: skipped. Probing for Eon EN25B64, 8192 KB: skipped. Probing for Eon EN25B64T, 8192 KB: skipped. Probing for Eon EN25D16, 2048 KB: skipped. Probing for Eon EN25F05, 64 KB: skipped. Probing for Eon EN25F10, 128 KB: skipped. Probing for Eon EN25F20, 256 KB: skipped. Probing for Eon EN25F40, 512 KB: skipped. Probing for Eon EN25F80, 1024 KB: skipped. Probing for Eon EN25F16, 2048 KB: skipped. Probing for Eon EN25F32, 4096 KB: skipped. Probing for Eon EN29F010, 128 KB: skipped. Probing for Eon EN29F002(A)(N)B, 256 KB: skipped. Probing for Eon EN29F002(A)(N)T, 256 KB: skipped. Probing for Fujitsu MBM29F004BC, 512 KB: skipped. Probing for Fujitsu MBM29F004TC, 512 KB: skipped. Probing for Fujitsu MBM29F400BC, 512 KB: skipped. Probing for Fujitsu MBM29F400TC, 512 KB: skipped. Probing for Hyundai HY29F002T, 256 KB: skipped. Probing for Hyundai HY29F002B, 256 KB: skipped. Probing for Hyundai HY29F040A, 512 KB: skipped. Probing for Intel 28F001BN/BX-B, 128 KB: skipped. Probing for Intel 28F001BN/BX-T, 128 KB: skipped. Probing for Intel 28F002BC/BL/BV/BX-T, 256 KB: skipped. Probing for Intel 28F008S3/S5/SC, 512 KB: skipped. Probing for Intel 28F004B5/BE/BV/BX-B, 512 KB: skipped. Probing for Intel 28F004B5/BE/BV/BX-T, 512 KB: skipped. Probing for Intel 28F400BV/BX/CE/CV-B, 512 KB: skipped. Probing for Intel 28F400BV/BX/CE/CV-T, 512 KB: skipped. Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX25L512, 64 KB: skipped. Probing for Macronix MX25L1005, 128 KB: skipped. Probing for Macronix MX25L2005, 256 KB: skipped. Probing for Macronix MX25L4005, 512 KB: skipped. Probing for Macronix MX25L8005, 1024 KB: skipped. Probing for Macronix MX25L1605, 2048 KB: skipped. Probing for Macronix MX25L1635D, 2048 KB: skipped. Probing for Macronix MX25L1635E, 2048 KB: skipped. Probing for Macronix MX25L3205, 4096 KB: skipped. Probing for Macronix MX25L3235D, 4096 KB: skipped. Probing for Macronix MX25L6405, 8192 KB: skipped. Probing for Macronix MX25L12805, 16384 KB: skipped. Probing for Macronix MX29F001B, 128 KB: skipped. Probing for Macronix MX29F001T, 128 KB: skipped. Probing for Macronix MX29F002B, 256 KB: skipped. Probing for Macronix MX29F002T, 256 KB: skipped. Probing for Macronix MX29F040, 512 KB: skipped. Probing for Macronix MX29LV040, 512 KB: skipped. Probing for MoselVitelic V29C51000B, 64 KB: skipped. Probing for MoselVitelic V29C51000T, 64 KB: skipped. Probing for MoselVitelic V29C51400B, 512 KB: skipped. Probing for MoselVitelic V29C51400T, 512 KB: skipped. Probing for MoselVitelic V29LC51000, 64 KB: skipped. Probing for MoselVitelic V29LC51001, 128 KB: skipped. Probing for MoselVitelic V29LC51002, 256 KB: skipped. Probing for Numonyx M25PE10, 128 KB: skipped. Probing for Numonyx M25PE20, 256 KB: skipped. Probing for Numonyx M25PE40, 512 KB: skipped. Probing for Numonyx M25PE80, 1024 KB: skipped. Probing for Numonyx M25PE16, 2048 KB: skipped. Probing for PMC Pm25LV010, 128 KB: skipped. Probing for PMC Pm25LV016B, 2048 KB: skipped. Probing for PMC Pm25LV020, 256 KB: skipped. Probing for PMC Pm25LV040, 512 KB: skipped. Probing for PMC Pm25LV080B, 1024 KB: skipped. Probing for PMC Pm25LV512, 64 KB: skipped. Probing for PMC Pm29F002T, 256 KB: skipped. Probing for PMC Pm29F002B, 256 KB: skipped. Probing for PMC Pm39LV010, 128 KB: skipped. Probing for PMC Pm39LV020, 256 KB: skipped. Probing for PMC Pm39LV040, 512 KB: skipped. Probing for PMC Pm49FL002, 256 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for PMC Pm49FL004, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Found chip "PMC Pm49FL004" (512 KB, LPC,FWH) at physical address 0xfff80000. Probing for Sanyo LF25FW203A, 2048 KB: skipped. Probing for Sharp LHF00L04, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for Spansion S25FL004A, 512 KB: skipped. Probing for Spansion S25FL008A, 1024 KB: skipped. Probing for Spansion S25FL016A, 2048 KB: skipped. Probing for Spansion S25FL032A, 4096 KB: skipped. Probing for Spansion S25FL064A, 8192 KB: skipped. Probing for SST SST25VF010.REMS, 128 KB: skipped. Probing for SST SST25VF016B, 2048 KB: skipped. Probing for SST SST25VF032B, 4096 KB: skipped. Probing for SST SST25VF064C, 8192 KB: skipped. Probing for SST SST25VF040.REMS, 512 KB: skipped. Probing for SST SST25VF040B, 512 KB: skipped. Probing for SST SST25LF040A.RES, 512 KB: skipped. Probing for SST SST25VF040B.REMS, 512 KB: skipped. Probing for SST SST25VF080B, 1024 KB: skipped. Probing for SST SST28SF040A, 512 KB: skipped. Probing for SST SST29EE010, 128 KB: skipped. Probing for SST SST29LE010, 128 KB: skipped. Probing for SST SST29EE020A, 256 KB: skipped. Probing for SST SST29LE020, 256 KB: skipped. Probing for SST SST39SF512, 64 KB: skipped. Probing for SST SST39SF010A, 128 KB: skipped. Probing for SST SST39SF020A, 256 KB: skipped. Probing for SST SST39SF040, 512 KB: skipped. Probing for SST SST39VF512, 64 KB: skipped. Probing for SST SST39VF010, 128 KB: skipped. Probing for SST SST39VF020, 256 KB: skipped. Probing for SST SST39VF040, 512 KB: skipped. Probing for SST SST39VF080, 1024 KB: skipped. Probing for SST SST49LF002A/B, 256 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF003A/B, 384 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF004A/B, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF004C, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for SST SST49LF008C, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 KB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. 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: skipped. Probing for SST SST49LF020A, 256 KB: skipped. Probing for SST SST49LF040, 512 KB: skipped. Probing for SST SST49LF040B, 512 KB: skipped. Probing for SST SST49LF080A, 1024 KB: skipped. Probing for SST SST49LF160C, 2048 KB: skipped. Probing for ST M25P05-A, 64 KB: skipped. Probing for ST M25P05.RES, 64 KB: skipped. Probing for ST M25P10-A, 128 KB: skipped. Probing for ST M25P10.RES, 128 KB: skipped. Probing for ST M25P20, 256 KB: skipped. Probing for ST M25P40, 512 KB: skipped. Probing for ST M25P40-old, 512 KB: skipped. Probing for ST M25P80, 1024 KB: skipped. Probing for ST M25P16, 2048 KB: skipped. Probing for ST M25P32, 4096 KB: skipped. Probing for ST M25P64, 8192 KB: skipped. Probing for ST M25P128, 16384 KB: skipped. Probing for ST M25PX32, 4096 KB: skipped. Probing for ST M25PX64, 8192 KB: skipped. Probing for ST M29F002B, 256 KB: skipped. Probing for ST M29F002T/NT, 256 KB: skipped. Probing for ST M29F040B, 512 KB: skipped. Probing for ST M29F400BB, 512 KB: skipped. Probing for ST M29F400BT, 512 KB: skipped. Probing for ST M29W010B, 128 KB: skipped. Probing for ST M29W040B, 512 KB: skipped. Probing for ST M29W512B, 64 KB: skipped. Probing for ST M50FLW040A, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 KB: probe_82802ab: id1 0x09, id2 0xd5, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 KB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. 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 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51001B, 128 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51001T, 128 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51002B, 256 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51004B, 512 KB: skipped. Probing for SyncMOS/MoselVitelic {F,S,V}29C51004T, 512 KB: skipped. Probing for SyncMOS/MoselVitelic {S,V}29C31004B, 512 KB: skipped. Probing for SyncMOS/MoselVitelic {S,V}29C31004T, 512 KB: skipped. Probing for TI TMS29F002RB, 256 KB: skipped. Probing for TI TMS29F002RT, 256 KB: skipped. Probing for Winbond W25Q80, 1024 KB: skipped. Probing for Winbond W25Q16, 2048 KB: skipped. Probing for Winbond W25Q32, 4096 KB: skipped. Probing for Winbond W25Q64, 8192 KB: skipped. Probing for Winbond W25x10, 128 KB: skipped. Probing for Winbond W25x20, 256 KB: skipped. Probing for Winbond W25x40, 512 KB: skipped. Probing for Winbond W25x80, 1024 KB: skipped. Probing for Winbond W25x16, 2048 KB: skipped. Probing for Winbond W25x32, 4096 KB: skipped. Probing for Winbond W25x64, 8192 KB: skipped. Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 KB: skipped. Probing for Winbond W29C020(C)/W29C022, 256 KB: skipped. Probing for Winbond W29C040/P, 512 KB: skipped. Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 KB: skipped. Probing for Winbond W39V040A, 512 KB: skipped. Probing for Winbond W39V040B, 512 KB: skipped. Probing for Winbond W39V040C, 512 KB: skipped. Probing for Winbond W39V040FA, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040FB, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V040FC, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V080A, 1024 KB: skipped. Probing for Winbond W49F002U/N, 256 KB: skipped. Probing for Winbond W49F020, 256 KB: skipped. Probing for Winbond W49V002A, 256 KB: skipped. Probing for Winbond W49V002FA, 256 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V080FA, 1024 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for Winbond W39V080FA (dual mode), 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e Probing for AMIC unknown AMIC SPI chip, 0 KB: skipped. Probing for Atmel unknown Atmel SPI chip, 0 KB: skipped. Probing for Eon unknown Eon SPI chip, 0 KB: skipped. Probing for Macronix unknown Macronix SPI chip, 0 KB: skipped. Probing for PMC unknown PMC SPI chip, 0 KB: skipped. Probing for SST unknown SST SPI chip, 0 KB: skipped. Probing for ST unknown ST SPI chip, 0 KB: skipped. Probing for Sanyo unknown Sanyo SPI chip, 0 KB: skipped. Probing for Generic unknown SPI chip (RDID), 0 KB: skipped. Probing for Generic unknown SPI chip (REMS), 0 KB: skipped. === This flash part has status UNTESTED for operations: 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 part. Please include the flashrom output with the additional -V option for all operations you tested (-V, -Vr, -Vw, -VE), and mention which mainboard or programmer you tested. Please mention your board in the subject line. Thanks for your help! Flash image seems to be a legacy BIOS. Disabling checks. Reading old flash chip contents... Erasing and writing flash chip... Looking at blockwise erase function 0... trying... 0x000000-0x000fff:S, 0x001000-0x001fff:S, 0x002000-0x002fff:S, 0x003000-0x003fff:S, 0x004000-0x004fff:S, 0x005000-0x005fff:S, 0x006000-0x006fff:S, 0x007000-0x007fff:S, 0x008000-0x008fff:S, 0x009000-0x009fff:S, 0x00a000-0x00afff:S, 0x00b000-0x00bfff:S, 0x00c000-0x00cfff:S, 0x00d000-0x00dfff:S, 0x00e000-0x00efff:S, 0x00f000-0x00ffff:S, 0x010000-0x010fff:S, 0x011000-0x011fff:S, 0x012000-0x012fff:S, 0x013000-0x013fff:S, 0x014000-0x014fff:S, 0x015000-0x015fff:S, 0x016000-0x016fff:S, 0x017000-0x017fff:S, 0x018000-0x018fff:S, 0x019000-0x019fff:S, 0x01a000-0x01afff:S, 0x01b000-0x01bfff:S, 0x01c000-0x01cfff:S, 0x01d000-0x01dfff:S, 0x01e000-0x01efff:S, 0x01f000-0x01ffff:S, 0x020000-0x020fff:S, 0x021000-0x021fff:S, 0x022000-0x022fff:S, 0x023000-0x023fff:S, 0x024000-0x024fff:S, 0x025000-0x025fff:S, 0x026000-0x026fff:S, 0x027000-0x027fff:S, 0x028000-0x028fff:S, 0x029000-0x029fff:S, 0x02a000-0x02afff:S, 0x02b000-0x02bfff:S, 0x02c000-0x02cfff:S, 0x02d000-0x02dfff:S, 0x02e000-0x02efff:S, 0x02f000-0x02ffff:S, 0x030000-0x030fff:S, 0x031000-0x031fff:S, 0x032000-0x032fff:S, 0x033000-0x033fff:S, 0x034000-0x034fff:S, 0x035000-0x035fff:S, 0x036000-0x036fff:S, 0x037000-0x037fff:S, 0x038000-0x038fff:S, 0x039000-0x039fff:S, 0x03a000-0x03afff:S, 0x03b000-0x03bfff:S, 0x03c000-0x03cfff:S, 0x03d000-0x03dfff:S, 0x03e000-0x03efff:S, 0x03f000-0x03ffff:S, 0x040000-0x040fff:S, 0x041000-0x041fff:S, 0x042000-0x042fff:S, 0x043000-0x043fff:S, 0x044000-0x044fff:S, 0x045000-0x045fff:S, 0x046000-0x046fff:S, 0x047000-0x047fff:S, 0x048000-0x048fff:S, 0x049000-0x049fff:S, 0x04a000-0x04afff:S, 0x04b000-0x04bfff:S, 0x04c000-0x04cfff:S, 0x04d000-0x04dfff:S, 0x04e000-0x04efff:S, 0x04f000-0x04ffff:S, 0x050000-0x050fff:S, 0x051000-0x051fff:S, 0x052000-0x052fff:S, 0x053000-0x053fff:S, 0x054000-0x054fff:S, 0x055000-0x055fff:S, 0x056000-0x056fff:S, 0x057000-0x057fff:S, 0x058000-0x058fff:S, 0x059000-0x059fff:S, 0x05a000-0x05afff:S, 0x05b000-0x05bfff:S, 0x05c000-0x05cfff:S, 0x05d000-0x05dfff:S, 0x05e000-0x05efff:S, 0x05f000-0x05ffff:S, 0x060000-0x060fff:S, 0x061000-0x061fff:S, 0x062000-0x062fff:S, 0x063000-0x063fff:S, 0x064000-0x064fff:S, 0x065000-0x065fff:S, 0x066000-0x066fff:S, 0x067000-0x067fff:S, 0x068000-0x068fff:S, 0x069000-0x069fff:S, 0x06a000-0x06afff:S, 0x06b000-0x06bfff:S, 0x06c000-0x06cfff:S, 0x06d000-0x06dfff:S, 0x06e000-0x06efff:S, 0x06f000-0x06ffff:S, 0x070000-0x070fff:EERASE FAILED at 0x00070002! Expected=0xff, Read=0x00, failed byte count from 0x00070000-0x00070fff: 0xf70 ERASE FAILED! Looking at blockwise erase function 1... trying... 0x000000-0x00ffff:S, 0x010000-0x01ffff:S, 0x020000-0x02ffff:S, 0x030000-0x03ffff:S, 0x040000-0x04ffff:S, 0x050000-0x05ffff:S, 0x060000-0x06ffff:S, 0x070000-0x07ffff:EERASE FAILED at 0x00070002! Expected=0xff, Read=0x00, failed byte count from 0x00070000-0x0007ffff: 0xfd35 ERASE FAILED! Looking at blockwise erase function 2... trying... 0x000000-0x07ffff:EERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte count from 0x00000000-0x0007ffff: 0x53f0b ERASE FAILED! Looking at blockwise erase function 3... not defined. trying... Done. Verifying flash... VERIFY FAILED at 0x0007010b! Expected=0x7c, Read=0x70, failed byte count from 0x00000000-0x0007ffff: 0x9f2 Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with FAILED: your board name in the subject line! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! Restoring PCI config space for 00:1f:0 reg 0xdc

1 0

Erase Fails on Winmate I370 Motherboard with PMC Pm49FL004 Flash Chip
by sdbarnes＠rockwellcollins.com 10 Dec '12

10 Dec '12

1 0

mail archives down?
by Bernd Blaauw 10 Dec '12

10 Dec '12

Are the Pipermail mail archives down for some reason? Seeing this at flashrom, seabios and coreboot, of which I'm only subscribed to the first one (thus reading the other 2 from web archive). Getting a 403/Forbidden when clicking the Archives link at: http://www.flashrom.org/mailman/listinfo/flashrom Bernd

2 1

GA-A75M-UD2H
by Stefan Tauner 09 Dec '12

09 Dec '12

re GA-A75M-UD2H and your log at http://paste.flashrom.org/view.php?id=1490 yes, it looks good. thanks for the log. if you chose the correct file it should have booted afterwards without a problem. is/was that the case? please give us a bit more than 2 minutes in the middle of our night to react next time on IRC or send a mail to the mailing list instead ;) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Failure on 7252 MSI K9NBPM2-FID motherboard
by gordy perkins 08 Dec '12

08 Dec '12

Hello - thanks for the great effort on flashrom. My particular board doesn't flash. Here are the particulars. Ubuntu 12.04, if that matters. 0.9.6.1 failed too... gordy@macoushla:~/Downloads/7252v58$ sudo flashromflashrom v0.9.5.2-r1517 on Linux 3.2.0-34-generic-pae (i686), built with libpci 3.1.8, GCC 4.6.3, little endianflashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK.Found chipset "NVIDIA MCP51". Enabling flash write... OK.Found Winbond flash chip "W39V040B" (512 kB, LPC) at physical address 0xfff80000.Found Winbond flash chip "W39V040FB" (512 kB, FWH) at physical address 0xfff80000.Multiple flash chips were detected: "W39V040B", "W39V040FB"Please specify which chip to use with the -c <chipname> option.gordy@macoushla:~/Downloads/7252v58$ sudo flashrom -w A7252NMS.580 -c W39V040Bflashrom v0.9.5.2-r1517 on Linux 3.2.0-34-generic-pae (i686), built with libpci 3.1.8, GCC 4.6.3, little endianflashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK.Found chipset "NVIDIA MCP51". Enabling flash write... OK.Found Winbond flash chip "W39V040B" (512 kB, LPC) at physical address 0xfff80000.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 0x0000ad80! Expected=0xff, Read=0x44, failed byte count from 0x00000000-0x0000ffff: 0x5200ERASE FAILED!Reading current flash chip contents... done. ERASE FAILED at 0x0000ad80! Expected=0xff, Read=0x44, failed byte count from 0x00000000-0x0007ffff: 0x657a4ERASE 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) ormail flashrom@flashrom.org!-------------------------------------------------------------------------------You may now reboot or simply leave the machine running.gordy@macoushla:~/Downloads/7252v58$ sudo flashrom -w A7252NMS.580 -c W39V040FBflashrom v0.9.5.2-r1517 on Linux 3.2.0-34-generic-pae (i686), built with libpci 3.1.8, GCC 4.6.3, little endianflashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK.Found chipset "NVIDIA MCP51". Enabling flash write... OK.Found Winbond flash chip "W39V040FB" (512 kB, FWH) at physical address 0xfff80000.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 0x0000ad80! Expected=0xff, Read=0x44, failed byte count from 0x00000000-0x0000ffff: 0x5200ERASE FAILED!Reading current flash chip contents... done. ERASE FAILED at 0x0000ad80! Expected=0xff, Read=0x44, failed byte count from 0x00000000-0x0007ffff: 0x657a4ERASE 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) ormail flashrom@flashrom.org!-------------------------------------------------------------------------------You may now reboot or simply leave the machine running.gordy@macoushla:~/Downloads/7252v58$

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom December 2012