- flashrom - mail.coreboot.org

asus P4P800MX error flash
by E 09 Jun '16

09 Jun '16

root@fe:~/flash# ./flashrom --programmer internal flashrom v0.9.9-r1955 on Linux 3.13.0-38-generic (i686) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... delay loop is unreliable, trying to continue OK. Found chipset "Intel ICH5/ICH5R". Enabling flash write... OK. Found PMC flash chip "Pm49FL004" (512 kB, LPC, FWH) mapped at physical address 0xfff80000. No operations were specified. root@fe:~/flash# ./flashrom --programmer internal -c "Pm49FL004" -w 1003MXAS.rom flashrom v0.9.9-r1955 on Linux 3.13.0-38-generic (i686) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... delay loop is unreliable, trying to continue OK. Found chipset "Intel ICH5/ICH5R". Enabling flash write... OK. Found PMC flash chip "Pm49FL004" (512 kB, LPC, FWH) mapped at physical address 0xfff80000. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x0006c000! Expected=0xff, Found=0x07, failed byte count from 0x0006c000-0x0006cfff: 0xff2 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00060000! Expected=0xff, Found=0xf5, failed byte count from 0x00060000-0x0006ffff: 0x8fc6 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x0000a768! Expected=0xff, Found=0x44, failed byte count from 0x00000000-0x0007ffff: 0x6dda0 ERASE FAILED! Looking for another erase function. No usable erase functions left. FAILED! Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... done. Good, 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. root@fe:~/flash#

1 0

help with flashrom
by Nikos Mixailidis 07 Jun '16

07 Jun '16

hello everybody i need your help i try to flash my bios from my tablet onda v919 i try to backup my current bios with this command: sudo flashrom -p ch341a_spi --read backup.bin and i get this error Calibrating delay loop... OK. Couldn't open device 1a86:5512. Error: Programmer initialization failed. what am i doing wrong? i find this guide to help me https://peejseej.nl/2016/05/flash-an-bricked-onda-v919-air-ch-bios/comment-…

1 0

[PATCH] Add support for Fudan SPI flash chips
by Stefan Tauner 01 Jun '16

01 Jun '16

This includes the following chips: - FM25F005 - FM25F01 - FM25F02 and FM25F02A - FM25F04 and FM25F04A - FM25Q08 - FM25Q16 - FM25Q32 Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> --- flashchips.c | 272 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ flashchips.h | 10 +++ 2 files changed, 282 insertions(+) diff --git a/flashchips.c b/flashchips.c index 40b6b8e..e532168 100644 --- a/flashchips.c +++ b/flashchips.c @@ -5446,6 +5446,278 @@ const struct flashchip flashchips[] = { }, { + .vendor = "Fudan", + .name = "FM25F005", + .bustype = BUS_SPI, + .manufacture_id = FUDAN_ID_NOPREFIX, + .model_id = FUDAN_FM25F005, + .total_size = 64, + .page_size = 256, + /* OTP: 256B total; enter 0x3A */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = { + { + .eraseblocks = { {4 * 1024, 16} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 2} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 1} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {64 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {64 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_bp2_tb_bpl, + .unlock = spi_disable_blockprotect_bp2_srwd, + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B), dual I/O (0x3B) supported */ + .voltage = {2700, 3600}, /* 2.3-2.7V acceptable results in lower performance */ + }, + + { + .vendor = "Fudan", + .name = "FM25F01", + .bustype = BUS_SPI, + .manufacture_id = FUDAN_ID_NOPREFIX, + .model_id = FUDAN_FM25F01, + .total_size = 128, + .page_size = 256, + /* OTP: 256B total; enter 0x3A */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = { + { + .eraseblocks = { {4 * 1024, 32} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 4} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 2} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {128 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {128 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_bp2_tb_bpl, + .unlock = spi_disable_blockprotect_bp2_srwd, + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B), dual I/O (0x3B) supported */ + .voltage = {2700, 3600}, /* 2.3-2.7V acceptable results in lower performance */ + }, + + { + .vendor = "Fudan", + .name = "FM25F02(A)", + .bustype = BUS_SPI, + .manufacture_id = FUDAN_ID_NOPREFIX, + .model_id = FUDAN_FM25F02, + .total_size = 256, + .page_size = 256, + /* OTP: 256B total; enter 0x3A, (A version only:) read ID 0x4B */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = { + { + .eraseblocks = { {4 * 1024, 64} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 8} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 4} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {1024 * 256, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {1024 * 256, 1} }, + .block_erase = spi_block_erase_c7, + }, + }, + .printlock = spi_prettyprint_status_register_bp2_tb_bpl, + .unlock = spi_disable_blockprotect_bp2_srwd, + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B), dual I/O (0x3B) supported */ + .voltage = {2700, 3600}, /* 2.3-2.7V acceptable results in lower performance */ + }, + + { + .vendor = "Fudan", + .name = "FM25F04(A)", + .bustype = BUS_SPI, + .manufacture_id = FUDAN_ID_NOPREFIX, + .model_id = FUDAN_FM25F04, + .total_size = 512, + .page_size = 256, + /* OTP: 256B total; enter 0x3A, (A version only:) read ID 0x4B */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = { + { + .eraseblocks = { {4 * 1024, 128} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 16} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 8} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {1024 * 512, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {1024 * 512, 1} }, + .block_erase = spi_block_erase_c7, + }, + }, + .printlock = spi_prettyprint_status_register_bp2_tb_bpl, + .unlock = spi_disable_blockprotect_bp2_srwd, + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B), dual I/O (0x3B) supported */ + .voltage = {2700, 3600}, + }, + + { + .vendor = "Fudan", + .name = "FM25Q08", + .bustype = BUS_SPI, + .manufacture_id = FUDAN_ID_NOPREFIX, + .model_id = FUDAN_FM25Q08, + .total_size = 1024, + .page_size = 256, + /* supports SFDP */ + /* OTP: 1024B total; read 0x48; write 0x42, erase 0x44, read ID 0x4B */ + /* QPI enable 0x38, disable 0xFF */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP | FEATURE_QPI, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = { + { + .eraseblocks = { {4 * 1024, 256} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 32} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 16} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + }, + }, + .printlock = spi_prettyprint_status_register_bp2_tb_bpl, /* bit6 selects size of protected blocks; TODO: SR2 */ + .unlock = spi_disable_blockprotect_bp2_srwd, + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {2700, 3600}, + }, + + { + .vendor = "Fudan", + .name = "FM25Q16", + .bustype = BUS_SPI, + .manufacture_id = FUDAN_ID_NOPREFIX, + .model_id = FUDAN_FM25Q16, + .total_size = 2048, + .page_size = 256, + /* supports SFDP */ + /* OTP: 1024B total; read 0x48; write 0x42, erase 0x44, read ID 0x4B */ + /* QPI enable 0x38, disable 0xFF */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP | FEATURE_QPI, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = { + { + .eraseblocks = { {4 * 1024, 512} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 64} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 32} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {2 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {2 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_bp2_tb_bpl, /* bit6 selects size of protected blocks; TODO: SR2 */ + .unlock = spi_disable_blockprotect_bp2_srwd, + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {2700, 3600}, + }, + + { + .vendor = "Fudan", + .name = "FM25Q32", + .bustype = BUS_SPI, + .manufacture_id = FUDAN_ID_NOPREFIX, + .model_id = FUDAN_FM25Q32, + .total_size = 4096, + .page_size = 256, + /* supports SFDP */ + /* OTP: 1024B total; read 0x48; write 0x42, erase 0x44, read ID 0x4B */ + /* QPI enable 0x38, disable 0xFF */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP | FEATURE_QPI, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = { + { + .eraseblocks = { {4 * 1024, 1024} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 128} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 64} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {4 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {4 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + }, + }, + .printlock = spi_prettyprint_status_register_bp2_tb_bpl, /* bit6 selects size of protected blocks; TODO: SR2 */ + .unlock = spi_disable_blockprotect_bp2_srwd, + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {2700, 3600}, + }, + + { .vendor = "Fujitsu", .name = "MBM29F004BC", .bustype = BUS_PARALLEL, diff --git a/flashchips.h b/flashchips.h index 9ffb30f..0a65444 100644 --- a/flashchips.h +++ b/flashchips.h @@ -328,6 +328,16 @@ #define FIDELIX_FM25Q32 0x3216 #define FIDELIX_FM25Q64 0x3217 +#define FUDAN_ID 0x7F7F7F7F7F7F7F4A /* Shanghai Fudan Microelectronics resides in bank 8 */ +#define FUDAN_ID_NOPREFIX 0x04 /* Fudan, missing 0x7F prefix */ +#define FUDAN_FM25F005 0x3110 +#define FUDAN_FM25F01 0x3111 +#define FUDAN_FM25F02 0x3112 /* Same as FM25F02A */ +#define FUDAN_FM25F04 0x3113 /* Same as FM25F04A */ +#define FUDAN_FM25Q08 0x4014 +#define FUDAN_FM25Q16 0x4015 +#define FUDAN_FM25Q32 0x4016 + #define FUJITSU_ID 0x04 /* Fujitsu */ #define FUJITSU_MBM29DL400BC 0x0F #define FUJITSU_MBM29DL400TC 0x0C -- Kind regards, Stefan Tauner

1 0

ASRock X99 WS-E BIOS backup fail
by Luis Tirado 30 May '16

30 May '16

Hello, Detection of the flash chip on this board succeeds, however reading flash contents to backup file fails as: Reading flash... Transaction error! SSFS: SCIP=0, FDONE=1, FCERR=1, AEL=0 SSFC: SCGO=0, ACS=0, SPOP=0, COP=1, DBC=63, SME=0, SCF=0 Running OPCODE 0x03 failed at address 0x001000 (payload length was 64). Read operation failed! FAILED. Also, superiotool returns: No Super I/O found Perhaps that's the reason. See attached dumps for any additional details.

1 0

Re: [flashrom] Ideas for implementing support for 2nd status register
by Hatim Kanchwala 29 May '16

29 May '16

On Wednesday 25 May 2016 02:26 AM, David Hendricks wrote: > As Stefan points out, some decisions were made in ChromiumOS to avoid > modifying generic code and (in theory) make upstreaming easier. The > writeprotect stuff is the main example. We can re-visit some of those > decisions and put some code in generic locations if it makes sense to do so. > Thanks for the explanation. Highlighting use cases was helpful in understanding. I shall try to formulate future models based on clear use cases to convey more effectively. > I don't like the idea of using a FEATURE_SR2 bit - It doesn't describe > the functionality it represents in a useful manner IMO. As you point > out, reading SR2 needlessly can slow things down, especially for the > common use case where we only really care about reading the busy bit. Agreed. This was what I had in mind when I mentioned it. > For the write protection use case, the exact layout of the status > registers needs to be taken into account, not just whether SR2 is > present or not since SR2 is not as well standardized. To make matters > more complicated, Gigadevice GD25Q128 even has a 3rd status register > which has a bit that defines the entire write-protection scheme. Also, > some chips such as Spansion S25FS and S25FL series don't use status > registers in the same manner as other chips and instead define a set of > control registers with special opcodes to read/write them. > > Also, as Stefan points out, the status register bits are relevant to 4B > addressing and quad I/O in addition to write protection. The > implementation details are non-uniform. > I looked at the datasheets of the 28 SPI chips supported in flashrom that have multiple status registers. 24 of them have 35h opcode for RDSR2. Atmel(1) and Spansion(2) are complicated. And so is GD25Q128C. > Consequently, I think we need a combination of #2 and #3. For #2, we'll > have functions which read the status registers (but must be careful > since reading SR2 and SR3 aren't standardized AFAIK). For #3 we can > describe the functionality we desire in a reasonably generic way and add > chip-specific helper functions to carry out the task regardless of where > the bits we are interested in reside. I started going in this direction > for ChromiumOS's writeprotect.c, but it's still a work in progress: > https://chromium-review.googlesource.com/#/c/208271/ > https://chromium-review.googlesource.com/#/c/259440/ > https://chromium-review.googlesource.com/#/c/335822/ > https://chromium-review.googlesource.com/#/c/335823/ > So, based on the Chromium OS implementation (along with these patches, 2 of which I had to merge locally), this is the revised model. I agree that a combination of #2 and #3 will offer flexibility and can definitely convey more information. - enum status_register_bits enumerates all possible bits that we have - array of struct status_register_layout as part of struct flashchip - each array represents a status register and each element of array represents the bit (using the enum) - (*read_status)() within struct flashchip taking as argument which status register to read (SR1 or SR2 or SR3) - (*write_status)() within struct flashchip In addition to the above basic elements, we can have - const char *status_register_bit_name[] that has string-ified representation of corresponding bit from enum - array of int status_bit indexed by enum status_register_bits which is populated when corresponding read_status() is called To better convey the model, I have implemented some prototype code. Please have a look at the attached file. And have a look here (http://paste.flashrom.org/view.php?id=2918) for the output. Please ignore the violation of 112-character limit in the attached file. Please let me know your feedback on the model and on the proof-of-concept implementation. I would also love to hear suggestions/advice on the code style and quality. > tl;dr version: Overall I think we should just do the work of > representing the status register bits in a generic way, as you describe > in #3. It will be tedious at first, but many chips will be able to share > the same accessor functions. It's very important to be flexible so that > we don't end up with "square peg in a round hole" over-generalizing and > relying too heavily on if-statements/switch statements (a mistake I made > in the chromiumos sources). > I think a solution to making it less tedious would be to write a script to do as much of the modification as possible, and then manually deal with outliers. Based on comments in flashchips.c, we have 28 chips with more than one status register out of a total of 293 SPI chips (revisions that share definition are not considered different). Intuitively I think it best to roll out this feature in phases such that until the final phase, current (vanilla) flashrom behaviour exists in parallel. > On Tue, May 24, 2016 at 2:07 AM, Stefan Tauner > <stefan.tauner(a)alumni.tuwien.ac.at > <mailto:stefan.tauner@alumni.tuwien.ac.at>> wrote: > > On Tue, 24 May 2016 12:49:51 +0530 > Hatim Kanchwala <hatim(a)hatimak.me <mailto:hatim@hatimak.me>> wrote: > > > Hi, > > > > The GSoC coding period has started and I have been working on my > first > > sub-project, adding support for 2nd status register. Most supported > > chips that have multiple registers (around 80%) have opcode 0x35 for > > reading SR2 and, opcode 0x01 for writing SR2. I have developed 3 > models > > and would like to have some feedback on them. > > > > 1. Integrate read/write SR2 with existing functions > > PROPOSAL - > > - Define a feature bit FEATURE_SR2 > > - spi_read_status_register(), defined in spi25_statusreg.c, > additionally > > reads second status register depending on FEATURE_SR2 bit for > that flash > > - Change return to uint16_t for spi_read_status_register() > > - spi_write_status_register_flag(), defined in spi25_statusreg.c, > > considers higher byte of status to write to SR2, depending on > > FEATURE_SR2 bit for that flash. > > MERITS - > > - Fits in elegantly with existing implementation (IMO). Most code in > > flashrom stores status reads/writes in int, which can easily > accommodate > > the 16 bits > > - Very little hassle when editing struct flashchip in flashchips.c > > > > DEMERITS - > > - RDSR will take more time - will read SR2 even if not needed > > > > 2. Define separate functions to read/write SR2 > > PROPOSAL - > > - Define spi_read_status_register2() to read only SR2 > > - Define spi_write_status_register2_flag() and > > spi_write_status_register2() to write to SR2. This will read SR1 > first, > > then (SR2 << 8 | SR1) will be written using WRSR > > > > MERITS - > > - Flexibility (as compared to 1.) > > > > DEMERITS - > > - Need to write more lines (compared to 1.) when dealing with struct > > flashchip > > > > 3. struct status_register_layout > > The ChromiumOS fork defines a struct status_register_layout in > > writeprotect.c, which contains only BP and SRP bits' information. > > PROPOSAL - > > Do a similar flashrom-wide definition, which contains all status > > register bits' information. > > > > MERITS - > > - Very detailed representation of information > > > > DEMERITS - > > - Too much work when adding support for new chips > > - Overhaul of existing infrastructure > > > > IMHO, the first model is the best among these 3. I would like to know > > what you guys think about these, whether you have some new idea. > Looking > > forward to your feedback. Thanks for your time. > > Hi, > > thanks Hatim for this summary. It may make sense if David could sum up > the rationales behind the chromiumos implementation. AFAIK much of that > is driven by the desire to not touch flashchips.c to ease later > upstreaming. A more detailed explanation might help Hatim. > > What I miss from Hatim's proposals is how use cases affect the various > implementations. The main question that needs to be addressed before > implementing any kind of infrastructure like this is: what do we want > to do with it once it is there. > > Till now (vanilla) flashrom did only access the status registers for > gathering (and printing) the status, especially the write protection > bits, and for unlocking said bits. > In the future we want to at least be able to set various protections > additionally. What else do we need? Some bits are relevant to 4B > addressing and Quad I/O too for example... > > -- > Kind regards/Mit freundlichen Grüßen, Stefan Tauner > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org <mailto:flashrom@flashrom.org> > https://www.flashrom.org/mailman/listinfo/flashrom > > > > > -- > David Hendricks (dhendrix) > Systems Software Engineer, Google Inc. Thanks for your time. Bye, Hatim

3 4

Hi I'm Johnny can the usb jtag nt or usb jtag work with flashrom
by LONGJON CREATIONS 27 May '16

27 May '16

Hiya there I would like to know if the usb jtag nt can work with flashrom if so how or what device name would I use or can use give me an examplecommand I also have the first usb jtag not nt as well I'm using debian stretchthese are my hardware info per device below thank you in advance ☺ usb jtag nt ID 04b4:8613 Cypress Semiconductor Corp. CY7C68013 EZ-USB FX2 USB 2.0 Development Kit usb jtag ID 0547:2131 Anchor Chips, Inc. AN2131 EZUSB Microcontroller

1 0

i350 support in flashrom test results
by Olliver Schinagl 25 May '16

25 May '16

I just applied Stefan's patch [0] to the march master of flashrom and tested it on a Winyao WYI350T dual intel NIC: 04:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01) and successfully found a flash chip: Found Micron/Numonyx/ST flash chip "M25P40" (512 kB, SPI) on nicintel_spi. After dumping the firmware, writing a new iPXE rom everything seems to work: Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED. /tmp/bootutil64e -nic 1 1 2C534A012460 4:00.0 Gigabit YES PXE Enabled 15.9.253 Just gotta figure out how to append pxe and uefi images now :) Olliver [0] http://patchwork.coreboot.org/patch/4394/

1 0

I do nothing in hardward, but appear a problem, hope you can do it , thanks!
by 李晓伟 25 May '16

25 May '16

flashrom v0.9.9-unknown on MS-DOS 7 (i686) flashrom was built with libpci 3.1.5, GCC 4.9.2, little endian Command line (7 args): c:/flashrom/bin/flashrom.exe -p internal -V -w intel.bin -o li6.txt Calibrating delay loop... OS timer resolution is 60000 usecs, 398M loops per second, 10 myus = 0 us, 100 myus = 0 us, 1000 myus = 0 us, 10000 myus = 0 us, 240000 myus = 270000 us, OK. Initializing internal programmer Error accessing low megabyte, 0x100000 bytes at 0x00000000 dpmi mmap failed: No such file or directory (ENOENT) Failed getting access to coreboot low tables. Using Internal DMI decoder. Error accessing DMI, 0x10000 bytes at 0x000f0000 dpmi mmap failed: No such file or directory (ENOENT) Found chipset "VIA VT8237(R)" with PCI ID 1106:3227. Enabling flash write... OK. The following protocols are supported: Non-SPI. Probing for AMD Am29F010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for AMD Am29F010A/B, 128 kB: probe_jedec_common: id1 0xe2, id2 0x26, 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 0x88, id2 0xfe, 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 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F016D, 2048 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for AMD Am29F040B, 512 kB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F080, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F080B, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV001BB, 128 kB: probe_jedec_common: id1 0xe2, id2 0x26, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV001BT, 128 kB: probe_jedec_common: id1 0xe2, id2 0x26, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BB, 256 kB: probe_jedec_common: id1 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BT, 256 kB: probe_jedec_common: id1 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BB, 512 kB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BT, 512 kB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BB, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BT, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV040B, 512 kB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV081B, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002B, 256 kB: probe_jedec_common: id1 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002T, 256 kB: probe_jedec_common: id1 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29040B, 512 kB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, 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 0xbf, id2 0x60 Probing for Atmel AT29C010A, 128 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Atmel AT29C020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Atmel AT29C040A, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Atmel AT49BV512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Atmel AT49F002(N), 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Atmel AT49F002(N)T, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Atmel AT49(H)F010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Atmel AT49F020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Atmel AT49F040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Atmel AT49F080, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F080T, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Catalyst CAT28F512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Bright BM29F040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for ESMT F49B002UA, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Eon EN29F010, 128 kB: probe_jedec_common: id1 0xe2, id2 0x26, 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 0x88, id2 0xfe, 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 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29LV040(A), 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Eon EN29LV640B, 8192 kB: probe_en29lv640b: id1 0xffff, id2 0x00ff Probing for Eon EN29GL064(A)B, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Eon EN29GL064(A)T, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Eon EN29GL064H/L, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Eon EN29GL128, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Fujitsu MBM29F004BC, 512 kB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F004TC, 512 kB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F400BC, 512 kB: probe_jedec_common: id1 0x4e, id2 0x50, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F400TC, 512 kB: probe_jedec_common: id1 0x4e, id2 0x50, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29LV160BE, 2048 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29LV160TE, 2048 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Hyundai HY29F002T, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Hyundai HY29F002B, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Hyundai HY29F040A, 512 kB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F001BN/BX-B, 128 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Intel 28F001BN/BX-T, 128 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Intel 28F002BC/BL/BV/BX-T, 256 kB: probe_82802ab: id1 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F008S3/S5/SC, 512 kB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-B, 512 kB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-T, 512 kB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-B, 512 kB: probe_82802ab: id1 0x4e, id2 0x50, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-T, 512 kB: probe_82802ab: id1 0x4e, id2 0x50, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ISSI IS29GL064B, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for ISSI IS29GL064T, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for ISSI IS29GL064H/L, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for ISSI IS29GL128H/L, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29F001B, 128 kB: probe_jedec_common: id1 0xe2, id2 0x26, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F001T, 128 kB: probe_jedec_common: id1 0xe2, id2 0x26, 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 0x88, id2 0xfe, 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 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F022(N)B, 256 kB: probe_jedec_common: id1 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F022(N)T, 256 kB: probe_jedec_common: id1 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F040, 512 kB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29GL320EB, 4096 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29GL320ET, 4096 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29GL320EH/L, 4096 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29GL640EB, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29GL640ET, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29GL640EH/L, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29GL128F, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Macronix MX29LV040, 512 kB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51000B, 64 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for MoselVitelic V29C51000T, 64 kB: probe_jedec_common: id1 0xbf, id2 0x60 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 0xbf, id2 0x60 Probing for MoselVitelic V29LC51001, 128 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for MoselVitelic V29LC51002, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for PMC Pm29F002T, 256 kB: Chip lacks correct probe timing information, using default 10ms/40us. probe_jedec_common: id1 0x88, id2 0xfe, 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 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV010, 128 kB: probe_jedec_common: id1 0xe2, id2 0x26, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV020, 256 kB: probe_jedec_common: id1 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV040, 512 kB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV512, 64 kB: probe_jedec_common: id1 0xbb, id2 0xb3, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Sharp LH28F008BJT-BTLZ1, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST28SF040A, 512 kB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29EE010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST29LE010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST29EE020A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST29LE020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST39SF512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST39SF010A, 128 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST39SF020A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST39SF040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST39VF512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST39VF010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST39VF020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST39VF040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST39VF080, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 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) mapped at physical address 0xfff80000. Lock status for 0x000000 (size 0x010000) is 01, write locked Lock status for 0x010000 (size 0x010000) is 01, write locked Lock status for 0x020000 (size 0x010000) is 01, write locked Lock status for 0x030000 (size 0x010000) is 01, write locked Lock status for 0x040000 (size 0x010000) is 01, write locked Lock status for 0x050000 (size 0x010000) is 01, write locked Lock status for 0x060000 (size 0x010000) is 01, write locked Lock status for 0x070000 (size 0x010000) is 01, write locked Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 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 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 M29F002B, 256 kB: probe_jedec_common: id1 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002T/NT, 256 kB: probe_jedec_common: id1 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F040B, 512 kB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F400BB, 512 kB: probe_jedec_common: id1 0x4e, id2 0x50, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F400BT, 512 kB: probe_jedec_common: id1 0x4e, id2 0x50, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29W010B, 128 kB: probe_jedec_common: id1 0xe2, id2 0x26, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29W040B, 512 kB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29W512B, 64 kB: probe_jedec_common: id1 0xbb, id2 0xb3, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW080, 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 SyncMOS/MoselVitelic {F,S,V}29C51001B, 128 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SyncMOS/MoselVitelic {F,S,V}29C51001T, 128 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SyncMOS/MoselVitelic {F,S,V}29C51002B, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 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 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for TI TMS29F002RT, 256 kB: probe_jedec_common: id1 0x88, id2 0xfe, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C512A/W29EE512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x60 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 0xbf, id2 0x60 Probing for Winbond W29C020(C)/W29C022, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W29C040/P, 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W29GL032CB, 4096 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Winbond W29GL032CT, 4096 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Winbond W29GL032CH/L, 4096 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Winbond W29GL064CB, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Winbond W29GL064CT, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Winbond W29GL064CH/L, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Winbond W29GL128C, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content Probing for Winbond W39F010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39L010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39L020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49F002U/N, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W49F020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xbf, id2 0x60 Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xbf, id2 0x60 Found SST flash chip "SST49LF004A/B" (512 kB, FWH). Lock status for 0x000000 (size 0x010000) is 01, write locked Trying to clear lock for 0x000000... Lock status for 0x000000 (size 0x010000) is 00, full access OK Lock status for 0x010000 (size 0x010000) is 01, write locked Trying to clear lock for 0x010000... Lock status for 0x010000 (size 0x010000) is 00, full access OK Lock status for 0x020000 (size 0x010000) is 01, write locked Trying to clear lock for 0x020000... Lock status for 0x020000 (size 0x010000) is 00, full access OK Lock status for 0x030000 (size 0x010000) is 01, write locked Trying to clear lock for 0x030000... Lock status for 0x030000 (size 0x010000) is 00, full access OK Lock status for 0x040000 (size 0x010000) is 01, write locked Trying to clear lock for 0x040000... Lock status for 0x040000 (size 0x010000) is 00, full access OK Lock status for 0x050000 (size 0x010000) is 01, write locked Trying to clear lock for 0x050000... Lock status for 0x050000 (size 0x010000) is 00, full access OK Lock status for 0x060000 (size 0x010000) is 01, write locked Trying to clear lock for 0x060000... Lock status for 0x060000 (size 0x010000) is 00, full access OK Lock status for 0x070000 (size 0x010000) is 01, write locked Trying to clear lock for 0x070000... Lock status for 0x070000 (size 0x010000) is 00, full access OK 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:EFAILED at 0x00000000! Expected=0xff, Found=0x4e, failed byte count from 0x00000000-0x00000fff: 0xafd ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 1... 0x000000-0x00ffff:EFAILED at 0x00000000! Expected=0xff, Found=0x4e, failed byte count from 0x00000000-0x0000ffff: 0x15fa ERASE FAILED! Looking for another erase function. No usable erase functions left. FAILED! Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... done. Good, 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 PCI config space for 00:11:0 reg 0x59 Restoring PCI config space for 00:11:0 reg 0x40 Restoring PCI config space for 00:11:0 reg 0x41

1 0

Ideas for implementing support for 2nd status register
by Hatim Kanchwala 24 May '16

24 May '16

Hi, The GSoC coding period has started and I have been working on my first sub-project, adding support for 2nd status register. Most supported chips that have multiple registers (around 80%) have opcode 0x35 for reading SR2 and, opcode 0x01 for writing SR2. I have developed 3 models and would like to have some feedback on them. 1. Integrate read/write SR2 with existing functions PROPOSAL - - Define a feature bit FEATURE_SR2 - spi_read_status_register(), defined in spi25_statusreg.c, additionally reads second status register depending on FEATURE_SR2 bit for that flash - Change return to uint16_t for spi_read_status_register() - spi_write_status_register_flag(), defined in spi25_statusreg.c, considers higher byte of status to write to SR2, depending on FEATURE_SR2 bit for that flash. MERITS - - Fits in elegantly with existing implementation (IMO). Most code in flashrom stores status reads/writes in int, which can easily accommodate the 16 bits - Very little hassle when editing struct flashchip in flashchips.c DEMERITS - - RDSR will take more time - will read SR2 even if not needed 2. Define separate functions to read/write SR2 PROPOSAL - - Define spi_read_status_register2() to read only SR2 - Define spi_write_status_register2_flag() and spi_write_status_register2() to write to SR2. This will read SR1 first, then (SR2 << 8 | SR1) will be written using WRSR MERITS - - Flexibility (as compared to 1.) DEMERITS - - Need to write more lines (compared to 1.) when dealing with struct flashchip 3. struct status_register_layout The ChromiumOS fork defines a struct status_register_layout in writeprotect.c, which contains only BP and SRP bits' information. PROPOSAL - Do a similar flashrom-wide definition, which contains all status register bits' information. MERITS - - Very detailed representation of information DEMERITS - - Too much work when adding support for new chips - Overhaul of existing infrastructure IMHO, the first model is the best among these 3. I would like to know what you guys think about these, whether you have some new idea. Looking forward to your feedback. Thanks for your time. Bye, Hatim

3 2

Failed coreboot flash on pixel2
by Richard Weerasinghe 24 May '16

24 May '16

Here is the output: chronos@localhost /tmp $ sudo flashrom -w coreboot-seabios-samus-20160324-coolstar.rom flashrom v0.9.4 : df00e76 : Mar 22 2016 19:53:33 UTC on Linux 3.14.0 (x86_64), built with libpci 3.1.10, GCC 4.9.x-google 20150123 (prerelease), little endian Erasing and writing flash chip... Transaction error! spi_block_erase_20 failed during command execution at address 0x3e0000 ERASE FAILED! Reading current flash chip contents... spi_block_erase_52 failed during command execution at address 0x3e0000 ERASE FAILED! Reading current flash chip contents... Transaction error! spi_block_erase_d8 failed during command execution at address 0x3e0000 ERASE FAILED! Reading current flash chip contents... spi_chip_erase_60 failed during command execution ERASE FAILED! Reading current flash chip contents... spi_chip_erase_c7 failed during command execution ERASE 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) or mail flashrom(a)flashrom.org! ------------------------------------------------------------------------------- You may now reboot or simply leave the machine running. FAILED If you need more info, please let me know. cheers Richard ᐧ

1 0

ft2232_spi JTAGkey OE disabled for CS high
by Ulrich Holeschak 20 May '16

20 May '16

Hello, when using the ft2232_spi driver with Amontec JTAGkey, the OE signal (bit 4) is disabled when de-asserting CS: msg_pspew("De-assert CS#\n"); buf[i++] = SET_BITS_LOW; buf[i++] = cs_bits; buf[i++] = pindir; This means that the CS high signal is floating and the voltage level is unstable. Filtering the OE bit fixes this issue: msg_pspew("De-assert CS#\n"); buf[i++] = SET_BITS_LOW; buf[i++] = cs_bits & 0x0F; // keep OE active buf[i++] = pindir; Regards, Ulrich

1 0

T420 internal flashing: Transactions Error
by Arian Sanusi 18 May '16

18 May '16

Hi All, I'm trying to re-flash coreboot on a T420 that already runs coreboot - the same image that's currently flashed actually. According to coreboot wiki, that should be possible. [1] I think I enabled write-lock of the ME region in coreboot, but I can't find the option, nor the .config line anymore. flashrom: flashrom v0.9.9-r1954 on Linux 4.3.0-1-amd64 (x86_64) coreboot: * master 831d65d intel/apollolake: Fix logic error Can anyone help? Thank you Arian Attached: flashrom output, coreboot .config

1 0

Results for board: MSI MS-7528 G31M3(-F)
by callmeclean 16 May '16

16 May '16

I've successfully read from & written updated BIOS to this motherboard, both verified. The modelling is a bit confusing, there are a few revisions of the board. I can't say for certain, but it seems G31M3 and G31M3-F are the same board. BIOS images from G31M3-F product page work on my board missing the -F (which I can't find any official mention of). Attached are the output of flashrom -p internal -V, lspci -nnvvxxx and superiotool -deV in results1.txt, results2.txt and results3.txt respectively. Please tell me if attachments are not acceptable and I will reply with the full text (the outputs are very long!).

1 0

Re: [flashrom] ENE KB9012 Programming with flashrom
by Joerg Albert 16 May '16

16 May '16

On 01.05.2016 10:37, Paul Kocialkowski wrote: > Hi, > > could you CC the flashrom mailing list in your future responses? This will > probably interest others! I wasn't aware of this mailing lists, thanks! > Le dimanche 24 avril 2016 à 23:15 +0200, Joerg Albert a écrit : >> I'll try to program the internal SPI of a KB9012 (inside a Thinkpad S531) - as >> soon as I've found the correct image and soldered the necessary wires. > The KB9012 chips has an internal flash memory that is distinct from the BIOS' > SPI flash, so beware not to confuse both! I'm aware of this. The S531 manual says, that the system indicator LED shall flash three times when the power supply gets connected (without switching the notebook on). As I don't see this and the voltage at the KB9012 is correct I guess that the EC is not working properly. Flashing the BIOS SPI may be the second step ;-) >> Found your patch here: >> >> http://patchwork.coreboot.org/patch/4325/ >> >> Why couldn't I use FlashDirectAccess? Is this meant to program external SPI >> flash only? > Yes, that's my understanding of it too. It just makes a bridge between the BIOS' > SPI flash and the KB9012 pads. This is because it's often easier to reflash it > using the keyboard connector, that is often available without fully opening the > device. > > What you want if you need to reflash the EC is not FlashDirectAccess, but EDI. > Note that some firmwares explicitly disable it, so you have to ground pin 42 to > enter "test mode", where the 8051 is not running. > > Note that the EDI pins are often exported on the keyboard connector, which makes > soldering more doable. > The keyboard connector of the S531 has a pitch of 0.5mm, too close for my soldering experience. I couldn't find a flex cable matching the connector either, so I went for soldering wires to some vias/testpoints instead. Connected a RaspberryPi and had some problems with the detection of the KB9012. It seemed to detect the KB9012 on every second trial only: -------------- pi@raspberrypi ~ $ flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -c "KB9012 (EDI)" -V flashrom v0.9.9-r1954 on Linux 3.18.11+ (armv6l) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.1.9, GCC 4.6.3, little endian Command line (5 args): flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -c KB9012 (EDI) -V Calibrating delay loop... OS timer resolution is 5 usecs, 229M loops per second, 10 myus = 11 us, 100 myus = 103 us, 1000 myus = 994 us, 10000 myus = 10064 us, 20 myus = 26 us, OK. Initializing linux_spi programmer Using device /dev/spidev0.0 Using 1024 kHz clock The following protocols are supported: SPI. Probing for ENE KB9012 (EDI), 128 kB: probing for EDI EDI: found hw version 195 EDI id 4 Found ENE flash chip "KB9012 (EDI)" (128 kB, SPI) on linux_spi. No operations were specified. pi@raspberrypi ~ $ flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -c "KB9012 (EDI)" -V flashrom v0.9.9-r1954 on Linux 3.18.11+ (armv6l) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.1.9, GCC 4.6.3, little endian Command line (5 args): flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -c KB9012 (EDI) -V Calibrating delay loop... OS timer resolution is 4 usecs, 226M loops per second, 10 myus = 11 us, 100 myus = 102 us, 1000 myus = 1839 us, 10000 myus = 10424 us, 16 myus = 21 us, OK. Initializing linux_spi programmer Using device /dev/spidev0.0 Using 1024 kHz clock The following protocols are supported: SPI. Probing for ENE KB9012 (EDI), 128 kB: probing for EDI EDI: failed to read hw version (-1) No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. pi@raspberrypi ~ $ flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -c "KB9012 (EDI)" -V flashrom v0.9.9-r1954 on Linux 3.18.11+ (armv6l) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.1.9, GCC 4.6.3, little endian Command line (5 args): flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -c KB9012 (EDI) -V Calibrating delay loop... OS timer resolution is 5 usecs, 229M loops per second, 10 myus = 11 us, 100 myus = 102 us, 1000 myus = 994 us, 10000 myus = 10061 us, 20 myus = 22 us, OK. Initializing linux_spi programmer Using device /dev/spidev0.0 Using 1024 kHz clock The following protocols are supported: SPI. Probing for ENE KB9012 (EDI), 128 kB: probing for EDI EDI: found hw version 195 EDI id 4 Found ENE flash chip "KB9012 (EDI)" (128 kB, SPI) on linux_spi. No operations were specified. -------- I've also tried with "speed=2048" (as the KB9012 manual states a minimum clock of 1MHz) - same problem. / /I've added some error/debug printouts and it seems like the KB9012 answers with all-zeros on each second start of the probe. If the buffer content is correct everything else afterwards works fine. So I've added a quick workaround in edi_read_byte() and edi_read() to re-do any read if the buffer contains zero at the first byte. See the patches attached. No idea why it behaves that way, maybe the SPI detection on these pins is a bit shaky? Pin 42 was grounded and the KB9012 remained powered during the whole session. Cheers, Joerg

2 1

BIOS image write and safety
by Nicolas Clerc 13 May '16

13 May '16

Hi guys, I need for a specific project to change BIOS Settings on many computers. So far, I used flashrom to read out the flash memory of my BIOS. Flashrom successfully detects the Winbond W25Q32.V flash, and I can dump the whole 32Mbits. With your experience, do you know if it is *generally* quite safe to write an image that has been dumped (both using flashrom ofc) ? I have been doing several memory dumps of this BIOS flash, each one separated by a reboot, and can see a modification between each dump. I suspect there's a kind of event log or journal that is kept by the BIOS, but I can't find a way to read it (neither BIOS menu nor external software). The BIOS is from AMI. Any advice is welcome, Cheers Nicolas

1 0

SST26VF032B support
by Peter Hall 10 May '16

10 May '16

Hi, I got the flashrom working on a BeagleBone programming a SST26VF032B with some modifications to 0.9.9. Do you want me to upload the modifications? I mostly copied the changes from another post, but I can't remember where that was from and I made some tweaks myself. These changes definitely work, I've test this multiple times on multiple boards. Let me know if you want the source Regards Peter Hall Software Development Manager Raster Vision Ltd. Tel: 01892 722228 / +44 1892 722228. www.rvl.co.uk <http://www.rvl.co.uk/> Raster Vision Ltd is a company registered in England and Wales, number: 02753356. Registered office: Unit 1, Crundalls, Gedges Hill, Matfield, Tonbridge, Kent, TN12 7EA, UK. C2- Restricted

1 0

Re: [flashrom] New SPI NOR Flash product Support
by Victor Lim 10 May '16

10 May '16

Thanks, David, For Gigadevice part numbers, we do keep ID, read, erase, write opcodes, sector protection, and architecture the same. I am wondering if Flashrom program needs to call out the new part numbers so that users know which part number to choose from. Regards, Victor From: David Hendricks [mailto:dhendrix@google.com] Sent: Sunday, May 8, 2016 7:43 PM To: Victor Lim <vlim(a)gigadevice.com> Cc: Hatim Kanchwala <hatim(a)hatimak.me>; flashrom <flashrom(a)flashrom.org>; Katherine (GigaDevice//US) <ksong(a)gigadevice.com> Subject: Re: [flashrom] New SPI NOR Flash product Support Hello Victor, Chips with same ID and read, erase, and write opcodes are supported. For ChromeOS platforms it is also important that new revision chips have identical block protection capabilities as the older parts (I've had difficulties with other vendors regarding this...). On Fri, May 6, 2016 at 4:55 PM, Victor Lim <vlim(a)gigadevice.com <mailto:vlim@gigadevice.com> > wrote: Hi, Hatim, We have new revision chips that share the same ID as the previous revision, will they be considered supported because they share the same basic Erase and program command. New part # GD25LQ64C: manufacturer ID: 0x6017 Currently supported part # GD25LQ64: manufacturer ID: 0x6017 New part # GD25LQ128C: manufacturer ID: 0x6018 Currently supported part # GD25LQ128: manufacturer ID: 0x6018 Do you need new samples for verification? We do keep the same ID for new revision release, so the SW should work for new revision parts. Regards, Victor -----Original Message----- From: Hatim Kanchwala [mailto:hatim@hatimak.me <mailto:hatim@hatimak.me> ] Sent: Friday, March 25, 2016 1:27 PM To: Victor Lim <vlim(a)gigadevice.com <mailto:vlim@gigadevice.com> > Cc: flashrom(a)flashrom.org <mailto:flashrom@flashrom.org> ; ksong(a)gigadevice.com <mailto:ksong@gigadevice.com> Subject: Re: [flashrom] New SPI NOR Flash product Support Hello Victor, I am doing fine, thanks :) The following chips have been tested successfully - GD25D05B/10B, GD25LQ10B/20B/40B/80B, GD25Q21B/41B and GD25VQ41B (reported by David Hendrix). Test logs for the first 8 of these chips can be found here - https://www.flashrom.org/pipermail/flashrom/2016-March/014537.html. The patches for all these chips and additionally GD25Q80C/16C have been sent and are waiting for further review. I have ordered some IC clips, so I will test the remaining chips as soon as those arrive. Unfortunately, one of the chips you explicitly requested support for, GD25Q128C was not included in the samples so was not tested. But support for it has already been added ;) Apologies for the late reply. :) On Tuesday 22 March 2016 01:20 AM, Victor Lim wrote: > Hi, Hatim, > > How are you doing? Hope all the sample test results are good. > Can you please update the status so that I can ask customer to try out. > > Regards, > > Victor > > > > -----Original Message----- > From: Hatim Kanchwala [mailto:hatim@hatimak.me <mailto:hatim@hatimak.me> ] > Sent: Wednesday, February 24, 2016 9:02 AM > To: Victor Lim <vlim(a)gigadevice.com <mailto:vlim@gigadevice.com> > > Cc: flashrom(a)flashrom.org <mailto:flashrom@flashrom.org> ; ksong(a)gigadevice.com <mailto:ksong@gigadevice.com> > Subject: Re: [flashrom] New SPI NOR Flash product Support > > Hello Victor, > > Support for two chips you requested was added some time ago in r1937 > (look here https://tracker.coreboot.org/trac/flashrom/changeset/1937). > I am waiting for samples to perform tests. FedEx was in touch > regarding documents for customs clearance, so delivery should be in a > day or two. In the meanwhile I am working on support for other > GigaDevice chips (http://www.gigadevice.com/product-series/12.html). > > On Wednesday 24 February 2016 04:47 AM, Victor Lim wrote: >> Hi, Hatim, >> >> How is the new program to include these two part #? >> I have sent the samples to you, but they are held up at the Fedex >> facility at New Delhi. >> Can you please give Fedex the instruction for delivery? >> The tracking # is 806824856677 >> >> Regards, >> >> Victor >> >> >> >> >> -----Original Message----- >> From: Victor Lim [mailto:vlim@gigadevice.com <mailto:vlim@gigadevice.com> ] >> Sent: Tuesday, February 9, 2016 3:02 PM >> To: 'Hatim Kanchwala' <hatim(a)hatimak.me <mailto:hatim@hatimak.me> > >> Cc: 'flashrom(a)flashrom.org <mailto:flashrom@flashrom.org> ' <flashrom(a)flashrom.org <mailto:flashrom@flashrom.org> > >> Subject: RE: [flashrom] New SPI NOR Flash product Support >> >> Thanks, Hatim, >> >> Please help me on these two part #s, datasheets are attached. >> 1) GD25VQ41B >> 2) GD25Q128C >> >> Can you provide the ship to address, I will send you same samples. >> What package type do you prefer? >> >> Regards, >> >> Victor >> >> >> >> -----Original Message----- >> From: Hatim Kanchwala [mailto:hatim@hatimak.me <mailto:hatim@hatimak.me> ] >> Sent: Tuesday, February 9, 2016 12:27 PM >> To: Victor Lim <vlim(a)gigadevice.com <mailto:vlim@gigadevice.com> > >> Cc: flashrom(a)flashrom.org <mailto:flashrom@flashrom.org> >> Subject: Re: [flashrom] New SPI NOR Flash product Support >> >> Hello Victor, >> >> I have recently started looking at flashrom and have contributed by >> adding a few SPI flashchip definitions. I would be glad to add >> support for the SPI chips. Usually datasheets are sufficient for >> adding flashchip support (as long as datasheets convey full >> information on functionality). However, the chips remain untested. I >> would be glad to test them as well if you are willing to provide >> samples (I am at a University, so I have access to a lab with equipment for testing). >> >> On Wednesday 10 February 2016 12:18 AM, Victor Lim wrote: >>> Hi, Flashrom team, >>> >>> >>> >>> I am the FAE manager for Gigadevice and would like to know how I can >>> work >> with you to add our part # to your support list. >>> >>> A customer of mine is looking to program our GD25VQ41B with your >>> tool and >> found that it is not supported by your tools. >>> >>> It would like grateful if you can support our entire SPI NOR portfolio. >>> >>> >>> >>> Regards, >>> >>> >>> >>> Victor Lim(Gigadevice/MK IV/FAE Manager) >>> >>> >>> >>> Gigadevice Semiconductor Inc. >>> >>> Tel: 408-855-8336 <tel:408-855-8336> >>> Mobile: 408-883-3856 <tel:408-883-3856> >>> >>> Website: www.gigadevice.com <http://www.gigadevice.com> <http://www.gigadevice.com/> >>> >>> 2975 Bowers Ave,Suite 323 >>> >>> Santa Clara, CA 95051, USA >>> >>> >>> >>> This email was sent to you by GigaDevice, A Global Innovative Memory >> Architect >>> >>> >> --------------------------------------------------------------------- >> - >> ------ >> --------------------------------------------------------------------- >> - >> ------ >> --------------------------------------------------------------------- >> - >> ------ >> --------------------------------------------------------------------- >> - >> ------ >> --------------------------------------------------------------------- >> - >> ------ >> --------------------------------------------------------------------- >> - >> ------ >> --------------------------------------------------------------------- >> - >> ------ >> --------------------------------------------------------------------- >> - >> ------ >> --------------------------------------------------------------------- >> - >> ------ >> --------------------------------------------------------------------- >> - >> ------ >> --------------------------------------------------------------------- >> - >> ------ >> --------------------------------------------------------------------- >> - >> ------ >> --------------------------------------------------------------------- >> - >> ------ >> -- >>> >>> The information contained in this e-mail message (and any attachment >> transmitted herewith) is privileged and confidential and is intended >> for the exclusive use of the addressee(s). If you are not an intended >> addressee, any disclosure, reproduction, distribution or other >> dissemination or use of this communication is strictly prohibited. If >> you have received this communication in error, please delete this >> communication and contact us by replying to this e-mail immediately. >>> >>> >>> >>> >>> >>> _______________________________________________ >>> flashrom mailing list >>> flashrom(a)flashrom.org <mailto:flashrom@flashrom.org> >>> http://www.flashrom.org/mailman/listinfo/flashrom >>> >> > > -- > Kind Regards, > Hatim Kanchwala > http://hatimak.me > B. Tech. Electrical Engineering > Indian Institute of Technology Patna > > -- Kind Regards, Hatim Kanchwala http://hatimak.me B. Tech. Electrical Engineering Indian Institute of Technology Patna _______________________________________________ flashrom mailing list flashrom(a)flashrom.org <mailto:flashrom@flashrom.org> https://www.flashrom.org/mailman/listinfo/flashrom -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

2 1

New SPI NOR Flash product Support
by Victor Lim 09 May '16

09 May '16

Hi, Flashrom team, I am the FAE manager for Gigadevice and would like to know how I can work with you to add our part # to your support list. A customer of mine is looking to program our GD25VQ41B with your tool and found that it is not supported by your tools. It would like grateful if you can support our entire SPI NOR portfolio. Regards, Victor Lim(Gigadevice/MK IV/FAE Manager) Gigadevice Semiconductor Inc. Tel: 408-855-8336 Mobile: 408-883-3856 Website: <http://www.gigadevice.com/> www.gigadevice.com 2975 Bowers Ave,Suite 323 Santa Clara, CA 95051, USA This email was sent to you by GigaDevice, A Global Innovative Memory Architect _____ The information contained in this e-mail message (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this communication in error, please delete this communication and contact us by replying to this e-mail immediately.

4 12

Support
by Pera Peric 08 May '16

08 May '16

As instructed, I'm sending an email with verbose parameter included. The chip in question is w25q64fvsig. Also, please advise if something can be done about flashing with the descriptor locked (other than using an external programmer). Best

1 0

[PATCH 1/2] dediprog: Reimplement target chip option
by Nico Huber 07 May '16

07 May '16

Signed-off-by: Nico Huber <nico.huber(a)secunet.com> --- dediprog.c | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/dediprog.c b/dediprog.c index 019de46..b7276e5 100644 --- a/dediprog.c +++ b/dediprog.c @@ -942,7 +942,7 @@ int dediprog_init(void) int spispeed_idx = 1; int millivolt = 3500; long usedevice = 0; - long target = 1; + long target = FLASH_TYPE_APPLICATION_FLASH_1; int i, ret; spispeed = extract_programmer_param("spispeed"); @@ -1014,7 +1014,18 @@ int dediprog_init(void) free(target_str); return 1; } - msg_pinfo("Using target %li.\n", target); + switch (target) { + case 1: + msg_pinfo("Using target %s.\n", "FLASH_TYPE_APPLICATION_FLASH_1"); + target = FLASH_TYPE_APPLICATION_FLASH_1; + break; + case 2: + msg_pinfo("Using target %s.\n", "FLASH_TYPE_APPLICATION_FLASH_2"); + target = FLASH_TYPE_APPLICATION_FLASH_2; + break; + default: + break; + } } free(target_str); @@ -1073,7 +1084,7 @@ int dediprog_init(void) dediprog_set_leds(LED_ALL); /* Select target/socket, frequency and VCC. */ - if (set_target_flash(FLASH_TYPE_APPLICATION_FLASH_1) || + if (set_target_flash(target) || dediprog_set_spi_speed(spispeed_idx) || dediprog_set_spi_voltage(millivolt)) { dediprog_set_leds(LED_ERROR); -- 2.7.0

2 3

My current libflashrom/layout branch
by Nico Huber 04 May '16

04 May '16

Hi all, this is my current work on layout support and libflashrom. I don't have the time currently to clean it more up / respond to a review, as I will be on vacation for about three weeks. Most things are pretty clean though. So I sent it in, in case anyone wants to look at it or just play with it. One note on layout semantics: It's clear from other patches that there are different concepts of a don't-read-all option. It's either read only the flash parts that are not included (shall be kept intact) or read only those parts that are included (will be changed). I implemented the latter. It's quite useful for systems with a locked ME region.

1 14

GUI for Flashrom in Kodi
by C. Butz 01 May '16

01 May '16

Dear team, Looking for a cheap and reliable flash-programmer, I came across Flashrom and its functionality on Raspberry. In the process of playing around with this combination I discovered Kodi and wrote a GUI for Kodi to use Flashrom there. Source code and additional information can be found @ http://forum.kodi.tv/showthread.php?tid=272150 Let me know if there is any issue with licenses or anything else that requires correction! Thanks & best regards Chris Butz

1 0

Re: [flashrom] Giving to -i option some real use
by Salvador Eduardo Tropea 25 Apr '16

25 Apr '16

Hi Michael: I see your point, and see it can be confusing if the interpretation is changed. What about reading the whole erase regions affected by each interval? (like David points out) I mean this: /** * Look for the starting address of the erase region that contains @addr. * The size of this region is returned in @sz */ int find_page_start(unsigned int addr, struct eraseblock *blocks, unsigned int *sz) { unsigned int page_start, i, size, count, group_size; /* Look for the beggining of the erase region containing start address */ page_start = 0; for (i = 0; i < NUM_ERASEREGIONS; i++) { size = blocks[i].size; count = blocks[i].count; group_size = size * count; if (page_start + group_size > addr) { /* The address is inside one of these erase regions */ *sz = size; return page_start + ((addr - page_start) / size) * size; } else {/* Not here */ page_start += group_size; } } msg_gerr("ERROR: address out of memory!?\n"); exit(1); return -1; } /** * Read all the erase regions containing the @start-@end interval. * Returns the last address fetched in @real_end_p */ int read_pages(struct flashctx *flash, uint8_t *oldcontents, unsigned int start, unsigned int end, unsigned int *real_end_p) { int k; unsigned int real_start, real_end, size; k = find_erase_function(flash); if (k == -1) { msg_gerr("ERROR: No erase function available.\n"); return -1; } real_start = find_page_start(start, flash->chip->block_erasers[k].eraseblocks, &size); msg_gdbg("Start of range 0x%X rounded to page boundary: 0x%X\n", start, real_start); real_end = find_page_start(end, flash->chip->block_erasers[k].eraseblocks, &size); real_end += size - 1; msg_gdbg("End of range 0x%X rounded to page boundary: 0x%X\n", end, real_end); *real_end_p = real_end; return flash->chip->read(flash, oldcontents + real_start, real_start, real_end - real_start + 1); } /** * Fill the @oldcontents buffer with data from the memory. The regions not included by the user are filled * with data from @newcontents instead of the actual memory content. It forces to skip them. * This function is used only when @oldcontents is empty. * Is also mandatory that at least one region was specified by the user. */ int read_cur_content(struct flashctx *flash, uint8_t *oldcontents, const uint8_t *newcontents) { unsigned int start = 0; romentry_t *entry; unsigned int size = flash->chip->total_size * 1024; unsigned int region_end; int ret = 0; /* We will read from memory only the regions indicated by the user. * The rest will contain the same as the newcontents */ memcpy(oldcontents, newcontents, size); /* Catch a missuse */ if (num_include_args == 0) { msg_perr("Internal error! build_old_image() invoked, but no regions specified.\n"); return 1; } /* Non-included romentries are ignored. * The union of all included romentries is fetched from memory. */ while (start < size) { entry = get_next_included_romentry(start); /* No more romentries for remaining region? */ if (!entry) break; /* For included regions, read memory content content. */ msg_gdbg("Read a chunk 0x%06x-0x%06x.\n", entry->start, entry->end); ret = read_pages(flash, oldcontents, entry->start, entry->end, &region_end); if (ret != 0) { msg_gerr("Failed to read chunk 0x%06x-0x%06x.\n", entry->start, entry->end); break; } start = region_end + 1; /* Catch overflow. */ if (!start) break; } return ret; } The find_erase_function() is in flashrom.c and is like this: /* Look for the first valid erase function. Returns -1 if none. */ int find_erase_function(struct flashctx *flash) { int k; msg_cdbg("\nLooking for an erase function.\n"); for (k = 0; k < NUM_ERASEFUNCTIONS; k++) { if (k != 0) msg_cdbg("Looking for another erase function.\n"); msg_cdbg("Trying erase function %i... ", k); if (!check_block_eraser(flash, k, 1)) { msg_cdbg("OK\n"); return k; } msg_cdbg("INVALID\n"); } msg_cdbg("No usable erase functions left.\n"); return -1; } In the case of the range I'm using I get: (with -VV) ... Reading old flash chip contents... Read a chunk 0x000000-0x007e2b. Looking for an erase function. Trying erase function 0... OK Start of range 0x0 rounded to page boundary: 0x0 End of range 0x7E2B rounded to page boundary: 0x7FFF ... In this way we know the content of the blocks that we'll erase. The values look ok, since the first eraser have 4k pages. Note: this code uses the first usable erase function, erase_and_write_flash will try the same eraser. If this eraser fails we will need more data, but in this case erase_and_write_flash reads all the memory again. Regards, SET El 20/04/16 a las 15:23, Michael Karcher escribió: > On 04/20/2016 12:07 PM, Salvador Eduardo Tropea wrote: >> /** >> * Fill the @oldcontents buffer with data from the memory. The regions >> not included by the user are filled >> * with data from @newcontents instead of the actual memory content. >> It forces to skip them. >> * This function is used only when @oldcontents is empty. >> * Is also mandatory that at least one region was specified by the user. >> */ >> >> My intention was to use the same (nasty) tricks that the code already >> uses. By forcing areas to match the rest of the code avoids touching it. > My concern is still valid. The claim "It forces to skip them" appears > wrong. If the area of the new and the old image match, the code tries to > optimize by not touching the area, but there is no guarantee that the > area is indeed untouched. If the old contents of the chip has been read, > flashrom "hides" the fact that it touched an area that did not need to > be touched by reflashing the old contents after erasing. This hiding > breaks down if flashrom doesn't know the real contents. > > Here is an example of what I mean: Assume a flash chip containing four > nibbles (used instead of bytes for presentation purposes; nibbles are > represented in hex digits); the chip contains two independently erasable > areas of two nibbles each, and I use a layout file like this (the erased > state is the nibble value F). > > 0:2 please_flash > 3:3 please_keep > > Assume the flash chip contains 0127, and the new image contains 1230. > Without -A, and selecting the image "please_flash" the following steps > are taken: > > 1) The file is loaded, newcontents is "1230". > 2) ROM contents are read. oldcontents is "0127" > 3) build_new_image/modify_new_image_from_old copies the last nibble from > oldcontents to newcontents, because it is in "please_keep", not in > "please_flash". newcontents is now "1237" > 4) The first two nibbles are erased, because the old value "01" does not > match "12". Now they are "FF" > 5) The first two nibbles are programmed to "12" > 6) The second *two* nibbles are erased because "27" does not match "37". > Now they are "FF" > 7) The second two nibbles are programmed to "37". > The flash chip now contains 1237. > > With -A, the following steps are taken: > > 1) The file is loaded, newcontents is "1230" > 2) read_cur_content loads the first three nibbles from the flash memory, > and takes the last one from newcontents. oldcontents is "0120". > 3) The first two nibbles are erased, because the old value "01" does not > match "12". Now they are "FF" > 4) The first two nibbles are programmed to "12" > 5) The second *two* nibbles are erased because "20" does not match "30". > Now they are "FF" > 6) The second two nibbles are programmed to "30". > The flash chip now contains 1230. > > As you see, the last nibble is modified to "0" instead of being kept at > "7". There might be situations in which it doesn't matter that a nibble > outside of the requested area is changed, but it definitely is different > from how we handled layout files and partial flashing up to now. Note > especially how copying the last nibble (the zero with -A, the 7 without > -A) from newcontents to oldcontents did not force the nibble to be > untouched in either case, but in the first case flashrom knew what to > write so the 7 appears to be unmodified while in fact it was erased and > rewritten. > > Regards, > Michael Karcher > -- Ing. Salvador Eduardo Tropea http://utic.inti.gob.ar/ INTI - Micro y Nanoelectrónica (CMNB) http://www.inti.gob.ar/ Unidad Técnica Sistemas Inteligentes Av. General Paz 5445 Tel: (+54 11) 4724 6300 ext. 6919 San Martín - B1650KNA FAX: (+54 11) 4754 5194 Buenos Aires * Argentina

3 4

Results of "flashrom -V -p internal" on Dell Optiplex 9010
by Przemek Klosowski 25 Apr '16

25 Apr '16

flashrom v0.9.7-r1850 on Linux 4.3.5-300.fc23.x86_64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.3.1, GCC 5.1.1 20150612 (Red Hat 5.1.1-3), little endian Command line (3 args): flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 3871M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 997 us, 10000 myus = 9977 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. Using External DMI decoder. DMI string chassis-type: "Mini Tower" DMI string system-manufacturer: "Dell Inc." DMI string system-product-name: "OptiPlex 9010" DMI string system-version: "01" DMI string baseboard-manufacturer: "Dell Inc." DMI string baseboard-product-name: "0M9KCM" DMI string baseboard-version: "A00" Found chipset "Intel Q77" with PCI ID 8086:1e47. This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... Root Complex Register Block address = 0xfed1c000 GCS = 0xc61: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) Top Swap: not enabled 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 enabled 0xff600000/0xff200000 FWH decode enabled 0xff500000/0xff100000 FWH decode enabled 0xff400000/0xff000000 FWH decode enabled Maximum FWH chip size: 0x100000 bytes SPI Read Configuration: prefetching enabled, caching enabled, BIOS_CNTL = 0x0a: BIOS Lock Enable: enabled, BIOS Write Enable: disabled Warning: Setting Bios Control at 0xdc from 0x0a to 0x09 failed. New value is 0x0a. SPIBAR = 0x00007f9404c22000 + 0x3800 0x04: 0xe009 (HSFS) HSFS: FDONE=1, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=1 Warning: SPI Configuration Lockdown activated. Reading OPCODES... done 0x06: 0x0004 (HSFC) HSFC: FGO=0, FCYCLE=2, FDBC=0, SME=0 0x50: 0x00000a0b (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0x0a, BRRA 0x0b 0x54: 0x00000000 FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only. 0x58: 0x0bff0600 FREG1: BIOS region (0x00600000-0x00bfffff) is read-write. 0x5C: 0x05ff0005 FREG2: Warning: Management Engine region (0x00005000-0x005fffff) is locked. 0x60: 0x00040001 FREG3: Gigabit Ethernet region (0x00001000-0x00004fff) is read-write. Not all flash regions are freely accessible by flashrom. This is most likely due to an active ME. Please see http://flashrom.org/ME for details. Writes have been disabled for safety reasons. You can enforce write support with the ich_spi_force programmer option, but you will most likely harm your hardware! If you force flashrom you will get no support if something breaks. On a few mainboards it is possible to enable write access by setting a jumper (see its documentation or the board itself). 0x90: 0xc0 (SSFS) SSFS: SCIP=0, FDONE=0, FCERR=0, AEL=0 0x91: 0xf84010 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=1, DBC=0, SME=0, SCF=0 0x94: 0x0006 (PREOP) 0x96: 0x043b (OPTYPE) 0x98: 0x05200302 (OPMENU) 0x9C: 0x0000019f (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x00802005 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 0xC8: 0x00002005 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20 0xD0: 0x00000800 (FPB) Enabling hardware sequencing due to multiple flash chips detected. PROBLEMS, continuing anyway The following protocols are supported: FWH, Programmer-specific. Probing for Programmer Opaque flash chip, 0 kB: Found 2 attached SPI flash chips with a combined density of 12288 kB. The flash address space (0x000000 - 0xbfffff) is divided at address 0x800000 in two partitions. The first partition ranges from 0x000000 to 0x7fffff. In that range are 2048 erase blocks with 4096 B each. The second partition ranges from 0x800000 to 0xbfffff. In that range are 1024 erase blocks with 4096 B each. Found Programmer flash chip "Opaque flash chip" (12288 kB, Programmer-specific) mapped at physical address 0x0000000000000000. Probing 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 Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xea, id2 0xd0, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Found Programmer flash chip "Opaque flash chip" (12288 kB, Programmer-specific). No operations were specified. Restoring MMIO space at 0x7f9404c258a0 Restoring PCI config space for 00:1f:0 reg 0xdc

1 0

[PATCH 0/1] Add support for reading the current flash contents from a file
by Paul Kocialkowski 23 Apr '16

23 Apr '16

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

4 6

Re: [flashrom] [PATCH 1/1] Add support for reading the current flash contents from a file
by Paul Kocialkowski 23 Apr '16

23 Apr '16

Le mercredi 20 avril 2016 à 16:54 -0700, David Hendricks a écrit : > Looks pretty good to me. FWIW, we implemented something nearly identical in > the chromiumos branch a few years ago: https://chromium-review.googlesource.co > m/#/c/10180/ (we called it "--diff"). It's been quite useful for development, > especially when working with large chips and slow external programmers. This has been my use case as well, in particular with the kb9012 embedded controller flash. Nice to see that this use case is shared with others and that we came up with a quite similar implementation independently! > On Tue, Apr 19, 2016 at 12:25 PM, Paul Kocialkowski <contact(a)paulk.fr> wrote: > > Hi, > > > > Could we get the review moving on this patch? I first sent it over 4 months > > ago > > and got no feedback. I'd really like to have this feature merged, as I'm > > using > > it very often! > > > > Thanks > > > > Le lundi 29 février 2016 à 19:44 +0100, Paul Kocialkowski a écrit : > > > When developing software that has to be flashed to a flash chip to be > > > executed, > > > it often takes a long time to read the current flash contents (for > > flashrom to > > > know what pages to erase and reprogram) each time, when writing the new > > image. > > > However, when the flash was just reprogrammed, its current state is known > > to > > > be > > > the previous image that was flashed (assuming it was verified). > > > > > > Thus, it makes sense to provide that image as a file for the flash > > contents > > > instead of wasting valuable time read the whole flash each time. > > > > > > Signed-off-by: Paul Kocialkowski <contact(a)paulk.fr> > > > --- > > > cli_classic.c | 46 ++++++++++++++++++++++++++++------------------ > > > flash.h | 2 +- > > > flashrom.c | 14 +++++++++++--- > > > 3 files changed, 40 insertions(+), 22 deletions(-) > > > > > > diff --git a/cli_classic.c b/cli_classic.c > > > index a2c2014..dc0164d 100644 > > > --- a/cli_classic.c > > > +++ b/cli_classic.c > > > @@ -44,24 +44,25 @@ static void cli_classic_usage(const char *name) > > > "[-E|(-r|-w|-v) <file>] [-l <layoutfile> [-i <imagename>]...] > > > [-n] [-f]]\n" > > > "[-V[V[V]]] [-o <logfile>]\n\n", name); > > > > > > - printf(" -h | --help print this help text\n" > > > - " -R | --version print version > > > (release)\n" > > > - " -r | --read <file> read flash and save to > > > <file>\n" > > > - " -w | --write <file> write <file> to flash\n" > > > - " -v | --verify <file> verify flash against > > > <file>\n" > > > - " -E | --erase erase flash memory\n" > > > - " -V | --verbose more verbose output\n" > > > - " -c | --chip <chipname> probe only for specified > > > flash chip\n" > > > - " -f | --force force specific > > operations > > > (see man page)\n" > > > - " -n | --noverify don't auto-verify\n" > > > - " -l | --layout <layoutfile> read ROM layout from > > > <layoutfile>\n" > > > - " -i | --image <name> only flash image <name> > > > from flash layout\n" > > > - " -o | --output <logfile> log output to > > > <logfile>\n" > > > - " -L | --list-supported print supported > > > devices\n" > > > + printf(" -h | --help print this help > > text\n" > > > + " -R | --version print version > > > (release)\n" > > > + " -r | --read <file> read flash and save to > > > <file>\n" > > > + " -w | --write <file> write <file> to > > > flash\n" > > > + " -v | --verify <file> verify flash against > > > <file>\n" > > > + " -E | --erase erase flash memory\n" > > > + " -V | --verbose more verbose output\n" > > > + " -c | --chip <chipname> probe only for > > > specified flash chip\n" > > > + " -f | --force force specific > > > operations (see man page)\n" > > > + " -n | --noverify don't auto-verify\n" > > > + " -l | --layout <layoutfile> read ROM layout from > > > <layoutfile>\n" > > > + " -i | --image <name> only flash image > > <name> > > > from flash layout\n" > > > + " -o | --output <logfile> log output to > > > <logfile>\n" > > > + " -C | --flash-contents <contentsfile> assume flash contents > > > to be <contentsfile>\n" > > > + " -L | --list-supported print supported > > > devices\n" > > > #if CONFIG_PRINT_WIKI == 1 > > > - " -z | --list-supported-wiki print supported devices > > > in wiki syntax\n" > > > + " -z | --list-supported-wiki print supported > > devices > > > in wiki syntax\n" > > > #endif > > > - " -p | --programmer <name>[:<param>] specify the programmer > > > device. One of\n"); > > > + " -p | --programmer <name>[:<param>] specify the programmer > > > device. One of\n"); > > > list_programmers_linebreak(4, 80, 0); > > > printf(".\n\nYou can specify one of -h, -R, -L, " > > > #if CONFIG_PRINT_WIKI == 1 > > > @@ -106,7 +107,7 @@ int main(int argc, char *argv[]) > > > enum programmer prog = PROGRAMMER_INVALID; > > > int ret = 0; > > > > > > - static const char optstring[] = "r:Rw:v:nVEfc:l:i:p:Lzho:"; > > > + static const char optstring[] = "r:Rw:v:nVEfc:l:i:C:p:Lzho:"; > > > static const struct option long_options[] = { > > > {"read", 1, NULL, 'r'}, > > > {"write", 1, NULL, 'w'}, > > > @@ -118,6 +119,7 @@ int main(int argc, char *argv[]) > > > {"force", 0, NULL, 'f'}, > > > {"layout", 1, NULL, 'l'}, > > > {"image", 1, NULL, 'i'}, > > > + {"flash-contents", 1, NULL, 'C'}, > > > {"list-supported", 0, NULL, 'L'}, > > > {"list-supported-wiki", 0, NULL, 'z'}, > > > {"programmer", 1, NULL, 'p'}, > > > @@ -128,6 +130,7 @@ int main(int argc, char *argv[]) > > > }; > > > > > > char *filename = NULL; > > > + char *contentsfile = NULL; > > > char *layoutfile = NULL; > > > #ifndef STANDALONE > > > char *logfile = NULL; > > > @@ -221,6 +224,9 @@ int main(int argc, char *argv[]) > > > cli_classic_abort_usage(); > > > } > > > break; > > > + case 'C': > > > + contentsfile = strdup(optarg); > > > + break; > > > case 'L': > > > if (++operation_specified > 1) { > > > fprintf(stderr, "More than one operation " > > > @@ -332,6 +338,9 @@ int main(int argc, char *argv[]) > > > if (layoutfile && check_filename(layoutfile, "layout")) { > > > cli_classic_abort_usage(); > > > } > > > + if (contentsfile && check_filename(contentsfile, "contents")) { > > > + cli_classic_abort_usage(); > > > + } > > > > > > #ifndef STANDALONE > > > if (logfile && check_filename(logfile, "log")) > > > @@ -542,7 +551,7 @@ int main(int argc, char *argv[]) > > > * Give the chip time to settle. > > > */ > > > programmer_delay(100000); > > > - ret |= doit(fill_flash, force, filename, read_it, write_it, > > erase_it, > > > verify_it); > > > + ret |= doit(fill_flash, force, filename, contentsfile, read_it, > > > write_it, erase_it, verify_it); > > > > > > unmap_flash(fill_flash); > > > out_shutdown: > > > @@ -554,6 +563,7 @@ out: > > > layout_cleanup(); > > > free(filename); > > > free(layoutfile); > > > + free(contentsfile); > > > free(pparam); > > > /* clean up global variables */ > > > free((char *)chip_to_probe); /* Silence! Freeing is not modifying > > > contents. */ > > > diff --git a/flash.h b/flash.h > > > index dc5c140..2cf7ca6 100644 > > > --- a/flash.h > > > +++ b/flash.h > > > @@ -284,7 +284,7 @@ void print_buildinfo(void); > > > void print_banner(void); > > > void list_programmers_linebreak(int startcol, int cols, int paren); > > > int selfcheck(void); > > > -int doit(struct flashctx *flash, int force, const char *filename, int > > > read_it, int write_it, int erase_it, int verify_it); > > > +int doit(struct flashctx *flash, int force, const char *filename, const > > char > > > *contentsfile, int read_it, int write_it, int erase_it, int verify_it); > > > int read_buf_from_file(unsigned char *buf, unsigned long size, const char > > > *filename); > > > int write_buf_to_file(const unsigned char *buf, unsigned long size, const > > > char *filename); > > > > > > diff --git a/flashrom.c b/flashrom.c > > > index d5c3238..d11f89d 100644 > > > --- a/flashrom.c > > > +++ b/flashrom.c > > > @@ -1978,8 +1978,9 @@ int chip_safety_check(const struct flashctx *flash, > > int > > > force, int read_it, int > > > * but right now it allows us to split off the CLI code. > > > * Besides that, the function itself is a textbook example of abysmal > > code > > > flow. > > > */ > > > -int doit(struct flashctx *flash, int force, const char *filename, int > > > read_it, > > > - int write_it, int erase_it, int verify_it) > > > +int doit(struct flashctx *flash, int force, const char *filename, > > > + const char *contentsfile, int read_it, int write_it, int erase_it, > > > + int verify_it) > > > { > > > uint8_t *oldcontents; > > > uint8_t *newcontents; > > > @@ -2068,7 +2069,14 @@ int doit(struct flashctx *flash, int force, const > > char > > > *filename, int read_it, > > > * preserved, but in that case we might perform unneeded erase which > > > * takes time as well. > > > */ > > > - if (read_all_first) { > > > + if (contentsfile) { > > > + msg_cinfo("Reading old flash chip contents from file... "); > > > + if (read_buf_from_file(oldcontents, size, contentsfile)) { > > > + ret = 1; > > > + msg_cinfo("FAILED.\n"); > > > + goto out; > > > + } > > > + } else if (read_all_first) { > > > msg_cinfo("Reading old flash chip contents... "); > > > if (flash->chip->read(flash, oldcontents, 0, size)) { > > > ret = 1; > > > > _______________________________________________ > > flashrom mailing list > > flashrom(a)flashrom.org > > https://www.flashrom.org/mailman/listinfo/flashrom > > > > -- > David Hendricks (dhendrix) > Systems Software Engineer, Google Inc.

1 0

not able to flash W25Q64.W (cherry trail Atom z8300)
by Piotr Kasprzak 23 Apr '16

23 Apr '16

my log http://pastebin.com/ZEreZnm0 <http://pastebin.com/ZEreZnm0> and i found in windows program for flashing bios this file Maybe thats help Thanks for any help. Im brick my miniPC box … i dont have picture on TV but i have still working linux there and connection over SSH - so im able to flash bios, but „flashroom” dont work yet with this chipset :( Let me know about any news ! I will be greatefull Thanks Best Regards Piotr Kasprzak ; For ME8.x and older platforms and Bay Trail platforms ; ; rev 2.7.8 ; ; These settings are not part recommendations, nor are they an indication these parts are supported on Intel platforms. ; ; All parts on this list have NOT been validated, and it is the responsibility of the customer to validate the flash parts used on their platform. ; ; Flash parts may change opcodes and architectures so please refer to the respective flash datasheet and errata/application note and flash vendor to confirm. ; ; ; ;Description of fields: ; 1) Display name ; 2) Device ID (2 or 3 bytes) ; 3) Device Size (in bits in hexadecimal (0x) notation, For example 8 Mbit = (8*1024*1024) = (8,388,608) convert to hex 0x800000 ; 16Mbit=0x1000000, 32Mbit=0x2000000, 64Mbit=0x4000000, 128Mbit=0x8000000, 256Mbit=0x10000000, 512Mbit=0x20000000 ; 4) Block Erase Size (in bytes - 256, 4K, 64K) ; 5) Block Erase Command ; 6) Write Granularity (1 or 64) ; 7) Enable Write Status Register Command (1- True, 0- False) ; 8) Chip Erase Command ; 9) Chip Erase Timeout (in milliseconds) ; ; Winbond W25X80V, 0xEF3014, 0x800000, 0x10000, 0xD8, 64, 0, 0xc7, 80000 W25X16BV, 0xEF3015, 0x1000000, 0x10000, 0xD8, 64, 0, 0xc7, 80000 W25X32BV, 0xEF3016, 0x2000000, 0x10000, 0xD8, 64, 0, 0xc7, 80000 W25X64BV, 0xEF3017, 0x4000000, 0x10000, 0xD8, 64, 0, 0xc7, 80000 W25Q40BV, 0XEF4013, 0x400000, 0x1000, 0x20, 64, 0, 0xc7, 80000 W25Q80BV, 0xEF4014, 0x800000, 0x1000, 0x20, 64, 0, 0xc7, 80000 W25Q16BV(CV), 0xEF4015, 0x1000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 W25Q32BV, 0xEF4016, 0x2000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 W25Q64BV(CV)(FV), 0xEF4017, 0x4000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 W25Q128BV(FV), 0xEF4018, 0x8000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 W25Q64DW, 0XEF6017, 0x4000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 W25Q128FW, 0xEF6018, 0x8000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 W25Q64FW, 0XEF6017, 0x4000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 ; Macronix MX25L1605A(D)(36E)(06E), 0xC22015, 0x1000000, 0x1000, 0x20, 64, 0, 0x60, 80000 MX25L3205A(D)(06E), 0xC22016, 0x2000000, 0x10000, 0xD8, 64, 0, 0xC7, 80000 MX25L6405D(45E)(36E)(06E)(73E), 0xC22017, 0x4000000, 0x1000, 0x20, 64, 0, 0x60, 80000 MX25L12805D(45E)(36E)(35E), 0xC22018, 0x8000000, 0x1000, 0x20, 64, 0, 0x60, 80000 MX25L8005(35E)(06E)(36E), 0xC22014, 0x800000, 0x1000, 0x20, 64, 0, 0x60, 80000 MX25L3225D(35D)(36D), 0xC25E16, 0x2000000, 0x10000, 0xD8, 64, 0, 0xC7, 80000 MX25L25635E(L25735E), 0xC22019, 0x10000000, 0x1000, 0x20, 64, 0, 0x60, 80000 MX25L1635D, 0xC22415, 0x1000000, 0x1000, 0x20, 64, 0, 0x60, 80000 MX25L6455E, 0xC22617, 0x4000000, 0x1000, 0x20, 64, 0, 0x60, 80000 MX2L12855E, 0xC22618, 0x8000000, 0x1000, 0x20, 64, 0, 0x60, 80000 MX25L4006E, 0xC22013, 0x400000, 0x1000, 0x20, 64, 0, 0x60, 80000 MX25U6435F, 0xC22537, 0x4000000, 0x1000, 0x20, 64, 0, 0x60, 80000 MX25U12835F, 0xC22538, 0x8000000, 0x1000, 0x20, 64, 0, 0x60, 80000 ; Micron/Numonyx M25PE10, 0x208011, 0x100000, 0x1000, 0x20, 64, 0, 0xC7, 80000 M25PE20, 0x208012, 0x200000, 0x1000, 0x20, 64, 0, 0xC7, 80000 M25PE40, 0x208013, 0x400000, 0x1000, 0x20, 64, 0, 0xC7, 80000 M25PE80, 0x208014, 0x800000, 0x1000, 0x20, 64, 0, 0xC7, 80000 M25PE16, 0x208015, 0x1000000, 0x1000, 0x20, 64, 0, 0xC7, 80000 M25PX80, 0x207114, 0x800000, 0x1000, 0x20, 64, 0, 0xC7, 80000 M25PX16, 0x207115, 0x1000000, 0x1000, 0x20, 64, 0, 0xC7, 80000 M25PX32, 0x207116, 0x2000000, 0x1000, 0x20, 64, 0, 0xC7, 80000 M25PX64, 0x207117, 0x4000000, 0x1000, 0x20, 64, 0, 0xC7, 80000 N25Q16, 0x20BA15, 0x1000000, 0x1000, 0x20, 64, 0, 0xC7, 80000 N25Q128, 0x20BA18, 0x8000000, 0x10000, 0xD8, 64, 0, 0xC7, 80000 N25Q032, 0x20BA16, 0x2000000, 0x1000, 0x20, 64, 0, 0xC7, 80000 N25Q064, 0x20BA17, 0x4000000, 0x1000, 0x20, 64, 0, 0xC7, 80000 ; Atmel/Adesto AT26DF081, 0x1F4500, 0x800000, 0x1000, 0x20, 1, 0, 0x60, 20000 AT25/26DF081A, 0x1F4501, 0x800000, 0x1000, 0x20, 64, 0, 0x60, 20000 AT25DF081, 0x1F4502, 0x800000, 0x1000, 0x20, 64, 0, 0X60, 20000 AT26DF161, 0x1F4600, 0x1000000, 0x1000, 0x20, 64, 0, 0x60, 35000 AT26DF161A, 0x1F4601, 0x1000000, 0x1000, 0X20, 64, 0, 0x60, 35000 AT25DF161, 0x1F4602, 0x1000000, 0x1000, 0x20, 64, 0, 0x60, 35000 AT25DQ161, 0x1F8600, 0x1000000, 0x1000, 0x20, 64, 0, 0x60, 35000 AT25/26DF321, 0x1F4700, 0x2000000, 0x1000, 0x20, 64, 0, 0x60, 60000 AT25DF321A, 0x1F4701, 0x2000000, 0x1000, 0x20, 64, 0, 0x60, 60000 AT25DF641(A), 0x1F4800, 0x4000000, 0x1000, 0x20, 64, 0, 0x60, 120000 AT25DQ641, 0x1F8800, 0x4000000, 0x1000, 0x20, 64, 0, 0x60, 120000 ; SST/Microchip SST25VF016B, 0xBF2541, 0x1000000, 0x1000, 0x20, 1, 0, 0x60, 50 SST25VF032B, 0XBF254A, 0x2000000, 0x1000, 0x20, 1, 0, 0x60, 50 SST25VF040B, 0xBF258D, 0x400000, 0x1000, 0x20, 1, 0, 0x60, 50 SST25VF080B, 0xBF258E, 0x800000, 0x1000, 0x20, 1, 0, 0x60, 50 SST25VF064C, 0xBF254B, 0x4000000, 0x1000, 0x20, 64, 0, 0x60, 50 ; Chingis Pm25LV080B, 0x9D7F13, 0x800000, 0x1000, 0x20, 64, 0, 0xc7, 80000 Pm25LV016B, 0x9D7F14, 0x1000000, 0x1000, 0x20, 64, 0, 0x60, 80000 Pm25LQ080, 0x7F9D44, 0x800000, 0x1000, 0x20, 64, 0, 0xC7, 80000 Pm25LQ016, 0x7F9D45, 0x1000000, 0x1000, 0x20, 64, 0, 0xC7, 80000 Pm25LQ032, 0x7F9D46, 0x2000000, 0x1000, 0x20, 64, 0, 0xC7, 80000 Pm25LD512C2, 0x7F9D20, 0x20000000, 0x1000, 0x20, 64, 0, 0xC7, 80000 ; EON EN25Q40, 0x1C3013, 0x400000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25F80, 0x1C3114, 0x800000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25Q80A, 0x1C3014, 0x800000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25F16, 0x1C3115, 0x1000000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25F32, 0x1C3116, 0x2000000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25Q32B, 0x1C3016, 0x2000000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25Q64, 0x1C3017, 0x4000000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25Q128, 0x1C3018, 0x8000000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25Q16(A), 0x1C3015, 0x1000000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25QH16, 0x1C7015, 0x1000000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25QH32, 0x1C7016, 0x2000000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25QH256, 0x1C7019, 0x10000000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25QH128, 0x1C7018, 0x4000000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25QH64, 0x1C7017, 0x800000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25QH80, 0x1C7014, 0x800000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25F64, 0x1C3117, 0x4000000, 0x1000, 0x20, 64, 0, 0x60, 80000 EN25S64, 0x1C3817, 0x4000000, 0x1000, 0x20, 64, 0, 0x60, 80000 ; AMIC A25L016, 0x373015, 0x1000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 A25L032, 0x373016, 0x2000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 A25LQ32A, 0x374016, 0x2000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 A25LQ16, 0x374015, 0x1000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 A25L040, 0x373013, 0x400000, 0x1000, 0x20, 64, 0, 0xc7, 80000 A25L080, 0x373014, 0x800000, 0x1000, 0x20, 64, 0, 0xc7, 80000 A25LQ64, 0x374017, 0x4000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 ; GigaDeivce GD25Q80, 0xC84014, 0x800000, 0x1000, 0x20, 64, 0, 0xc7, 80000 GD25Q16, 0xC84015, 0x1000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 GD25Q32, 0xC84016, 0x2000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 GD25Q64, 0xC84017, 0x4000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 GD25Q128, 0xC84018, 0x8000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 GD25LQ16, 0xC86015, 0x1000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 GD25LQ32C, 0xC86016, 0x2000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 GD25LQ64, 0xC86017, 0x4000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 GD25LQ128C, 0xC86018, 0x8000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 GD25LQ256C, 0xC86019, 0x10000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 ; Spansion S25FL016K, 0xEF4015, 0x1000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 S25FL032K, 0xEF4016, 0x2000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 S25FL064K, 0xEF4017, 0x4000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 ; Fidelix FM25Q16, 0xF83215, 0x1000000, 0x1000, 0x20, 64, 0, 0x60, 50000 FM25Q32, 0xF83216, 0x2000000, 0x1000, 0x20, 64, 0, 0x60, 80000 FM25Q64, 0xF83217, 0x4000000, 0x1000, 0x20, 64, 0, 0x60, 100000 FM25Q128, 0xF83218, 0x8000000, 0x1000, 0x20, 64, 0, 0x60, 150000 ; ESMT F25L32PA(2S), 0x8C2116, 0x2000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 F25L64PA, 0x8C2117, 0x4000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 F225L16PA, 0x8C2015, 0x1000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 F25L04PA, 0x8C3013, 0x400000, 0x1000, 0x20, 64, 0, 0x60, 80000 F25L08PA, 0x8C3014, 0x800000, 0x1000, 0x20, 64, 0, 0xc7, 80000 F25L16PA(2S), 0x8C2115, 0x1000000, 0x1000, 0x20, 64, 0, 0xc7, 80000 F25L32PA, 0x8C2016, 0x2000000, 0x1000, 0x20, 64, 0, 0xc7, 80000

1 0

Re: [flashrom] Giving to -i option some real use
by Salvador Eduardo Tropea 22 Apr '16

22 Apr '16

Hi David! El 21/04/16 a las 18:19, David Hendricks escribió: > > > On Thu, Apr 21, 2016 at 1:41 PM, Salvador Eduardo Tropea > <salvador(a)inti.gob.ar <mailto:salvador@inti.gob.ar>> wrote: > > Hi David: > > Thanks for your comments. > > > El 20/04/16 a las 20:42, David Hendricks escribió: > > Hello Salvador, > Yes, this is a very useful feature - we've had it in the > chromiumos branch for a while now :-) > > I need to read your implementation. Ours is called > "fast-verify" which will read and only verify portions of the > flash specified with -i arguments. > > > What about writes? My problem is that I have a 4 MiB flash and > that usually need to use 32kB from it. > > > Yes, it works for writes as well. Using your layout file as an example: > 00000000:00007e2b fpga > 00007e2c:003fffff free > > If the eraseblock size is 4KB and you run /"/flashrom -p <programmer> > -l layout -i fpga -w foo.bin --fast-verify/"/, chromium's flashrom will: > 1. Detect the flash chip. > 2. Parse the -i argument > 3. Do a partial read. This is broken into a multiple steps. > 3a. Determine the "required_erase_size", for example, 4KB. Right now > the mechanism is crude and chooses the smallest block size that is > eraseable. > 3b. Align regions that are read based on required_erase_size. 0000 is > already aligned, but 7e2b will be aligned up to 7fff. > 3c. Read the aligned region content, which is 0000:7fff instead of > 0000:7e2b, into the new content buffer. > 4. Copy the new content from the "fpga" region into the new content > buffer. > 5. Erase and write 0000:7fff > 6. Verify from 0000:7fff > > Overall it looks pretty similar to what you posted. Yes. > Here's the original implementation: > https://chromium-review.googlesource.com/#/c/240176/ > <https://chromium-review.googlesource.com/#/c/240176/4>. There are a > couple of follow-up patches as well, in case you're interested. I taked a look at this. The patch have a lot in common. In my patch I use the first "usable" eraser, just like erase_and_write_flash. If this eraser fails the code will try to recover reading the whole memory. So I think this is ok. So assuming that the first "usable" eraser is a good choice I compute the alignments using *all* the eraseblocks information. My intention is to support cases like it: .block_erasers = { { .eraseblocks = { {16 * 1024, 1}, {8 * 1024, 2}, {32 * 1024, 1}, {64 * 1024, 3}, }, .block_erase = erase_sector_jedec, }, { .eraseblocks = { {256 * 1024, 1} }, .block_erase = erase_chip_block_jedec, }, }, Here the first eraser is "erase_sector_jedec", but it have really complex "block size", is not one size, but a crazy list of sizes: 16 kiB, 8 kiB, 8 kiB, 32 kiB, 64 kiB, 64 kiB, 64 kiB So I walk the list computing the beggining of each block and checking if the address is inside it. From what I see in the link above your patch uses a single size, the smallest. > > One more thing to note - Be careful about interactions with the > proposed patch to read the current contents of flash from a file: > https://www.flashrom.org/pipermail/flashrom/2015-December/014034.html. > Specifically, make sure that the aligned offsets are used for reading > old content no matter if the old content is in a flash chip or a file. Thanks. It looks compatible. Regards, SET -- Ing. Salvador Eduardo Tropea http://utic.inti.gob.ar/ INTI - Micro y Nanoelectrónica (CMNB) http://www.inti.gob.ar/ Unidad Técnica Sistemas Inteligentes Av. General Paz 5445 Tel: (+54 11) 4724 6300 ext. 6919 San Martín - B1650KNA FAX: (+54 11) 4754 5194 Buenos Aires * Argentina

1 0

Re: [flashrom] Giving to -i option some real use
by Salvador Eduardo Tropea 21 Apr '16

21 Apr '16

Hi David: Thanks for your comments. El 20/04/16 a las 20:42, David Hendricks escribió: > Hello Salvador, > Yes, this is a very useful feature - we've had it in the chromiumos > branch for a while now :-) > > I need to read your implementation. Ours is called "fast-verify" which > will read and only verify portions of the flash specified with -i > arguments. What about writes? My problem is that I have a 4 MiB flash and that usually need to use 32kB from it. > It will also restore content surrounding regions (to address Michael's > concern) by aligning the bytes read with the erase size. So if you > wish to change a small amount of content within an eraseable block, > the entire block will be read and erased. The region specified with -i > will be written with new content, and the remaining bytes within the > block will have the old content restored. > > Here's our tree in case you'd like to take a look: > https://chromium.googlesource.com/chromiumos/third_party/flashrom/ Thanks for the link. Regards, SET > > > On Tue, Apr 19, 2016 at 10:48 AM, Salvador Eduardo Tropea > <salvador(a)inti.gob.ar <mailto:salvador@inti.gob.ar>> wrote: > > Hi All! > > Now I'm using an FPGA board with 4 MiB of flash, was using one > with 128 kiB. So now the time to read/write/verify the whole > memory is enough to annoy me ;-) > So I tried creating a layout like this: > > <-- > 00000000:00007e2b fpga > 00007e2c:003fffff free > <-- > > Note: yes only 32300 bytes used, the rest can be used for other > purposes (0,77%). > > And then I used "-i fpga". > But it didn't help ... flashrom read the 4 MiB twice (one at the > beggining and another for the verification). > Looking at the code I found a variable named read_all_first with a > comment about the lack of implementation. > So I implemented the needed code to: > 1) Add a command line option to make it 0 (avoiding the big > reads). This option can be used only when at least one image is > indicated with -i > 2) Skip the big read when read_all_first is 0. Only the regions > indicated by the user are actually fetched from the memory. > 3) Same for the verification stage. > > Additionally I added a command line option to show the progress, > very usefull for big memories (and impatient users ;-). > > Are these additions desired in the project? If yes: I want to > discuss the implementation details. If no: I'll just keep them for > my use. > > Regards, SET > > -- > Ing. Salvador Eduardo Tropea http://utic.inti.gob.ar/ > INTI - Micro y Nanoelectrónica (CMNB) http://www.inti.gob.ar/ > Unidad Técnica Sistemas Inteligentes Av. General Paz 5445 > Tel: (+54 11) 4724 6300 ext. 6919 > <tel:%28%2B54%2011%29%204724%206300%20ext.%206919> San Martín > - B1650KNA > FAX: (+54 11) 4754 5194 <tel:%28%2B54%2011%29%204754%205194> > Buenos Aires * Argentina > > > > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org <mailto:flashrom@flashrom.org> > https://www.flashrom.org/mailman/listinfo/flashrom > > > > > -- > David Hendricks (dhendrix) > Systems Software Engineer, Google Inc. -- Ing. Salvador Eduardo Tropea http://utic.inti.gob.ar/ INTI - Micro y Nanoelectrónica (CMNB) http://www.inti.gob.ar/ Unidad Técnica Sistemas Inteligentes Av. General Paz 5445 Tel: (+54 11) 4724 6300 ext. 6919 San Martín - B1650KNA FAX: (+54 11) 4754 5194 Buenos Aires * Argentina

2 1

Re: [flashrom] unknown chip
by Idwer Vollering 21 Apr '16

21 Apr '16

Hi, I think you meant MX25U12835F. This fork of flashrom code seems to have done the work for us: https://github.com/rjarzmik/flashrom2/blob/master/src/chips/mx25u12835f.c HTH, Idwer 2016-04-19 15:34 GMT+02:00 John Bork <johnbork023(a)gmail.com>: > Hi, > > got this probe result from a MX25U12845F chip, if you want to add it to your > support list. > > BR > John Bork > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://www.flashrom.org/mailman/listinfo/flashrom

1 0

Giving to -i option some real use
by Salvador Eduardo Tropea 21 Apr '16

21 Apr '16

Hi All! Now I'm using an FPGA board with 4 MiB of flash, was using one with 128 kiB. So now the time to read/write/verify the whole memory is enough to annoy me ;-) So I tried creating a layout like this: <-- 00000000:00007e2b fpga 00007e2c:003fffff free <-- Note: yes only 32300 bytes used, the rest can be used for other purposes (0,77%). And then I used "-i fpga". But it didn't help ... flashrom read the 4 MiB twice (one at the beggining and another for the verification). Looking at the code I found a variable named read_all_first with a comment about the lack of implementation. So I implemented the needed code to: 1) Add a command line option to make it 0 (avoiding the big reads). This option can be used only when at least one image is indicated with -i 2) Skip the big read when read_all_first is 0. Only the regions indicated by the user are actually fetched from the memory. 3) Same for the verification stage. Additionally I added a command line option to show the progress, very usefull for big memories (and impatient users ;-). Are these additions desired in the project? If yes: I want to discuss the implementation details. If no: I'll just keep them for my use. Regards, SET -- Ing. Salvador Eduardo Tropea http://utic.inti.gob.ar/ INTI - Micro y Nanoelectrónica (CMNB) http://www.inti.gob.ar/ Unidad Técnica Sistemas Inteligentes Av. General Paz 5445 Tel: (+54 11) 4724 6300 ext. 6919 San Martín - B1650KNA FAX: (+54 11) 4754 5194 Buenos Aires * Argentina

3 3

[PATCH v3 1/2] Add support for selecting the erased bit value with a flag
by Paul Kocialkowski 19 Apr '16

19 Apr '16

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

1 2

unknown chip
by John Bork 19 Apr '16

19 Apr '16

Hi, got this probe result from a MX25U12845F chip, if you want to add it to your support list. BR John Bork

1 0

Re: [flashrom] using DLP-USB1232H/MinnowboardMAX, verification error. is it due to DP_IO3L in SPI header not connected ?
by Sathish Kumar Balasubramaniam -ERS, HCL Tech 19 Apr '16

19 Apr '16

I got the problem. It's since I provided 1.8v to SPI chip VCC while the CS,SCLK,SI,SO logic levels (from DLP-USB1232H) are higher than 1.8v which also needs to be down to 1.8v to work. Regards, B.Sathish Kumar -----Original Message----- From: Sathish Kumar Balasubramaniam -ERS, HCL Tech Sent: 19 April 2016 00:59 To: flashrom(a)flashrom.org Subject: RE: using DLP-USB1232H/MinnowboardMAX, verification error. is it due to DP_IO3L in SPI header not connected ? forgot to add env info OS: Ubuntu 14.04.4 64bit flashrom version - 0.9.9 ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ----------------------------------------------------------------------------------------------------------------------------------------------------

1 0

Re: [flashrom] using DLP-USB1232H/MinnowboardMAX, verification error. is it due to DP_IO3L in SPI header not connected ?
by Sathish Kumar Balasubramaniam -ERS, HCL Tech 18 Apr '16

18 Apr '16

forgot to add env info OS: Ubuntu 14.04.4 64bit flashrom version - 0.9.9 ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ----------------------------------------------------------------------------------------------------------------------------------------------------

1 0

using DLP-USB1232H/MinnowboardMAX, verification error. is it due to DP_IO3L in SPI header not connected ?
by Sathish Kumar Balasubramaniam -ERS, HCL Tech 18 Apr '16

18 Apr '16

I am trying to use DLP-USB1232H with flashrom for programming SPI flash in Minnowboard MAX. I connected CS,SCLK,SO,SI (referred https://www.flashrom.org/FT2232SPI_Programmer). I didn't connect WP# and HOLD# to VCC and not sure whether it is needed in minnowboard max. I am not able to find where to connect DDP_IO3L in SPI header of Minnowboard MAX. i.e., to which pin in DLP-USB1232H when I tried to execute "flashrom -p ft2232_spi:type=2232H,port=A" sometimes it does not detect the chip. when I try again removing and reconnecting the USB wire, chip will get detected. I am able to read the chip contents any time. But when I try to write contents, it says done, but verification says error , content at ... not expected. I tried reading again and checked. the content is not written properly. Is this due to that I have not connected DDP_IO3L pin from minnowboard max ? Regards, B.Sathish Kumar ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ----------------------------------------------------------------------------------------------------------------------------------------------------

1 0

Re: [flashrom] FAILED: W25Q64.W
by David Hendricks 17 Apr '16

17 Apr '16

Hi Davinder, The transaction error is likely caused by the Management Engine: https://www.flashrom.org/ME On Fri, Apr 15, 2016 at 10:19 PM, Davinder Pal Singh Sawhney < davinder.sawhney(a)gmail.com> wrote: > Dear Sir, > > Please help me. Here is complete log > > flashrom -p internal -w backup.bin > flashrom v0.9.9-r1954 on Linux 3.16.0-4-686-pae (i686) > flashrom is free software, get the source code at https://flashrom.org > > Calibrating delay loop... OK. > No DMI table found. > Found chipset "Intel Braswell". > This chipset is marked as untested. If you are using an up-to-date version > of flashrom *and* were (not) able to successfully update your firmware > with it, > then please email a report to flashrom(a)flashrom.org including a verbose > (-V) log. > Thank you! > Enabling flash write... Warning: BIOS region SMM protection is enabled! > Warning: Setting Bios Control at 0x0 from 0x22 to 0x01 failed. > New value is 0x22. > Warning: SPI Configuration Lockdown activated. > OK. > Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) mapped at physical > address 0xff800000. > Reading old flash chip contents... done. > Erasing and writing flash chip... Transaction error! > spi_block_erase_20 failed during command execution at address 0x416000 > Reading current flash chip contents... done. Looking for another erase > function. > spi_block_erase_52 failed during command execution at address 0x410000 > Reading current flash chip contents... done. Looking for another erase > function. > spi_block_erase_d8 failed during command execution at address 0x410000 > Reading current flash chip contents... done. Looking for another erase > function. > spi_chip_erase_60 failed during command execution > Reading current flash chip contents... done. Looking for another erase > function. > spi_chip_erase_c7 failed during command execution > Looking for another erase function. > No usable erase functions left. > FAILED! > Uh oh. Erase/write failed. Checking if anything has changed. > Reading current flash chip contents... done. > Apparently at least some data has 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! > > > flashrom -V > flashrom v0.9.9-r1954 on Linux 3.16.0-4-686-pae (i686) > flashrom is free software, get the source code at https://flashrom.org > > flashrom was built with libpci 3.2.1, GCC 4.9.2, little endian > Command line (1 args): flashrom -V > Please select a programmer with the --programmer parameter. > Previously this was not necessary because there was a default set. > To choose the mainboard of this computer use 'internal'. Valid choices are: > internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, > it8212, ft2232_spi, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, > nicintel, nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, > usbblaster_spi, pickit2_spi, ch341a_spi. > > -- > Best Regards, > Davinder > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://www.flashrom.org/mailman/listinfo/flashrom > -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

Issue flashing MX25L3206E
by Thomas Leclercq 17 Apr '16

17 Apr '16

Hello, I'm trying to flash back a bricked BIOS, i followed the instructions here : https://rog.asus.com/forum/archive/index.php/t-24576.html Here's what i get when trying to read the chip : flashrom v0.9.7-r1860 on Windows 6.1 (x86) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with GCC 4.9.1, little endian Command line (5 args): flashrom -r bios_img.bin -p buspirate_spi:dev=COM4,spispeed=1M -V Calibrating delay loop... OS timer resolution is 1000 usecs, 1565M loops per second, 10 myus = 0 us, 100 myus = 1000 us, 1000 myus = 1000 us, 10000 myus = 10000 us, 4000 myus = 4001 us, OK. Initializing buspirate_spi programmer Baud rate is 115200. Detected Bus Pirate hardware v3a Detected Bus Pirate firmware 5.10 Using SPI command set v2. SPI speed is 1MHz Raw bitbang mode version 1 Raw SPI mode version 1 The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L05PU, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L10PT, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L10PU, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L20PT, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L20PU, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L40PT, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L40PU, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L80P, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L16PT, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L16PU, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L080, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L016, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L032, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25LQ16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25LQ64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF021, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF041A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF081, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF081A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF321, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF321A, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF641(A), 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DL081, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DL161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DQ161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512B, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25FS010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25FS040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT26DF041, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT26DF081A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT26DF161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT26DF161A, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT26F004, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45CS1282, 16896 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB011D, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB021D, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB041D, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB081D, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB161D, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB321C, 4224 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB321D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB321E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB642D, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for ESMT F25L008A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for ESMT F25L32PA, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B05, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B05T, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B10T, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B20T, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B40T, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B80T, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B16T, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B32T, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B64T, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F05, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25Q40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25Q80(A), 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25Q16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25Q32(A/B), 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25Q64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25Q128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25QH16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25QH32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25QH64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25QH128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25S10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25S20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25S40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25S80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25S16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25S32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25S64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25LQ32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q20(B), 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q40(B), 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q80(B), 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q16(B), 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q32(B), 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q64(B), 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q128B, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25T80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F160S33B8, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F160S33T8, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F320S33B8, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F320S33T8, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F640S33B8, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F640S33T8, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX23L1654, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX23L3254, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX23L6454, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX23L12854, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L2005(C), 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L4005(A/C), 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L8005/MX25V8005, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L1605, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L1605A/MX25L1606E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L1635D, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L1635E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L3205(A), 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L3206E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L3273E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L3235D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L6405(D), 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L6406E/MX25L6436E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L6445E/MX25L6473E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L12805(D), 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25U1635E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25U3235E/F, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25U6435E/F, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25U12835F, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P05, 64 kB: probe_spi_res1: id 0x0 Probing for Micron/Numonyx/ST M25P10-A, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P10, 128 kB: probe_spi_res1: id 0x0 Probing for Micron/Numonyx/ST M25P20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: probe_spi_res1: id 0x0 Probing for Micron/Numonyx/ST M25P40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: probe_spi_res1: id 0x0 Probing for Micron/Numonyx/ST M25P80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PE10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PE20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PE40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M45PE10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M45PE20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M45PE40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Nantronics N25S10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Nantronics N25S20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Nantronics N25S40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Nantronics N25S80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Nantronics N25S16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LD256C, 32 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LD512(C), 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LD010(C), 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LD020(C), 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LD040(C), 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for PMC Pm25LV010A, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LV020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LV040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LV080B, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LV016B, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW203A, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Sanyo LE25FW403A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Spansion S25FL004A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL008A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL016A, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL032A/P, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL064A/P, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL204K, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL208K, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL132K, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL164K, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL127S-64kB, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL127S-256kB, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL128P......0, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL128P......1, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL128S......0, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL128S......1, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL129P......0, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL129P......1, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF020B, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF040B, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF080B, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25VF016B, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25VF032B, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25VF064C, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25WF512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25WF010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25WF020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25WF040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25WF080, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q40.V, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q80.V, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q16.V, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q32.V, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q64.V, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q128.V, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q20.W, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q40.W, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q80.W, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q16.W, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q32.W, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q64.W, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Unknown SFDP-capable chip, 0 kB: No SFDP signature found. Probing for AMIC unknown AMIC SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel unknown Atmel SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon unknown Eon SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix unknown Macronix SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC unknown PMC SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST unknown SST SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for ST unknown ST SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Generic unknown SPI chip (RDID), 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on buspirate_spi. Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, id2 0x0 Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). === This flash part has status NOT WORKING for operations: PROBE READ ERASE 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 chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Raw bitbang mode version 1 Bus Pirate shutdown completed. ____________________________________________________ ____________________________________________________ I've seen that there's probably a connection problem, so i've tried moving the pins of the bus pirate and it gives me the same error messages. Is there something i can do ? Thank you for your precious help Cordialement, Thomas LECLERCQ thomas.leclercq94(a)gmail.com

1 0

FAILED: W25Q64.W
by Davinder Pal Singh Sawhney 16 Apr '16

16 Apr '16

Dear Sir, Please help me. Here is complete log flashrom -p internal -w backup.bin flashrom v0.9.9-r1954 on Linux 3.16.0-4-686-pae (i686) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. No DMI table found. Found chipset "Intel Braswell". This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... Warning: BIOS region SMM protection is enabled! Warning: Setting Bios Control at 0x0 from 0x22 to 0x01 failed. New value is 0x22. Warning: SPI Configuration Lockdown activated. OK. Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) mapped at physical address 0xff800000. Reading old flash chip contents... done. Erasing and writing flash chip... Transaction error! spi_block_erase_20 failed during command execution at address 0x416000 Reading current flash chip contents... done. Looking for another erase function. spi_block_erase_52 failed during command execution at address 0x410000 Reading current flash chip contents... done. Looking for another erase function. spi_block_erase_d8 failed during command execution at address 0x410000 Reading current flash chip contents... done. Looking for another erase function. spi_chip_erase_60 failed during command execution Reading current flash chip contents... done. Looking for another erase function. spi_chip_erase_c7 failed during command execution Looking for another erase function. No usable erase functions left. FAILED! Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... done. Apparently at least some data has 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! flashrom -V flashrom v0.9.9-r1954 on Linux 3.16.0-4-686-pae (i686) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.2.1, GCC 4.9.2, little endian Command line (1 args): flashrom -V Please select a programmer with the --programmer parameter. Previously this was not necessary because there was a default set. To choose the mainboard of this computer use 'internal'. Valid choices are: internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, it8212, ft2232_spi, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel, nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, usbblaster_spi, pickit2_spi, ch341a_spi. -- Best Regards, Davinder

1 0

linux 4.5 segfault logs
by Arthur Heymans 15 Apr '16

15 Apr '16

Hi Sorry in the previous email the bios machine was not running 4.5 kernel coreboot machine: bios machine: -- Arthur Heymans

2 1

Support for MX25L51245G?
by Jorge Juarez 14 Apr '16

14 Apr '16

Hi, I had tried to program the MX25L51245G flash chip and I got only the output when using the command you mention in the code:flashrom -VV [plus the -p/--programmer parameter]' My output is: flashrom v0.9.7-r1861-4ba on Linux 3.10.17-poky-edison+ (i686)with patch for support SPI flash chips with 4-bytes addressingflashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.1, GCC 4.8.2, little endianCommand line (3 args): flashrom -VV -p linux_spi:dev=/dev/spidev5.1,spispeed=1000Calibrating delay loop... OS timer resolution is 3 usecs, 166M loops per second, 10 myus = 12 us, 100 myus = 103 us, 1000 myus = 1000 us, 10000 myus = 10095 us, 12 myus = 15 us, OK.Initializing linux_spi programmerUsing device /dev/spidev5.1Using 1000 kHz clockThe following protocols are supported: SPI.Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0x07, id2 0x07Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0x07, id2 0x07Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0x07, id2 0x07Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0x07, id2 0x07Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0x07, id2 0x07Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT45DB321E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L2005(C), 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L4005(A/C), 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L8005/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L1605A/MX25L1606E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L3206E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L3273E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L6405(D), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L6406E/MX25L6436E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L6445E/MX25L6473E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25L12805(D), 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix MX25U12835F, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID.Probing for Micron/Numonyx/ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID.Probing for Micron/Numonyx/ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID.Probing for Micron/Numonyx/ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID.Probing for Micron/Numonyx/ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x19, id2 0x19Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x19, id2 0x19Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x19, id2 0x19Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x19, id2 0x19Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x19, id2 0x19Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x19, id2 0x19Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x19, id2 0x19Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x19, id2 0x19Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL132K, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL164K, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL127S-64kB, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL127S-256kB, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL128P......0, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL128P......1, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL128S......1, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL129P......0, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Spansion S25FL129P......1, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0xc2, id2 0x19Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x19, id2 0x19Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x19, id2 0x19Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0xc2, id2 0x19Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0xc2, id2 0x19Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0xc2, id2 0x19Probing for SST SST25VF020B, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xc2, id2 0x19Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xc2, id2 0x19Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for SST SST25WF080, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25Q40.V, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25Q256.V, 32768 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25Q40.W, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25Q80.W, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Unknown SFDP-capable chip, 0 kB: SFDP revision = 1.6SFDP number of parameter headers is 3 (NPH = 2). SFDP parameter table header 0/2: ID 0xff00, version 1.6 Length 64 B, Parameter Table Pointer 0x000030Parsing JEDEC flash parameter table... 3-Byte (and optionally 4-Byte) addressing. Status register is non-volatile and the standard does not allow vendors to tell us whether EWSR/WREN is needed for status register writes - assuming EWSR. Write chunk size is at least 64 B. Flash chip size is 65536 kB. Block eraser 0: 16384 x 4096 B with opcode 0x20 Block eraser 1: 2048 x 32768 B with opcode 0x52 Block eraser 2: 1024 x 65536 B with opcode 0xd8 Tried to add a duplicate block eraser: 16384 x 4096 B with opcode 0x20. Page size is 256 B. Enter 4-bytes addressing mode by CMD B7hdone. SFDP parameter table header 1/2: ID 0xffc2, version 1.0 Length 16 B, Parameter Table Pointer 0x000110 SFDP parameter table header 2/2: ID 0xff84, version 1.0 Length 8 B, Parameter Table Pointer 0x0000c0Parsing JEDEC 4-byte address instuction table... Found Read CMD 13h with 4-bytes address Found Write CMD 12h with 4-bytes address Found Erase (type 1) CMD 21h with 4-bytes address Block eraser 0 (type 1) changed to opcode 0x21 Found Erase (type 2) CMD 5Ch with 4-bytes address Block eraser 1 (type 2) changed to opcode 0x5c Found Erase (type 3) CMD DCh with 4-bytes address Block eraser 2 (type 3) changed to opcode 0xdcdone.===SFDP has autodetected a flash chip which is not natively supported by flashrom yet.All standard operations (read, verify, erase and write) should work, but to support all possible features we need to add them manually.You can help us by mailing us the output of the following command to flashrom(a)flashrom.org:'flashrom -VV [plus the -p/--programmer parameter]'Thanks for your help!===Found Unknown flash chip "SFDP-capable chip" (65536 kB, SPI) on linux_spi.Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x201aProbing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xc2, id2 0x19Found Unknown flash chip "SFDP-capable chip" (65536 kB, SPI).No operations were specified. Hope the support for this chip is coming son,Thanks

1 0

Success: flashrom 0.9.9, Asus P5GD1
by Constantin Melnik 12 Apr '16

12 Apr '16

# ./flashrom -p internal:boardenable=force -V -w P5GD114.ROM flashrom v0.9.9-r1955 on Linux 2.6.32-573.22.1.el6.x86_64 (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.1.10, GCC 4.4.7 20120313 (Red Hat 4.4.7-16), little endian Command line (5 args): ./flashrom -p internal:boardenable=force -V -w P5GD114.ROM Calibrating delay loop... OS timer resolution is 1 usecs, 1753M loops per second, 10 myus = 9 us, 100 myus = 91 us, 1000 myus = 959 us, 10000 myus = 9145 us, 4 myus = 3 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Desktop" DMI string system-manufacturer: "System manufacturer" DMI string system-product-name: "System Product Name" DMI string system-version: "System Version" DMI string baseboard-manufacturer: "ASUSTeK Computer INC." DMI string baseboard-product-name: "P5GD1" DMI string baseboard-version: "Rev 1.xx" Found Winbond Super I/O, id 0x88 Found chipset "Intel ICH6/ICH6R" with PCI ID 8086:2640. Enabling flash write... 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x3 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 disabled 0xffe80000/0xffa80000 FWH decode disabled 0xffe00000/0xffa00000 FWH decode disabled 0xffd80000/0xff980000 FWH decode disabled 0xffd00000/0xff900000 FWH decode disabled 0xffc80000/0xff880000 FWH decode disabled 0xffc00000/0xff800000 FWH decode disabled 0xff700000/0xff300000 FWH decode disabled 0xff600000/0xff200000 FWH decode disabled 0xff500000/0xff100000 FWH decode disabled 0xff400000/0xff000000 FWH decode disabled Maximum FWH chip size: 0x80000 bytes SPI Read Configuration: prefetching disabled, caching enabled, BIOS_CNTL = 0x01: BIOS Lock Enable: disabled, BIOS Write Enable: enabled OK. NOTE: Running an untested board enable procedure. Please report success/failure to flashrom(a)flashrom.org. Enabling full flash access for board "ASUS P5GD1(-VM)"... Intel ICH LPC bridge: Raising GPIO21. OK. The following protocols are supported: FWH. Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x3a, id2 0x4e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xda, id2 0x34 Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xda, id2 0x34 Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xda, id2 0x34 Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xda, id2 0x34 Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xda, id2 0x34 Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x3a, id2 0x4e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xda, id2 0x34 Found Winbond flash chip "W39V040FA" (512 kB, FWH) mapped at physical address 0x00000000fff80000. Lockout bits: Hardware bootblock locking (#TBL) is not active. Hardware remaining chip locking (#WP) is not active.. Software 64 kB bootblock locking is not active. Software 16 kB bootblock locking is not active. Lock status of block at 0x00007f28936d8002 is Full Access. Lock status of block at 0x00007f28936e8002 is Full Access. Lock status of block at 0x00007f28936f8002 is Full Access. Lock status of block at 0x00007f2893708002 is Full Access. Lock status of block at 0x00007f2893718002 is Full Access. Lock status of block at 0x00007f2893728002 is Full Access. Lock status of block at 0x00007f2893738002 is Full Access. Lock status of block at 0x00007f2893748002 is Full Access. Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xda, id2 0x34 Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xda, id2 0x34 Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xda, id2 0x34 Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xda, id2 0x34 Found Winbond flash chip "W39V040FA" (512 kB, FWH). 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:E, 0x001000-0x001fff:E, 0x002000-0x002fff:EW, 0x003000-0x003fff:EW, 0x004000-0x004fff:EW, 0x005000-0x005fff:EW, 0x006000-0x006fff:EW, 0x007000-0x007fff:EW, 0x008000-0x008fff:EW, 0x009000-0x009fff:EW, 0x00a000-0x00afff:EW, 0x00b000-0x00bfff:EW, 0x00c000-0x00cfff:EW, 0x00d000-0x00dfff:EW, 0x00e000-0x00efff:EW, 0x00f000-0x00ffff:EW, 0x010000-0x010fff:EW, 0x011000-0x011fff:EW, 0x012000-0x012fff:EW, 0x013000-0x013fff:EW, 0x014000-0x014fff:EW, 0x015000-0x015fff:EW, 0x016000-0x016fff:EW, 0x017000-0x017fff:EW, 0x018000-0x018fff:EW, 0x019000-0x019fff:EW, 0x01a000-0x01afff:EW, 0x01b000-0x01bfff:EW, 0x01c000-0x01cfff:EW, 0x01d000-0x01dfff:EW, 0x01e000-0x01efff:EW, 0x01f000-0x01ffff:EW, 0x020000-0x020fff:EW, 0x021000-0x021fff:EW, 0x022000-0x022fff:EW, 0x023000-0x023fff:EW, 0x024000-0x024fff:EW, 0x025000-0x025fff:EW, 0x026000-0x026fff:EW, 0x027000-0x027fff:EW, 0x028000-0x028fff:EW, 0x029000-0x029fff:EW, 0x02a000-0x02afff:EW, 0x02b000-0x02bfff:EW, 0x02c000-0x02cfff:EW, 0x02d000-0x02dfff:EW, 0x02e000-0x02efff:EW, 0x02f000-0x02ffff:EW, 0x030000-0x030fff:EW, 0x031000-0x031fff:EW, 0x032000-0x032fff:EW, 0x033000-0x033fff:EW, 0x034000-0x034fff:EW, 0x035000-0x035fff:EW, 0x036000-0x036fff:EW, 0x037000-0x037fff:EW, 0x038000-0x038fff:EW, 0x039000-0x039fff:EW, 0x03a000-0x03afff:EW, 0x03b000-0x03bfff:EW, 0x03c000-0x03cfff:EW, 0x03d000-0x03dfff:EW, 0x03e000-0x03efff:EW, 0x03f000-0x03ffff:EW, 0x040000-0x040fff:EW, 0x041000-0x041fff:EW, 0x042000-0x042fff:EW, 0x043000-0x043fff:EW, 0x044000-0x044fff:EW, 0x045000-0x045fff:EW, 0x046000-0x046fff:EW, 0x047000-0x047fff:EW, 0x048000-0x048fff:EW, 0x049000-0x049fff:EW, 0x04a000-0x04afff:EW, 0x04b000-0x04bfff:EW, 0x04c000-0x04cfff:EW, 0x04d000-0x04dfff:EW, 0x04e000-0x04efff:EW, 0x04f000-0x04ffff:EW, 0x050000-0x050fff:EW, 0x051000-0x051fff:EW, 0x052000-0x052fff:EW, 0x053000-0x053fff:EW, 0x054000-0x054fff:EW, 0x055000-0x055fff:EW, 0x056000-0x056fff:EW, 0x057000-0x057fff:EW, 0x058000-0x058fff:EW, 0x059000-0x059fff:EW, 0x05a000-0x05afff:EW, 0x05b000-0x05bfff:EW, 0x05c000-0x05cfff:EW, 0x05d000-0x05dfff:EW, 0x05e000-0x05efff:EW, 0x05f000-0x05ffff:EW, 0x060000-0x060fff:EW, 0x061000-0x061fff:EW, 0x062000-0x062fff:EW, 0x063000-0x063fff:EW, 0x064000-0x064fff:S, 0x065000-0x065fff:S, 0x066000-0x066fff:S, 0x067000-0x067fff:S, 0x068000-0x068fff:S, 0x069000-0x069fff:S, 0x06a000-0x06afff:S, 0x06b000-0x06bfff:EW, 0x06c000-0x06cfff:E, 0x06d000-0x06dfff:E, 0x06e000-0x06efff:E, 0x06f000-0x06ffff:S, 0x070000-0x070fff:EW, 0x071000-0x071fff:EW, 0x072000-0x072fff:EW, 0x073000-0x073fff:EW, 0x074000-0x074fff:EW, 0x075000-0x075fff:EW, 0x076000-0x076fff:EW, 0x077000-0x077fff:EW, 0x078000-0x078fff:EW, 0x079000-0x079fff:EW, 0x07a000-0x07afff:EW, 0x07b000-0x07bfff:EW, 0x07c000-0x07cfff:EW, 0x07d000-0x07dfff:S, 0x07e000-0x07efff:S, 0x07f000-0x07ffff:EW Erase/write done. Verifying flash... VERIFIED. Restoring PCI config space for 00:1f:0 reg 0xdc -------------------------------------- NOTICE OF CONFIDENTIALITY This e-mail, including all materials contained in or attached to this e-mail, contains proprietary and confidential information solely for the internal use of the intended recipient. If you have received this email in error, please notify us immediately by return e-mail or otherwise and ensure that it is permanently deleted from your systems, and do not print, copy, distribute or read its contents. AVIS DE CONFIDENTIALITÉ Le présent courriel, y compris tous les documents qu'il contient ou qui y sont joints, renferme des renseignements exclusifs et confidentiels destinés uniquement à l'usage interne du destinataire prévu. Si vous avez reçu le présent courriel par erreur, veuillez nous aviser immédiatement, notamment par retour de courriel, et vous assurer qu'il est supprimé de façon permanente de vos systèmes; veuillez également vous abstenir d'imprimer, de copier, de distribuer ou de lire son contenu.

1 0

untested chipset intel
by Jan van Roessel 12 Apr '16

12 Apr '16

Marked as untested chipset Intel NUC, see attached log With kind regards, Jan van Roessel

1 0

Patch to add support for iCE40 FPGAs
by Salvador Eduardo Tropea 11 Apr '16

11 Apr '16

Hi! The following patch adds support to configure Lattice iCE40 FPGAs (formerly Silicon Blue parts). The support is to add support for the SPI flash memories attached to the FPGA. iCE40 FPGAs read its configuration from an SPI memory. This patch should support the HW-USBN-2B Lattice cable, but I used a generic FTDI FT2232 cable. It works very well for the iCE40 Blink Evaluation Kit. This kit have an M25P10-A SPI flash. Note that Lattice provides a tool for free, but I had problems with the command line version of the tool. Not to mention that the GUI version takes 1 minute, 6 seconds to configure the memory and flashrom 6 seconds ;-) About the patch: - The patch is for ft2232_spi.c file, it adds a new cable type to the ft2232_spi driver. - The type is named ice40 - Lattice's cable used GPIOL0 as CS (named SS), for this reason the patch uses this pin. - During the flash configuration the FPGA must in reset state. GPIOL3 controls the RESET line (active low), this is the same line used by Lattice cable. - Before even trying to detect a memory you must wake-up it. This is because the FPGA puts the memory to sleep. I know it sound a little bit crazy to send a command to a memory that you don't even know is there, but you can't detect it (read ID commands are ignored when the memory is in deep power down mode). - At exit the patch puts the memory to sleep and disconnects the cable. This releases the reset and hence the FPGA boots from the memory. Ideally you should check if the FPGA successfully loaded the memory content. But for this you need to read the CDONE line, lamentably this line can't be accessed in the Blink kit. Is this patch acceptable? Regards, SET -- Ing. Salvador Eduardo Tropea http://utic.inti.gob.ar/ INTI - Micro y Nanoelectrónica (CMNB) http://www.inti.gob.ar/ Unidad Técnica Sistemas Inteligentes Av. General Paz 5445 Tel: (+54 11) 4724 6300 ext. 6919 San Martín - B1650KNA FAX: (+54 11) 4754 5194 Buenos Aires * Argentina

1 0

Memory in Deep Power Down
by Salvador Eduardo Tropea 08 Apr '16

08 Apr '16

Hi! I have the following problem: the flash memory I need to program is usually at sleep. So I must wake-up it, sending a "Release from Power-down" (0xAB) command. This command (and the one to make it sleep again: Deep Power Down (0xB9)), seems to be widely supported by SPI flash chips. The most annoying detail is that you must try to wake-up the memory, even before you really know the memory is there. The memory won't reply an ID when sleeping. Right now I have a patched flashrom with support for a new SPI cable. I added the wake-up/sleep commands to the cable, but it looks confusing, because this is something that belongs to the memory. Any advice? Regards, SET -- Ing. Salvador Eduardo Tropea http://utic.inti.gob.ar/ INTI - Micro y Nanoelectrónica (CMNB) http://www.inti.gob.ar/ Unidad Técnica Sistemas Inteligentes Av. General Paz 5445 Tel: (+54 11) 4724 6300 ext. 6919 San Martín - B1650KNA FAX: (+54 11) 4754 5194 Buenos Aires * Argentina

1 0

Re: [flashrom] flashrom Digest, Vol 83, Issue 4
by Max 06 Apr '16

06 Apr '16

Antonio, seems you have purchased typical Chineese VT6421 card with fake ROM. VT6421 supports only LPC chips. Nowadays China manufacturers simply utilizes old parallel flash chips by this manner. Look thoroughly, this IC, most likely, even not connected to flash chip interface pins of VT6421 (sometimes it even soldered only on corner pins). Look with Google translate on this thread: http://forum.ixbt.com/topic.cgi?id=11:38403, with this key post: http://forum.ixbt.com/topic.cgi?id=11:38403:488#488. There's enthusiast who developed flash tool and heavily modified RAID BIOS and explored Chinese flash chip phenomenon. There are also described flash addressing issues. It's possible to desolder fake chip, add required few component and set real working BIOS chip. Actually, I done all that, soldered IC socket for BIOs chip and nowadays searching for supported LPC flash chip. =================================== Message: 2 Date: Tue, 5 Apr 2016 14:01:43 +0200 From: "Antonio Estrada Respeto" <aestradarespeto(a)gmail.com> To: <flashrom(a)flashrom.org> Subject: Re: [flashrom] VT6421 sata card with sst39Vf512 eprom Message-ID: <6FBFE9CEFEF54581B7BA6A024BA7C6B3@Asrock960gm> Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Thank you for your support. I have tried to take the output file as you request, but no luck. I always start freedos in my usb sdcard boot choosing the number 3 option, then input cswdpr0, and then execute flashrom comand. But if I try to make -o logfilename.txt, the system refuses to save the file (it says that the file does not exists). If I do not execute cswdpr0 at first time, always have a disk write error. I suppose it will be related to the file log error. Best regards, Max Arephin. 2016-04-05 20:05 GMT+03:00 <flashrom-request(a)flashrom.org>: > Send flashrom mailing list submissions to > flashrom(a)flashrom.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.flashrom.org/mailman/listinfo/flashrom > or, via email, send a message with subject or body 'help' to > flashrom-request(a)flashrom.org > > You can reach the person managing the list at > flashrom-owner(a)flashrom.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of flashrom digest..." > > > Today's Topics: > > 1. Re: [PATCH] 4 byte address mode for Macronix MX25L25735F > (Peter Martini) > 2. Re: VT6421 sata card with sst39Vf512 eprom > (Antonio Estrada Respeto) > 3. Re: MX25L6445E erase and write failed! (The Raven) > 4. Adding support for MX25L6455EMI (The Raven) > 5. Adding some functionality to the FTDI driver > (Salvador Eduardo Tropea) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 5 Apr 2016 05:06:56 -0400 > From: Peter Martini <petercmartini(a)gmail.com> > To: Tim Chick <Tim.Chick(a)mediatek.com> > Cc: David Hendricks <dhendrix(a)google.com>, "flashrom(a)flashrom.org" > <flashrom(a)flashrom.org> > Subject: Re: [flashrom] [PATCH] 4 byte address mode for Macronix > MX25L25735F > Message-ID: > < > CAFyW6MS_YkaA2_wM2H8RCeSHK2xDAFjEdCFyHv55_+TtMdw+NA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi all, > > I'd asked about support for the MX25L25635E earlier on this list [ > https://www.flashrom.org/pipermail/flashrom/2015-September/013855.html], > and have confirmed with the patches referenced there that I can read and > flash my chip. I'll try this patch tonight when I get home and report > back; I'd love to see this support main-lined. > > Peter > > On Tue, Apr 5, 2016 at 3:18 AM, Tim Chick <Tim.Chick(a)mediatek.com> wrote: > > > Hi David, > > > > > > > > There was a mistake in the logic, which I have corrected. > > > > > > > > I was also asked by someone else on the list if it worked with the > > MX25L25635F, which is 32Mbytes, but uses 3-byte addressing by default. > > > > > > > > So I made the attached changes, which switch the chip to 4-byte mode. It > > also has some dedicated 4-byte commands, and a BAR register, but it > seemed > > easiest to just use what I had tested for the MX25L25735F. I can?t > actually > > test the MX25L25635F though, as I don?t have one. > > > > > > > > Thanks, > > Tim > > > > > > > > > > > > *From:* David Hendricks [mailto:dhendrix@google.com] > > *Sent:* 04 April 2016 23:21 > > *To:* Tim Chick > > *Cc:* flashrom(a)flashrom.org > > *Subject:* Re: [flashrom] [PATCH] 4 byte address mode for Macronix > > MX25L25735F > > > > > > > > On Thu, Mar 31, 2016 at 8:21 AM, Tim Chick <Tim.Chick(a)mediatek.com> > wrote: > > > > Hi List, > > > > > > > > Flashrom would not detect this chip. When the definition was added, > > everything failed as the chip only supports 4 byte address operation. > > > > > > > > Interesting - I didn't know such chips existed. The ones I've used have > > backwards-compatible commands that support 3-byte addresses. FYI - Some > > other high-capacity chips have 4-byte address enable bit in a config > > register that will make the usual read/write/erase instructions accept 4 > > byte addresses. And yet other large chips have alternative instructions > > that function the same but only accept a 4-byte address. > > > > > > > > The attached patch adds 4 byte address support for 4 byte only chips, as > > determined by the JEDEC flash parameter table, and support for this chip > > specifically. > > > > > > > > I?ve only allowed it to work with the SPI_CONTROLLER_FT2232 controller, > as > > that is the only one I have to test. > > > > > > > > I?ve also only ported spi_block_erase_20 ? the other block erase > functions > > will fail. > > > > > > > > Please let me know what you think! > > > > > > > > Good stuff! FWIW, I have a work-in-progress patch on chromium.org ( > > https://chromium-review.googlesource.com/#/c/323359/) for the other > types > > of high-capacity flash chips. I've tested on a Spansion S25FS256 using > > linux_spi and ft2232. It needs a lot of clean-up, but might be of help. > > Most of the changes were to convert read/write/erase functions to use > > allocated buffers whose length depends on whether we're using a 3- or > > 4-byte address. > > > > > > > > I'll borrow some ideas from your patch as well to support the "4-byte > > address only" chips. > > > > > > > > -- > > > > David Hendricks (dhendrix) > > Systems Software Engineer, Google Inc. > > > > ************* Email Confidentiality Notice ******************** > > The information contained in this e-mail message (including any > > attachments) may be confidential, proprietary, privileged, or otherwise > > exempt from disclosure under applicable laws. It is intended to be > > conveyed only to the designated recipient(s). Any use, dissemination, > > distribution, printing, retaining or copying of this e-mail (including > its > > attachments) by unintended recipient(s) is strictly prohibited and may > > be unlawful. If you are not an intended recipient of this e-mail, or > believe > > that you have received this e-mail in error, please notify the sender > > immediately (by replying to this e-mail), delete any and all copies of > > this e-mail (including any attachments) from your system, and do not > > disclose the content of this e-mail to any other person. Thank you! > > > > > > _______________________________________________ > > flashrom mailing list > > flashrom(a)flashrom.org > > https://www.flashrom.org/mailman/listinfo/flashrom > > >

1 0

Adding some functionality to the FTDI driver
by Salvador Eduardo Tropea 05 Apr '16

05 Apr '16

Hi! flashrom is a very nice tool. I'm using it to configure Lattice iCE40 FPGAs. These FPGAs uses an SPI configuration memory (M25P10-A in my case). To communicate with the flash I'm using an FTDI 2232H cable (my own version, supports 0.9 to 5 V signals). The software provided by Lattice works. But I had problems with the command line version of the tool (the GUI is fine). So I searched for solutions and found flashrom. I was able to flash the chip and start the FPGA without problems. Flashrom is really fast and very easy to use. Now I want to avoid some annoying details, and I thought about adding a couple of new options to flashrom. My problem is that I need to control a system reset line. I can't access the SPI flash if the FPGA isn't in reset state (is directly connected to the SPI flash). It means that I must assert the reset line, do all the flashrom stuff and then deassert reset. This is quite easy to implement. In fact I could add a new "cable" to the ftdi.c file. But this won't solve similar problems. So I was thinking about adding options to the FTDI driver to control the initial and final state of the FTDI I/O lines. This is a little bit more complex, but will add support for a lot of situations. So my questions are: 1) Is this kind of addition desired. 2) Which way is preferred? simple/limited, complex/versatile. Regards, SET -- Ing. Salvador Eduardo Tropea http://utic.inti.gob.ar/ INTI - Micro y Nanoelectrónica (CMNB) http://www.inti.gob.ar/ Unidad Técnica Sistemas Inteligentes Av. General Paz 5445 Tel: (+54 11) 4724 6300 ext. 6919 San Martín - B1650KNA FAX: (+54 11) 4754 5194 Buenos Aires * Argentina

1 0

Adding support for MX25L6455EMI
by The Raven 05 Apr '16

05 Apr '16

Hi I have two of those chips and added support for them. This chip looks similar to the "MX25L6406E", so i took this part of code and modified it to fit the MX25L6455EMI. I have tested all erase modes (logs available if needed). spi_block_erase_20 spi_block_erase_52 spi_block_erase_d8 spi_block_erase_60 spi_block_erase_c7 I am not a coder and it's years ago since my last patch. So sorry for not posting a patch. :-( Here are my modifications (are the correct?): File flashchips.h #define MACRONIX_MX25L6455EMI 0x2617 /* MX25L6455EMI (4k 0x20) */ File flashchips.c { .vendor = "Macronix", .name = "MX25L6455EMI", .bustype = BUS_SPI, .manufacture_id = MACRONIX_ID, .model_id = MACRONIX_MX25L6455EMI, .total_size = 8192, .page_size = 256, .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, .tested = TEST_OK_PREW, .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_52, }, { .eraseblocks = { {64 * 1024, 128} }, .block_erase = spi_block_erase_d8, }, { .eraseblocks = { {8 * 1024 * 1024, 1} }, .block_erase = spi_block_erase_60, }, { .eraseblocks = { {8 * 1024 * 1024, 1} }, .block_erase = spi_block_erase_c7, } }, .printlock = spi_prettyprint_status_register_bp3_srwd, .unlock = spi_disable_blockprotect_bp3_srwd, .write = spi_chip_write_256, .read = spi_chip_read, /* Fast read (0x0B), dual I/O read supported */ .voltage = {2700, 3600}, },

1 0

Re: [flashrom] MX25L6445E erase and write failed!
by The Raven 05 Apr '16

05 Apr '16

Hi again I think the problem was that this (my) chips are defective. :-( Tested now some of them and only two are not working as they should. So i think this case can be closed. THX

1 0

VT6421 sata card with sst39Vf512 eprom
by Antonio Estrada Respeto 05 Apr '16

05 Apr '16

I have tried the below flashrom option (code tested) in order to find a right response on my no name VT6421A pci sata card, but no luck. Environment is Freedos in an usb boot sdcard device in a standard PC. Address was from 0xffff0000 to others. The card is found by flashrom at 1106:3249 BDF 02:0b.0 . The card has an Eprom flashable sst39Vf512 at is printed in top of it. Final messages are: Requested bar is of type rom. Error: No suported PCI found. Error: Program initialization failed. I managed flashrom to work with my 3C905TX and do it in the same environment as a charm. I know VT6421A hardware is very tricky depending on every pci maker. The final goal is to flash a 64k boot rom ins this card. Any help will be wellcome. Thanks in advance. The code tested: flashrom –p atavia offset=(different address) –V

3 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom