- flashrom - mail.coreboot.org

Re: [flashrom] about CH341A programmer
by Márton Miklós 18 Jul '15

18 Jul '15

Hi, Someone had already reverse engineered the protocol and created an SPI flasher tool for that: https://github.com/setarcos/ch341prog Using this code it won't be a big issue to add flashrom support. Regards, Miklos Marton > I can write to log usb activity with operations with CH341A usb > programmer from original 1.18 software with operation read, write.. > this log is very happy with support of CH341A in flashrom? >> On Tue, 6 Jan 2015 05:20:22 +0500 >> novoagansk(a)gmail.com wrote: >>> ????????????, . >>> >>> Sorry, Please tell me about: how add support for this programmer in flashrom? >>> >>> If you can - please tell me "example" how USB device parallel add in >>> flashrom. >>> >>> or other links to support any usb devices in flashrom.. >>> >>> >>> CH341A usb chip: >>> http://www.seekic.com/circuit_diagram/Basic_Circuit/USB_to_parallel_serial_… >> There is not much information available about that chip. The available >> English datasheets do not cover the most important part: the >> communication protocol between the chip and the host. Without that it >> is not exactly trivial to add support for it in flashrom. One has to >> reverse engineer the protocol first. Members of the flashrom community >> have done that for the Dediprog SF100 once but they are no longer >> active, so please don't expect it to be done. dediprog.c is probably >> the most similar programmer flashrom currently supports because it is >> the only one that uses a completely custom USB protocol. > > > Üdvözlettel, Márton Miklós +36-70-39-60-009 Üdvözlettel, Márton Miklós +36-70-39-60-009

2 1

thank you
by arno van der meer 14 Jul '15

14 Jul '15

Using flashrom i was able to repair about 180 computers. The computers are to be shipped to projects in Africa. Thanks to you thousands of students can get a computer education. With kind regards arno van der meer

1 0

user question about the ITE IT8518E SuperIO / EC
by hzh 13 Jul '15

13 Jul '15

Hello flashrom / coreboot / lm_sensors team I'm not even completely sure if I am on the correct mailinglist for my question so please excuse if I asked in the wrong category. Well, my question is quite generic. I have a laptop here which would in theory be very fine for Coreboot with a freedom OS. It's a HP 635. It's based mainly on AMD tech (E-350, A50M chipset or something close to that), Realtek (NIC, card reader) and Atheros (wireless) components. So kind of everything works. Well. Nearly. You know, there was some sort of chips, that never really cause me trouble in the past. They were there and would just always work: The Super IO chips. ITE, Fintek, Winbond, whatever. But now there is this ITE IT8518E Super IO (correctly it's an EC) which just won't seem to have a driver or documentation. HP wasn't really of help here as far as I reached anyone there. ITE was slow to respond and I don't how if I can just ask them "hey, it would be nice to have specs for writing a freedom driver for the Linux (BSD/whatever) kernel / lm_sensors and have it supported for flashrom / coreboot". Especially since I am no code hacker, I'm one of those strange users. ;) Without support for that chip there likely won't be any flashrom and thus no coreboot, right? That would be sad since otherwise the box is very suitable and fairly well equipped for the price (also has a non glare screen). I can provide you with a bunch of outputs from flashrom, superiotool, lm_sensors, lspci, lshw, dmidecode, acpidump and whatsnot if that is of help. Greetings and have nice week Haldor

1 0

Fwd: PM25LD512-SCE
by Oscar Enrique Goñi 13 Jul '15

13 Jul '15

Hi Stefan, thanks for your help! I have updated with those packages and now I can recognize the chip. However, I have an issue while trying to write the flash, here is the basic output: Calibrating delay loop... OK. Found PMC flash chip "Pm25LD512(C)" (64 kB, SPI) on ft2232_spi. Block protection could not be disabled! Reading old flash chip contents... done. Erasing and writing flash chip... and never progress. Moreover, no signals are present on the PINs and this is a part of the verbose output: Found PMC flash chip "Pm25LD512(C)" (64 kB, SPI). Some block protection in effect, disabling... Block protection could not be disabled! Chip status register is 0x20. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set Chip status register: Bit 6 is not set Chip status register: Bit 5 is set Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Reading old flash chip contents... done. Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:E Do you have any idea of the issue? Thanks in advance! Oscar 2015-07-06 21:44 GMT-03:00 Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> : > On Mon, 6 Jul 2015 10:27:32 -0300 > Oscar Enrique Goñi <ogoni(a)redimec.com.ar> wrote: > > > Hi! > > I'm Oscar, I'm from Argentina. I am trying to program the SPI Flash > > mentioned in the subject. The chip is inside an Industral computer which > > upgrade process failed (OS halted :S). I´m using the AMONTEC Jtagkey > > programmer and following the instructions on > > > http://flashrom.org/FT2232SPI_Programmer#Amontec_JTAGkey.2FJTAGkey2.2FJTAGk… > > > > Unfortunately, I am not able to write the chip (I am 99% sure that it is > OK) > > > > I only get: > > iot@iot-MS-7529:~$ flashrom -p ft2232_spi:type=jtagkey -w > > /home/iot/Escritorio/V2H0ET11.BIN > > flashrom v0.9.6.1-r1563 on Linux 3.13.0-32-generic (i686) > > flashrom is free software, get the source code at > http://www.flashrom.org > > > > Calibrating delay loop... OK. > > Found PMC flash chip "unknown PMC SPI chip" (0 kB, SPI) on ft2232_spi. > > === > > Does the programmer not support the chip? In that case, is there any way > to > > add that support? > > Hi, > > please upgrade flashrom. Support for your chip was added later. If I am > correct and you are using Ubuntu, you can use these packages: > https://launchpad.net/~flashrom-developers/+archive/ubuntu/flashrom-daily > > -- > Kind regards/Mit freundlichen Grüßen, Stefan Tauner > -- Ing. Oscar Enrique Goñi Mayor Novoa 845 B7001HVQ Tel (+54)(249) 444-2280 Tandil, BsAs. Argentina -- Ing. Oscar Enrique Goñi Mayor Novoa 845 B7001HVQ Tel (+54)(249) 444-2280 Tandil, BsAs. Argentina

1 0

Re: [flashrom] [PATCH 2/5] dediprog: Tidy up commands and remove dead nonsense code.
by Stefan Tauner 13 Jul '15

13 Jul '15

On Sun, 28 Jun 2015 16:52:51 -0700 David Hendricks <david.hendricks(a)gmail.com> wrote: > Sounds good to me. > > Acked-by: David Hendricks <dhendrix(a)chromium.org> Thanks, r1896. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

3 3

Support for ENE KB9012QF A3
by LIY 2012 12 Jul '15

12 Jul '15

Hello, I would like to request flashrom support for the ENE KB9012QF A3 chip. This chip has 128KB of internal flash memory that can be accessed through the SPI interface. The data sheet for this chip can be found at the following URL http://www.s-manuals.com/pdf/datasheet/k/b/kb9012_r0.9_ene.pdf The relevant section starts on page 218. I was able to read the contents of the chip using the SPI bus on my Raspberry pi, but unfortunately, I lack the skills to write to the chip. There is very little documentation on the write command, and I was unable to get it working in my tests. Thank you for your consideration.

1 0

Re: [flashrom] 3Com 3C905-TX Support
by Bruno Rocca 09 Jul '15

09 Jul '15

Hi Stefan, Thanks for your help and your time, I have tested the new .exe but flashrom can't detect any flash/eeprom chip on the NIC. I tested AMD and SST chips (DIP32 and PLCC32 with an adapter). I have the same card as Idwer, same model, same revision. Maybe this card was not meant for updating the chip, after all, or maybe the card is blocking write access to the flash chip. Thank you again, if you need help testing another NIC and Flash chips, just let me know. Regards, Bruno Rocca ---- Mensaje original --- De: "Stefan Tauner" <stefan.tauner(a)alumni.tuwien.ac.at> Enviado: 9 de julio de 2015 3:00 AM Para: "Bruno Rocca" <brunorocca(a)outlook.com> Cc: flashrom(a)flashrom.org Asunto: Re: [flashrom] 3Com 3C905-TX Support On Wed, 8 Jul 2015 23:24:52 -0500 Bruno Rocca <brunorocca(a)outlook.com> wrote: > Good evening, I have used flashrom for DOS on two NICs (Realtek and Intel) and have successfully flashed 128KB chips (AMD and SST). I also have a 3Com 3C905-TX, but flashrom does not support it. The vendor ID is 10B7 and the device ID is 9050. Is there any way to force flashrom to flash with this NIC? I hope this can be done. Thank you very much for your help, flashrom is an excelent tool. Hi, there is a pci programmer parameter to select one of multiple PCI devices but I don't think there is a way to force the driver to use it, if it does not in its list of supported devices. I am not exactly sure why we have never added the ID. I think Idwer had problem with his model, but apparently someone has used the following patch successfully but it was not merged. http://patchwork.coreboot.org/patch/4086/raw/ I have applied a similar patch (attached) and built a DOS executable for you: http://buildbot.flashrom.org/buildresults/flashrom-000180-Hie/dos/flashrom.… -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

3Com 3C905-TX Support
by Bruno Rocca 09 Jul '15

09 Jul '15

Good evening, I have used flashrom for DOS on two NICs (Realtek and Intel) and have successfully flashed 128KB chips (AMD and SST). I also have a 3Com 3C905-TX, but flashrom does not support it. The vendor ID is 10B7 and the device ID is 9050. Is there any way to force flashrom to flash with this NIC? I hope this can be done. Thank you very much for your help, flashrom is an excelent tool. Regards, Bruno Rocca

2 1

Re: [flashrom] PM25LD512-SCE
by Stefan Tauner 08 Jul '15

08 Jul '15

On Wed, 8 Jul 2015 08:17:02 -0300 Oscar Enrique Goñi <ogoni(a)redimec.com.ar> wrote: > Hi Stefan, thanks for your help! > I have updated with those packages and now I can recognize the chip. > However, I have an issue while trying to write the flash, here is the basic > output: > > Calibrating delay loop... OK. > Found PMC flash chip "Pm25LD512(C)" (64 kB, SPI) on ft2232_spi. > Block protection could not be disabled! > Reading old flash chip contents... done. > Erasing and writing flash chip... > > and never progress. Moreover, no signals are present on the PINs > > and this is a part of the verbose output: > > Found PMC flash chip "Pm25LD512(C)" (64 kB, SPI). > Some block protection in effect, disabling... Block protection could not be > disabled! > Chip status register is 0x20. > Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not > set > Chip status register: Bit 6 is not set > Chip status register: Bit 5 is set > Chip status register: Block Protect 2 (BP2) is not set > Chip status register: Block Protect 1 (BP1) is not set > Chip status register: Block Protect 0 (BP0) is not set > Chip status register: Write Enable Latch (WEL) is not set > Chip status register: Write In Progress (WIP/BUSY) is not set > Reading old flash chip contents... done. > Erasing and writing flash chip... Trying erase function 0... > 0x000000-0x000fff:E > > Do you have any idea of the issue? Hi, according to the datasheet of your flashchip (it is a non-C version BTW), that bit #5 should always read as 0. However, flashrom should not care about it (and the message about failing to disable the block protection is a bug I need to investigate later), so that should not be the cause of the problem. The real problem is a loop in flashrom that queries the flash chip's status register after initiating an erase. We currently wait indefinitely for the flash chip to signal that it is done. Some chips never do that if they are broken and then flashrom keeps running till killed. There are a few hacks you could try, but you would need to modify the source of flashrom and recompile it (it is not very hard but you should be familiar with the command line). However, I fear that it won't help you because the chip is broken. This could also explain why the update process failed. You could replace the flash chip with a similar model if you are able to solder it in place. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] PM25LD512-SCE
by Stefan Tauner 08 Jul '15

08 Jul '15

On Mon, 6 Jul 2015 10:27:32 -0300 Oscar Enrique Goñi <ogoni(a)redimec.com.ar> wrote: > Hi! > I'm Oscar, I'm from Argentina. I am trying to program the SPI Flash > mentioned in the subject. The chip is inside an Industral computer which > upgrade process failed (OS halted :S). I´m using the AMONTEC Jtagkey > programmer and following the instructions on > http://flashrom.org/FT2232SPI_Programmer#Amontec_JTAGkey.2FJTAGkey2.2FJTAGk… > > Unfortunately, I am not able to write the chip (I am 99% sure that it is OK) > > I only get: > iot@iot-MS-7529:~$ flashrom -p ft2232_spi:type=jtagkey -w > /home/iot/Escritorio/V2H0ET11.BIN > flashrom v0.9.6.1-r1563 on Linux 3.13.0-32-generic (i686) > flashrom is free software, get the source code at http://www.flashrom.org > > Calibrating delay loop... OK. > Found PMC flash chip "unknown PMC SPI chip" (0 kB, SPI) on ft2232_spi. > === > Does the programmer not support the chip? In that case, is there any way to > add that support? Hi, please upgrade flashrom. Support for your chip was added later. If I am correct and you are using Ubuntu, you can use these packages: https://launchpad.net/~flashrom-developers/+archive/ubuntu/flashrom-daily -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] C232HM + MX25L1606E
by Stefan Tauner 07 Jul '15

07 Jul '15

On Tue, 7 Jul 2015 15:44:52 +0800 an jacker <nimdakey(a)gmail.com> wrote: > Hi, > thank you for your replay. i connect the chip and C232HM as follow: > > > my Chip ------------C232HM > > (1)CS# ----- CS > (2)SO ----- TDI > (3)WP# ----- (not connected) > (4)VSS ----- GND > (5)SI ----- TDO > (6)SCK ----- CLK > (7)HOLD----- (not connected) > (8)VDD ----- 3.3V > > Wherein did I make my mistake? > how do i connect it? > can you give me a tip? thank you You should *always* connect *all* input pins of an IC. Connect 3 and 7 to 3.3V. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] C232HM + MX25L1606E
by Stefan Tauner 07 Jul '15

07 Jul '15

Hi, your chip is not connected properly. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

PM25LD512-SCE
by Oscar Enrique Goñi 06 Jul '15

06 Jul '15

Hi! I'm Oscar, I'm from Argentina. I am trying to program the SPI Flash mentioned in the subject. The chip is inside an Industral computer which upgrade process failed (OS halted :S). I´m using the AMONTEC Jtagkey programmer and following the instructions on http://flashrom.org/FT2232SPI_Programmer#Amontec_JTAGkey.2FJTAGkey2.2FJTAGk… Unfortunately, I am not able to write the chip (I am 99% sure that it is OK) I only get: iot@iot-MS-7529:~$ flashrom -p ft2232_spi:type=jtagkey -w /home/iot/Escritorio/V2H0ET11.BIN flashrom v0.9.6.1-r1563 on Linux 3.13.0-32-generic (i686) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found PMC flash chip "unknown PMC SPI chip" (0 kB, SPI) on ft2232_spi. === Does the programmer not support the chip? In that case, is there any way to add that support? Hope you can aid me! Best Regards -- Ing. Oscar Enrique Goñi Mayor Novoa 845 B7001HVQ Tel (+54)(249) 444-2280 Tandil, BsAs. Argentina

1 0

Re: [flashrom] [PATCH 0/3] Some serprog improvements
by Urja Rannikko 05 Jul '15

05 Jul '15

On Sun, Jun 28, 2015 at 4:56 AM, Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> wrote: > I plan to include them (and probably some of Urja's patches too) in > flashrom 0.9.8.1. > > Stefan Tauner (3): > serprog: clear NDELAY flag only once after opening the port. > serprog: ignore failures when setting serial port options. > serprog: allow to omit specifying a baud rate. > > flashrom.8.tmpl | 26 ++++++++++++----------- > programmer.h | 4 +--- > serial.c | 66 ++++++++++++++++++++++++++++++++++++++++----------------- > serprog.c | 44 ++++++++++++++++++++------------------ > 4 files changed, 84 insertions(+), 56 deletions(-) > These all 3 tested as a series on two of my serprog flashers, one with an FT232RL (arduino LPC+SPI shield) and one with a virtual serial port, a Teensy 3.1 LPC+SPI (and on two PCs just to check that my i586 works too.). Did try out the ability to leave out the baudrate of both of those (one run to set the rate is needed on the "real serial port" == FT232RL). Also reviewed the code, no comments from me. Acked-by: Urja Rannikko <urjaman(a)gmail.com> -- Urja Rannikko

1 0

[commit] r1896 - trunk
by repository service 05 Jul '15

05 Jul '15

Author: stefanct Date: Sun Jul 5 18:53:22 2015 New Revision: 1896 URL: http://flashrom.org/trac/flashrom/changeset/1896 Log: dediprog: Tidy up commands and remove dead nonsense code. Use names for the commands and request types instead of magic numbers and remove some of the unnecessary unexplained arguments. Also, cleanup the nonsense code left over from RE. Most of it can not be explained by official documentation and was recorded with ancient firmware/software. Based on the following chromiumos changes: Change-Id: I80a0dcdf40eedc89da48fb2c54cd9d9fd13e6fa1 Change-Id: If61bac2c8194b3ec30a80422d871842c66f0cd74 Signed-off-by: Simon Glass <sjg(a)chromium.org> Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: David Hendricks <dhendrix(a)chromium.org> Modified: trunk/dediprog.c Modified: trunk/dediprog.c ============================================================================== --- trunk/dediprog.c Tue Jun 30 01:24:23 2015 (r1895) +++ trunk/dediprog.c Sun Jul 5 18:53:22 2015 (r1896) @@ -2,6 +2,8 @@ * This file is part of the flashrom project. * * Copyright (C) 2010 Carl-Daniel Hailfinger + * Copyright (C) 2015 Simon Glass + * Copyright (C) 2015 Stefan Tauner * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by @@ -38,13 +40,13 @@ #define FIRMWARE_VERSION(x,y,z) ((x << 16) | (y << 8) | z) #define DEFAULT_TIMEOUT 3000 +#define REQTYPE_OTHER_OUT (USB_ENDPOINT_IN | USB_TYPE_VENDOR | USB_RECIP_OTHER) /* 0x43 */ +#define REQTYPE_OTHER_IN (USB_ENDPOINT_IN | USB_TYPE_VENDOR | USB_RECIP_OTHER) /* 0xC3 */ +#define REQTYPE_EP_OUT (USB_ENDPOINT_OUT | USB_TYPE_VENDOR | USB_RECIP_ENDPOINT) /* 0x42 */ +#define REQTYPE_EP_IN (USB_ENDPOINT_IN | USB_TYPE_VENDOR | USB_RECIP_ENDPOINT) /* 0xC2 */ static usb_dev_handle *dediprog_handle; -static int dediprog_firmwareversion; static int dediprog_endpoint; -#define DEDI_SPI_CMD_PAGEWRITE 0x1 -#define DEDI_SPI_CMD_AAIWRITE 0x4 - enum dediprog_leds { LED_INVALID = -1, LED_NONE = 0, @@ -54,6 +56,80 @@ LED_ALL = 7, }; +/* IO bits for CMD_SET_IO_LED message */ +enum dediprog_ios { + IO1 = 1 << 0, + IO2 = 1 << 1, + IO3 = 1 << 2, + IO4 = 1 << 3, +}; + +enum dediprog_cmds { + CMD_TRANSCEIVE = 0x01, + CMD_POLL_STATUS_REG = 0x02, + CMD_SET_VPP = 0x03, + CMD_SET_TARGET = 0x04, + CMD_READ_EEPROM = 0x05, + CMD_WRITE_EEPROM = 0x06, + CMD_SET_IO_LED = 0x07, + CMD_READ_PROG_INFO = 0x08, + CMD_SET_VCC = 0x09, + CMD_SET_STANDALONE = 0x0A, + CMD_GET_BUTTON = 0x11, + CMD_GET_UID = 0x12, + CMD_SET_CS = 0x14, + CMD_IO_MODE = 0x15, + CMD_FW_UPDATE = 0x1A, + CMD_FPGA_UPDATE = 0x1B, + CMD_READ_FPGA_VERSION = 0x1C, + CMD_SET_HOLD = 0x1D, + CMD_READ = 0x20, + CMD_WRITE = 0x30, + CMD_WRITE_AT45DB = 0x31, + CMD_NAND_WRITE = 0x32, + CMD_NAND_READ = 0x33, + CMD_SET_SPI_CLK = 0x61, + CMD_CHECK_SOCKET = 0x62, + CMD_DOWNLOAD_PRJ = 0x63, + CMD_READ_PRJ_NAME = 0x64, + // New protocol/firmware only + CMD_CHECK_SDCARD = 0x65, + CMD_READ_PRJ = 0x66, +}; + +enum dediprog_target { + FLASH_TYPE_APPLICATION_FLASH_1 = 0, + FLASH_TYPE_FLASH_CARD, + FLASH_TYPE_APPLICATION_FLASH_2, + FLASH_TYPE_SOCKET, +}; + +enum dediprog_readmode { + READ_MODE_STD = 1, + READ_MODE_FAST = 2, + READ_MODE_ATMEL45 = 3, + READ_MODE_4B_ADDR_FAST = 4, + READ_MODE_4B_ADDR_FAST_0x0C = 5, /* New protocol only */ +}; + +enum dediprog_writemode { + WRITE_MODE_PAGE_PGM = 1, + WRITE_MODE_PAGE_WRITE = 2, + WRITE_MODE_1B_AAI = 3, + WRITE_MODE_2B_AAI = 4, + WRITE_MODE_128B_PAGE = 5, + WRITE_MODE_PAGE_AT26DF041 = 6, + WRITE_MODE_SILICON_BLUE_FPGA = 7, + WRITE_MODE_64B_PAGE_NUMONYX_PCM = 8, /* unit of length 512 bytes */ + WRITE_MODE_4B_ADDR_256B_PAGE_PGM = 9, + WRITE_MODE_32B_PAGE_PGM_MXIC_512K = 10, /* unit of length 512 bytes */ + WRITE_MODE_4B_ADDR_256B_PAGE_PGM_0x12 = 11, + WRITE_MODE_4B_ADDR_256B_PAGE_PGM_FLAGS = 12, +}; + + +static int dediprog_firmwareversion = FIRMWARE_VERSION(0, 0, 0); + #if 0 /* Might be useful for other pieces of code as well. */ static void print_hex(void *buf, size_t len) @@ -84,8 +160,6 @@ return NULL; } -//int usb_control_msg(usb_dev_handle *dev, int requesttype, int request, int value, int index, char *bytes, int size, int timeout); - /* This function sets the GPIOs connected to the LEDs as well as IO1-IO4. */ static int dediprog_set_leds(int leds) { @@ -108,7 +182,8 @@ } target_leds ^= 7; - int ret = usb_control_msg(dediprog_handle, 0x42, 0x07, 0x09, target_leds, NULL, 0x0, DEFAULT_TIMEOUT); + int ret = usb_control_msg(dediprog_handle, REQTYPE_EP_OUT, CMD_SET_IO_LED, 0x09, target_leds, + NULL, 0x0, DEFAULT_TIMEOUT); if (ret != 0x0) { msg_perr("Command Set LED 0x%x failed (%s)!\n", leds, usb_strerror()); return 1; @@ -147,8 +222,8 @@ /* Wait some time as the original driver does. */ programmer_delay(200 * 1000); } - ret = usb_control_msg(dediprog_handle, 0x42, 0x9, voltage_selector, - 0xff, NULL, 0x0, DEFAULT_TIMEOUT); + ret = usb_control_msg(dediprog_handle, REQTYPE_EP_OUT, CMD_SET_VCC, voltage_selector, 0, + NULL, 0x0, DEFAULT_TIMEOUT); if (ret != 0x0) { msg_perr("Command Set SPI Voltage 0x%x failed!\n", voltage_selector); @@ -178,13 +253,6 @@ { NULL, 0x0 }, }; -/* After dediprog_set_spi_speed, the original app always calls - * dediprog_set_spi_voltage(0) and then - * dediprog_check_devicestring() four times in a row. - * After that, dediprog_command_a() is called. - * This looks suspiciously like the microprocessor in the SF100 has to be - * restarted/reinitialized in case the speed changes. - */ static int dediprog_set_spi_speed(unsigned int spispeed_idx) { if (dediprog_firmwareversion < FIRMWARE_VERSION(5, 0, 0)) { @@ -192,12 +260,13 @@ return 0; } - msg_pdbg("SPI speed is %s Hz\n", spispeeds[spispeed_idx].name); + const struct dediprog_spispeeds *spispeed = &spispeeds[spispeed_idx]; + msg_pdbg("SPI speed is %sHz\n", spispeed->name); - int ret = usb_control_msg(dediprog_handle, 0x42, 0x61, spispeeds[spispeed_idx].speed, 0xff, + int ret = usb_control_msg(dediprog_handle, REQTYPE_EP_OUT, CMD_SET_SPI_CLK, spispeed->speed, 0xff, NULL, 0x0, DEFAULT_TIMEOUT); if (ret != 0x0) { - msg_perr("Command Set SPI Speed 0x%x failed!\n", spispeeds[spispeed_idx].speed); + msg_perr("Command Set SPI Speed 0x%x failed!\n", spispeed->speed); return 1; } return 0; @@ -233,7 +302,7 @@ /* Command Read SPI Bulk. No idea which read command is used on the * SPI side. */ - ret = usb_control_msg(dediprog_handle, 0x42, 0x20, start % 0x10000, + ret = usb_control_msg(dediprog_handle, REQTYPE_EP_OUT, CMD_READ, start % 0x10000, start / 0x10000, (char *)count_and_chunk, sizeof(count_and_chunk), DEFAULT_TIMEOUT); if (ret != sizeof(count_and_chunk)) { @@ -342,7 +411,7 @@ /* Command Write SPI Bulk. No idea which write command is used on the * SPI side. */ - ret = usb_control_msg(dediprog_handle, 0x42, 0x30, start % 0x10000, start / 0x10000, + ret = usb_control_msg(dediprog_handle, REQTYPE_EP_OUT, CMD_WRITE, start % 0x10000, start / 0x10000, (char *)count_and_cmd, sizeof(count_and_cmd), DEFAULT_TIMEOUT); if (ret != sizeof(count_and_cmd)) { msg_perr("Command Write SPI Bulk failed, %i %s!\n", ret, @@ -420,12 +489,12 @@ static int dediprog_spi_write_256(struct flashctx *flash, const uint8_t *buf, unsigned int start, unsigned int len) { - return dediprog_spi_write(flash, buf, start, len, DEDI_SPI_CMD_PAGEWRITE); + return dediprog_spi_write(flash, buf, start, len, WRITE_MODE_PAGE_PGM); } static int dediprog_spi_write_aai(struct flashctx *flash, const uint8_t *buf, unsigned int start, unsigned int len) { - return dediprog_spi_write(flash, buf, start, len, DEDI_SPI_CMD_AAIWRITE); + return dediprog_spi_write(flash, buf, start, len, WRITE_MODE_2B_AAI); } static int dediprog_spi_send_command(struct flashctx *flash, @@ -437,29 +506,26 @@ int ret; msg_pspew("%s, writecnt=%i, readcnt=%i\n", __func__, writecnt, readcnt); - /* Paranoid, but I don't want to be blamed if anything explodes. */ - if (writecnt > 16) { - msg_perr("Untested writecnt=%i, aborting.\n", writecnt); + if (writecnt > UINT16_MAX) { + msg_perr("Invalid writecnt=%i, aborting.\n", writecnt); return 1; } - /* 16 byte reads should work. */ - if (readcnt > 16) { - msg_perr("Untested readcnt=%i, aborting.\n", readcnt); + if (readcnt > UINT16_MAX) { + msg_perr("Invalid readcnt=%i, aborting.\n", readcnt); return 1; } - ret = usb_control_msg(dediprog_handle, 0x42, 0x1, 0xff, - readcnt ? 0x1 : 0x0, (char *)writearr, writecnt, - DEFAULT_TIMEOUT); + ret = usb_control_msg(dediprog_handle, REQTYPE_EP_OUT, CMD_TRANSCEIVE, 0, readcnt ? 0x1 : 0x0, + (char *)writearr, writecnt, DEFAULT_TIMEOUT); if (ret != writecnt) { msg_perr("Send SPI failed, expected %i, got %i %s!\n", writecnt, ret, usb_strerror()); return 1; } - if (!readcnt) + if (readcnt == 0) return 0; - memset(readarr, 0, readcnt); - ret = usb_control_msg(dediprog_handle, 0xc2, 0x01, 0xbb8, 0x0000, + + ret = usb_control_msg(dediprog_handle, REQTYPE_EP_IN, CMD_TRANSCEIVE, 0, 0, (char *)readarr, readcnt, DEFAULT_TIMEOUT); if (ret != readcnt) { msg_perr("Receive SPI failed, expected %i, got %i %s!\n", @@ -475,27 +541,27 @@ int fw[3]; char buf[0x11]; +#if 0 /* Command Prepare Receive Device String. */ - memset(buf, 0, sizeof(buf)); - ret = usb_control_msg(dediprog_handle, 0xc3, 0x7, 0x0, 0xef03, buf, - 0x1, DEFAULT_TIMEOUT); + ret = usb_control_msg(dediprog_handle, REQTYPE_OTHER_IN, 0x7, 0x0, 0xef03, + buf, 0x1, DEFAULT_TIMEOUT); /* The char casting is needed to stop gcc complaining about an always true comparison. */ if ((ret != 0x1) || (buf[0] != (char)0xff)) { msg_perr("Unexpected response to Command Prepare Receive Device" " String!\n"); return 1; } +#endif /* Command Receive Device String. */ - memset(buf, 0, sizeof(buf)); - ret = usb_control_msg(dediprog_handle, 0xc2, 0x8, 0xff, 0xff, buf, - 0x10, DEFAULT_TIMEOUT); + ret = usb_control_msg(dediprog_handle, REQTYPE_EP_IN, CMD_READ_PROG_INFO, 0, 0, + buf, 0x10, DEFAULT_TIMEOUT); if (ret != 0x10) { msg_perr("Incomplete/failed Command Receive Device String!\n"); return 1; } buf[0x10] = '\0'; msg_pdbg("Found a %s\n", buf); - if (memcmp(buf, "SF100", 0x5)) { + if (memcmp(buf, "SF100", 0x5) != 0) { msg_perr("Device not a SF100!\n"); return 1; } @@ -513,24 +579,20 @@ return 0; } -/* Command A seems to be some sort of device init. It is either followed by - * dediprog_check_devicestring (often) or Command A (often) or - * Command F (once). - */ -static int dediprog_command_a(void) +static int dediprog_device_init(void) { int ret; char buf[0x1]; memset(buf, 0, sizeof(buf)); - ret = usb_control_msg(dediprog_handle, 0xc3, 0xb, 0x0, 0x0, buf, - 0x1, DEFAULT_TIMEOUT); + ret = usb_control_msg(dediprog_handle, REQTYPE_OTHER_IN, 0x0B, 0x0, 0x0, + buf, 0x1, DEFAULT_TIMEOUT); if (ret < 0) { msg_perr("Command A failed (%s)!\n", usb_strerror()); return 1; } if ((ret != 0x1) || (buf[0] != 0x6f)) { - msg_perr("Unexpected response to Command A!\n"); + msg_perr("Unexpected response to init!\n"); return 1; } return 0; @@ -546,9 +608,8 @@ int ret; char buf[0x3]; - memset(buf, 0, sizeof(buf)); - ret = usb_control_msg(dediprog_handle, 0xc3, 0x7, 0x0, 0xef00, buf, - 0x3, DEFAULT_TIMEOUT); + ret = usb_control_msg(dediprog_handle, REQTYPE_OTHER_IN, 0x7, 0x0, 0xef00, + buf, 0x3, DEFAULT_TIMEOUT); if (ret < 0) { msg_perr("Command B failed (%s)!\n", usb_strerror()); return 1; @@ -563,120 +624,29 @@ } #endif -/* Command Chip Select is only sent after dediprog_check_devicestring, but not after every - * invocation of dediprog_check_devicestring. It is only sent after the first - * dediprog_command_a(); dediprog_check_devicestring() sequence in each session. - * Bit #1 of the value changes the chip select: 0 is target 1, 1 is target 2 and parameter target can be 1 or 2 - * respectively. We don't know how to encode "3, Socket" and "0, reference card" yet. On SF100 the vendor - * software "DpCmd 6.0.4.06" selects target 2 when requesting 3 (which is unavailable on that hardware). - */ -static int dediprog_chip_select(int target) +static int set_target_flash(enum dediprog_target target) { - int ret; - uint16_t value = ((target - 1) & 1) << 1; - msg_pdbg("Selecting target chip %i\n", target); - ret = usb_control_msg(dediprog_handle, 0x42, 0x4, value, 0x0, NULL, - 0x0, DEFAULT_TIMEOUT); - if (ret != 0x0) { - msg_perr("Command Chip Select failed (%s)!\n", usb_strerror()); + int ret = usb_control_msg(dediprog_handle, REQTYPE_EP_OUT, CMD_SET_TARGET, target, 0, + NULL, 0, DEFAULT_TIMEOUT); + if (ret != 0) { + msg_perr("set_target_flash failed (%s)!\n", usb_strerror()); return 1; } return 0; } #if 0 -/* Very strange. Seems to be a programmer keepalive or somesuch. - * Wait unsuccessfully for timeout ms to read one byte. - * Is usually called after setting voltage to 0. - * Present in all logs with Firmware 2.1.1 and 3.1.8 - */ -static int dediprog_command_f(int timeout) -{ - int ret; - char buf[0x1]; - - memset(buf, 0, sizeof(buf)); - ret = usb_control_msg(dediprog_handle, 0xc2, 0x11, 0xff, 0xff, buf, - 0x1, timeout); - /* This check is most probably wrong. Command F always causes a timeout - * in the logs, so we should check for timeout instead of checking for - * success. - */ - if (ret != 0x1) { - msg_perr("Command F failed (%s)!\n", usb_strerror()); - return 1; - } - return 0; -} - -/* Start/stop blinking? - * Present in eng_detect_blink.log with firmware 3.1.8 - * Preceded by Command J - */ -static int dediprog_command_g(void) -{ - int ret; - - ret = usb_control_msg(dediprog_handle, 0x42, 0x07, 0x09, 0x03, NULL, 0x0, DEFAULT_TIMEOUT); - if (ret != 0x0) { - msg_perr("Command G failed (%s)!\n", usb_strerror()); - return 1; - } - return 0; -} - -/* Something. - * Present in all logs with firmware 5.1.5 - * Always preceded by Command Receive Device String - * Always followed by Command Set SPI Voltage nonzero - */ -static int dediprog_command_h(void) -{ - int ret; - - ret = usb_control_msg(dediprog_handle, 0x42, 0x07, 0x09, 0x05, NULL, 0x0, DEFAULT_TIMEOUT); - if (ret != 0x0) { - msg_perr("Command H failed (%s)!\n", usb_strerror()); - return 1; - } - return 0; -} - -/* Shutdown for firmware 5.x? - * Present in all logs with firmware 5.1.5 - * Often preceded by a SPI operation (Command Read SPI Bulk or Receive SPI) - * Always followed by Command Set SPI Voltage 0x0000 - */ -static int dediprog_command_i(void) +/* Returns true if the button is currently pressed. */ +static bool dediprog_get_button(void) { - int ret; - - ret = usb_control_msg(dediprog_handle, 0x42, 0x07, 0x09, 0x06, NULL, 0x0, DEFAULT_TIMEOUT); - if (ret != 0x0) { - msg_perr("Command I failed (%s)!\n", usb_strerror()); + char buf[1]; + int ret = usb_control_msg(dediprog_handle, REQTYPE_EP_IN, CMD_GET_BUTTON, 0, 0, + buf, 0x1, DEFAULT_TIMEOUT); + if (ret != 0) { + msg_perr("Could not get button state (%s)!\n", usb_strerror()); return 1; } - return 0; -} - -/* Start/stop blinking? - * Present in all logs with firmware 5.1.5 - * Always preceded by Command Receive Device String on 5.1.5 - * Always followed by Command Set SPI Voltage nonzero on 5.1.5 - * Present in eng_detect_blink.log with firmware 3.1.8 - * Preceded by Command B in eng_detect_blink.log - * Followed by Command G in eng_detect_blink.log - */ -static int dediprog_command_j(void) -{ - int ret; - - ret = usb_control_msg(dediprog_handle, 0x42, 0x07, 0x09, 0x07, NULL, 0x0, DEFAULT_TIMEOUT); - if (ret != 0x0) { - msg_perr("Command J failed (%s)!\n", usb_strerror()); - return 1; - } - return 0; + return buf[0] != 1; } #endif @@ -728,28 +698,6 @@ return millivolt; } -static int dediprog_setup(long target) -{ - /* URB 6. Command A. */ - if (dediprog_command_a()) { - return 1; - } - /* URB 7. Command A. */ - if (dediprog_command_a()) { - return 1; - } - /* URB 8. Command Prepare Receive Device String. */ - /* URB 9. Command Receive Device String. */ - if (dediprog_check_devicestring()) { - return 1; - } - /* URB 10. Command Chip Select */ - if (dediprog_chip_select(target)) { - return 1; - } - return 0; -} - static const struct spi_master spi_master_dediprog = { .type = SPI_CONTROLLER_DEDIPROG, .max_data_read = MAX_DATA_UNSPECIFIED, @@ -765,12 +713,7 @@ { msg_pspew("%s\n", __func__); -#if 0 - /* Shutdown on firmware 5.x */ - if (dediprog_firmwareversion == 5) - if (dediprog_command_i()) - return 1; -#endif + dediprog_firmwareversion = FIRMWARE_VERSION(0, 0, 0); /* URB 28. Command Set SPI Voltage to 0. */ if (dediprog_set_spi_voltage(0x0)) @@ -815,6 +758,7 @@ } free(spispeed); } + voltage = extract_programmer_param("voltage"); if (voltage) { millivolt = parse_voltage(voltage); @@ -910,90 +854,28 @@ return 1; /* Perform basic setup. */ - if (dediprog_setup(target)) { + if (dediprog_device_init()) + return 1; + if (dediprog_check_devicestring()) return 1; - } /* Set all possible LEDs as soon as possible to indicate activity. * Because knowing the firmware version is required to set the LEDs correctly we need to this after * dediprog_setup() has queried the device and set dediprog_firmwareversion. */ dediprog_set_leds(LED_ALL); - /* After setting voltage and speed, perform setup again. */ - if (dediprog_set_spi_voltage(0) || dediprog_set_spi_speed(spispeed_idx) || dediprog_setup(target)) { - dediprog_set_leds(LED_ERROR); - return 1; - } - - /* URB 11. Command Set SPI Voltage. */ - if (dediprog_set_spi_voltage(millivolt)) { + /* Select target/socket, frequency and VCC. */ + if (set_target_flash(FLASH_TYPE_APPLICATION_FLASH_1) || + dediprog_set_spi_speed(spispeed_idx) || + dediprog_set_spi_voltage(millivolt)) { dediprog_set_leds(LED_ERROR); return 1; } register_spi_master(&spi_master_dediprog); - /* RE leftover, leave in until the driver is complete. */ -#if 0 - /* Execute RDID by hand if you want to test it. */ - dediprog_do_stuff(); -#endif - dediprog_set_leds(LED_NONE); return 0; } -#if 0 -/* Leftovers from reverse engineering. Keep for documentation purposes until - * completely understood. - */ -static int dediprog_do_stuff(void) -{ - char buf[0x4]; - /* SPI command processing starts here. */ - - /* URB 12. Command Send SPI. */ - /* URB 13. Command Receive SPI. */ - memset(buf, 0, sizeof(buf)); - /* JEDEC RDID */ - msg_pdbg("Sending RDID\n"); - buf[0] = JEDEC_RDID; - if (dediprog_spi_send_command(JEDEC_RDID_OUTSIZE, JEDEC_RDID_INSIZE, - (unsigned char *)buf, (unsigned char *)buf)) - return 1; - msg_pdbg("Receiving response: "); - print_hex(buf, JEDEC_RDID_INSIZE); - /* URB 14-27 are more SPI commands. */ - /* URB 28. Command Set SPI Voltage. */ - if (dediprog_set_spi_voltage(0x0)) - return 1; - /* URB 29-38. Command F, unsuccessful wait. */ - if (dediprog_command_f(544)) - return 1; - /* URB 39. Command Set SPI Voltage. */ - if (dediprog_set_spi_voltage(0x10)) - return 1; - /* URB 40. Command Set SPI Speed. */ - if (dediprog_set_spi_speed(0x2)) - return 1; - /* URB 41 is just URB 28. */ - /* URB 42,44,46,48,51,53 is just URB 8. */ - /* URB 43,45,47,49,52,54 is just URB 9. */ - /* URB 50 is just URB 6/7. */ - /* URB 55-131 is just URB 29-38. (wait unsuccessfully for 4695 (maybe 4751) ms)*/ - /* URB 132,134 is just URB 6/7. */ - /* URB 133 is just URB 29-38. */ - /* URB 135 is just URB 8. */ - /* URB 136 is just URB 9. */ - /* URB 137 is just URB 11. */ - - /* Command Start Bulk Read. Data is u16 blockcount, u16 blocksize. */ - /* Command Start Bulk Write. Data is u16 blockcount, u16 blocksize. */ - /* Bulk transfer sizes for Command Start Bulk Read/Write are always - * 512 bytes, rest is filled with 0xff. - */ - - return 0; -} -#endif

1 0

W25Q80.V: ASrock G41M-VS3 successfully reflashed
by Александр Трубицын 05 Jul '15

05 Jul '15

Hi! -- with best regards, Alexander V. Trubitsyn

2 1

MX25L8006E: Gigabyte EG43M-S2H successfully reflashed to F7C bios
by Александр Трубицын 05 Jul '15

05 Jul '15

Hi! -- With best regards, Alexander V. Trubitsyn

2 1

Gigabyte H55M-S2 don't reflashed
by Александр Трубицын 05 Jul '15

05 Jul '15

Hi! I can't read the name of the flash chip on the motherboard. Try to read it later with magnifying glass. -- With best regards, Alexander V. Trubitsyn

2 3

W25Q64.V: Asrock H67DE3 don't read from flash
by Александр Трубицын 05 Jul '15

05 Jul '15

Hi! I try to read flash by the boot from usb-stick into non UEFI mode. May be boot it in UEFY mode???

2 1

MX25L6406E: Gigabyte GA-H77-DS3H successfully reflashed
by Александр Трубицын 05 Jul '15

05 Jul '15

Hi! -- with best regards, Alexander V. Trubitsyn

2 1

Serprog future, 32bit addressing, and I'd like to get rid of write+poll sequences for each byte...
by Urja Rannikko 04 Jul '15

04 Jul '15

Hi, So Stefan suggested that serprog should switch to 32-bit addressing and do it with a change of protocol version, thus creating a compatibility boundary and also significantly slowing down the case of 1-byte writes (write_jedec_1, write_28sf040, write_82802ab, ... also write_en29lv640b but that writes 16bit words*) but with the positive side of keeping the flashrom serprog driver simpler in that sense (no supoprt code for old 24bit)... I had different ideas (either a 2-byte command to switch the highest byte of the address or just a bunch of new 32bit addressing commands), but I thought about it for a moment, trying to find what would be needed for the protocol version change to be OK with me: 1. frser-duino (and other SPI-only) being about the only serprog firmware not used only by developers should continue to work; in essense we'd allow protocol version 1 if supported bustypes is only SPI because for SPI-only functionality the versions would be identical (maybe if contains SPI and other mask only to SPI and print warning, but i dunno.) - I'd switch the libfrser SPI-only build to announce version 2 much later (if at all), in essense when most distributed flashrom versions would've gotten the version 2 support. 2. We should get rid of write_jedec_1 resulting in a huge sequence of 1-byte writes (and polls) being sent to the programmer - this is the case that the bigger addressing would noticeably impact (with like 5 ops with address per byte written). Also, I'm now assuming this would be after we get something like the write_jedec_1 changes and poll opcode supoprt I've made here: https://github.com/urjaman/flashrom/commits/serprog-improvements into flashrom. I'll try to look at them again and clean that up into a patch sequence for review/comments in the meantime. So my suggestion/idea is that we'd essentially hint the programmer code about the 1-byte write sequence being done, kinda something like this: static int write_byte_program_jedec_common(const struct flashctx *flash, const uint8_t *src, chipaddr dst, unsigned int mask) { chipaddr bios = flash->virtual_memory; chip_hint(BYTE_PGM_START); /* Issue JEDEC Byte Program command */ start_program_jedec_common(flash, mask); chip_hint(BYTE_PGM_DATA_ADDR_DATA_BYTE); /* transfer data from source to destination */ chip_writeb(flash, *src, dst); toggle_ready_jedec(flash, bios); chip_hint(BYTE_PGM_END); return 0; } where each hint (except start/end just to contain the sequence) would only affect the next operation (write or poll) done, and the possible options would be: immediate/const address and data (default if no hint) variable address (const data) (this'd be used by the 82802b and 28sf040 stuff) variable data (const address) (no use for this afaik but these can be implemented as 2 bits that allow this). variable address and data where "variable" means the address and data of the byte being written and const being just embedded into the sequence that is repeated for each byte. Serprog code would create the sequence for writing the byte on the first byte and transfer it into the device and on subsequent bytes just verify that the sequence hasnt changed (if has, send a new sequence - this would allow the sequence to contain stuff like a page address, as long as it doesnt change on every byte) and compile these programming writeb's into an extended write-n command that'd be sent to the device where each byte would represent going through the sequence stored previously with new address and data for that byte. * write_en29lv640b: I dunno what do do about this for this case... maybe just leave it as is until somebody has one and wants to test stuff...I mean we could design the serprog protocol to allow hinting of 2-byte sequences too... So, comments? -- Urja Rannikko

1 0

Re: [flashrom] [PATCH 4/5] dediprog: Support new communication protocol.
by David Woodhouse 03 Jul '15

03 Jul '15

On Mon, 2015-06-22 at 03:37 +0200, Stefan Tauner wrote: > +/* Returns true if firmware (and thus hardware) supports the "new" protocol */ > +static bool is_new_prot(void) > { > - size_t i; > + /* if (SF100) */ > + return dediprog_firmwareversion >= FIRMWARE_VERSION(5, 5, 0); > + /* else if (SF600) > + return dediprog_firmwareversion >= FIRMWARE_VERSION(6, 9, 0); > */ ... and in dediprog_check_devicestring() we still have: msg_pdbg("Found a %s\n", buf); if (memcmp(buf, "SF100", 0x5) != 0) { msg_perr("Device not a SF100!\n"); return 1; } Is this patch set actually intended to support SF600? I had assumed so, so I've rounded up some potential testers for that, and was just trying to put together something for them to test... -- David Woodhouse Open Source Technology Centre David.Woodhouse(a)intel.com Intel Corporation

1 0

Aspeed 2450
by Paul van der Vlis 02 Jul '15

02 Jul '15

Hello, I would like support for the Aspeed ast2450. This BMC SOC is interesting, because there is a free IPMI solution for it from Facebook. It's in many servers from Supermicro's, MSI, ASUS, Advantech, Gigabyte, Tyan and Lenovo. https://github.com/facebook/openbmc https://code.facebook.com/posts/1601610310055392/introducing-openbmc-an-ope… With regards, Paul van der Vlis. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl/

1 1

Fwd: W836xx
by mstaken＠comcast.net 02 Jul '15

02 Jul '15

----- Forwarded Message ----- From: mstaken(a)comcast.net To: flashrom(a)flashrom.org Sent: Mon, 29 Jun 2015 00:12:19 -0000 (UTC) Subject: W836xx flashrom v0.9.5.2-r1546 on Linux 3.2.0-4-amd64 (x86_64) flashrom was built with libpci 3.1.7, GCC 4.6.2, little endian Command line (7 args): flashrom -p internal:laptop=this_is_not_a_laptop -V -r bios.rom -o flashrom.log Calibrating delay loop... OS timer resolution is 1 usecs, 665M loops per second, 10 myus = 10 us, 100 myus = 101 us, 1000 myus = 1000 us, 10000 myus = 10017 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "Hewlett-Packard" DMI string system-product-name: "23-g017c" DMI string system-version: " " DMI string baseboard-manufacturer: "Hewlett-Packard" DMI string baseboard-product-name: "2B06" DMI string baseboard-version: "A01" DMI string chassis-type: "All In One" DMI chassis-type is not specific enough. W836xx enter config mode worked or we were already in config mode. W836xx leave config mode had no effect. Active config mode, unknown reg 0x20 ID: 85. Please send the output of "flashrom -V" to flashrom(a)flashrom.org with W836xx: your board name: flashrom -V as the subject to help us finish support for your Super I/O. Thanks. Found ITE EC, ID 0x8518,Rev 0x08 on port 0x4e. ======================================================================== WARNING! You may be running flashrom on an unsupported laptop. We could not detect this for sure because your vendor has not setup the SMBIOS tables correctly. You can enforce execution by adding '-p internal:laptop=this_is_not_a_laptop' to the command line, but please read the following warning if you are not sure. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See http://www.flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== Proceeding anyway because user forced us to. Found chipset "AMD Hudson" with PCI ID 1022:780e. Enabling flash write... SPI base address is at 0xfec10000 AltSpiCSEnable=0, SpiRomEnable=1, AbortEnable=0 PrefetchEnSPIFromIMC=0, PrefetchEnSPIFromHost=1, SpiOpEnInLpcMode=1 SpiArbEnable=1, SpiAccessMacRomEn=1, SpiHostAccessRomEn=0, ArbWaitCount=7, SpiBridgeDisable=1, DropOneClkOnRd=0 NormSpeed is Reserved MHz GPIO11 used for SPI_DO GPIO12 used for SPI_DI GPIO31 used for SPI_HOLD GPIO32 used for SPI_CS GPIO47 used for SPI_CLK SB700 IMC is not active. ROM strap override is not active OK. Super I/O ID 0x8518 is not on the list of flash capable controllers. The following protocols are supported: LPC, FWH, SPI. Probing for AMIC A25L05PT, 64 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L05PU, 64 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L10PT, 128 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L10PU, 128 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L20PT, 256 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L20PU, 256 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L40PT, 512 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L40PU, 512 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L80P, 1024 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L16PT, 2048 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L16PU, 2048 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L512, 64 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L010, 128 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L020, 256 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L040, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L080, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L016, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25L032, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A25LQ032, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT25DF021, 256 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT25DF041A, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT25DF081, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT25DF081A, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT25DF161, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT25DF321, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT25DF321A, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT25DF641(A), 8192 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT25DQ161, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT25F512B, 64 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT25FS010, 128 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT25FS040, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT26DF041, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT26DF081A, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT26DF161, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT26DF161A, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT26F004, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT45CS1282, 16896 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT45DB011D, 128 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT45DB021D, 256 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT45DB041D, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT45DB081D, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT45DB161D, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT45DB321C, 4224 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT45DB321D, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel AT45DB642D, 8192 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for EMST F25L008A, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B05, 64 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B05T, 64 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B10, 128 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B10T, 128 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B20, 256 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B20T, 256 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B40, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B40T, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B80, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B80T, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B16, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B16T, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B32, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B32T, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B64, 8192 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25B64T, 8192 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25F05, 64 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25F10, 128 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25F20, 256 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25F40, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25F80, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25F16, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25F32, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25Q40, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25Q80(A), 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25Q16, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25Q32(A/B), 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25Q64, 8192 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25Q128, 16384 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25QH16, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon EN25QH32, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for GigaDevice GD25Q20, 256 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for GigaDevice GD25Q40, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for GigaDevice GD25Q80, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for GigaDevice GD25Q16, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for GigaDevice GD25Q32, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for GigaDevice GD25Q64, 8192 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for GigaDevice GD25Q128, 16384 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Macronix MX25L512, 64 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Macronix MX25L1005, 128 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Macronix MX25L2005, 256 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Macronix MX25L4005, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Macronix MX25L8005, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Macronix MX25L1605, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Macronix MX25L1635D, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Macronix MX25L1635E, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Macronix MX25L3205, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Macronix MX25L3235D, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Macronix MX25L6405, 8192 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Macronix MX25L12805, 16384 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Numonyx M25PE10, 128 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Numonyx M25PE20, 256 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Numonyx M25PE40, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Numonyx M25PE80, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Numonyx M25PE16, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Numonyx N25Q064, 8192 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for PMC Pm25LV010, 128 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for PMC Pm25LV016B, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for PMC Pm25LV020, 256 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for PMC Pm25LV040, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for PMC Pm25LV080B, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for PMC Pm25LV512, 64 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Sanyo LF25FW203A, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Spansion S25FL004A, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Spansion S25FL008A, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Spansion S25FL016A, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Spansion S25FL032A, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Spansion S25FL064A, 8192 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for SST SST25LF040A, 512 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 5 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for SST SST25LF080A, 1024 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 5 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for SST SST25VF010, 128 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 5 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for SST SST25VF016B, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for SST SST25VF032B, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for SST SST25VF064C, 8192 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for SST SST25VF040, 512 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 5 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for SST SST25VF040B, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for SST SST25VF040B.REMS, 512 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 5 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for SST SST25VF080B, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25P05-A, 64 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25P05, 64 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. SB600 FIFO pointer corruption! Pointer is 3, wanted 5 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25P10-A, 128 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25P10, 128 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. SB600 FIFO pointer corruption! Pointer is 3, wanted 5 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25P20, 256 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25P40, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25P40-old, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. SB600 FIFO pointer corruption! Pointer is 3, wanted 5 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25P80, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25P16, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25P32, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25P64, 8192 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25P128, 16384 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25PX16, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25PX32, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST M25PX64, 8192 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Winbond W25Q80, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Winbond W25Q16, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Winbond W25Q32, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Winbond W25Q64, 8192 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Winbond W25Q128, 16384 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Winbond W25X10, 128 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Winbond W25X20, 256 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Winbond W25X40, 512 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Winbond W25X80, 1024 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Winbond W25X16, 2048 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Winbond W25X32, 4096 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Winbond W25X64, 8192 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Unknown SFDP-capable chip, 0 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 6 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Receiving SFDP signature failed. Probing for AMIC unknown AMIC SPI chip, 0 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 4 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Atmel unknown Atmel SPI chip, 0 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Eon unknown Eon SPI chip, 0 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Macronix unknown Macronix SPI chip, 0 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for PMC unknown PMC SPI chip, 0 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for SST unknown SST SPI chip, 0 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for ST unknown ST SPI chip, 0 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Sanyo unknown Sanyo SPI chip, 0 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Generic unknown SPI chip (RDID), 0 kB: SB600 FIFO pointer corruption! Pointer is 0, wanted 3 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for Generic unknown SPI chip (REMS), 0 kB: SB600 FIFO pointer corruption! Pointer is 3, wanted 5 Something else is accessing the flash chip and causes random corruption. Please stop all applications and drivers and IPMI which access the flash chip. Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x00, id2 0x56, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0x85, id2 0xdb, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0x00, id2 0x56, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0x85, id2 0xdb, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x00, id2 0x56, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x85, id2 0xdb, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0x85, id2 0xdb, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0x85, id2 0xdb, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xa4, id2 0x28, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0x00, id2 0x56, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0x00, id2 0x56, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0x85, id2 0xdb, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xa4, id2 0x28, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0x85, id2 0xdb, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0x85, id2 0xdb, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x00, id2 0x56, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xa4, id2 0x28, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0x85, id2 0xdb, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xa4, id2 0x28, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0x85, id2 0xdb, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0x00, id2 0x56, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x00, id2 0x56, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0x85, id2 0xdb, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0x82, id2 0x84, id1 parity violation, id1 is normal flash content, id2 is normal flash content No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically.

1 0

Re: [flashrom] need a windows snapshot for flashrom v 0.9.8 or v 0.9.7
by Topolinux 02 Jul '15

02 Jul '15

Hi David G ZHAO, Stefan Tauner is right you have to take a look at the documentations (http://flashrom.org/Downloads#Binary_packages), there it's the answer. Anyway being you unable to compile it by yourself following the instructions, here you go where you can take a chance: http://buildbot.flashrom.org/buildresults/?M=D You may find usable Windows binaries there, but please pay attention that they are usually untested and not recommended to be trusted blindly. You are warned. Regards, Topolinux

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom