flashrom May 2014

flashrom@flashrom.org

46 participants
188 discussions

[PATCH] Add support for nforce1 chipset flash enable
by Marcin Kościelnicki 03 May '14

03 May '14

Signed-Off-By: Marcin Kościelnicki <koriakin(a)0x04.net> Index: chipset_enable.c =================================================================== --- chipset_enable.c (revision 1764) +++ chipset_enable.c (working copy) @@ -1075,6 +1075,15 @@ return 0; } +static int enable_flash_nvidia_nforce(struct pci_dev *dev, const char *name) +{ + rpci_write_byte(dev, 0x7a, 0); + if (enable_flash_nvidia_common(dev, name)) + return ERROR_NONFATAL; + else + return 0; +} + static int enable_flash_nvidia_nforce2(struct pci_dev *dev, const char *name) { rpci_write_byte(dev, 0x92, 0); @@ -1417,6 +1426,7 @@ {0x10de, 0x00e0, OK, "NVIDIA", "NForce3", enable_flash_nvidia_nforce2}, /* Slave, should not be here, to fix known bug for A01. */ {0x10de, 0x00d3, OK, "NVIDIA", "CK804", enable_flash_ck804}, + {0x10de, 0x01b2, OK, "NVIDIA", "NForce", enable_flash_nvidia_nforce}, {0x10de, 0x0260, OK, "NVIDIA", "MCP51", enable_flash_ck804}, {0x10de, 0x0261, NT, "NVIDIA", "MCP51", enable_flash_ck804}, {0x10de, 0x0262, NT, "NVIDIA", "MCP51", enable_flash_ck804},

3 2

AN-M2HD(MCP68): flashrom -V
by Vinarz Balázs 03 May '14

03 May '14

Dear Developer! Heres the outputs of the Abit AN-M2HD board. I cant wrote the Winbod chip. xubuntu@xubuntu:~/Desktop$ sudo flashrom -p internal -Eflashrom v0.9.6.1-r1563 on Linux 3.13.0-8-generic (x86_64)flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK.Found chipset "NVIDIA MCP67". Enabling flash write... This chipset is not really supported yet. Guesswork...Please send the output of "flashrom -V" to flashrom(a)flashrom.org withyour board name: flashrom -V as the subject to help us finish support for yourchipset. Thanks.OK.Found Winbond flash chip "W39V040B" (512 kB, LPC) at physical address 0xfff80000.Erasing and writing flash chip... Erase/write done.xubuntu@xubuntu:~/Desktop$ sudo flashrom -p internal -w JN.BIN flashrom v0.9.6.1-r1563 on Linux 3.13.0-8-generic (x86_64)flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK.Found chipset "NVIDIA MCP67". Enabling flash write... This ch ipset is not really supported yet. Guesswork...Please send the output of "flashrom -V" to flashrom(a)flashrom.org withyour board name: flashrom -V as the subject to help us finish support for yourchipset. Thanks.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... writing sector at 0x7fd89382a000 failed!Reading current flash chip contents... done. writing sector at 0x7fd89382a000 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 re boot or simply leave the machine running.xub! untu@xubuntu:~/Desktop$ sudo flashrom -p internal -Vflashrom v0.9.6.1-r1563 on Linux 3.13.0-8-generic (x86_64)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 endianCommand line (3 args): flashrom -p internal -VCalibrating delay loop... OS timer resolution is 1 usecs, 388M loops per second, delay more than 10% too short (got 65% of expected delay), recalculating... 494M loops per second, delay more than 10% too short (got 84% of expected delay), recalculating... 509M loops per second, delay more than 10% too short (got 86% of expected delay), recalculating... 457M loops per second, delay more than 10% too short (got 77% of expected delay), recalculating... 511M loops per second, delay loop is unreliable, trying to continue 10 myus = 9 us, 100 myus = 86 us, 1000 myus = 852 us, 10000 myus = 8542 us, 4 myus = 5 us, OK.Initializing internal programmerNo coreboot table found.DMI string system-manufacturer: " ."DMI string system-product-name: "."DMI string system-version: "Unknow"DMI string baseboard-manufacturer: "http://www.abit.com.tw/"DMI string baseboard-product-name: "AN-M2HD(MCP68)"DMI string baseboard-version: "1.x "DMI string chassis-type: "Desktop"Found chipset "NVIDIA MCP67" with PCI ID 10de:0548. 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 0Flash bus type is LPCFound SMBus device 10de:0542 at 00:01:1MCP SPI BAR is at 0xfec80000Strange. MCP SPI BAR is valid, but chipset apparently doesn't have SPI enabled.Please send the output of "flashrom -V" to flashrom(a)flashrom.org withyour board name: flashrom -V as the subject to help us finish support for yourchipset. Thanks.OK.The following protocols are supported: LPC.Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content! Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54Probing 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 contentProbing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for ST M50FLW040B, 5 12 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54Found Winbond flash chip "W39V040B" (512 kB, LPC) at physical address 0xfff80000.Lockout bits:Hardware bootblock locking (#TBL) is active.Hardware remaining chip locking (#WP) is active..Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for Winb ond W39V080A, 1024 kB: probe_jedec_common: id1 0xff, ! id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xda, id2 0x54Found Winbond flash chip "W39V040B" (512 kB, LPC).No operations were specified.Restoring PCI config space for 00:01:0 reg 0x6dRestoring PCI config space for 00:01:0 reg 0x90Restoring PCI config space for 00:01:0 reg 0x8cRestoring PCI config space for 00:01:0 reg 0x88xubuntu@xubuntu:~/Desktop$ Thans

2 1

Support for MX25L12835F
by Tony Li 03 May '14

03 May '14

Hi, Has anyone done support for an MX25L12835F? Thanks, Tony

2 5

Re: [flashrom] Flashrom work with motherboard ASUS M3N-H/HDMI
by Stefan Tauner 03 May '14

03 May '14

On Wed, 5 Mar 2014 13:57:17 +0100 Franc SERRES <sefran007(a)gmail.com> wrote: > Hi > > I'm correctly flashing my motherboard ASUS M3N-H/HDMI for upgrading to a > new official ASUS BIOS under Kubuntu 13.10. > > I join a tar.gz file with all results of manipulations how it's ask by this > software. > > Thank's for your great Jobs guy > Hello Franc, thanks for your report! I have added your board to our list of supported hardware and will commit that later together with other small changes. Please don't send firmware images to the list in the future. They are copyrighted... Also you might be interesting in the -o switch that creates a verbose log file (as alternative to redirecting stdout and stderr with > stuff). -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

[PATCH] Support for S25FL164K/S25FL132K
by Nikolay Martynov 03 May '14

03 May '14

* Updated according to manufacturers datasheet (to the best of my abilities to read it) * Tested with actual S25FL164K via arduino spi Signed-off-by: Nikolay Martynov <mar.kolya(a)gmail.com> --- flashchips.c | 72 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ flashchips.h | 3 +++ 2 files changed, 75 insertions(+) diff --git a/flashchips.c b/flashchips.c index a6db11e..3347e4e 100644 --- a/flashchips.c +++ b/flashchips.c @@ -9451,6 +9451,78 @@ const struct flashchip flashchips[] = { { .vendor = "Spansion", + .name = "S25FL132K", + .bustype = BUS_SPI, + .manufacture_id = SPANSION_ID, + .model_id = SPANSION_S25FL132K, + .total_size = 4096, + .page_size = 256, + /* OTP: 1024B total, 256B reserved; read 0x48; write + * 0x42, erase 0x44 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = { + { + .eraseblocks = { {4 * 1024, 1024} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {64 * 1024, 64} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { { 4096 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { { 4096 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_default_bp3, + .unlock = spi_disable_blockprotect_bp3_srwd, /* #WP pin write-protects SRWP bit. */ + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B), dual I/O (0x3B) supported */ + .voltage = {2700, 3600}, + }, + + { + .vendor = "Spansion", + .name = "S25FL164K", + .bustype = BUS_SPI, + .manufacture_id = SPANSION_ID, + .model_id = SPANSION_S25FL164K, + .total_size = 8192, + .page_size = 256, + /* OTP: 1024B total, 256B reserved; read 0x48; write + * 0x42, erase 0x44 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = { + { + .eraseblocks = { {4 * 1024, 2048} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {64 * 1024, 128} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { { 8192 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { { 8192 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_default_bp3, + .unlock = spi_disable_blockprotect_bp3_srwd, /* #WP pin write-protects SRWP bit. */ + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B), dual I/O (0x3B) supported */ + .voltage = {2700, 3600}, + }, + + { + .vendor = "Spansion", .name = "S25FL128S......0", /* uniform 256kB sectors */ .bustype = BUS_SPI, .manufacture_id = SPANSION_ID, diff --git a/flashchips.h b/flashchips.h index e6e5e8a..b0d64be 100644 --- a/flashchips.h +++ b/flashchips.h @@ -565,6 +565,9 @@ #define SPANSION_S25FL204 0x4013 #define SPANSION_S25FL208 0x4014 #define SPANSION_S25FL216 0x4015 /* Same as S25FL216K, but the latter supports OTP, 3 status regs, quad I/O, SFDP etc. */ +#define SPANSION_S25FL132K 0x4016 +#define SPANSION_S25FL164K 0x4017 + /* * SST25 chips are SPI, first byte of device ID is memory type, second * byte of device ID is related to log(bitsize) at least for some chips. -- 1.8.3.2

2 2

raspberry pi as lpc programmer
by goran metlic 03 May '14

03 May '14

Hi I'm not proficient in programming and have used before available information about flashing bios chips. I have flashed SPI bios using flashrom and RPI. Now I need to flash LPC chip - SST49LF080A. I don't have access to programmer that can program this chip but i was wandering what needs to be done to enable raspberry pi to flash this type of chips. I have seen programmer using Atmel chip so i wanted to know if something can be changed on raspberry pi side to enable LPC flashing (or parallel for that matter). I'm willing to experiment with raspberry pi and LPC / parallel chips. Kind Regards Goran Metlic

2 1

Flashrom very slow to erase chip
by anthony enos 03 May '14

03 May '14

I am using Dediprog programmer and currently using 8192 kB SPI Winbond "W25Q64.W" chip. Currently my time to erase chip is in excess of 10 mins. On the programmer i can see it is working in 4 KB chunks at about 4 chunks per second. So very roughly 16 KB/s. Is this right? Is there any way to erase a chip faster. Any insight on this matter would be greatly appreciated. Regards, Anthony Enos

2 1

issue with Micron N25Q128
by Shih-Chieh Huang 03 May '14

03 May '14

Hi, I am having problem programing N25Q128 using flashrom0.9.7. I got the following errors from erasing address at 0x83f000. I have tried different boards and they failed at the same locations. There are three versions of N25Q128, uniform, top, and bottom. Only the 8 first/last sectors of top/bottom version supports subsector erase. But, from N25Q128 configuration in flashchip.c, it first tries SSE (0x20) for the entire chip. Could it be the problem? Is there a fix for this? Thank you very much. Found Micron/Numonyx/ST flash chip "N25Q128..3E" (16384 kB, SPI). This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). Block protection is disabled. 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..... <skip some subsector erase messages..... > 0x774000-0x774fff:S, 0x775000-0x775fff:S, 0x776000-0x776fff:S, 0x777000-0x777fff:S, 0x778000-0x778fff:S, 0x779000-0x779fff:S, 0x77a000-0x77afff:S, 0x77b000-0x77bfff:S, 0x77c000-0x77cfff:S, 0x77d000-0x77dfff:S, 0x77e000-0x77efff:S, 0x77f000-0x77ffff:S, 0x780000-0x780fff:S, 0x781000-0x781fff:S, 0x782000-0x782fff:S, 0x783000-0x783fff:S, 0x784000-0x784fff:S, 0x785000-0x785fff:S, 0x786000-0x786fff:S, 0x787000-0x787fff:S, 0x788000-0x788fff:S, 0x789000-0x789fff:S, 0x78a000-0x78afff:S, 0x78b000-0x78bfff:S, 0x78c000-0x78cfff:S, 0x78d000-0x78dfff:S, 0x78e000-0x78efff:S, 0x78f000-0x78ffff:S, 0x790000-0x790fff:S, 0x791000-0x791fff:S, 0x792000-0x792fff:S, 0x793000-0x793fff:S, 0x794000-0x794fff:S, 0x795000-0x795fff:S, 0x796000-0x796fff:S, 0x797000-0x797fff:S, 0x798000-0x798fff:S, 0x799000-0x799fff:S, 0x79a000-0x79afff:S, 0x79b000-0x79bfff:S, 0x79c000-0x79cfff:S, 0x79d000-0x79dfff:S, 0x79e000-0x79efff:S, 0x79f000-0x79ffff:S, 0x7a0000-0x7a0fff:S, 0x7a1000-0x7a0 (payload length was 64). spi_nbyte_program failed during command execution at address 0x83f000 Reading current flash chip contents... done. Looking for another erase function. Trying erase function 1... 0x000000-0x00ffff:S, 0x010000-0x01ffff:S, 0x020000-0x02ffff:S, 0x030000-0x03ffff:S, 0x040000-0x04ffff:S, 0x050000-0x05ffff:S, 0x060000-0x06ffff:S, 0x070000-0x07ffff:S, 0x080000-0x08ffff:S, 0x090000-0x09ffff:S, 0x0a0000-0x0affff:S, 0x0b0000-0x0bffff:S, 0x0c0000-0x0cffff:S, 0x0d0000-0x0dffff:S, 0x0e0000-0x0effff:S, 0x0f0000-0x0fffff:S, 0x100000-0x10ffff:S, 0x110000-0x11ffff:S, 0x120000-0x12ffff:S, 0x130000-0x13ffff:S, 0x140000-0x14ffff:S, 0x150000-0x15ffff:S, 0x160000-0x16ffff:S, 0x170000-0x17ffff:S, 0x180000-0x18ffff:S, 0x190000-0x19ffff:S, 0x1a0000-0x1affff:S, 0x1b0000-0x1bffff:S, 0x1c0000-0x1cffff:S, 0x1d0000-0x1dffff:S, 0x1e0000-0x1effff:S, 0x1f0000-0x1fffff:S, 0x200000-0x20ffff:S, 0x210000-0x21ffff:S, 0x220000-0x22ffff:S, 0x230000-0x23ffff:S, 0x240000-0x24ffff:S, 0x250000-0x25ffff:S, 0x260000-0x26ffff:S, 0x270000-0x27ffff:S, 0x280000-0x28ffff:S, 0x290000-0x29ffff:S, 0x2a0000-0x2affff:S, 0x2b0000-0x2bffff:S, 0x2c0000-0x2cffff:S, 0x2d0000-0x2dffff:S, 0x2e0000-0x2effff:S, 0x2f0000-0x2fffff:S, 0x300000-0x30ffff:S, 0x310000-0x31ffff:S, 0x320000-0x32ffff:S, 0x330000-0x33ffff:S, 0x340000-0x34ffff:S, 0x350000-0x35ffff:S, 0x360000-0x36ffff:S, 0x370000-0x37ffff:S, 0x380000-0x38ffff:S, 0x390000-0x39ffff:S, 0x3a0000-0x3affff:S, 0x3b0000-0x3bffff:S, 0x3c0000-0x3cffff:S, 0x3d0000-0x3dffff:S, 0x3e0000-0x3effff:S, 0x3f0000-0x3fffff:S, 0x400000-0x40ffff:S, 0x410000-0x41ffff:S, 0x420000-0x42ffff:S, 0x430000-0x43ffff:S, 0x440000-0x44ffff:S, 0x450000-0x45ffff:S, 0x460000-0x46ffff:S, 0x470000-0x47ffff:S, 0x480000-0x48ffff:S, 0x490000-0x49ffff:S, 0x4a0000-0x4affff:S, 0x4b0000-0x4bffff:S, 0x4c0000-0x4cffff:S, 0x4d0000-0x4dffff:S, 0x4e0000-0x4effff:S, 0x4f0000-0x4fffff:S, 0x500000-0x50ffff:S, 0x510000-0x51ffff:S, 0x520000-0x52ffff:S, 0x530000-0x53ffff:S, 0x540000-0x54ffff:S, 0x550000-0x55ffff:S, 0x560000-0x56ffff:S, 0x570000-0x57ffff:S, 0x580000-0x58ffff:S, 0x590000-0x59ffff:S, 0x5a0000-0x5affff:S, 0x5b0000-0x5bffff:S, 0x5c0000-0x5cffff:S, 0x5d0000-0x5dffff:S, 0x5e0000-0x5effff:S, 0x5f0000-0x5fffff:S, 0x600000-0x60ffff:S, 0x610000-0x61ffff:S, 0x620000-0x62ffff:S, 0x630000-0x63ffff:S, 0x640000-0x64ffff:S, 0x650000-0x65ffff:S, 0x660000-0x66ffff:S, 0x670000-0x67ffff:S, 0x680000-0x68ffff:S, 0x690000-0x69ffff:S, 0x6a0000-0x6affff:S, 0x6b0000-0x6bffff:S, 0x6c0000-0x6cffff:S, 0x6d0000-0x6dffff:S, 0x6e0000-0x6effff:S, 0x6f0000-0x6fffff:S, 0x700000-0x70ffff:S, 0x710000-0x71ffff:S, 0x720000-0x72ffff:S, 0x730000-0x73ffff:S, 0x740000-0x74ffff:S, 0x750000-0x75ffff:S, 0x760000-0x76ffff:S, 0x770000-0x77ffff:S, 0x780000-0x78ffff:S, 0x790000-0x79ffff:S, 0x7a0000-0x7affff:S, 0x7b0000-0x7bffff:S, 0x7c0000-0x7cffff:S, 0x7d0000-0x7dffff:S, 0x7e0000-0x7effff:S, 0x7f0000-0x7fffff:S, 0x800000-0x80ffff:S, 0x810000-0x81ffff:S, 0x820000-0x82ffff:S, 0x830000-0x83ffff:WTransaction error! SSFS: SCIP=0, FDONE=1, FCERR=1, AEL=0 SSFC: SCGO=0, ACS=1, SPOP=0, COP=0, DBC=63, SME=0, SCF=0 Running OPCODE 0x02 failed at address 0x83f000 (payload length was 64). spi_nbyte_program failed during command execution at address 0x83f000 Reading current flash chip contents... done. Looking for another erase function. Trying erase function 2... 0x000000-0xffffff:WTransaction error! SSFS: SCIP=0, FDONE=1, FCERR=1, AEL=0 SSFC: SCGO=0, ACS=1, SPOP=0, COP=0, DBC=63, SME=0, SCF=0 Running OPCODE 0x02 failed at address 0x83f000 (payload length was 64). spi_nbyte_program failed during command execution at address 0x83f000 Looking for another erase function. No usable erase functions left. 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 chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! ------------------------------------------------------------------------------- You may now reboot or simply leave the machine running. Restoring MMIO space at 0x7ff240f028a0 Restoring MMIO space at 0x7ff240f0289c Restoring MMIO space at 0x7ff240f02898 Restoring MMIO space at 0x7ff240f02896 Restoring MMIO space at 0x7ff240f02894 flashchips.c: { .vendor = "Micron/Numonyx/ST", .name = "N25Q128..3E", /* ..3E = 3V, uniform 64KB/4KB blocks/sectors */ .bustype = BUS_SPI, .manufacture_id = ST_ID, .model_id = ST_N25Q128__3E, .total_size = 16384, .page_size = 256, /* supports SFDP */ /* OTP: 64B total; read 0x4B, write 0x42 */ .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, .tested = TEST_OK_PREW, .probe = probe_spi_rdid, .probe_timing = TIMING_ZERO, .block_erasers = { { .eraseblocks = { {4 * 1024, 4096 } }, .block_erase = spi_block_erase_20, }, { .eraseblocks = { {64 * 1024, 256} }, .block_erase = spi_block_erase_d8, }, { .eraseblocks = { {16384 * 1024, 1} }, .block_erase = spi_block_erase_c7, } }, Thanks, Cliff

2 3

Re: [flashrom] ZOTAC IONITX-A-E: flashrom -V
by Stefan Tauner 03 May '14

03 May '14

Hello Maciej, thanks for your report! I have added your board and your chipset to our list of supported hardware and will commit that later together with other small changes. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] N25Q064A13E
by Stefan Tauner 02 May '14

02 May '14

On Sat, 22 Feb 2014 01:36:00 -0500 Corey Osgood <corey.osgood(a)gmail.com> wrote: > It looks like the windows build of flashrom was broken at some point > so the latest version won't compile for windows (mingw doesn't like > gnu_printf). IIRC that depends on the version... and mingw was forked/reimplemented too. In general the builds are definitely not broken, i686-w64-mingw32-gcc works fine for me. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

← Newer
1
...
11
12
13
14
15
16
17
18
19
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom May 2014