- flashrom - mail.coreboot.org

Varification trouble - flashrom v0.9.9-r1954, Intel I210 NIC over SPI, Microchip SST25VF040B
by Lamont Dean 12 Dec '17

12 Dec '17

Hello, Flashrom can find the Intel I210 NIC SPI connected to the SST25VF040B flash chip and seems to program but fails to verify and gave me this email to write to about it. The output is included below. Before and after a power cycle the Intel I210 still says its in its unprogrammed state. I'd like to program a Microchip SST26VF016B flash in place of the ...25VF040... but its not on the list so I'm going through the comments I found on the wedsite Design Guide <https://www.flashrom.org/Development_Guidelines>. I'm new to Linux and things so we'll see how it goes. Any help you can offer would be greatly appreciated. Thanks, LaMont Dean Hardware Engineer ImSAR, LLC. ...flashrom> sudo flashrom -VVVV -p nicintel_spi:pci=01:00.0 -c SST25VF040B -w Dev_Start_I210_Copper_NOMNG_4Mb_A2_3.25_0.03.bin flashrom v0.9.9-r1954 on Linux 4.4.38-tegra (aarch64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.3.1, GCC 5.4.0 20160609, little endian Command line (7 args): flashrom -VVVV -p nicintel_spi:pci=01:00.0 -c SST25VF040B -w Dev_Start_I210_Copper_NOMNG_4Mb_A2_3.25_0.03.bin Calibrating delay loop... OS timer resolution is 1 usecs, 2531M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1001 us, 10000 myus = 10022 us, 4 myus = 4 us, OK. Initializing nicintel_spi programmer Found "Intel Unprogrammed i210 Gigabit Ethernet Controller" (8086:1531, BDF 01:00.0). === This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output to flashrom(a)flashrom.org if it works for you. Please add the name of your PCI device to the subject. Thank you for your help! === PCI header type 0x00 Requested BAR is of type MEM, 32bit, not prefetchable PCI header type 0x00 Requested BAR is of type MEM, 32bit, not prefetchable page_size=1000 pre-rounding: start=0x0000000050800000, len=0x1000, end=0x0000000050801000 post-rounding: start=0x0000000050800000, len=0x1000, end=0x0000000050801000 The following protocols are supported: SPI. Probing for SST SST25VF040B, 512 kB: programmer_map_flash_region: mapping SST25VF040B from 0x00000000fff80000 to 0x0000000000000000 RDID returned 0xbf 0x25 0x8d. probe_spi_rdid_generic: id1 0xbf, id2 0x258d Found SST flash chip "SST25VF040B" (512 kB, SPI) on nicintel_spi. Chip status register is 0x1c. Chip status register: Block Protect Write Disable (BPL) is not set Chip status register: Auto Address Increment Programming (AAI) is not set Chip status register: Block Protect 3 (BP3) is not set Chip status register: Block Protect 2 (BP2) is set Chip status register: Block Protect 1 (BP1) is set Chip status register: Block Protect 0 (BP0) is set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Resulting block protection : all blocks programmer_unmap_flash_region: unmapped 0x0000000000000000 programmer_map_flash_region: mapping SST25VF040B from 0x00000000fff80000 to 0x0000000000000000 Some block protection in effect, disabling... Block protection could not be disabled! Chip status register is 0x1c. Chip status register: Block Protect Write Disable (BPL) is not set Chip status register: Auto Address Increment Programming (AAI) is not set Chip status register: Block Protect 3 (BP3) is not set Chip status register: Block Protect 2 (BP2) is set Chip status register: Block Protect 1 (BP1) is set Chip status register: Block Protect 0 (BP0) is set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Resulting block protection : all blocks Reading old flash chip contents... done. Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:W, 0x001000-0x001fff:S, 0x002000-0x002fff:W, 0x003000-0x003fff:W, 0x004000-0x004fff:W, 0x005000-0x005fff:W, 0x006000-0x006fff:W, 0x007000-0x007fff:W, 0x008000-0x008fff:W, 0x009000-0x009fff:W, 0x00a000-0x00afff:W, 0x00b000-0x00bfff:W, 0x00c000-0x00cfff:W, 0x00d000-0x00dfff:W, 0x00e000-0x00efff:W, 0x00f000-0x00ffff:W, 0x010000-0x010fff:W, 0x011000-0x011fff:W, 0x012000-0x012fff:W, 0x013000-0x013fff:W, 0x014000-0x014fff:W, 0x015000-0x015fff:W, 0x016000-0x016fff:W, 0x017000-0x017fff:W, 0x018000-0x018fff:W, 0x019000-0x019fff:W, 0x01a000-0x01afff:W, 0x01b000-0x01bfff:W, 0x01c000-0x01cfff:W, 0x01d000-0x01dfff:W, 0x01e000-0x01efff:W, 0x01f000-0x01ffff:W, 0x020000-0x020fff:W, 0x021000-0x021fff:W, 0x022000-0x022fff:W, 0x023000-0x023fff:W, 0x024000-0x024fff:W, 0x025000-0x025fff:W, 0x026000-0x026fff:W, 0x027000-0x027fff:W, 0x028000-0x028fff:W, 0x029000-0x029fff:W, 0x02a000-0x02afff:W, 0x02b000-0x02bfff:W, 0x02c000-0x02cfff:W, 0x02d000-0x02dfff:W, 0x02e000-0x02efff:W, 0x02f000-0x02ffff:W, 0x030000-0x030fff:W, 0x031000-0x031fff:W, 0x032000-0x032fff:W, 0x033000-0x033fff:W, 0x034000-0x034fff:W, 0x035000-0x035fff:W, 0x036000-0x036fff:W, 0x037000-0x037fff:W, 0x038000-0x038fff:S, 0x039000-0x039fff:S, 0x03a000-0x03afff:S, 0x03b000-0x03bfff:S, 0x03c000-0x03cfff:W, 0x03d000-0x03dfff:W, 0x03e000-0x03efff:W, 0x03f000-0x03ffff:S, 0x040000-0x040fff:S, 0x041000-0x041fff:S, 0x042000-0x042fff:S, 0x043000-0x043fff:S, 0x044000-0x044fff:S, 0x045000-0x045fff:S, 0x046000-0x046fff:S, 0x047000-0x047fff:S, 0x048000-0x048fff:S, 0x049000-0x049fff:S, 0x04a000-0x04afff:S, 0x04b000-0x04bfff:S, 0x04c000-0x04cfff:S, 0x04d000-0x04dfff:S, 0x04e000-0x04efff:S, 0x04f000-0x04ffff:S, 0x050000-0x050fff:S, 0x051000-0x051fff:S, 0x052000-0x052fff:S, 0x053000-0x053fff:S, 0x054000-0x054fff:S, 0x055000-0x055fff:S, 0x056000-0x056fff:S, 0x057000-0x057fff:S, 0x058000-0x058fff:S, 0x059000-0x059fff:S, 0x05a000-0x05afff:S, 0x05b000-0x05bfff:S, 0x05c000-0x05cfff:S, 0x05d000-0x05dfff:S, 0x05e000-0x05efff:S, 0x05f000-0x05ffff:S, 0x060000-0x060fff:S, 0x061000-0x061fff:S, 0x062000-0x062fff:S, 0x063000-0x063fff:S, 0x064000-0x064fff:S, 0x065000-0x065fff:S, 0x066000-0x066fff:S, 0x067000-0x067fff:S, 0x068000-0x068fff:S, 0x069000-0x069fff:S, 0x06a000-0x06afff:S, 0x06b000-0x06bfff:S, 0x06c000-0x06cfff:S, 0x06d000-0x06dfff:S, 0x06e000-0x06efff:S, 0x06f000-0x06ffff:S, 0x070000-0x070fff:S, 0x071000-0x071fff:S, 0x072000-0x072fff:S, 0x073000-0x073fff:S, 0x074000-0x074fff:S, 0x075000-0x075fff:S, 0x076000-0x076fff:S, 0x077000-0x077fff:S, 0x078000-0x078fff:S, 0x079000-0x079fff:S, 0x07a000-0x07afff:S, 0x07b000-0x07bfff:S, 0x07c000-0x07cfff:S, 0x07d000-0x07dfff:S, 0x07e000-0x07efff:S, 0x07f000-0x07ffff:S Erase/write done. Verifying flash... FAILED at 0x00000000! Expected=0x00, Found=0xff, failed byte count from 0x00000000-0x0007ffff: 0x3527c Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! programmer_unmap_flash_region: unmapped 0x0000000000000000

1 0

Error Message - Your flash chip is in an unknown state.
by Kazer Soze 12 Dec '17

12 Dec '17

Good morning I have a "W25Q128.V" chip on my board and i made a backup off the old boot. I have try to inject the new one but no luck at all. I have this error message appear. "Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25Q128.V" (16384 kB, SPI) on linux_spi. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x000af000! Expected=0xff, Found=0x00, failed byte count from 0x000af000-0x000affff: 0x500 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Erase/write done. Verifying flash... FAILED at 0x00036bca! Expected=0x00, Found=0x04, failed byte count from 0x00000000-0x00ffffff: 0x1ea6 Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks!" Any chance that you could help me please?

1 0

W836xx: QNAP 253a: flashrom -V
by uno 10 Dec '17

10 Dec '17

./flashrom -V -p internal flashrom v0.9.8-unknown on Linux 4.2.8 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.1, GCC 4.8.2, little endian Command line (3 args): ./flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 745M loops per second, 10 myus = 10 us, 100 myus = 109 us, 1000 myus = 1009 us, 10000 myus = 10020 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Other" DMI chassis-type is not specific enough. DMI string system-manufacturer: "Default string" DMI string system-product-name: "Default string" DMI string system-version: "Default string" DMI string baseboard-manufacturer: "AMI Corporation" DMI string baseboard-product-name: "Aptio CRB" DMI string baseboard-version: "Default string" 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 -p internal" 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 0x8528, Rev 0x0a on port 0x2e. ======================================================================== 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 the manpage and 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. ======================================================================== Aborting. Error: Programmer initialization failed. [/share/Public] #

1 0

Re: [flashrom] chipset not found
by David Hendricks 10 Dec '17

10 Dec '17

On Wed, Dec 6, 2017 at 8:29 PM, David Velasco <david(a)bemusic.al> wrote: > Hi carl, > > I have the following error: > > # flashrom --programmer internal > flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Calibrating delay loop... OK. > WARNING: *No chipset found. Flash detection will most likely fail.* > No EEPROM/flash device found. > Note: flashrom can never write if the flash chip isn't found automatically. > # flashrom --programmer internal > flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Calibrating delay loop... OK. > WARNING: No chipset found. Flash detection will most likely fail. > No EEPROM/flash device found. > Note: flashrom can never write if the flash chip isn't found automatically. > # flashrom > flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Please select a programmer with the --programmer parameter. > Previously this was not necessary because there was a default set. > To choose the mainboard of this computer use 'internal'. Valid choices are: > internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, > it8212, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel, > nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, pickit2_spi, > ch341a_spi. > > > I can give you the result of > > lspci -nnvvvxxx > > Yes, please copy + paste lspci output to https://paste.flashrom.org/ .

1 0

chipset not found
by David Velasco 07 Dec '17

07 Dec '17

Hi carl, I have the following error: # flashrom --programmer internal flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. WARNING: *No chipset found. Flash detection will most likely fail.* No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. # flashrom --programmer internal flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. WARNING: No chipset found. Flash detection will most likely fail. No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. # flashrom flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Please select a programmer with the --programmer parameter. Previously this was not necessary because there was a default set. To choose the mainboard of this computer use 'internal'. Valid choices are: internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, it8212, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel, nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, pickit2_spi, ch341a_spi. I can give you the result of lspci -nnvvvxxx Thanks!

1 0

No EEPROM/flash device found
by JASON.HT.HUANG 黃宏宗 06 Dec '17

06 Dec '17

Hi, I try to write bios. However, I always got “No EEPROM/flash device found”. Could you give me some suggestions. Thanks Jason.Huang 黃宏宗 Delta Networks, INC. TEL：+886-2-8797-3250 ext.3050 E-Mail：Jason.ht.huang(a)delta.com.tw ************************************************************************* This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. [Delta Electronics, INC. Taiwan] *************************************************************************

1 0

Re: [flashrom] particular spi flash controller
by Andriy Gapon 01 Dec '17

01 Dec '17

On 01/12/2017 19:36, David Hendricks wrote: > > > On Fri, Dec 1, 2017 at 12:11 AM, Andriy Gapon <avg(a)freebsd.org > <mailto:avg@freebsd.org>> wrote: > > > Hello. > > I wonder if anyone here encountered an SPI flash controller (master) that has a > three register interface where the first register is used for control and status > bits, the second register is used for setting a flash address (if one is needed) > and the third is used for reading or writing the flash data. A specific > operation is requested by writing an SPI opcode into the control register. > The interface seems to be rather simple, but I couldn't find any driver that > implements access to anything like that or any documentation that would describe > a similar interface. > > Does it sound familiar to anyone? > Could anyone give me some hints / pointers? > > > Is this an interface that you've actually used before? It sounds too simplistic > since at the very least you'd also need to set the number of bytes to transfer, > the direction, and have some control over chip select. Likely, those things are set in the control register, but I don't know the exact meaning of the bits. Also, some status bits are checked in the same register to make sure that the operation is completed. I can make some guesses, but I'd rather find documentation if possible. Meanwhile, I also looked at Linux drivers and this one seems to be somewhat similar but still different: http://elixir.free-electrons.com/linux/latest/source/drivers/spi/spi-falcon… See SFCMD / SFADDR / SFDATA. -- Andriy Gapon

1 0

particular spi flash controller
by Andriy Gapon 01 Dec '17

01 Dec '17

Hello. I wonder if anyone here encountered an SPI flash controller (master) that has a three register interface where the first register is used for control and status bits, the second register is used for setting a flash address (if one is needed) and the third is used for reading or writing the flash data. A specific operation is requested by writing an SPI opcode into the control register. The interface seems to be rather simple, but I couldn't find any driver that implements access to anything like that or any documentation that would describe a similar interface. Does it sound familiar to anyone? Could anyone give me some hints / pointers? Thanks! -- Andriy Gapon

2 1

Re: [flashrom] Using libflashrom from fwupd
by Richard Hughes 01 Dec '17

01 Dec '17

On 18 August 2017 at 09:10, Richard Hughes <hughsient(a)gmail.com> wrote: >> three calls into libflashrom which take some time > libflashrom would be called by fwupd Does anyone know the status of libflashrom now? I'm wondering whether to merge in the flashrom-cli tool to fwupd[1] or just wait for libflashrom to show up. Richard. [1] https://github.com/hughsie/fwupd/pull/295

1 0

Re: [flashrom] flashrom not "seeing" W25Q128FV
by Ivan Ivanov 26 Nov '17

26 Nov '17

Hi Yaron, its very interesting why MOSI voltage is low. Have you tried disconnecting the peripheral devices like RAM ? about Bus Pirate - which firmware you have? (Bus Pirate old firmware is not good quality, its much more stable if you flash a new "Community Firmware" to it - github BusPirate/Bus_Pirate ) Also please try getting CH341A - it is very cheap flasher which should be reliable thanks to its' simplicity. Another idea: there are small circuit boards called " Step-Up Voltage Regulator " - some versions of them convert 0.5-3.3V to 3.3V --- however if you increase the voltage, it would be less current (maybe not enough to transmit a signal). Still I really hope that you could flash it without complicating a setup by adding the new boards... Best regards, Ivan 2017-11-24 17:56 GMT+03:00 Yaron Shragai <yshragai.firmware(a)gmail.com>: > Thank you Ivan. > > As I mentioned, I did try with/without the board plugged in, and > with/without the VCC pin connected to the programmer. (I also tried, on an > identical board that still has a booting BIOS, powering it on to a point > that likely has no BMC traffic.) > > One thing that we have determined, using a scope, is that the VCC pin does > likely get appropriate voltage, but the signals on the MOSI pin are not at a > high enough voltage: The voltage at the MOSI pin, when signals are being > sent, is about 1/2 VCC. This explains why it almost always isn't successful > at finding the chip, but every once in a while, on a rare occasion, it is. > So now the question is, why is the voltage on the MOSI pin too low - what is > pulling it down. > > I'm getting identical results with both the Dediprog SF100 and a Bus Pirate > (not sure which version). And I did try the trick on the Bus Pirate where > you apply the VCC voltage to the Bus Pirate's VUP (pull-up voltage) pin, and > used the flashrom argument to turn on the pull-ups. > > Thanks, > Yaron > > > On Wed, Nov 22, 2017 at 10:29 AM, Ivan Ivanov <qmastery16(a)gmail.com> wrote: >> >> Hi Yaron, please read about the In-System Programming. It could be >> that the peripheral devices of your motherboard are consuming some >> percentage of the power that was aimed to power a BIOS chip during the >> access - because of that, there is not enough power for a BIOS chip >> and your attempts are failing. What to do: >> >> I) You could try to reduce the amount of peripheral devices - e.g. >> disconnect the RAM modules from your system and try again >> >> II) Also you can try to power a BIOS chip by the motherboard : >> 1) disconnect a VCC wire from your programmer, also disconnect WP and >> HOLD just in case >> 2) disconnect all the boot devices from your motherboard >> 3) connect a clip to a BIOS chip >> 4) connect a power adapter to your motherboard and turn it on >> 5) just in case, wait 5 minutes so that all the initialization >> processes will be completed >> 6) read the contains of a BIOS chip a few times >> 7) compare the checksums of read files, if they are the same - erase >> the BIOS chip (by filling it with FF's), turn off the motherboard, >> then turn it on again, wait 5 minutes - then flash your desired binary >> image to this BIOS chip >> >> III) Alternatively you may want to de-solder a BIOS chip from >> motherboard and connect it to your programmer with DIP adapter, but >> probably could be avoided if you do I) or II) successfully >> >> IV) Try a different programmer, e.g. CH341A which is super cheap >> simple hardware fully supported by flashrom - should be reliable >> >> I wish you good luck, sadly Supermicro X10DRT-Lis not supported by >> coreboot open source BIOS - hopefully you will be able to get a better >> hardware one day... >> >> Best regards, >> >> 2017-11-21 17:57 GMT+03:00 Yaron Shragai <yshragai.firmware(a)gmail.com>: >> > Hello, >> > I am trying to use flashrom to program a Winbond W25Q128FV chip, on a >> > Supermicro X10DRT-L mobo, with a Dediprog SF 100. >> > >> > I am running flashrom from an Ubuntu VM on a Win10 laptop as well as >> > from a >> > Minnowboard Max system running Ubuntu. >> > I am running flashrom v0.9.9-rc1-r1942, installed via apt. >> > I am connecting to the chip via a SOIC clip. >> > >> > I should note that I have looked at the product support data on the >> > flashrom >> > web site. It lists full support for the W25Q128FV. It does not list >> > the >> > X10DRT-L mobo. >> > >> > flashrom almost never "sees" the flash chip (output: "No EEPROM/flash >> > device >> > found."). >> > >> > I say "almost", b/c it did see it a couple of times (out of, I would >> > say, >> > ~100 tries) - which was enough for me to read out the pre-existing >> > content, >> > and write to it an image that has effectively bricked it. :-) So, now >> > I'm >> > trying to flash the pre-existing content back... (There is no >> > documented >> > way to force the X10DRT-L to use the recovery block, and I have yet to >> > find >> > an undocumented way...) >> > >> > I have tried with the system board plugged in and unplugged, and with >> > and >> > without connecting the VCC pin to the programmer. >> > >> > I have been using these two command lines, at various times: >> > flashrom -p dediprog >> > flashrom -p dediprog:voltage=3.5 >> > >> > When I add -VVV, the following relevant lines appear in the output: >> > >> > Probing for Winbond W25Q128.V, 16384 kB: programmer_map_flash_region: >> > mapping W25Q128.V from 0x00000000ff000000 to 0x0000000000000000 >> > dediprog_spi_send_command, writecnt=1, readcnt=3 >> > RDID returned 0xff 0xff 0xff. RDID byte 0 parity violation. >> > probe_spi_rdid_generic: id1 0xff, id2 0xffff >> > programmer_unmap_flash_region: unmapped 0x0000000000000000 >> > >> > ...and further down... >> > >> > Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: >> > dediprog_spi_send_command, writecnt=1, readcnt=3 >> > RDID returned 0xff 0xff 0xff. RDID byte 0 parity violation. >> > probe_spi_rdid_generic: id1 0xff, id2 0xffff >> > >> > One more datapoint: When I connect my laptop -> Dediprog -> to the flash >> > chip on the Minnowboard Max (Micron 25Q064A), it does recognize the >> > chip. >> > >> > Any advice would be appreciated! >> > >> > Thanks, >> > Yaron >> > >> > _______________________________________________ >> > flashrom mailing list >> > flashrom(a)flashrom.org >> > https://mail.coreboot.org/mailman/listinfo/flashrom > >

1 0

Re: [flashrom] flashrom not "seeing" W25Q128FV
by Yaron Shragai 24 Nov '17

24 Nov '17

Thank you Ivan. As I mentioned, I did try with/without the board plugged in, and with/without the VCC pin connected to the programmer. (I also tried, on an identical board that still has a booting BIOS, powering it on to a point that likely has no BMC traffic.) One thing that we have determined, using a scope, is that the VCC pin does likely get appropriate voltage, but the signals on the MOSI pin are not at a high enough voltage: The voltage at the MOSI pin, when signals are being sent, is about 1/2 VCC. This explains why it almost always isn't successful at finding the chip, but every once in a while, on a rare occasion, it is. So now the question is, why is the voltage on the MOSI pin too low - what is pulling it down. I'm getting identical results with both the Dediprog SF100 and a Bus Pirate (not sure which version). And I did try the trick on the Bus Pirate where you apply the VCC voltage to the Bus Pirate's VUP (pull-up voltage) pin, and used the flashrom argument to turn on the pull-ups. Thanks, Yaron On Wed, Nov 22, 2017 at 10:29 AM, Ivan Ivanov <qmastery16(a)gmail.com> wrote: > Hi Yaron, please read about the In-System Programming. It could be > that the peripheral devices of your motherboard are consuming some > percentage of the power that was aimed to power a BIOS chip during the > access - because of that, there is not enough power for a BIOS chip > and your attempts are failing. What to do: > > I) You could try to reduce the amount of peripheral devices - e.g. > disconnect the RAM modules from your system and try again > > II) Also you can try to power a BIOS chip by the motherboard : > 1) disconnect a VCC wire from your programmer, also disconnect WP and > HOLD just in case > 2) disconnect all the boot devices from your motherboard > 3) connect a clip to a BIOS chip > 4) connect a power adapter to your motherboard and turn it on > 5) just in case, wait 5 minutes so that all the initialization > processes will be completed > 6) read the contains of a BIOS chip a few times > 7) compare the checksums of read files, if they are the same - erase > the BIOS chip (by filling it with FF's), turn off the motherboard, > then turn it on again, wait 5 minutes - then flash your desired binary > image to this BIOS chip > > III) Alternatively you may want to de-solder a BIOS chip from > motherboard and connect it to your programmer with DIP adapter, but > probably could be avoided if you do I) or II) successfully > > IV) Try a different programmer, e.g. CH341A which is super cheap > simple hardware fully supported by flashrom - should be reliable > > I wish you good luck, sadly Supermicro X10DRT-Lis not supported by > coreboot open source BIOS - hopefully you will be able to get a better > hardware one day... > > Best regards, > > 2017-11-21 17:57 GMT+03:00 Yaron Shragai <yshragai.firmware(a)gmail.com>: > > Hello, > > I am trying to use flashrom to program a Winbond W25Q128FV chip, on a > > Supermicro X10DRT-L mobo, with a Dediprog SF 100. > > > > I am running flashrom from an Ubuntu VM on a Win10 laptop as well as > from a > > Minnowboard Max system running Ubuntu. > > I am running flashrom v0.9.9-rc1-r1942, installed via apt. > > I am connecting to the chip via a SOIC clip. > > > > I should note that I have looked at the product support data on the > flashrom > > web site. It lists full support for the W25Q128FV. It does not list the > > X10DRT-L mobo. > > > > flashrom almost never "sees" the flash chip (output: "No EEPROM/flash > device > > found."). > > > > I say "almost", b/c it did see it a couple of times (out of, I would say, > > ~100 tries) - which was enough for me to read out the pre-existing > content, > > and write to it an image that has effectively bricked it. :-) So, now > I'm > > trying to flash the pre-existing content back... (There is no documented > > way to force the X10DRT-L to use the recovery block, and I have yet to > find > > an undocumented way...) > > > > I have tried with the system board plugged in and unplugged, and with and > > without connecting the VCC pin to the programmer. > > > > I have been using these two command lines, at various times: > > flashrom -p dediprog > > flashrom -p dediprog:voltage=3.5 > > > > When I add -VVV, the following relevant lines appear in the output: > > > > Probing for Winbond W25Q128.V, 16384 kB: programmer_map_flash_region: > > mapping W25Q128.V from 0x00000000ff000000 to 0x0000000000000000 > > dediprog_spi_send_command, writecnt=1, readcnt=3 > > RDID returned 0xff 0xff 0xff. RDID byte 0 parity violation. > > probe_spi_rdid_generic: id1 0xff, id2 0xffff > > programmer_unmap_flash_region: unmapped 0x0000000000000000 > > > > ...and further down... > > > > Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: > > dediprog_spi_send_command, writecnt=1, readcnt=3 > > RDID returned 0xff 0xff 0xff. RDID byte 0 parity violation. > > probe_spi_rdid_generic: id1 0xff, id2 0xffff > > > > One more datapoint: When I connect my laptop -> Dediprog -> to the flash > > chip on the Minnowboard Max (Micron 25Q064A), it does recognize the chip. > > > > Any advice would be appreciated! > > > > Thanks, > > Yaron > > > > _______________________________________________ > > flashrom mailing list > > flashrom(a)flashrom.org > > https://mail.coreboot.org/mailman/listinfo/flashrom >

1 0

Re: [flashrom] winbond 25q128jvfm
by David Hendricks 22 Nov '17

22 Nov '17

Hi Ron, Can you check the full part number? There appears to be a couple versions of this chip, one with ID 0x4018 (like the existing W25Q128.V chips) and another version with additional instructions that identifies with 0x7018. I found a W25Q128JVSIQ and it reads/writes successfully with the existing code. If your chip ends with an 'M' instead of a 'Q' then you can try this, which just does as Nico suggested: https://review.coreboot.org/#/c/22567/ On Fri, Nov 17, 2017 at 9:49 AM, ron minnich <rminnich(a)gmail.com> wrote: > any suggestions on making this part work? I have not done this in a while. > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom >

1 0

Re: [flashrom] flashrom not "seeing" W25Q128FV
by Ivan Ivanov 22 Nov '17

22 Nov '17

Hi Yaron, please read about the In-System Programming. It could be that the peripheral devices of your motherboard are consuming some percentage of the power that was aimed to power a BIOS chip during the access - because of that, there is not enough power for a BIOS chip and your attempts are failing. What to do: I) You could try to reduce the amount of peripheral devices - e.g. disconnect the RAM modules from your system and try again II) Also you can try to power a BIOS chip by the motherboard : 1) disconnect a VCC wire from your programmer, also disconnect WP and HOLD just in case 2) disconnect all the boot devices from your motherboard 3) connect a clip to a BIOS chip 4) connect a power adapter to your motherboard and turn it on 5) just in case, wait 5 minutes so that all the initialization processes will be completed 6) read the contains of a BIOS chip a few times 7) compare the checksums of read files, if they are the same - erase the BIOS chip (by filling it with FF's), turn off the motherboard, then turn it on again, wait 5 minutes - then flash your desired binary image to this BIOS chip III) Alternatively you may want to de-solder a BIOS chip from motherboard and connect it to your programmer with DIP adapter, but probably could be avoided if you do I) or II) successfully IV) Try a different programmer, e.g. CH341A which is super cheap simple hardware fully supported by flashrom - should be reliable I wish you good luck, sadly Supermicro X10DRT-Lis not supported by coreboot open source BIOS - hopefully you will be able to get a better hardware one day... Best regards, 2017-11-21 17:57 GMT+03:00 Yaron Shragai <yshragai.firmware(a)gmail.com>: > Hello, > I am trying to use flashrom to program a Winbond W25Q128FV chip, on a > Supermicro X10DRT-L mobo, with a Dediprog SF 100. > > I am running flashrom from an Ubuntu VM on a Win10 laptop as well as from a > Minnowboard Max system running Ubuntu. > I am running flashrom v0.9.9-rc1-r1942, installed via apt. > I am connecting to the chip via a SOIC clip. > > I should note that I have looked at the product support data on the flashrom > web site. It lists full support for the W25Q128FV. It does not list the > X10DRT-L mobo. > > flashrom almost never "sees" the flash chip (output: "No EEPROM/flash device > found."). > > I say "almost", b/c it did see it a couple of times (out of, I would say, > ~100 tries) - which was enough for me to read out the pre-existing content, > and write to it an image that has effectively bricked it. :-) So, now I'm > trying to flash the pre-existing content back... (There is no documented > way to force the X10DRT-L to use the recovery block, and I have yet to find > an undocumented way...) > > I have tried with the system board plugged in and unplugged, and with and > without connecting the VCC pin to the programmer. > > I have been using these two command lines, at various times: > flashrom -p dediprog > flashrom -p dediprog:voltage=3.5 > > When I add -VVV, the following relevant lines appear in the output: > > Probing for Winbond W25Q128.V, 16384 kB: programmer_map_flash_region: > mapping W25Q128.V from 0x00000000ff000000 to 0x0000000000000000 > dediprog_spi_send_command, writecnt=1, readcnt=3 > RDID returned 0xff 0xff 0xff. RDID byte 0 parity violation. > probe_spi_rdid_generic: id1 0xff, id2 0xffff > programmer_unmap_flash_region: unmapped 0x0000000000000000 > > ...and further down... > > Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: > dediprog_spi_send_command, writecnt=1, readcnt=3 > RDID returned 0xff 0xff 0xff. RDID byte 0 parity violation. > probe_spi_rdid_generic: id1 0xff, id2 0xffff > > One more datapoint: When I connect my laptop -> Dediprog -> to the flash > chip on the Minnowboard Max (Micron 25Q064A), it does recognize the chip. > > Any advice would be appreciated! > > Thanks, > Yaron > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom

1 0

W836xx: Wasp_BR: flashrom -V
by August Dumatubun 22 Nov '17

22 Nov '17

Hi. I did a flashrom -p internal. My laptop is not supported ;( As requested, here's the output of flashrom -V -p internal. " flashrom v0.9.8-r1888 on Linux 4.4.92-31-default (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.1, GCC 4.8.5, little endian Command line (3 args): flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 1406M loops per second, 10 myus = 9 us, 100 myus = 97 us, 1000 myus = 1087 us, 10000 myus = 10091 us, 4 myus = 3 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Notebook" Laptop detected via DMI. DMI string system-manufacturer: "Acer" DMI string system-product-name: "Aspire E5-553G" DMI string system-version: "V1.13" DMI string baseboard-manufacturer: "Acer" DMI string baseboard-product-name: "Wasp_BR" DMI string baseboard-version: "V1.13" 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: 89. Please send the output of "flashrom -V -p internal" 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. " Regards, August.

1 0

flashrom not "seeing" W25Q128FV
by Yaron Shragai 21 Nov '17

21 Nov '17

Hello, I am trying to use flashrom to program a Winbond W25Q128FV chip, on a Supermicro X10DRT-L mobo, with a Dediprog SF 100. I am running flashrom from an Ubuntu VM on a Win10 laptop as well as from a Minnowboard Max system running Ubuntu. I am running flashrom v0.9.9-rc1-r1942, installed via apt. I am connecting to the chip via a SOIC clip. I should note that I have looked at the product support data on the flashrom web site. It lists full support for the W25Q128FV. It does not list the X10DRT-L mobo. flashrom almost never "sees" the flash chip (output: "No EEPROM/flash device found."). I say "almost", b/c it did see it a couple of times (out of, I would say, ~100 tries) - which was enough for me to read out the pre-existing content, and write to it an image that has effectively bricked it. :-) So, now I'm trying to flash the pre-existing content back... (There is no documented way to force the X10DRT-L to use the recovery block, and I have yet to find an undocumented way...) I have tried with the system board plugged in and unplugged, and with and without connecting the VCC pin to the programmer. I have been using these two command lines, at various times: flashrom -p dediprog flashrom -p dediprog:voltage=3.5 When I add -VVV, the following relevant lines appear in the output: Probing for Winbond W25Q128.V, 16384 kB: programmer_map_flash_region: mapping W25Q128.V from 0x00000000ff000000 to 0x0000000000000000 dediprog_spi_send_command, writecnt=1, readcnt=3 RDID returned 0xff 0xff 0xff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff programmer_unmap_flash_region: unmapped 0x0000000000000000 ...and further down... Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: dediprog_spi_send_command, writecnt=1, readcnt=3 RDID returned 0xff 0xff 0xff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff One more datapoint: When I connect my laptop -> Dediprog -> to the flash chip on the Minnowboard Max (Micron 25Q064A), it does recognize the chip. Any advice would be appreciated! Thanks, Yaron

1 0

not working on mintBox2
by Javier 21 Nov '17

21 Nov '17

Hi, Please notice I'm not subscribed, so please CC me... On a mintbox2 running Arch, I tried flashrom, just to initially find out about my mintBox2 HW, as indicated in [1], but it fails with outputs suggested in [2]: https://gist.github.com/je-vv/fca0fe3b2ce6d8999194a01fa0d10fc3#file-flashro… https://gist.github.com/je-vv/fca0fe3b2ce6d8999194a01fa0d10fc3#file-lspci-l… https://gist.github.com/je-vv/fca0fe3b2ce6d8999194a01fa0d10fc3#file-superio… The thing is that this is not a laptop, and according the mintbox2 specs, the chipset is "Mobile Intel QM77 Chipset (Panther Point)" [3]. So the warning about a laptop is sort of weird. Granted it's a mini-pc any ways... Also granted that according to [4], the status seems "dep" (orange). Noticed that I tried setting as a parameter for linux "iomem=relaxed" with exactly the same results... Am I definitely out of luck with flashrom? -- Javier [1] https://wiki.archlinux.org/index.php/Flashing_BIOS_from_Linux#Usage_2 [2] https://www.flashrom.org/Board_Testing_HOWTO [3] http://www.fit-pc.com/web/products/mintbox/mintbox-specifications [4] https://www.flashrom.org/Supported_hardware#Supported_mainboards

1 0

flashrom not "seeing" W25Q128FV
by Yaron Shragai 20 Nov '17

20 Nov '17

Hello, I am trying to use flashrom to program a Winbond W25Q128FV chip, on a Supermicro X10DRT-L mobo, with a Dediprog SF 100. I am running flashrom from an Ubuntu VM on a Win10 laptop as well as from a Minnowboard Max system running Ubuntu. I am running flashrom v0.9.9-rc1-r1942, installed via apt. I am connecting to the chip via a SOIC clip. I should note that I have looked at the product support data on the flashrom web site. It lists full support for the W25Q128FV. It does not list the X10DRT-L mobo. flashrom almost never "sees" the flash chip (output: "No EEPROM/flash device found."). I say "almost", b/c it did see it a couple of times (out of, I would say, ~100 tries) - which was enough for me to read out the pre-existing content, and write to it an image that has effectively bricked it. :-) So, now I'm trying to flash the pre-existing content back... (There is no documented way to force the X10DRT-L to use the recovery block, and I have yet to find an undocumented way...) I have tried with the system board plugged in and unplugged, and with and without connecting the VCC pin to the programmer. I have been using these two command lines, at various times: flashrom -p dediprog flashrom -p dediprog:voltage=3.5 When I add -VVV, the following relevant lines appear in the output: Probing for Winbond W25Q128.V, 16384 kB: programmer_map_flash_region: mapping W25Q128.V from 0x00000000ff000000 to 0x0000000000000000 dediprog_spi_send_command, writecnt=1, readcnt=3 RDID returned 0xff 0xff 0xff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff programmer_unmap_flash_region: unmapped 0x0000000000000000 ...and further down... Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: dediprog_spi_send_command, writecnt=1, readcnt=3 RDID returned 0xff 0xff 0xff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff One more datapoint: When I connect my laptop -> Dediprog -> to the flash chip on the Minnowboard Max (Micron 25Q064A), it does recognize the chip. Any advice would be appreciated! Thanks, Yaron

1 0

Re: [flashrom] working board - elitegroup P6STMT
by Nico Huber 20 Nov '17

20 Nov '17

Hi Branden, On 10.11.2017 19:20, Branden Waldner wrote: > Attached are more log files that the Board Testing HOWTO wiki entry asks for. > > The board name from dmidecode seems to just be the chipset name, sis > 630, rather then the actual board name. Hopefully there is still > something to identify the board with autodetect. Thanks for reporting, I've filed a patch [1] to mark SiS 630 as tested. Though, I don't understand what you want to have auto-detected? From the logs I grasp, that you didn't have to identify anything manually. Nico [1] https://review.coreboot.org/22522

2 1

Re: [flashrom] Addenum12/11/2017 problem when flashing p5b-deluxe : mb marked ok but can't flash
by Nico Huber 19 Nov '17

19 Nov '17

On 12.11.2017 15:17, Marc wrote: > Now using the -VVV option : > > Bonjour everybody, > > May I get your advices ? > > ... > Error accessing ICH RCRB, 0x4000 bytes at 0x00000000fed1c000 > /dev/mem mmap failed: Operation not permitted That's a common issue also mentioned in our FAQ [1]. Linux limits access to the hardware. Try booting with iomem=relaxed in your kernel command line. Nico [1] https://www.flashrom.org/FAQ > FAILED! > FATAL ERROR! > Error: Programmer initialization failed. > > > I have bios 0506 and want to write the 1238. > > ONLY EMAIL COMMUNICATION PLEASE. > > Thanks for your attention. > > Gégé >

1 0

Patch to add Librem 15 laptop to flashrom whitelist
by Harry Prevor 19 Nov '17

19 Nov '17

Attached is a patch to whitelist the Librem 15 laptop on flashrom, so that I don't have to write "force_I_want_a_brick" every time I use it. I also added the laptop's info to print.c so it shows up as a supported device. This is my first ever patch, so please let me know if there is anything missing or that I can do to improve it! Added as per this PureOS bug: https://tracker.pureos.net/T170 P.S. Please CC me on any replies as I am not receiving messages from this list. Thanks! -- Harry Prevor http://habs.sdf.org/

3 2

Re: [flashrom] winbond 25q128jvfm
by Nico Huber 19 Nov '17

19 Nov '17

Hi Ron, On 17.11.2017 18:49, ron minnich wrote: > any suggestions on making this part work? I have not done this in a while. its brother 25Q128*F*V is already supported (as W25Q128.V, where . is a wildcard, alas, not matching the *J*V). I'd start by copying the W25Q128.V entry in flashchips.c as W28Q128JV and adding its id to flashchips.h (should be 0x7018). Then carefully compare the copied infos to the new chip's datasheet (instruction table should be most useful) before giving it a shot ;) Nico

1 0

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Nico Huber 19 Nov '17

19 Nov '17

Hi Anders, On 11.11.2017 17:27, Anders Nelson wrote: > Hi again, > > I don't see details on what image file formats are supported - does > Flashrom use only binary files? yes, that's right, conversion from other formats is out of flashrom's scope. > I see the ROM layout file explanation so I guess I can use that but it > would be nice to use an Intel HEX format if possible. There are already tools to convert such formats to binary and we have no intention to include something like this. Flashrom's task is simply to synchronize the flash chip's contents with those of a file. Though, I'd understand if you miss support to pipe the output of a conversion into flashrom. Nico

2 1

Move PicKit2 form libusb0 to libusb
by tgotic 18 Nov '17

18 Nov '17

Hi, Recently I tried to use flashrom with PicKit2 on Windows. I was unable to get it working with various libusb0 dll's, so I rewrote pickit2_spi.c to use libusb (form libusb.info). Since other external USB programmers use libusb, flashrom doesn't depend on obsolete libusb0 anymore. Please find attached new pickit2_spi.c, patch for Makefile, and a result of write operation. Signed-off-by: Tomislav Gotić <tgotic(a)gmail.com>

1 0

non-working board - asus p2-99 - failed to detect chip
by Branden Waldner 18 Nov '17

18 Nov '17

Flashrom isn't able to detect the flash chip on this board. I've tried while running factory asus p2-99 firmware, with p2b firmware, and with coreboot. This board seems use the same pcb layout as the p2b, but with 440zx northbridge whichs supports only 2 ram slots instead of 3 and with the hardware monitor chip being optional. The vendor aflash tool works while running an asus bios - both p2-99 and p2b, but not with coreboot. I've tried using the piix gpo board enable function on all possible gpos - high and low, but didn't get anywhere, besides finding out gpo0 is the fan. Since the original p2b testing seems to be fairly old - and this board is basically the same - should I test an old version of flashrom? I was going to try 0.9.0, but it does not build nicely, it stops with compiler warnings. Probably could still build it with some cflag adjustments, but I wasn't sure if that was the only problem. I'm mostly just posting this to be compete about it, though any recommendations would be appreciated. ps. The old post I had about a P4S5MG/GL+ board with SiS 650 chipset not working turned out to be the flash chip failing. Figured I might as well mention it.

1 0

spi_send_command invoked on a few chips that don't look to support it
by Kevin Shelton 17 Nov '17

17 Nov '17

Hello, on a board with a GD25Q127C/GD25Q128C and a board with a W25Q128FW, I've observed the below from flashrom --wp-status output: WP: write protect range: spi_send_command called, but SPI is unsupported on this hardware. Please report a bug at flashrom(a)flashrom.org Let me know how I can help.

1 0

winbond 25q128jvfm
by ron minnich 17 Nov '17

17 Nov '17

any suggestions on making this part work? I have not done this in a while.

1 0

error read chip from appel A1534
by RABAH MALKI 17 Nov '17

17 Nov '17

flashrom>flashrom -V -p buspirate_spi:dev=com19 -c "MX25L6 445E" -w 4flash.bin flashrom v0.9.7-r1781 on Windows 6.1 (x86) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with GCC 4.8.2, little endian Command line (7 args): flashrom -V -p buspirate_spi:dev=com19 -c MX25L6445E -w 4 flash.bin Calibrating delay loop... OS timer resolution is 1000 usecs, 1629M loops per sec ond, 10 myus = 0 us, 100 myus = 0 us, 1000 myus = 1000 us, 10000 myus = 10001 us , 4000 myus = 4000 us, OK. Initializing buspirate_spi programmer Baud rate is 115200. Detected Bus Pirate hardware v4 Detected Bus Pirate firmware 6.2 Using SPI command set v2. SPI speed is 8MHz Raw bitbang mode version 1 Raw SPI mode version 1 The following protocols are supported: SPI. Probing for Macronix MX25L6445E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 Found Macronix flash chip "MX25L6445E" (8192 kB, SPI) on buspirate_spi. Chip status register is 0x40. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set Chip status register: Bit 6 is set Chip status register: Block Protect 3 (BP3) is not 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 This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). Reading old flash chip contents... done. Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:E FAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x000000 00-0x00000fff: 0x92 ERASE FAILED!

1 0

a flash chip (Module No: MX25L12873FPI) which is not natively supported
by Yan Harley (閆海紅 BXC) 13 Nov '17

13 Nov '17

flashrom v0.9.9-r1954 on Linux 4.9.41-v7+ (armv7l) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.3.1, GCC 5.3.1 20160205, little endian Command line (3 args): flashrom -VV -p linux_spi:dev=/dev/spidev0.0,spispeed=10000 Calibrating delay loop... OS timer resolution is 1 usecs, 300M loops per second, 10 myus = 10 us, 100 myus = 209 us, 1000 myus = 1123 us, 10000 myus = 10297 us, 4 myus = 4 us, OK. Initializing linux_spi programmer Using device /dev/spidev0.0 Using 10000 kHz clock The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L05PU, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L10PT, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L10PU, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L20PT, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L20PU, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L40PT, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L40PU, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L80P, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L16PT, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L16PU, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L080, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L016, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L032, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25LQ16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25LQ64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF021, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF041A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF081, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF081A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF321, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF321A, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF641(A), 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DL081, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DL161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DQ161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0x07, id2 0x07 Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0x07, id2 0x07 Probing for Atmel AT25F512B, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0x07, id2 0x07 Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0x07, id2 0x07 Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0x07, id2 0x07 Probing for Atmel AT25FS010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25FS040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT26DF041, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT26DF081A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT26DF161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT26DF161A, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT26F004, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45CS1282, 16896 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB011D, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB021D, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB041D, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB081D, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB161D, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB321C, 4224 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB321D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB321E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB642D, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for ESMT F25L008A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for ESMT F25L32PA, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B05, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B05T, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25P05, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B10T, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25P10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B20T, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25P20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B40T, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25P40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B80T, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25P80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B16T, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25P16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B32T, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25P32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B64T, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25P64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F05, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25Q40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25Q80(A), 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25Q16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25Q32(A/B), 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25Q64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25Q128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25QH16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25QH32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25QH64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25QH128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25S10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25S20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25S40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25S80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25S16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25S32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25S64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for ESI ES25P40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for ESI ES25P80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for ESI ES25P16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25LQ40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25LQ80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25LQ16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25LQ32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25LQ64(B), 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25LQ128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q20(B), 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q40(B), 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q80(B), 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q16(B), 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q32(B), 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q64(B), 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q128B, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q128C, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25T80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25VQ21B, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25VQ40C, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25VQ41B, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25VQ80C, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25VQ16C, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F160S33B8, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F160S33T8, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F320S33B8, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F320S33T8, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F640S33B8, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F640S33T8, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX23L1654, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX23L3254, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX23L6454, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX23L12854, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L1605, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L1635D, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L1635E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L3205(A), 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L3273E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L3235D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L6405, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L6405D, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L12805D, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25U1635E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25U3235E/F, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25U6435E/F, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25U12835F, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L6495F, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of REMS. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of REMS. Probing for Micron/Numonyx/ST M25P20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of REMS. Probing for Micron/Numonyx/ST M25P40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of REMS. Probing for Micron/Numonyx/ST M25P80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PE10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PE20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PE40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M45PE10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M45PE20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M45PE40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Nantronics N25S10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Nantronics N25S20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Nantronics N25S40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Nantronics N25S80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Nantronics N25S16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LD256C, 32 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LD512(C), 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LD010(C), 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LD020(C), 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LD040(C), 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LQ020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LQ040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LQ080, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LQ016, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LQ032C, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for PMC Pm25LV010A, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LV020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LV040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LV080B, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LV016B, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FU406C/LE25U40CMC, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Sanyo LE25FW203A, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Sanyo LE25FW403A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Spansion S25FL004A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL008A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL016A, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL032A/P, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL064A/P, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL204K, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL208K, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL132K, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL164K, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL127S-64kB, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL127S-256kB, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL128P......0, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL128P......1, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL128S......0, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL128S......1, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL129P......0, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL129P......1, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0xc2, id2 0x17 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0xc2, id2 0x17 Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0xc2, id2 0x17 Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0xc2, id2 0x17 Probing for SST SST25VF020B, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xc2, id2 0x17 Probing for SST SST25VF040B, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xc2, id2 0x17 Probing for SST SST25WF020A, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25WF040B, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25WF080B, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25VF080B, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25VF016B, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25VF032B, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25VF064C, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25WF512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25WF010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25WF020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25WF040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25WF080, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q40.V, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q80.V, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q16.V, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q32.V, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q64.V, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q128.V, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q20.W, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q40.W, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q80.W, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q16.W, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q32.W, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q64.W, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Unknown SFDP-capable chip, 0 kB: SFDP revision = 1.0 SFDP number of parameter headers is 2 (NPH = 1). SFDP parameter table header 0/1: ID 0x00, version 1.0 Length 36 B, Parameter Table Pointer 0x000030 Parsing JEDEC flash parameter table... 3-Byte only addressing. Status register is non-volatile and the standard does not allow vendors to tell us whether EWSR/WREN is needed for status register writes - assuming EWSR. Write chunk size is at least 64 B. Flash chip size is 16384 kB. Block eraser 0: 4096 x 4096 B with opcode 0x20 Tried to add a duplicate block eraser: 4096 x 4096 B with opcode 0x20. Block eraser 1: 512 x 32768 B with opcode 0x52 Block eraser 2: 256 x 65536 B with opcode 0xd8 done. SFDP parameter table header 1/1: ID 0xc2, version 1.0 Length 16 B, Parameter Table Pointer 0x000060 === SFDP has autodetected a flash chip which is not natively supported by flashrom yet. All standard operations (read, verify, erase and write) should work, but to support all possible features we need to add them manually. You can help us by mailing us the output of the following command to flashrom(a)flashrom.org: 'flashrom -VV [plus the -p/--programmer parameter]' Thanks for your help! === Found Unknown flash chip "SFDP-capable chip" (16384 kB, SPI) on linux_spi. Probing for AMIC unknown AMIC SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel unknown Atmel SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon unknown Eon SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix unknown Macronix SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC unknown PMC SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST unknown SST SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for ST unknown ST SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Generic unknown SPI chip (RDID), 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xc2, id2 0x17 Found Unknown flash chip "SFDP-capable chip" (16384 kB, SPI). No operations were specified.

1 0

Addenum12/11/2017 problem when flashing p5b-deluxe : mb marked ok but can't flash
by Marc 12 Nov '17

12 Nov '17

Now using the -VVV option : Bonjour everybody, May I get your advices ? I tried to flash my mb but got an error message, here are the infos you may need : flashrom v0.9.9-r1954 on Linux 4.9.0-3-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.5.2, GCC 6.3.0 20170221, little endian Command line (7 args): flashrom -w P5B-ASUS-Deluxe-1238.ROM -p internal -o test.txt -VVV Calibrating delay loop... OS timer resolution is 1 usecs, 1599M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1007 us, 10000 myus = 10001 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. page_size=1000 pre-rounding: start=0x00000000000f0000, len=0x10000, end=0x0000000000100000 post-rounding: start=0x00000000000f0000, len=0x10000, end=0x0000000000100000 page_size=1000 pre-rounding: start=0x00000000000f06a0, len=0xa9c, end=0x00000000000f113c post-rounding: start=0x00000000000f0000, len=0x2000, end=0x00000000000f2000 DMI string chassis-type: "Desktop" page_size=1000 pre-rounding: start=0x00007facc09a06a0, len=0xa9c, end=0x00007facc09a113c post-rounding: start=0x00007facc09a0000, len=0x2000, end=0x00007facc09a2000 page_size=1000 pre-rounding: start=0x00007facc09a2000, len=0x10000, end=0x00007facc09b2000 post-rounding: start=0x00007facc09a2000, len=0x10000, end=0x00007facc09b2000 DMI string system-manufacturer: "System manufacturer" DMI string system-product-name: "System Product Name" DMI string system-version: "System Version" DMI string baseboard-manufacturer: "ASUSTeK Computer INC." DMI string baseboard-product-name: "P5B-Deluxe" DMI string baseboard-version: "Rev 1.xx" Found chipset "Intel ICH8/ICH8R" with PCI ID 8086:2810. Enabling flash write... Root Complex Register Block address = 0xfed1c000 page_size=1000 pre-rounding: start=0x00000000fed1c000, len=0x4000, end=0x00000000fed20000 post-rounding: start=0x00000000fed1c000, len=0x4000, end=0x00000000fed20000 Error accessing ICH RCRB, 0x4000 bytes at 0x00000000fed1c000 /dev/mem mmap failed: Operation not permitted FAILED! FATAL ERROR! Error: Programmer initialization failed. I have bios 0506 and want to write the 1238. ONLY EMAIL COMMUNICATION PLEASE. Thanks for your attention. Gégé

1 0

12/11/2017 problem when flashing p5b-deluxe : mb marked ok but can't flash
by Marc 12 Nov '17

12 Nov '17

Bonjour everybody, May I get your advices ? I tried to flash my mb but got an error message, here are the infos you may need : flashrom v0.9.9-r1954 on Linux 4.9.0-3-amd64 (x86_64) flashrom was built with libpci 3.5.2, GCC 6.3.0 20170221, little endian Command line (6 args): flashrom -w P5B-ASUS-Deluxe-1238.ROM -p internal -o test.txt Calibrating delay loop... OS timer resolution is 1 usecs, 1599M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1000 us, 10000 myus = 10005 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Desktop" DMI string system-manufacturer: "System manufacturer" DMI string system-product-name: "System Product Name" DMI string system-version: "System Version" DMI string baseboard-manufacturer: "ASUSTeK Computer INC." DMI string baseboard-product-name: "P5B-Deluxe" DMI string baseboard-version: "Rev 1.xx" Found chipset "Intel ICH8/ICH8R" with PCI ID 8086:2810. Enabling flash write... Root Complex Register Block address = 0xfed1c000 Error accessing ICH RCRB, 0x4000 bytes at 0x00000000fed1c000 /dev/mem mmap failed: Operation not permitted FAILED! FATAL ERROR! Error: Programmer initialization failed. I have bios 0506 and want to write the 1238. ONLY EMAIL COMMUNICATION PLEASE. Thanks for your attention. Gégé

1 0

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Anders Nelson 11 Nov '17

11 Nov '17

Hi again, I don't see details on what image file formats are supported - does Flashrom use only binary files? I see the ROM layout file explanation so I guess I can use that but it would be nice to use an Intel HEX format if possible. =] -- Anders Nelson +1 (517) 775-6129 www.erogear.com On Sat, Nov 11, 2017 at 4:16 PM, Anders Nelson <anders.k.nelson(a)gmail.com> wrote: > We (you mostly) nailed it!: > > === > > chrx@chrx:~/Github/flashrom$ ./flashrom -p ft2232_spi:type=2232H,port=A, > divisor=4 > flashrom v0.9.9-86-ge1a960e on Linux 4.9.4-galliumos-braswell (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > Found Micron/Numonyx/ST flash chip "N25Q128..3E" (16384 kB, SPI) on > ft2232_spi. > No operations were specified. > > === > > Thanks! > > -- > Anders Nelson > > +1 (517) 775-6129 > > www.erogear.com > > On Wed, Nov 8, 2017 at 3:50 PM, Anders Nelson <anders.k.nelson(a)gmail.com> > wrote: > >> Woooo looks like that did it! I don't have a flash device connected yet >> but Flashrom certainly found the 2232. >> >> Thanks for the help, I hope I can contribute definitions for the flash >> chips I use (Cypress/Spansion 128/256Mbit) if I find they aren't in the >> database already. >> >> =] >> >> -- >> Anders Nelson >> >> +1 (517) 775-6129 >> >> www.erogear.com >> >> On Wed, Nov 8, 2017 at 3:31 PM, Nico Huber <nico.h(a)gmx.de> wrote: >> >>> On 08.11.2017 16:11, Anders Nelson wrote: >>> > Ohhh my god you're right - when I call the program as ./flashrom it >>> runs >>> > now! >>> > >>> > I am still getting an error though it's new: >>> > >>> > === >>> > >>> > chrx@chrx:~/Github/flashrom$ ./flashrom -p ft2232_spi >>> > flashrom v0.9.9-86-ge1a960e on Linux 4.9.4-galliumos-braswell (x86_64) >>> > flashrom is free software, get the source code at https://flashrom.org >>> > >>> > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). >>> > Unable to open FTDI device: -3 (device not found). >>> > Error: Programmer initialization failed. >>> >>> I guess, you have to specify the model (likely 2232H in your case). See >>> the manpage `man ./flashrom.8`. If that doesn't work, you can check the >>> output of `lsusb` if your board uses a special USB device id that we >>> might have to add to flashrom. >>> >>> > >>> > === >>> > >>> > The FTDI device enumerates as /dev/ttyUSB0 and /dev/ttyUSB1... Is it >>> > necessary to add a rule to udev or something to get Flashrom to find >>> it? >>> >>> Unlikely. >>> >>> Nico >>> >>> >> >

1 0

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Anders Nelson 11 Nov '17

11 Nov '17

We (you mostly) nailed it!: === chrx@chrx:~/Github/flashrom$ ./flashrom -p ft2232_spi:type=2232H,port=A,divisor=4 flashrom v0.9.9-86-ge1a960e on Linux 4.9.4-galliumos-braswell (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Micron/Numonyx/ST flash chip "N25Q128..3E" (16384 kB, SPI) on ft2232_spi. No operations were specified. === Thanks! -- Anders Nelson +1 (517) 775-6129 www.erogear.com On Wed, Nov 8, 2017 at 3:50 PM, Anders Nelson <anders.k.nelson(a)gmail.com> wrote: > Woooo looks like that did it! I don't have a flash device connected yet > but Flashrom certainly found the 2232. > > Thanks for the help, I hope I can contribute definitions for the flash > chips I use (Cypress/Spansion 128/256Mbit) if I find they aren't in the > database already. > > =] > > -- > Anders Nelson > > +1 (517) 775-6129 > > www.erogear.com > > On Wed, Nov 8, 2017 at 3:31 PM, Nico Huber <nico.h(a)gmx.de> wrote: > >> On 08.11.2017 16:11, Anders Nelson wrote: >> > Ohhh my god you're right - when I call the program as ./flashrom it runs >> > now! >> > >> > I am still getting an error though it's new: >> > >> > === >> > >> > chrx@chrx:~/Github/flashrom$ ./flashrom -p ft2232_spi >> > flashrom v0.9.9-86-ge1a960e on Linux 4.9.4-galliumos-braswell (x86_64) >> > flashrom is free software, get the source code at https://flashrom.org >> > >> > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). >> > Unable to open FTDI device: -3 (device not found). >> > Error: Programmer initialization failed. >> >> I guess, you have to specify the model (likely 2232H in your case). See >> the manpage `man ./flashrom.8`. If that doesn't work, you can check the >> output of `lsusb` if your board uses a special USB device id that we >> might have to add to flashrom. >> >> > >> > === >> > >> > The FTDI device enumerates as /dev/ttyUSB0 and /dev/ttyUSB1... Is it >> > necessary to add a rule to udev or something to get Flashrom to find it? >> >> Unlikely. >> >> Nico >> >> >

1 0

Re: [flashrom] working board - elitegroup P6STMT
by Branden Waldner 10 Nov '17

10 Nov '17

Attached are more log files that the Board Testing HOWTO wiki entry asks for. The board name from dmidecode seems to just be the chipset name, sis 630, rather then the actual board name. Hopefully there is still something to identify the board with autodetect. Just to be complete, the board is also marked as Rev: 1.0.

1 0

flashrom -p ch341a_spi -c GD25Q128C
by L. D. Pinney 09 Nov '17

09 Nov '17

Running on the latest Debian package.I checked https://www.flashrom.org/Supported_hardwareand looked @ git log a bit ... didn't find anything about testing this chip .... SO root@black:/data/MTD_Images# time flashrom -p ch341a_spi -c GD25Q128C -w NB-PR2.imgflashrom v0.9.9-r1954 on Linux 4.9.0-4-amd64 (x86_64)flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK.Found GigaDevice flash chip "GD25Q128C" (16384 kB, SPI) on ch341a_spi.===This flash part has status UNTESTED for operations: PROBE READ ERASE WRITEThe test status of this chip may have been updated in the latest developmentversion of flashrom. If you are running the latest development version,please email a report to flashrom(a)flashrom.org if any of the above operationswork correctly for you with this flash chip. Please include the flashrom logfile for all operations you tested (see the man page for details), and mentionwhich mainboard or programmer you tested in the subject line.Thanks for your help!Reading old flash chip contents... done.Erasing and writing flash chip... Erase/write done.Verifying flash... VERIFIED. real 5m49.633suser 0m17.820ssys 0m38.380s This chip is installed on a prototype wireless router.It seems to work OK.[ 0.537541] m25p80 spi0.0: gd25q128 (16384 Kbytes)

1 0

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Nico Huber 08 Nov '17

08 Nov '17

On 08.11.2017 16:11, Anders Nelson wrote: > Ohhh my god you're right - when I call the program as ./flashrom it runs > now! > > I am still getting an error though it's new: > > === > > chrx@chrx:~/Github/flashrom$ ./flashrom -p ft2232_spi > flashrom v0.9.9-86-ge1a960e on Linux 4.9.4-galliumos-braswell (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > Unable to open FTDI device: -3 (device not found). > Error: Programmer initialization failed. I guess, you have to specify the model (likely 2232H in your case). See the manpage `man ./flashrom.8`. If that doesn't work, you can check the output of `lsusb` if your board uses a special USB device id that we might have to add to flashrom. > > === > > The FTDI device enumerates as /dev/ttyUSB0 and /dev/ttyUSB1... Is it > necessary to add a rule to udev or something to get Flashrom to find it? Unlikely. Nico

2 1

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Nico Huber 08 Nov '17

08 Nov '17

Hi Anders, On 07.11.2017 23:44, Anders Nelson wrote: > root@chrx:/home/chrx/Github/flashrom# make clean Doing such things as root is very discouraged. > Replacing all version templates with v0.9.9-86-ge1a960e. > rm -f flashrom flashrom.exe libflashrom.a *.o *.d flashrom.8 > flashrom.8.html build_details.txt > make[1]: Entering directory > '/home/chrx/Github/flashrom/util/ich_descriptors_tool' > rm -f ich_descriptors_tool ich_descriptors_tool.exe > rm -rf .dep .obj > make[1]: Leaving directory > '/home/chrx/Github/flashrom/util/ich_descriptors_tool' > > === > > [...build completes without error...] Well, like Stefan said, this is the part that could have told me that libftdi is already installed. > > === > root@chrx:/home/chrx/Github/flashrom# flashrom -p ft2232_spi > flashrom v0.9.9-rc1-r1942 on Linux 4.9.4-galliumos-braswell (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Error: Unknown programmer "ft2232_spi". Valid choices are: > internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, > it8212, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel, > nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, pickit2_spi, > ch341a_spi. > Please run "flashrom --help" for usage info. I could have seen this earlier... you are not calling your self-built flashrom at all. You call the one pre-installed by GalliumOS. If you want to run a binary that is not in a directory in your $PATH envi- ronment variable, you have to prefix it with a path, e.g. `./flashrom -p ft2232_spi` if you want to run the flashrom in the current directory. Nico

2 1

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Stefan Tauner 08 Nov '17

08 Nov '17

Hi, you always leave out the important part of the logs. The build process shows which libraries it finds at the top. Details about reasons why it failed can be gathered from the build_details.txt file if need be. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Nico Huber 07 Nov '17

07 Nov '17

Hi Anders, On 07.11.2017 21:31, Anders Nelson wrote: > Argh: > > === > > root@chrx:/home/chrx/Github/flashrom# flashrom -p ft2232_spi > flashrom v0.9.9-rc1-r1942 on Linux 4.9.4-galliumos-braswell (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Error: Unknown programmer "ft2232_spi". Valid choices are: > internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, > it8212, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel, > nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, pickit2_spi, > ch341a_spi. > Please run "flashrom --help" for usage info. > > === > > "ft2232_spi" is what I see in the source code, should I be using another > option to use my FTDI 2232H board as a programmer? no, that's the right one. But the `make` failed you again. It checks if libftdi is available and silently ignores ft2232_spi if not (even if explicitly asked to build ft2232_spi support in, pretty weird). Anyway, the solution is simple, install libftdi along with it's development package. Under Ubuntu this would be `apt-get install libftdi-dev`. Then run the same `make` command again. Hope that (finally) helps, Nico

2 1

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Anders Nelson 07 Nov '17

07 Nov '17

Argh: === root@chrx:/home/chrx/Github/flashrom# flashrom -p ft2232_spi flashrom v0.9.9-rc1-r1942 on Linux 4.9.4-galliumos-braswell (x86_64) flashrom is free software, get the source code at https://flashrom.org Error: Unknown programmer "ft2232_spi". Valid choices are: internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, it8212, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel, nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, pickit2_spi, ch341a_spi. Please run "flashrom --help" for usage info. === "ft2232_spi" is what I see in the source code, should I be using another option to use my FTDI 2232H board as a programmer? Thanks, -- Anders Nelson +1 (517) 775-6129 www.erogear.com On Tue, Nov 7, 2017 at 8:07 PM, Anders Nelson <anders.k.nelson(a)gmail.com> wrote: > Also am I correct in saying the help listing needs to be updated with more > --programmer options? I don't see the 2232H device in there. I'll Google it > in the meantime. > > It's really (really) nice to see such fast and comprehensive support for > an open source project. Many thanks. > > =] > > -- > Anders Nelson > > +1 (517) 775-6129 > > www.erogear.com > > On Tue, Nov 7, 2017 at 7:56 PM, Anders Nelson <anders.k.nelson(a)gmail.com> > wrote: > >> Hi guys, sorry for the delay again! >> >> TL;DR: I did "make clean CONFIG_INTERNAL=no" and it looks like it built >> successfully! Here's the email as I assembled it before doing the "make >> clean": >> >> === >> >> root@chrx:/home/chrx/Github/flashrom# git describe >> v0.9.9-86-ge1a960e >> >> === >> >> I've attached the output files you asked for to this message. >> >> I did not change the code at all and I pulled from the master branch here >> IIRC: https://github.com/flashrom/flashrom >> >> I tried to build using "make CONFIG_INTERNAL=no" early on but this was >> the error output: >> >> === >> >> cli_classic.o: In function `main': >> cli_classic.c:(.text.startup+0xaac): undefined reference to >> `force_boardmismatch' >> print.o: In function `print_supported_boards_helper': >> print.c:(.text+0x245): undefined reference to `board_matches' >> print.o: In function `print_supported': >> print.c:(.text+0xf11): undefined reference to `chipset_enables' >> print.c:(.text+0xff3): undefined reference to `chipset_enables' >> spi.o: In function `spi_get_valid_read_addr': >> spi.c:(.text+0x12c): undefined reference to `ichspi_bbar' >> collect2: error: ld returned 1 exit status >> Makefile:1018: recipe for target 'flashrom' failed >> make: *** [flashrom] Error 1 >> >> === >> >> Everything above that in the build process looked ok! >> >> >> -- >> Anders Nelson >> >> +1 (517) 775-6129 >> >> www.erogear.com >> >> On Sat, Nov 4, 2017 at 11:21 AM, Nico Huber <nico.h(a)gmx.de> wrote: >> >>> Hi Anders, >>> >>> On 03.11.2017 21:35, Anders Nelson wrote: >>> > Hi guys, >>> > >>> > Here's the error I get trying to apply the patch: >>> > >>> > "root@chrx:/home/chrx/Github/flashrom# git apply --check >>> > /home/chrx/Downloads/ich_descriptors-amd64.patch >>> > error: patch failed: ich_descriptors.c:1064 >>> > error: ich_descriptors.c: patch does not apply" >>> >>> sorry, I was looking at the wrong version of the code. Doesn't matter, >>> see below. >>> >>> > >>> > Derp? Here's my output from "cc -v": >>> > >>> > ... >>> > >>> > And here's the output from the second command you asked for: >>> > >>> > "root@chrx:/home/chrx/Github/flashrom# cc -dM -E - < /dev/null >>> > ... >>> > #define __x86_64__ 1 >>> > ... >>> > #define __amd64__ 1 >>> > ... >>> >>> Both are there that's fine. And I think now, that my original assumption >>> that this could be an issue was wrong: We do check for x86 not only in >>> the Makefile but also in ichspi.c too (pretty weird redundancy) and the >>> latter check is in sync with ich_descriptors.c. >>> >>> I've also tried to build flashrom on Ubuntu 16.04 with the same compiler >>> version... and it worked *shrug*. >>> >>> > >>> > Whaaatsa goin' onnn? Thanks for your help! >>> >>> No clue, actually. Did you already try to build with `make >>> CONFIG_INTERNAL=no`? Just want to know, that this doesn't stall >>> your work. We are ofc very interested to understand and fix the >>> actual problem. >>> >>> Can you please send us a copy of the `ichspi.o` and `ich_descriptors.o` >>> of the failing build. >>> >>> Did you change anything in the code? or tried to build different >>> versions? switch branches? in case, you could try a `make clean` >>> (although, I can't imagine why it would be necessary). >>> >>> Oh, I nearly forgot: Please show us the output of `git describe` (I'm >>> loosing track of our branches atm). >>> >>> Nico >>> >> >> >

1 0

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Anders Nelson 07 Nov '17

07 Nov '17

Also am I correct in saying the help listing needs to be updated with more --programmer options? I don't see the 2232H device in there. I'll Google it in the meantime. It's really (really) nice to see such fast and comprehensive support for an open source project. Many thanks. =] -- Anders Nelson +1 (517) 775-6129 www.erogear.com On Tue, Nov 7, 2017 at 7:56 PM, Anders Nelson <anders.k.nelson(a)gmail.com> wrote: > Hi guys, sorry for the delay again! > > TL;DR: I did "make clean CONFIG_INTERNAL=no" and it looks like it built > successfully! Here's the email as I assembled it before doing the "make > clean": > > === > > root@chrx:/home/chrx/Github/flashrom# git describe > v0.9.9-86-ge1a960e > > === > > I've attached the output files you asked for to this message. > > I did not change the code at all and I pulled from the master branch here > IIRC: https://github.com/flashrom/flashrom > > I tried to build using "make CONFIG_INTERNAL=no" early on but this was the > error output: > > === > > cli_classic.o: In function `main': > cli_classic.c:(.text.startup+0xaac): undefined reference to > `force_boardmismatch' > print.o: In function `print_supported_boards_helper': > print.c:(.text+0x245): undefined reference to `board_matches' > print.o: In function `print_supported': > print.c:(.text+0xf11): undefined reference to `chipset_enables' > print.c:(.text+0xff3): undefined reference to `chipset_enables' > spi.o: In function `spi_get_valid_read_addr': > spi.c:(.text+0x12c): undefined reference to `ichspi_bbar' > collect2: error: ld returned 1 exit status > Makefile:1018: recipe for target 'flashrom' failed > make: *** [flashrom] Error 1 > > === > > Everything above that in the build process looked ok! > > > -- > Anders Nelson > > +1 (517) 775-6129 > > www.erogear.com > > On Sat, Nov 4, 2017 at 11:21 AM, Nico Huber <nico.h(a)gmx.de> wrote: > >> Hi Anders, >> >> On 03.11.2017 21:35, Anders Nelson wrote: >> > Hi guys, >> > >> > Here's the error I get trying to apply the patch: >> > >> > "root@chrx:/home/chrx/Github/flashrom# git apply --check >> > /home/chrx/Downloads/ich_descriptors-amd64.patch >> > error: patch failed: ich_descriptors.c:1064 >> > error: ich_descriptors.c: patch does not apply" >> >> sorry, I was looking at the wrong version of the code. Doesn't matter, >> see below. >> >> > >> > Derp? Here's my output from "cc -v": >> > >> > ... >> > >> > And here's the output from the second command you asked for: >> > >> > "root@chrx:/home/chrx/Github/flashrom# cc -dM -E - < /dev/null >> > ... >> > #define __x86_64__ 1 >> > ... >> > #define __amd64__ 1 >> > ... >> >> Both are there that's fine. And I think now, that my original assumption >> that this could be an issue was wrong: We do check for x86 not only in >> the Makefile but also in ichspi.c too (pretty weird redundancy) and the >> latter check is in sync with ich_descriptors.c. >> >> I've also tried to build flashrom on Ubuntu 16.04 with the same compiler >> version... and it worked *shrug*. >> >> > >> > Whaaatsa goin' onnn? Thanks for your help! >> >> No clue, actually. Did you already try to build with `make >> CONFIG_INTERNAL=no`? Just want to know, that this doesn't stall >> your work. We are ofc very interested to understand and fix the >> actual problem. >> >> Can you please send us a copy of the `ichspi.o` and `ich_descriptors.o` >> of the failing build. >> >> Did you change anything in the code? or tried to build different >> versions? switch branches? in case, you could try a `make clean` >> (although, I can't imagine why it would be necessary). >> >> Oh, I nearly forgot: Please show us the output of `git describe` (I'm >> loosing track of our branches atm). >> >> Nico >> > >

1 0

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Nico Huber 07 Nov '17

07 Nov '17

Hi Anders, On 03.11.2017 21:35, Anders Nelson wrote: > Hi guys, > > Here's the error I get trying to apply the patch: > > "root@chrx:/home/chrx/Github/flashrom# git apply --check > /home/chrx/Downloads/ich_descriptors-amd64.patch > error: patch failed: ich_descriptors.c:1064 > error: ich_descriptors.c: patch does not apply" sorry, I was looking at the wrong version of the code. Doesn't matter, see below. > > Derp? Here's my output from "cc -v": > > ... > > And here's the output from the second command you asked for: > > "root@chrx:/home/chrx/Github/flashrom# cc -dM -E - < /dev/null > ... > #define __x86_64__ 1 > ... > #define __amd64__ 1 > ... Both are there that's fine. And I think now, that my original assumption that this could be an issue was wrong: We do check for x86 not only in the Makefile but also in ichspi.c too (pretty weird redundancy) and the latter check is in sync with ich_descriptors.c. I've also tried to build flashrom on Ubuntu 16.04 with the same compiler version... and it worked *shrug*. > > Whaaatsa goin' onnn? Thanks for your help! No clue, actually. Did you already try to build with `make CONFIG_INTERNAL=no`? Just want to know, that this doesn't stall your work. We are ofc very interested to understand and fix the actual problem. Can you please send us a copy of the `ichspi.o` and `ich_descriptors.o` of the failing build. Did you change anything in the code? or tried to build different versions? switch branches? in case, you could try a `make clean` (although, I can't imagine why it would be necessary). Oh, I nearly forgot: Please show us the output of `git describe` (I'm loosing track of our branches atm). Nico

2 1

Flashrom and Bus Pirate issue on cFeon EN25F16
by biagiodemaio 07 Nov '17

07 Nov '17

root@Aspire-5742:~# flashrom -p buspirate_spi:dev=/dev/ttyUSB0,spispeed=1M flashrom v0.9.9-r1954 on Linux 4.13.0-16-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Atmel flash chip "unknown Atmel SPI chip" (0 kB, SPI) on buspirate_spi. === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! I am using a Bus Pirate v3 (version 3.6 on chart) This are Bus Pirate actual dates : Bus Pirate v3.5 Community Firmware v7.1 - goo.gl/gCzQnW [HiZ 1-WIRE UART I2C SPI 2WIRE 3WIRE KE5 DEVID:0x0447 REVID:0x3046 (24FJ64GA00 2 B8) http://dangerousprototypes.com Trying to read a Eeprom chip cFeon EN25F16 and got this issue. Looking for Bus Pirate I found other users to manifest prooblems with Flashrom e Bus Pirate about cFeon ! I tried to read a Macronix chip and It did good. Then I used an CH341A programmer whit Flashrom an It reads well the EN25F16 ... so I don't know if problem is on Bus Pirate or on Flashrom compatibility with cFeon chips. Many thanks Biagio De Maio

1 0

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Stefan Tauner 03 Nov '17

03 Nov '17

On Tue, 31 Oct 2017 00:18:58 +0000 Anders Nelson <anders.k.nelson(a)gmail.com> wrote: > I'm trying to compile the latest stable source on my Ubuntu-based GalliumOS > system running on a recent x86_64 Chromebook. > > I get the error: > > ichspi.o: In function `ich_init_spi': > ichspi.c:(.text+0x26b2): undefined reference to > `read_ich_descriptors_via_fdo' Hi, can you please post more details about your build environment? E.g., the output of cc -v cc -dM -E - < /dev/null The latter should output all preprocessor defines, excluding/including the culprit 64b macros. According the best source I am aware of (https://sourceforge.net/p/predef/wiki/Architectures/) both, __amd64__ and __x86_64__ should be equivalently available in all systems we care about. But as Nico stated we have used both (and some additional variations) in various places which makes such breakage possible. Maybe we should use a similar approach as for discerning OSes with a central header file defining our own macros... I have once started such a thing in hwaccess.c. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] Patch to flashrom for Macronix M25U12835F flash support and write protection bug fix
by David Hendricks 03 Nov '17

03 Nov '17

Hello Alex, Thank you for this patch and your friendly nudge in the other thread. I have uploaded it to chromium.org so that they can review, test, and merge it: https://chromium-review.googlesource.com/c/chromiumos/third_party/flashrom/… On Mon, Sep 4, 2017 at 8:47 PM, <alexlu6(a)mxic.com.tw> wrote: > Dear Sir, > > I am from Macronix (Taiwan), here I send you the source patch that > could > fix the write protection error on Chromebook project which came form > Quatun Computer. > I hope you can help patching into the Flashrom project (branch: master). > Thanks a lot ! > > Alex Lu > Macronix , FAE Dept. > > > CONFIDENTIALITY NOTE: > > This e-mail and any attachments may contain confidential information > and/or personal data, which is protected by applicable laws. Please be > reminded that duplication, disclosure, distribution, or use of this e-mail > (and/or its attachments) or any part thereof is prohibited. If you receive > this e-mail in error, please notify us immediately and delete this mail as > well as its attachment(s) from your system. In addition, please be informed > that collection, processing, and/or use of personal data is prohibited > unless expressly permitted by personal data protection laws. Thank you for > your attention and cooperation. > > Macronix International Co., Ltd. > > ===================================================================== > > > CONFIDENTIALITY NOTE: > > This e-mail and any attachments may contain confidential information > and/or personal data, which is protected by applicable laws. Please be > reminded that duplication, disclosure, distribution, or use of this e-mail > (and/or its attachments) or any part thereof is prohibited. If you receive > this e-mail in error, please notify us immediately and delete this mail as > well as its attachment(s) from your system. In addition, please be informed > that collection, processing, and/or use of personal data is prohibited > unless expressly permitted by personal data protection laws. Thank you for > your attention and cooperation. > > Macronix International Co., Ltd. > > ===================================================================== > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom >

1 0

working board - elitegroup P6STMT
by Branden Waldner 02 Nov '17

02 Nov '17

I've been using this board for chips in testing coreboot on a asus p2-99. Chips are correctly identified when hot swapped and do not get corrupted on power down. Flashrom does _not_ work on the asus p2-99. It fails to find the flash chip. The p2-99 seems to be very similiar to the asus p2b, just with 440ZX instead of a 440BX northbridge and one less ram slot.

1 0

Re: [flashrom] 回信: flashrom post acknowledgement
by Nico Huber 01 Nov '17

01 Nov '17

Hello Alex, On 31.10.2017 07:42, alexlu6(a)mxic.com.tw wrote: > Dear Sir, > > I had posted the patch update for almost 2 months, Can you tell us > that > when will the update merged to the main flashrom project trunk ? Our not any time soon. It looks like you posted your patch to the wrong version of flashrom. There's another branch/fork at chromium[1]. I'll put some people in CC who can tell you how to push your patch there. Thanks anyway for your contribution. Nico [1] https://chromium.googlesource.com/chromiumos/third_party/flashrom/ PS. That your original mail had three! times the same confidentiality note, might have made many people simply ignore it. This is a public mailing list. Please don't send such notes to the public.

2 1

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Nico Huber 31 Oct '17

31 Oct '17

Hi Anders, On 31.10.2017 01:18, Anders Nelson wrote: > Hi guys, > > I'm trying to compile the latest stable source on my Ubuntu-based GalliumOS > system running on a recent x86_64 Chromebook. > > I get the error: > > ichspi.o: In function `ich_init_spi': > ichspi.c:(.text+0x26b2): undefined reference to > `read_ich_descriptors_via_fdo' looking at the code, there seem to be different ways used to decide if we build for x86. So some code for x86 gets built in but some other piece is missing. As you only need FTDI support, you can just try to build without the internal programmers (e.g. `make CONFIG_INTERNAL=no`). If you know how to apply it, please also try the patch attached and report back if it helps. > > I've installed all the packages noted in the README even though I'm only > interested in supporting the FTDI 2232H chip on the breakout board sold by > SeeedStudio. > > Any suggestions I can try to get this built? I'm relatively new to Linux so > I apologize in advance for any gaps in knowledge. Nothing to apologize for. That error is very unexpected. Nico

1 0

回信: flashrom post acknowledgement
by alexlu6＠mxic.com.tw 31 Oct '17

31 Oct '17

Dear Sir, I had posted the patch update for almost 2 months, Can you tell us that when will the update merged to the main flashrom project trunk ? Our customer is waiting for the update. Thanks! Alex Lu flashrom-bounces(a)flashrom.org 寄件人: "flashrom" <flashrom-bounces(a)flashrom.org> 2017/09/05 下午 01:04 收件人 alexlu6(a)mxic.com.tw, 副本抄送主旨 flashrom post acknowledgement Your message entitled Patch to flashrom for Macronix M25U12835F flash support and write protection bug fix was successfully received by the flashrom mailing list. List info page: https://mail.coreboot.org/mailman/listinfo/flashrom Your preferences: https://mail.coreboot.org/mailman/options/flashrom/alexlu6%40mxic.com.tw CONFIDENTIALITY NOTE: This e-mail and any attachments may contain confidential information and/or personal data, which is protected by applicable laws. Please be reminded that duplication, disclosure, distribution, or use of this e-mail (and/or its attachments) or any part thereof is prohibited. If you receive this e-mail in error, please notify us immediately and delete this mail as well as its attachment(s) from your system. In addition, please be informed that collection, processing, and/or use of personal data is prohibited unless expressly permitted by personal data protection laws. Thank you for your attention and cooperation. Macronix International Co., Ltd. ===================================================================== ============================================================================ CONFIDENTIALITY NOTE: This e-mail and any attachments may contain confidential information and/or personal data, which is protected by applicable laws. Please be reminded that duplication, disclosure, distribution, or use of this e-mail (and/or its attachments) or any part thereof is prohibited. If you receive this e-mail in error, please notify us immediately and delete this mail as well as its attachment(s) from your system. In addition, please be informed that collection, processing, and/or use of personal data is prohibited unless expressly permitted by personal data protection laws. Thank you for your attention and cooperation. Macronix International Co., Ltd. =====================================================================

1 0

Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Anders Nelson 31 Oct '17

31 Oct '17

Hi guys, I'm trying to compile the latest stable source on my Ubuntu-based GalliumOS system running on a recent x86_64 Chromebook. I get the error: ichspi.o: In function `ich_init_spi': ichspi.c:(.text+0x26b2): undefined reference to `read_ich_descriptors_via_fdo' I've installed all the packages noted in the README even though I'm only interested in supporting the FTDI 2232H chip on the breakout board sold by SeeedStudio. Any suggestions I can try to get this built? I'm relatively new to Linux so I apologize in advance for any gaps in knowledge. =] -- Anders Nelson +1 (517) 775-6129 www.erogear.com

1 0

Future flashrom development
by Nico Huber 25 Oct '17

25 Oct '17

Dear flashrom contributors, you might have noticed that there hasn't been a release of flashrom in the past 1.5 years. That doesn't mean that there wasn't any progress, though. Development has continued and some patches were merged into a common branch [1]. Alas, not in the `stable` branch of the official repository. I'd rather not discuss now, why (it's complicated). As the original plan was to have two separate branches `stable` and `staging` anyway [2] and we finally got the first commit for `stable` together (which was stalling the branch), I thought it would be a good idea to move the already baked and tested commits from `staging` to `stable`. Sadly, even this got stalled again. Plus, there is doubt if the two branches model is feasible at all: * How to maintain patch compatibility between them? * Should everything be first submitted to `staging`? * If not, who'd be allowed to decide to push directly to `stable` and why? * ... So I propose the following: Forget the two branches model, start a `master` branch with either the current state of `staging` or my proposed move to `stable` [3] and release flashrom-1.0 right away. Submission to the current `staging` branch took place within core- boot's Gerrit infrastructure. As for myself, I would like to con- tinue that for any flashrom branch. IMO, it works reasonably well to work on a branch together. Though, I know that not everybody is happy with Gerrit and am open for anything else that doesn't incur a bottleneck. Thoughts? Nico [1] `staging` on https://review.coreboot.org/cgit/flashrom.git [2] https://www.flashrom.org/Development_Guidelines#Branches [3] The result if somebody submits the following patch queue: https://review.coreboot.org/#/q/status:open+branch:stable+owner:"Nico Huber"

4 10

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom