flashrom

flashrom@flashrom.org

6 participants
9186 discussions

[commit] r1765 - trunk
by repository service 04 Mar '14

04 Mar '14

Author: hailfinger Date: Wed Mar 5 01:16:16 2014 New Revision: 1765 URL: http://flashrom.org/trac/flashrom/changeset/1765 Log: Clean up physmap, fix unaligned mapping problems Convert all physmaps in dmi.c to use aligned readonly maps. Convert all physmaps in cbtable.c to use unaligned readonly maps. Make physunmap() a generic architecture-independent wrapper. Add physunmap_unaligned() to complement physmap*_unaligned(). Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Acked-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Modified: trunk/cbtable.c trunk/dmi.c trunk/physmap.c trunk/programmer.h Modified: trunk/cbtable.c ============================================================================== --- trunk/cbtable.c Thu Nov 21 16:59:52 2013 (r1764) +++ trunk/cbtable.c Wed Mar 5 01:16:16 2014 (r1765) @@ -261,7 +261,7 @@ #else start = 0x0; #endif - table_area = physmap_ro("low megabyte", start, BYTES_TO_MAP - start); + table_area = physmap_ro_unaligned("low megabyte", start, BYTES_TO_MAP - start); if (ERROR_PTR == table_area) { msg_perr("Failed getting access to coreboot low tables.\n"); return -1; @@ -276,8 +276,9 @@ if (forward->tag == LB_TAG_FORWARD) { start = forward->forward; start &= ~(getpagesize() - 1); - physunmap(table_area, BYTES_TO_MAP); - table_area = physmap_ro("high tables", start, BYTES_TO_MAP); + physunmap_unaligned(table_area, BYTES_TO_MAP); + // FIXME: table_area is never unmapped below, nor is it unmapped above in the no-forward case + table_area = physmap_ro_unaligned("high tables", start, BYTES_TO_MAP); if (ERROR_PTR == table_area) { msg_perr("Failed getting access to coreboot high tables.\n"); return -1; Modified: trunk/dmi.c ============================================================================== --- trunk/dmi.c Thu Nov 21 16:59:52 2013 (r1764) +++ trunk/dmi.c Wed Mar 5 01:16:16 2014 (r1765) @@ -153,7 +153,7 @@ { int i = 0, j = 0; - uint8_t *dmi_table_mem = physmap_round("DMI Table", base, len); + uint8_t *dmi_table_mem = physmap_ro("DMI Table", base, len); if (dmi_table_mem == NULL) { msg_perr("Unable to access DMI Table\n"); return; Modified: trunk/physmap.c ============================================================================== --- trunk/physmap.c Thu Nov 21 16:59:52 2013 (r1764) +++ trunk/physmap.c Wed Mar 5 01:16:16 2014 (r1765) @@ -27,6 +27,7 @@ #include <string.h> #include <errno.h> #include "flash.h" +#include "programmer.h" #include "hwaccess.h" #if !defined(__DJGPP__) && !defined(__LIBPAYLOAD__) @@ -89,7 +90,7 @@ #define sys_physmap_rw_uncached sys_physmap #define sys_physmap_ro_cached sys_physmap -void physunmap(void *virt_addr, size_t len) +void sys_physunmap_unaligned(void *virt_addr, size_t len) { __dpmi_meminfo mi; @@ -118,7 +119,7 @@ #define sys_physmap_rw_uncached sys_physmap #define sys_physmap_ro_cached sys_physmap -void physunmap(void *virt_addr, size_t len) +void sys_physunmap_unaligned(void *virt_addr, size_t len) { } #elif defined(__MACH__) && defined(__APPLE__) @@ -139,7 +140,7 @@ #define sys_physmap_rw_uncached sys_physmap #define sys_physmap_ro_cached sys_physmap -void physunmap(void *virt_addr, size_t len) +void sys_physunmap_unaligned(void *virt_addr, size_t len) { unmap_physical(virt_addr, len); } @@ -192,13 +193,8 @@ return MAP_FAILED == virt_addr ? ERROR_PTR : virt_addr; } -void physunmap(void *virt_addr, size_t len) +void sys_physunmap_unaligned(void *virt_addr, size_t len) { - if (len == 0) { - msg_pspew("Not unmapping zero size at %p\n", virt_addr); - return; - } - munmap(virt_addr, len); } #endif @@ -242,7 +238,7 @@ return 1; } struct undo_physmap_data *d = data; - physunmap(d->virt_addr, d->len); + physunmap_unaligned(d->virt_addr, d->len); free(data); return 0; } @@ -292,7 +288,7 @@ struct undo_physmap_data *d = malloc(sizeof(struct undo_physmap_data)); if (d == NULL) { msg_perr("%s: Out of memory!\n", __func__); - physunmap(virt_addr, len); + physunmap_unaligned(virt_addr, len); return ERROR_PTR; } @@ -300,7 +296,7 @@ d->len = len; if (register_shutdown(undo_physmap, d) != 0) { msg_perr("%s: Could not register shutdown function!\n", __func__); - physunmap(virt_addr, len); + physunmap_unaligned(virt_addr, len); return ERROR_PTR; } } @@ -308,9 +304,41 @@ return virt_addr + offset; } +void physunmap_unaligned(void *virt_addr, size_t len) +{ + /* No need to check for zero size, such mappings would have yielded ERROR_PTR. */ + if (virt_addr == ERROR_PTR) { + msg_perr("Trying to unmap a nonexisting mapping!\n" + "Please report a bug at flashrom(a)flashrom.org\n"); + return; + } + + sys_physunmap_unaligned(virt_addr, len); +} + +void physunmap(void *virt_addr, size_t len) +{ + uintptr_t tmp; + + /* No need to check for zero size, such mappings would have yielded ERROR_PTR. */ + if (virt_addr == ERROR_PTR) { + msg_perr("Trying to unmap a nonexisting mapping!\n" + "Please report a bug at flashrom(a)flashrom.org\n"); + return; + } + tmp = (uintptr_t)virt_addr; + /* We assume that the virtual address of a page-aligned physical address is page-aligned as well. By + * extension, rounding a virtual unaligned address as returned by physmap should yield the same offset + * between rounded and original virtual address as between rounded and original physical address. + */ + round_to_page_boundaries(&tmp, &len); + virt_addr = (void *)tmp; + physunmap_unaligned(virt_addr, len); +} + void *physmap(const char *descr, uintptr_t phys_addr, size_t len) { - return physmap_common(descr, phys_addr, len, PHYSM_RW, PHYSM_NOCLEANUP, PHYSM_EXACT); + return physmap_common(descr, phys_addr, len, PHYSM_RW, PHYSM_NOCLEANUP, PHYSM_ROUND); } void *rphysmap(const char *descr, uintptr_t phys_addr, size_t len) @@ -318,12 +346,12 @@ return physmap_common(descr, phys_addr, len, PHYSM_RW, PHYSM_CLEANUP, PHYSM_ROUND); } -void *physmap_round(const char *descr, uintptr_t phys_addr, size_t len) +void *physmap_ro(const char *descr, uintptr_t phys_addr, size_t len) { - return physmap_common(descr, phys_addr, len, PHYSM_RW, PHYSM_NOCLEANUP, PHYSM_ROUND); + return physmap_common(descr, phys_addr, len, PHYSM_RO, PHYSM_NOCLEANUP, PHYSM_ROUND); } -void *physmap_ro(const char *descr, uintptr_t phys_addr, size_t len) +void *physmap_ro_unaligned(const char *descr, uintptr_t phys_addr, size_t len) { return physmap_common(descr, phys_addr, len, PHYSM_RO, PHYSM_NOCLEANUP, PHYSM_EXACT); } Modified: trunk/programmer.h ============================================================================== --- trunk/programmer.h Thu Nov 21 16:59:52 2013 (r1764) +++ trunk/programmer.h Wed Mar 5 01:16:16 2014 (r1765) @@ -277,9 +277,10 @@ /* physmap.c */ void *physmap(const char *descr, uintptr_t phys_addr, size_t len); void *rphysmap(const char *descr, uintptr_t phys_addr, size_t len); -void *physmap_round(const char *descr, uintptr_t phys_addr, size_t len); void *physmap_ro(const char *descr, uintptr_t phys_addr, size_t len); +void *physmap_ro_unaligned(const char *descr, uintptr_t phys_addr, size_t len); void physunmap(void *virt_addr, size_t len); +void physunmap_unaligned(void *virt_addr, size_t len); #if CONFIG_INTERNAL == 1 int setup_cpu_msr(int cpu); void cleanup_cpu_msr(void);

1 0

Re: [flashrom] [Ubuntu] Dediprog SF100 support with Winbond W25Q64FW
by Carl-Daniel Hailfinger 04 Mar '14

04 Mar '14

Hi Kurt, Am 24.02.2014 09:29 schrieb Kurt Qiao: > hope anyone can help me out, i try to implement flashrom to support > dediprog SF100 on my Ubuntu. config as below: > OS: Ubuntu12.04 X64 > Dediprog: SF100, fm ver: 5.5.0 We only have tested flashrom support with SF100 firmware versions from 2.0 to 5.2. It should work with firmware version 5.5, but we have not tested it. > SPI ROM: winbond W25Q64FW, id 0xef 6017 > > plugging my SF100, and use below cmd > flashrom -p dediprog -V > i can see the program detect my sf100 but fail to detect the SPI ROM. log > as attached file. > ---log---- > Probing for Winbond W25Q64.V, 8192 kB: RDID byte 0 parity violation. > probe_spi_rdid_generic: id1 0x53, id2 0x4631 > ----log--- > > as the log shows, seems flashrom read SPI ROM id is 0x53, 0x4631, but > actually my SPI ROM on board is winbond with id 0xef, 0x6017(i confirm this > with windows dediprog). > so i have no idea why flashrom detect wrong id, and the flashchips.h > already have WINBOND_NEX_W25Q64_W 0x6017 support. 0x53 0x46 0x31 is the string "SF1". This string is returned by the SF100 if we query the firmware version. I think we have a bug in the dediprog firmware or in the dediprog driver or in libusb. Which version of libusb are you using? Regards, Carl-Daniel -- http://www.hailfinger.org/

1 0

HM87 test report
by Vasiliy Vylegzhanin 04 Mar '14

04 Mar '14

read and write look ok

1 0

[PATCH] internal programmer: handle failed chip mapping
by Carl-Daniel Hailfinger 03 Mar '14

03 Mar '14

Mapping a chip with the internal programmer on x86 will fail if the chip is larger than 16 MByte due to traditional x86 architecture constraints. No LPC/FWH chips of sizes bigger than 4 MByte are known, and Parallel chips are limited to older x86 chipsets and way smaller sizes because of address line shortage. We do see quite large SPI chips (even >16 MByte) and flashrom shouldn't fail probing or accessing them. Given that we have no chance to map those chips into the address space completely, make sure they are handled properly with indirect accesses Caveat: The code is proof-of-concept quality and litters the codebase with exit(1). We need to discuss what do do in that case. Testing should be done on a x86 machine which has SPI flash, and with r1702 reverted to have the 32 MByte chips again in flashchips.c (ignore the incorrect r1701 changelog which speaks of 32 MByte chip removal, that only happens in r1702). If flashrom successfully finishes probing without an abort in between, the patch does what it should. Or not. Read on. Without this patch and a reverted r1702, flashrom may successfully finish probing anyway due to the earlier physmap cleanups by Niklas Söderlund (r1744 and r1745). That's just the result from missing error checks, though. Applying this patch against a r1701 checkout (all files being r1701) should result in a fixed probe vs. a failing probe for plain r1701. A backported version of the patch against r1701 can be found at http://paste.flashrom.org/view.php?id=2027 Thanks for reading. Regards, Carl-Daniel Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-internal_no_chip_mapping_larger_16mbyte/flash.h =================================================================== --- flashrom-internal_no_chip_mapping_larger_16mbyte/flash.h (Revision 1764) +++ flashrom-internal_no_chip_mapping_larger_16mbyte/flash.h (Arbeitskopie) @@ -186,6 +186,7 @@ struct flashctx { struct flashchip *chip; + bool virtual_memory_is_usable; chipaddr virtual_memory; /* Some flash devices have an additional register space. */ chipaddr virtual_registers; Index: flashrom-internal_no_chip_mapping_larger_16mbyte/it87spi.c =================================================================== --- flashrom-internal_no_chip_mapping_larger_16mbyte/it87spi.c (Revision 1764) +++ flashrom-internal_no_chip_mapping_larger_16mbyte/it87spi.c (Arbeitskopie) @@ -385,7 +385,7 @@ * the mainboard does not use IT87 SPI translation. This should be done * via a programmer parameter for the internal programmer. */ - if ((flash->chip->total_size * 1024 > 512 * 1024)) { + if (!flash->virtual_memory_is_usable || (flash->chip->total_size * 1024 > 512 * 1024)) { spi_read_chunked(flash, buf, start, len, 3); } else { mmio_readn((void *)(flash->virtual_memory + start), buf, len); Index: flashrom-internal_no_chip_mapping_larger_16mbyte/internal.c =================================================================== --- flashrom-internal_no_chip_mapping_larger_16mbyte/internal.c (Revision 1764) +++ flashrom-internal_no_chip_mapping_larger_16mbyte/internal.c (Arbeitskopie) @@ -365,45 +365,69 @@ } #endif +void *internal_map(const char *descr, uintptr_t phys_addr, size_t len) +{ + return physmap(descr, phys_addr, len); +} + +void internal_unmap(void *virt_addr, size_t len) +{ + physunmap(virt_addr, len); +} + static void internal_chip_writeb(const struct flashctx *flash, uint8_t val, chipaddr addr) { + if (!flash->virtual_memory_is_usable) + exit(1); mmio_writeb(val, (void *) addr); } static void internal_chip_writew(const struct flashctx *flash, uint16_t val, chipaddr addr) { + if (!flash->virtual_memory_is_usable) + exit(1); mmio_writew(val, (void *) addr); } static void internal_chip_writel(const struct flashctx *flash, uint32_t val, chipaddr addr) { + if (!flash->virtual_memory_is_usable) + exit(1); mmio_writel(val, (void *) addr); } static uint8_t internal_chip_readb(const struct flashctx *flash, const chipaddr addr) { + if (!flash->virtual_memory_is_usable) + exit(1); return mmio_readb((void *) addr); } static uint16_t internal_chip_readw(const struct flashctx *flash, const chipaddr addr) { + if (!flash->virtual_memory_is_usable) + exit(1); return mmio_readw((void *) addr); } static uint32_t internal_chip_readl(const struct flashctx *flash, const chipaddr addr) { + if (!flash->virtual_memory_is_usable) + exit(1); return mmio_readl((void *) addr); } static void internal_chip_readn(const struct flashctx *flash, uint8_t *buf, const chipaddr addr, size_t len) { + if (!flash->virtual_memory_is_usable) + exit(1); mmio_readn((void *)addr, buf, len); return; } Index: flashrom-internal_no_chip_mapping_larger_16mbyte/wbsio_spi.c =================================================================== --- flashrom-internal_no_chip_mapping_larger_16mbyte/wbsio_spi.c (Revision 1764) +++ flashrom-internal_no_chip_mapping_larger_16mbyte/wbsio_spi.c (Arbeitskopie) @@ -20,6 +20,7 @@ #if defined(__i386__) || defined(__x86_64__) +#include <stdlib.h> #include "flash.h" #include "chipdrivers.h" #include "programmer.h" @@ -204,6 +205,8 @@ static int wbsio_spi_read(struct flashctx *flash, uint8_t *buf, unsigned int start, unsigned int len) { + if (!flash->virtual_memory_is_usable) + exit(1); mmio_readn((void *)(flash->virtual_memory + start), buf, len); return 0; } Index: flashrom-internal_no_chip_mapping_larger_16mbyte/flashrom.c =================================================================== --- flashrom-internal_no_chip_mapping_larger_16mbyte/flashrom.c (Revision 1764) +++ flashrom-internal_no_chip_mapping_larger_16mbyte/flashrom.c (Arbeitskopie) @@ -68,8 +68,8 @@ .type = OTHER, .devs.note = NULL, .init = internal_init, - .map_flash_region = physmap, - .unmap_flash_region = physunmap, + .map_flash_region = internal_map, + .unmap_flash_region = internal_unmap, .delay = internal_delay, }, #endif @@ -1086,6 +1086,10 @@ base = flashbase ? flashbase : (0xffffffff - size + 1); flash->virtual_memory = (chipaddr)programmer_map_flash_region("flash chip", base, size); + if (flash->virtual_memory == (chipaddr)ERROR_PTR) + flash->virtual_memory_is_usable = false; + else + flash->virtual_memory_is_usable = true; /* We handle a forced match like a real match, we just avoid probing. Note that probe_flash() * is only called with force=1 after normal probing failed. Index: flashrom-internal_no_chip_mapping_larger_16mbyte/programmer.h =================================================================== --- flashrom-internal_no_chip_mapping_larger_16mbyte/programmer.h (Revision 1764) +++ flashrom-internal_no_chip_mapping_larger_16mbyte/programmer.h (Arbeitskopie) @@ -325,6 +325,8 @@ int register_superio(struct superio s); extern enum chipbustype internal_buses_supported; int internal_init(void); +void *internal_map(const char *descr, uintptr_t phys_addr, size_t len); +void internal_unmap(void *virt_addr, size_t len); #endif /* hwaccess.c */ -- http://www.hailfinger.org/

1 0

flashrom -V
by Volker Twer 01 Mar '14

01 Mar '14

Hey, I'm thinking about upgrading my BIOS and found "flashrom" in DEBIAN-repositories. Running a "read" on the builtin BIOS I saw the request for sending you some information - so here you are. Does "guesswork" mean, it might be unsafe to use this software on this board/bios? Thanks for your work! Greetings, Volker This ist the requested output flashrom v0.9.6.1-r1563 on Linux 3.13-3.slh.2-aptosid-686 (i686) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.9, GCC 4.7.1, little endian Command line (3 args): flashrom -V -p internal Calibrating delay loop... OS timer resolution is 2 usecs, 1238M loops per second, 10 myus = 11 us, 100 myus = 100 us, 1000 myus = 1001 us, 10000 myus = 9989 us, 8 myus = 9 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "System Manufacturer" DMI string system-product-name: "System Product Name" DMI string system-version: "System Version" DMI string baseboard-manufacturer: "NF-M2SV" DMI string baseboard-product-name: "www.abit.com.tw " DMI string baseboard-version: " " DMI string chassis-type: "Desktop" Found ITE Super I/O, ID 0x8726 on port 0x2e Found chipset "NVIDIA MCP61" with PCI ID 10de:03e0. Enabling flash write... This chipset is not really supported yet. Guesswork... ISA/LPC bridge reg 0x8a contents: 0x00, bit 6 is 0, bit 5 is 0 Flash bus type is LPC Found SMBus device 10de:03eb at 00:01:1 MCP SPI BAR is at 0x00000000 MCP SPI is not used. 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. Super I/O ID 0x8726 is not on the list of flash capable controllers. The following protocols are supported: LPC. Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xda, id2 0x50 Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x40, id2 0x07, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xda, id2 0x50 Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xda, id2 0x50 Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xda, id2 0x50 Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xda, id2 0x50 Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xda, id2 0x50 Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xda, id2 0x50 Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF160C, 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 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 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 M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xda, id2 0x50 Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xda, id2 0x50 Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xda, id2 0x50 Found Winbond flash chip "W39V040C" (512 kB, LPC) at physical address 0xfff80000. Lockout bits: Hardware bootblock locking (#TBL) is not active. Hardware remaining chip locking (#WP) is not active.. Probing for Winbond W39V080A, 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 W49V002A, 256 kB: probe_jedec_common: id1 0xda, id2 0x50 Found Winbond flash chip "W39V040C" (512 kB, LPC). No operations were specified. Restoring PCI config space for 00:01:0 reg 0x6d Restoring PCI config space for 00:01:0 reg 0x90 Restoring PCI config space for 00:01:0 reg 0x8c Restoring PCI config space for 00:01:0 reg 0x88

2 1

Re: [flashrom] Tested AT25DF161
by Stefan Tauner 01 Mar '14

01 Mar '14

On Sun, 2 Mar 2014 00:28:16 +0400 Alex K <lepik.stv(a)gmail.com> wrote: > Sorry, I do not quite understand your question, but I'll try to answer. > I forgot when recording chip, specify a log file entry. Because I have a > log file cleanup, and reading to compare the recorded information. > To clean the chip pin WP, I connect to the GND. For writing and reading > from the chip, pin WP connects to the VCC. > > […] > > I hope this information will help you. Yes, thank you. I'll mark the chip as fully tested. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] Tested AT25DF161
by Stefan Tauner 01 Mar '14

01 Mar '14

On Sat, 1 Mar 2014 23:12:15 +0400 Alex K <lepik.stv(a)gmail.com> wrote: > Hello I tested for cleaning work, reading, writing, memory AT25DF161 using > Bus Pirate v4. > Used: > flashrom v0.9.6.1-r1704 on Windows 6.1 (x86) > flashrom was built with GCC 4.7.2, little endian > Baud rate is 115200. > Detected Bus Pirate hardware v4 > Detected Bus Pirate firmware 6.2 ("v6.2-beta1") > Using SPI command set v2. > SPI speed is 8MHz > Raw bitbang mode version 1 > Raw SPI mode version 1 > The following protocols are supported: SPI. > Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 > 0x4602 > Found Atmel flash chip "AT25DF161" (2048 kB, SPI) on buspirate_spi. > Ignoring security lockdown (if present) > Ignoring status register byte 2 > Chip status register is 0x0c. > Chip status register: Sector Protection Register Lock (SRPL) is not set > Chip status register: Bit 6 is not set > Chip status register: Erase/Program Error (EPE) is not set > Chip status register: WP# pin (WPP) is asserted > Chip status register: Software Protection Status (SWP): all sectors are > protected > Chip status register: Write Enable Latch (WEL) is not set > Chip status register: Write In Progress (WIP/BUSY) is not set > === > > Initially, there was a problem with the use of long cables (> 20 cm). > After verification of the firmware did not pass. > Replaced wires from Bus Pirate at length (10cm), all turned out. Many > thanks for the utility. I think that you can remove the status UNTESTED > with this chip. Thank you again. > I think it is reasonable to point out the page on the wiki that the length > of wire for the Bus Pirate is very desirable <= 10 cm, to avoid many > mistakes. This saves the trouble of starting recording, reading chips. > > Sorry for my bad english, I'm from Russia. Hello Alex, thanks for your report! I am wondering a bit about the status register bits. According to your log the software write protection is enabled (and the parsing of the raw value 0x0c seems to be correct, so this is not only a cosmetic problem). Did you change anything since you wrote to the chip? Regarding the cable lengths: The troubleshooting section of the bus pirate wiki page links to this: http://flashrom.org/ISP and the first problem mentioned there are too long cables ;) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Tested AT25DF161
by Alex K 01 Mar '14

01 Mar '14

Hello I tested for cleaning work, reading, writing, memory AT25DF161 using Bus Pirate v4. Used: flashrom v0.9.6.1-r1704 on Windows 6.1 (x86) flashrom was built with GCC 4.7.2, little endian Baud rate is 115200. Detected Bus Pirate hardware v4 Detected Bus Pirate firmware 6.2 ("v6.2-beta1") Using SPI command set v2. SPI speed is 8MHz Raw bitbang mode version 1 Raw SPI mode version 1 The following protocols are supported: SPI. Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4602 Found Atmel flash chip "AT25DF161" (2048 kB, SPI) on buspirate_spi. Ignoring security lockdown (if present) Ignoring status register byte 2 Chip status register is 0x0c. Chip status register: Sector Protection Register Lock (SRPL) is not set Chip status register: Bit 6 is not set Chip status register: Erase/Program Error (EPE) is not set Chip status register: WP# pin (WPP) is asserted Chip status register: Software Protection Status (SWP): all sectors are protected Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set === Initially, there was a problem with the use of long cables (> 20 cm). After verification of the firmware did not pass. Replaced wires from Bus Pirate at length (10cm), all turned out. Many thanks for the utility. I think that you can remove the status UNTESTED with this chip. Thank you again. I think it is reasonable to point out the page on the wiki that the length of wire for the Bus Pirate is very desirable <= 10 cm, to avoid many mistakes. This saves the trouble of starting recording, reading chips. Sorry for my bad english, I'm from Russia. -- С уважением Алексей

1 0

FAILED: SST49LF004A/B
by Tim Sebastian 28 Feb '14

28 Feb '14

Hello, I'm trying to use flashrom to write a new bios to my device. It successfully writes the beginning of the bios and then fails with the error: 0x040000-0x040fff:W writing sector at 0xb7ea0000 failed! And again with the second erase function : Trying erase function 1... 0x000000-0x00ffff:EW, 0x010000-0x01ffff:S, 0x020000-0x02ffff:S, 0x030000-0x03ffff:S, 0x040000-0x04ffff:W writing sector at 0xb7ea0000 failed! leaving the bios in an unstable state. Further experimentation shows that writing the bios fails on both erasing and writing any sector after 0x040000, which is exactly halfway through the bios (2Mb out of 4Mb). Reading from those areas works without a problem. The lock status for every block is reported as 00, full access. Full log is below. I took a look at the source code for flashrom in order to see if I could easily fix the problem. I created a minimal flashrom-like clone that works with my chip: #include <sys/types.h> #include <sys/stat.h> #include <fcntl.h> #include <stdio.h> #include <sys/mman.h> #define D(bios, pos) *((volatile char*)bios + pos) void write_byte(void* bios, int pos, char value) { char tmp1, tmp2; int i = 0; int tries = 4; retry: D(bios, 0x5555) = 0xAA; D(bios, 0x2AAA) = 0x55; D(bios, 0x5555) = 0xA0; D(bios, pos) = value; tmp1 = D(bios, 0) & 0x40; while (i++ < 0xFFFFFFF) { tmp2 = D(bios, 0) & 0x40; if (tmp1 == tmp2) { break; } tmp1 = tmp2; } if (D(bios, pos) != value) { if (tries > 0) { tries--; goto retry; } printf("Error writing value\n"); } } void try_replace(void* bios, int pos) { printf("Pos = %x:\n", pos); printf("Old: %hhx\n", D(bios, pos)); write_byte(bios, pos, 0); printf("New: %hhx\n", D(bios, pos)); printf("\n"); } int main() { int fd = open("/dev/mem", O_RDWR); void *bios = mmap(NULL, 0x80000, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0xfff80000); char old; try_replace(bios, 0); try_replace(bios, 0x20000); try_replace(bios, 0x3ff00); try_replace(bios, 0x40000); try_replace(bios, 0x50000); try_replace(bios, 0x60000); try_replace(bios, 0x70000); munmap(bios, 0x80000); close(fd); return 0; } And it outputs: Pos = 0: Old: 25 New: 0 Pos = 20000: Old: 81 New: 0 Pos = 3ff00: Old: ff New: 0 Pos = 40000: Old: ff Error writing value New: ff Pos = 50000: Old: ff Error writing value New: ff Pos = 60000: Old: ff Error writing value New: ff Pos = 70000: Old: ff Error writing value New: ff *Note that running this script will write garbage to your bios. Make sure to keep an original backup nearby.* As you can see, the problem is easily reproducible. What can cause writing to fail on where the high bit of the address is set (0x40000-0x7ffff)? Full log: =========================================== flashrom v0.9.7-r1711 on Linux 2.6.35.12 (i586) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.0, GCC 4.6.1, little endian Command line (5 args): ./flashrom --programmer internal -w my_bios -V Calibrating delay loop... OS timer resolution is 4 usecs, 78M loops per second, 10 myus = 12 us, 100 myus = 108 us, 1000 myus = 1030 us, 10000 myus = 10131 us, 16 myus = 21 us, OK. Initializing internal programmer No coreboot table found. sh: dmidecode: not found dmidecode execution unsuccessful - continuing without DMI info Found Winbond Super I/O, id 0x52 WARNING: No chipset found. Flash detection will most likely fail. The following protocols are supported: Non-SPI. Probing for AMD Am29F010A/B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F002(N)BB, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F002(N)BT, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F016D, 2048 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F040B, 512 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F080B, 1024 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV001BB, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV001BT, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BB, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BT, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BB, 512 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BT, 512 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BB, 1024 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BT, 1024 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV040B, 512 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV081B, 1024 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002B, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002T, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29040B, 512 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Atmel AT29C512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C010A, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C020, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C040A, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Atmel AT49BV512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F002(N), 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F002(N)T, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49(H)F010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F020, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Atmel AT49F080, 1024 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Atmel AT49F080T, 1024 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Catalyst CAT28F512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Bright BM29F040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for ESMT F49B002UA, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F002(A)(N)B, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F002(A)(N)T, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29LV640B, 8192 kB: probe_en29lv640b: id1 0x0000, id2 0x0000 Probing for Fujitsu MBM29F004BC, 512 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F004TC, 512 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F400BC, 512 kB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for Fujitsu MBM29F400TC, 512 kB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for Hyundai HY29F002T, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Hyundai HY29F002B, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Hyundai HY29F040A, 512 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F001BN/BX-B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F001BN/BX-T, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F002BC/BL/BV/BX-T, 256 kB: probe_82802ab: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F008S3/S5/SC, 512 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-B, 512 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-T, 512 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-B, 512 kB: probe_82802ab: id1 0x25, id2 0x2d, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-T, 512 kB: probe_82802ab: id1 0x25, id2 0x2d, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F001B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F001T, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F002(N)B, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F002(N)T, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F040, 512 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29LV040, 512 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51000B, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51000T, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51400B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for MoselVitelic V29C51400T, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for MoselVitelic V29LC51000, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29LC51001, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29LC51002, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm29F002T, 256 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm29F002B, 256 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV020, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV040, 512 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV512, 64 kB: probe_jedec_common: 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 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Sharp LH28F008BJT-BTLZ1, 1024 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for SST SST28SF040A, 512 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for SST SST29EE010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29LE010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29EE020A, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29LE020, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF010A, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF020A, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST39VF512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF020, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST39VF080, 1024 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Found SST flash chip "SST49LF004A/B" (512 kB, FWH) at physical address 0xfff80000. Lock status for 0x000000 (size 0x010000) is 00, full access Lock status for 0x010000 (size 0x010000) is 00, full access Lock status for 0x020000 (size 0x010000) is 00, full access Lock status for 0x030000 (size 0x010000) is 00, full access Lock status for 0x040000 (size 0x010000) is 00, full access Lock status for 0x050000 (size 0x010000) is 00, full access Lock status for 0x060000 (size 0x010000) is 00, full access Lock status for 0x070000 (size 0x010000) is 00, full access Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002B, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002T/NT, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F040B, 512 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for ST M29F400BB, 512 kB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for ST M29F400BT, 512 kB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for ST M29W010B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29W040B, 512 kB: probe_jedec_common: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for ST M29W512B, 64 kB: probe_jedec_common: 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 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0x25, id2 0x7b, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51001B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51001T, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51002B, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51004B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SyncMOS/MoselVitelic {F,S,V}29C51004T, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SyncMOS/MoselVitelic {S,V}29C31004B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SyncMOS/MoselVitelic {S,V}29C31004T, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for TI TMS29F002RB, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for TI TMS29F002RT, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012-old, 128 kB: Old Winbond W29* probe method disabled because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29C010(M)/W29C011A/W29EE011/W29EE012-old' if you have a board with such a chip. Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C020(C)/W29C022, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C040/P, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39F010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39L010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39L020, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39L040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W49F002U/N, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49F020, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xd2, id2 0xce, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Found SST flash chip "SST49LF004A/B" (512 kB, FWH). Lock status for 0x000000 (size 0x010000) is 00, full access Lock status for 0x010000 (size 0x010000) is 00, full access Lock status for 0x020000 (size 0x010000) is 00, full access Lock status for 0x030000 (size 0x010000) is 00, full access Lock status for 0x040000 (size 0x010000) is 00, full access Lock status for 0x050000 (size 0x010000) is 00, full access Lock status for 0x060000 (size 0x010000) is 00, full access Lock status for 0x070000 (size 0x010000) is 00, full access Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. Reading old flash chip contents... done. Erasing and writing flash chip... Trying erase function 0... 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:EW, 0x03a000-0x03afff:W, 0x03b000-0x03bfff:W, 0x03c000-0x03cfff:W, 0x03d000-0x03dfff:W, 0x03e000-0x03efff:W, 0x03f000-0x03ffff:W, 0x040000-0x040fff:W writing sector at 0xb7ea0000 failed! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 1... 0x000000-0x00ffff:EW, 0x010000-0x01ffff:S, 0x020000-0x02ffff:S, 0x030000-0x03ffff:S, 0x040000-0x04ffff:W writing sector at 0xb7ea0000 failed! Looking for another erase function. No usable erase functions left. FAILED! Uh oh. Erase/write failed. Checking if anything changed. Your flash chip is in an unknown state. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF!

3 2

Getting Flashrom running on OS X v10.9.2 (Mavericks)
by Nicholas Ouimet 27 Feb '14

27 Feb '14

Hi Flashrom community, I'm trying to install Flashrom 0.9.7 on OS X v10.9.2 and I download the source, and then use terminal commands cd make AND I get an error Checking for libpci headers... .test.c:3:10: fatal error: 'pci/pci.h' file not found #include <pci/pci.h> So I read that I need to install PCUtils, and again, using the cd and then make, I get an error 192:~ ouimetnick$ cd /Users/ouimetnick/Desktop/flashrom/pciutils-3.1.9 192:pciutils-3.1.9 ouimetnick$ make /Applications/Xcode.app/Contents/Developer/usr/bin/make -C lib all make[1]: *** No rule to make target `/System/Library/Frameworks/ApplicationServices.framework/Headers/ApplicationServices.h', needed by `DirectHW.o'. Stop. make: *** [lib/libpci.a] Error 2 192:pciutils-3.1.9 ouimetnick$ How do I fix and install this? Also, DirectHW needs to be installed, and when attempting to install that (using the cd, and then make command), I get the following ** BUILD FAILED ** The following build commands failed: CompileC build/DirectHW.build/Release/KEXT.build/Objects-normal/i386/DirectHW.o DirectHW.cpp normal i386 c++ com.apple.compilers.llvm.clang.1_0.compiler (1 failure) make: *** [build] Error 65 192:DirectHW ouimetnick$ Could anyone offer some help? I want to get Flashrom running so I can use my Bus Pirate. Thanks, Nick ouimetnick(a)gmail.com

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom