- flashrom - mail.coreboot.org

S25FL127S-128k
by ruckzuck＠tuta.io July 11, 2020

July 11, 2020

Hallo here is the vvv log: flashrom -p linux_spi:dev=/dev/spidev0.0 --read flashdump.bin -VVV List only S25FL127S-64kB and S25FL127S-256k but not S25FL127S-128k why ? need flashrom a update ? Probing for Spansion S25FL127S-64kB, 16384 kB: programmer_map_flash_region: mapping S25FL127S-64kB from 0xff000000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Spansion S25FL127S-256kB, 16384 kB: programmer_map_flash_region: mapping S25FL127S-256kB from 0xff000000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Spansion S25FL128P......0, 16384 kB: programmer_map_flash_region: mapping S25FL128P......0 from 0xff000000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Spansion S25FL128P......1, 16384 kB: programmer_map_flash_region: mapping S25FL128P......1 from 0xff000000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Spansion S25FL128S......0, 16384 kB: programmer_map_flash_region: mapping S25FL128S......0 from 0xff000000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Spansion S25FL128S......1, 16384 kB: programmer_map_flash_region: mapping S25FL128S......1 from 0xff000000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Spansion S25FL129P......0, 16384 kB: programmer_map_flash_region: mapping S25FL129P......0 from 0xff000000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Spansion S25FL129P......1, 16384 kB: programmer_map_flash_region: mapping S25FL129P......1 from 0xff000000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25LF020A, 256 kB: programmer_map_flash_region: mapping SST25LF020A from 0xfffc0000 to 0x00000000 REMS returned 0x00 0x0d. probe_spi_rems: id1 0x0, id2 0xd programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25LF040A, 512 kB: programmer_map_flash_region: mapping SST25LF040A from 0xfff80000 to 0x00000000 RES returned 0x0d 0x0d. probe_spi_res2: id1 0xd, id2 0xd programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25LF080(A), 1024 kB: programmer_map_flash_region: mapping SST25LF080(A) from 0xfff00000 to 0x00000000 RES returned 0x0d 0x0d. probe_spi_res2: id1 0xd, id2 0xd programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25VF512(A), 64 kB: programmer_map_flash_region: mapping SST25VF512(A) from 0xffff0000 to 0x00000000 REMS returned 0x00 0x0d. probe_spi_rems: id1 0x0, id2 0xd programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25VF010(A), 128 kB: programmer_map_flash_region: mapping SST25VF010(A) from 0xfffe0000 to 0x00000000 REMS returned 0x00 0x0d. probe_spi_rems: id1 0x0, id2 0xd programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25VF020, 256 kB: programmer_map_flash_region: mapping SST25VF020 from 0xfffc0000 to 0x00000000 REMS returned 0x00 0x0d. probe_spi_rems: id1 0x0, id2 0xd programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25VF020B, 256 kB: programmer_map_flash_region: mapping SST25VF020B from 0xfffc0000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25VF040, 512 kB: programmer_map_flash_region: mapping SST25VF040 from 0xfff80000 to 0x00000000 REMS returned 0x00 0x0d. probe_spi_rems: id1 0x0, id2 0xd programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25VF040B, 512 kB: programmer_map_flash_region: mapping SST25VF040B from 0xfff80000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25VF040B.REMS, 512 kB: programmer_map_flash_region: mapping SST25VF040B.REMS from 0xfff80000 to 0x00000000 REMS returned 0x00 0x0d. probe_spi_rems: id1 0x0, id2 0xd programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25WF020A, 256 kB: programmer_map_flash_region: mapping SST25WF020A from 0xfffc0000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25WF040B, 512 kB: programmer_map_flash_region: mapping SST25WF040B from 0xfff80000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25WF080B, 1024 kB: programmer_map_flash_region: mapping SST25WF080B from 0xfff00000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25VF080B, 1024 kB: programmer_map_flash_region: mapping SST25VF080B from 0xfff00000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25VF016B, 2048 kB: programmer_map_flash_region: mapping SST25VF016B from 0xffe00000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25VF032B, 4096 kB: programmer_map_flash_region: mapping SST25VF032B from 0xffc00000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25VF064C, 8192 kB: programmer_map_flash_region: mapping SST25VF064C from 0xff800000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25WF512, 64 kB: programmer_map_flash_region: mapping SST25WF512 from 0xffff0000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25WF010, 128 kB: programmer_map_flash_region: mapping SST25WF010 from 0xfffe0000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25WF020, 256 kB: programmer_map_flash_region: mapping SST25WF020 from 0xfffc0000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25WF040, 512 kB: programmer_map_flash_region: mapping SST25WF040 from 0xfff80000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for SST SST25WF080, 1024 kB: programmer_map_flash_region: mapping SST25WF080 from 0xfff00000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25Q40.V, 512 kB: programmer_map_flash_region: mapping W25Q40.V from 0xfff80000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25Q80.V, 1024 kB: programmer_map_flash_region: mapping W25Q80.V from 0xfff00000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25Q16.V, 2048 kB: programmer_map_flash_region: mapping W25Q16.V from 0xffe00000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25Q32.V, 4096 kB: programmer_map_flash_region: mapping W25Q32.V from 0xffc00000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25Q64.V, 8192 kB: programmer_map_flash_region: mapping W25Q64.V from 0xff800000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25Q128.V, 16384 kB: programmer_map_flash_region: mapping W25Q128.V from 0xff000000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25Q20.W, 256 kB: programmer_map_flash_region: mapping W25Q20.W from 0xfffc0000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25Q40.W, 512 kB: programmer_map_flash_region: mapping W25Q40.W from 0xfff80000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25Q80.W, 1024 kB: programmer_map_flash_region: mapping W25Q80.W from 0xfff00000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25Q16.W, 2048 kB: programmer_map_flash_region: mapping W25Q16.W from 0xffe00000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25Q32.W, 4096 kB: programmer_map_flash_region: mapping W25Q32.W from 0xffc00000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25Q64.W, 8192 kB: programmer_map_flash_region: mapping W25Q64.W from 0xff800000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25Q128.W, 16384 kB: programmer_map_flash_region: mapping W25Q128.W from 0xff000000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25X10, 128 kB: programmer_map_flash_region: mapping W25X10 from 0xfffe0000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25X20, 256 kB: programmer_map_flash_region: mapping W25X20 from 0xfffc0000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25X40, 512 kB: programmer_map_flash_region: mapping W25X40 from 0xfff80000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25X80, 1024 kB: programmer_map_flash_region: mapping W25X80 from 0xfff00000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25X16, 2048 kB: programmer_map_flash_region: mapping W25X16 from 0xffe00000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25X32, 4096 kB: programmer_map_flash_region: mapping W25X32 from 0xffc00000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Winbond W25X64, 8192 kB: programmer_map_flash_region: mapping W25X64 from 0xff800000 to 0x00000000 RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e programmer_unmap_flash_region: unmapped 0x00000000 Probing for Unknown SFDP-capable chip, 0 kB: spi_sfdp_read_sfdp_chunk: addr=0x0, len=2, data: 0x35 0x33 spi_sfdp_read_sfdp_chunk: addr=0x2, len=2, data: 0x33 0x34 Signature = 0x34333335 (should be 0x50444653) No SFDP signature found. Probing for AMIC unknown AMIC SPI chip, 0 kB: RDID returned 0x00 0x18 0x0e 0x37. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e Probing for Atmel unknown Atmel SPI chip, 0 kB: RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e Probing for Eon unknown Eon SPI chip, 0 kB: RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e Probing for Macronix unknown Macronix SPI chip, 0 kB: RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e Probing for PMC unknown PMC SPI chip, 0 kB: RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e Probing for SST unknown SST SPI chip, 0 kB: RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e Probing for ST unknown ST SPI chip, 0 kB: RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e Probing for Sanyo unknown Sanyo SPI chip, 0 kB: RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e Probing for Generic unknown SPI chip (RDID), 0 kB: RDID returned 0x00 0x18 0x0e. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x180e Probing for Generic unknown SPI chip (REMS), 0 kB: REMS returned 0x00 0x0d. probe_spi_rems: id1 0x0, id2 0xd No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. pi@raspberrypi:~ $ -- Sicher gesendet mit Tutanota. Hol dir deine eigene verschlüsselte & werbefreie Mailbox: https://tutanota.com

2 1

Hardware Support
by ruckzuck＠tuta.io July 11, 2020

July 11, 2020

Hallo, Is the Spansion S25FL127S 128-Mb supportet ? If not become flashrom a update? that it work with this chip MFG zuck -- Sicher gesendet mit Tutanota. Hol dir deine eigene verschlüsselte & werbefreie Mailbox: https://tutanota.com

2 1

correct comand
by ruckzuck＠tuta.io July 11, 2020

July 11, 2020

Hallo, I hope my English is good inouge, I try: flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1 flashrom on Linux 4.19.118+ (armv6l) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25Q32.V" (4096 kB, SPI) on linux_spi. No operations were specified. And i try: flashrom -p linux_spi:dev=/dev/spidev0.0 -r old_bios.bin,spispeed=1 flashrom on Linux 4.19.118+ (armv6l) flashrom is free software, get the source code at https://flashrom.org Then come this: Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on linux_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! Read is not working on this chip. Aborting. Dit i make something wrong in the Comand, how look the correct Comand, or is W25Q32.V not suppotret ? In flashrom -L i see W25Q32.V. Sicher gesendet mit Tutanota. Hol dir deine eigene verschlüsselte & werbefreie Mailbox: https://tutanota.com

2 1

Successful test report: GD25LB128D (0xc8, 0x6018) / ch341a_spi
by ewx July 11, 2020

July 11, 2020

Hello; Successfuly tested following operations on a GD25LB128D chip (RDID 0xc8,0x6018) registering as "GD25LQ128C/GD25LQ128D" with the current codebase due to shared chip ID, w/ a CH341a programmer: - PROBE - READ - ERASE - WRITE See attached log files for details. Thank you and have a nice day!

1 0

Trying flashing ASROCK AB350M Pro4
by Karl SOULABAILLE - IWS July 5, 2020

July 5, 2020

hello, I am trying to flashing a board Asrock AB350M Pro4. Doesn't work, so here is information about board: # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 3.0.0 present. Table at 0x000E94F0. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: P5.10 Release Date: 10/05/2018 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.13 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: To Be Filled By O.E.M. Product Name: To Be Filled By O.E.M. Version: To Be Filled By O.E.M. Serial Number: To Be Filled By O.E.M. UUID: 6bc28570-be7b-0000-0000-000000000000 Wake-up Type: Power Switch SKU Number: To Be Filled By O.E.M. Family: To Be Filled By O.E.M. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASRock Product Name: AB350M Pro4 Version: Serial Number: Asset Tag: --- root@eureka6:~# flashrom -p internal flashrom on Linux 5.4.44-1-pve (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 chipset "AMD FP4". Enabling flash write... FCH device found but SMBus revision 0x61 does not match known values. Please report this to flashrom(a)flashrom.org and include this log and the output of lspci -nnvx, thanks!. Could not determine chipset generation.PROBLEMS, continuing anyway No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. --- root@eureka6:~# lspci -nnvx 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex [1022:15d0] Subsystem: ASRock Incorporation Raven/Raven2 Root Complex [1849:15d0] Flags: fast devsel 00: 22 10 d0 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 49 18 d0 15 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU [1022:15d1] Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU [1022:15d1] Flags: bus master, fast devsel, latency 0, IRQ 25 Capabilities: [40] Secure device <?> Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00: 22 10 d1 15 04 04 10 00 00 00 06 08 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 d1 15 30: 00 00 00 00 40 00 00 00 00 00 00 00 ff 01 00 00 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Flags: fast devsel 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 26 Bus: primary=00, secondary=15, subordinate=22, sec-latency=0 I/O behind bridge: 0000f000-0000ffff Memory behind bridge: fe700000-fe8fffff Prefetchable memory behind bridge: 00000000f0300000-00000000f03fffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:1453] Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [270] #19 Capabilities: [2a0] Access Control Services Capabilities: [370] L1 PM Substates Kernel driver in use: pcieport 00: 22 10 d3 15 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 15 22 00 f1 f1 00 20 20: 70 fe 80 fe 31 f0 31 f0 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 12 00 00:01.6 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 27 Bus: primary=00, secondary=2e, subordinate=2e, sec-latency=0 I/O behind bridge: 00001000-00001fff Memory behind bridge: f0400000-f05fffff Prefetchable memory behind bridge: 00000000f0600000-00000000f07fffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:1453] Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [270] #19 Capabilities: [2a0] Access Control Services Capabilities: [370] L1 PM Substates Kernel driver in use: pcieport 00: 22 10 d3 15 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 2e 2e 00 11 11 00 00 20: 40 f0 50 f0 61 f0 71 f0 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 12 00 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Flags: fast devsel 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A [1022:15db] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 28 Bus: primary=00, secondary=38, subordinate=38, sec-latency=0 I/O behind bridge: 0000e000-0000efff Memory behind bridge: fe300000-fe6fffff Prefetchable memory behind bridge: 00000000e0000000-00000000f01fffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot-), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A [1022:0000] Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] #19 Capabilities: [2a0] Access Control Services Kernel driver in use: pcieport 00: 22 10 db 15 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 38 38 00 e1 e1 00 00 20: 30 fe 60 fe 01 e0 11 f0 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 1a 00 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B [1022:15dc] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 29 Bus: primary=00, secondary=39, subordinate=39, sec-latency=0 Memory behind bridge: fe900000-fe9fffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot-), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B [1022:0000] Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] #19 Kernel driver in use: pcieport 00: 22 10 dc 15 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 39 39 00 f1 01 00 00 20: 90 fe 90 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 12 00 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) Subsystem: ASRock Incorporation FCH SMBus Controller [1849:790b] Flags: 66MHz, medium devsel Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4, sp5100_tco 00: 22 10 0b 79 03 04 20 02 61 00 05 0c 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 49 18 0b 79 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) Subsystem: ASRock Incorporation FCH LPC Bridge [1849:790e] Flags: bus master, 66MHz, medium devsel, latency 0 00: 22 10 0e 79 0f 00 20 02 51 00 01 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 49 18 0e 79 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0 [1022:15e8] Flags: fast devsel 00: 22 10 e8 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1 [1022:15e9] Flags: fast devsel 00: 22 10 e9 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2 [1022:15ea] Flags: fast devsel 00: 22 10 ea 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3 [1022:15eb] Flags: fast devsel Kernel driver in use: k10temp Kernel modules: k10temp 00: 22 10 eb 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4 [1022:15ec] Flags: fast devsel 00: 22 10 ec 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5 [1022:15ed] Flags: fast devsel 00: 22 10 ed 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6 [1022:15ee] Flags: fast devsel 00: 22 10 ee 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7 [1022:15ef] Flags: fast devsel 00: 22 10 ef 15 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 15:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset USB 3.1 xHCI Controller [1022:43bb] (rev 02) (prog-if 30 [XHCI]) Subsystem: ASRock Incorporation 300 Series Chipset USB 3.1 xHCI Controller [1849:43d0] Flags: bus master, fast devsel, latency 0, IRQ 41 Memory at fe8a0000 (64-bit, non-prefetchable) [size=32K] Capabilities: [50] MSI: Enable+ Count=1/8 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [200] #19 Capabilities: [300] Latency Tolerance Reporting Capabilities: [400] L1 PM Substates Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00: 22 10 bb 43 06 04 10 00 02 30 03 0c 10 00 80 00 10: 04 00 8a fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 49 18 d0 43 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 00 15:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset SATA Controller [1022:43b7] (rev 02) (prog-if 01 [AHCI 1.0]) Subsystem: ASRock Incorporation 300 Series Chipset SATA Controller [1849:43c8] Flags: bus master, fast devsel, latency 0, IRQ 37 Memory at fe880000 (32-bit, non-prefetchable) [size=128K] Expansion ROM at fe800000 [disabled] [size=512K] Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Kernel driver in use: ahci Kernel modules: ahci 00: 22 10 b7 43 06 04 10 00 02 01 06 01 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 88 fe 00 00 00 00 49 18 c8 43 30: 00 00 80 fe 50 00 00 00 00 00 00 00 0a 02 00 00 15:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43b2] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 31 Bus: primary=15, secondary=1d, subordinate=22, sec-latency=0 I/O behind bridge: 0000f000-0000ffff Memory behind bridge: fe700000-fe7fffff Prefetchable memory behind bridge: 00000000f0300000-00000000f03fffff Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Upstream Port, MSI 00 Capabilities: [c0] Subsystem: ASRock Incorporation Device [1849:43c6] Capabilities: [100] Advanced Error Reporting Kernel driver in use: pcieport 00: 22 10 b2 43 07 04 10 00 02 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 15 1d 22 00 f1 f1 00 00 20: 70 fe 70 fe 31 f0 31 f0 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 05 03 12 00 1d:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 33 Bus: primary=1d, secondary=1e, subordinate=1e, sec-latency=0 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Downstream Port (Slot+), MSI 00 Capabilities: [c0] Subsystem: ASRock Incorporation 300 Series Chipset PCIe Port [1849:43c7] Capabilities: [100] Advanced Error Reporting Capabilities: [200] #19 Capabilities: [400] L1 PM Substates Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 1d 1e 1e 00 f1 01 00 00 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 12 00 1d:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 35 Bus: primary=1d, secondary=1f, subordinate=1f, sec-latency=0 I/O behind bridge: 0000f000-0000ffff Memory behind bridge: fe700000-fe7fffff Prefetchable memory behind bridge: 00000000f0300000-00000000f03fffff Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Downstream Port (Slot+), MSI 00 Capabilities: [c0] Subsystem: ASRock Incorporation 300 Series Chipset PCIe Port [1849:43c7] Capabilities: [100] Advanced Error Reporting Capabilities: [200] #19 Capabilities: [400] L1 PM Substates Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 1d 1f 1f 00 f1 f1 00 00 20: 70 fe 70 fe 31 f0 31 f0 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 0a 01 12 00 1d:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 36 Bus: primary=1d, secondary=22, subordinate=22, sec-latency=0 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Downstream Port (Slot+), MSI 00 Capabilities: [c0] Subsystem: ASRock Incorporation 300 Series Chipset PCIe Port [1849:43c7] Capabilities: [100] Advanced Error Reporting Capabilities: [200] #19 Capabilities: [400] L1 PM Substates Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 1d 22 22 00 f1 01 00 00 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 12 00 1f:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 11) Subsystem: ASRock Incorporation Motherboard (one of many) [1849:8168] Flags: bus master, fast devsel, latency 0, IRQ 34 I/O ports at f000 [size=256] Memory at fe700000 (64-bit, non-prefetchable) [size=4K] Memory at f0300000 (64-bit, prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable+ Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number be-7b-6b-c2-85-70-00-00 Capabilities: [170] Latency Tolerance Reporting Kernel driver in use: r8169 Kernel modules: r8169 00: ec 10 68 81 07 04 10 00 11 00 00 02 10 00 00 00 10: 01 f0 00 00 00 00 00 00 04 00 70 fe 00 00 00 00 20: 0c 00 30 f0 00 00 00 00 00 00 00 00 49 18 68 81 30: 00 00 00 00 40 00 00 00 00 00 00 00 0a 01 00 00 38:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at f0000000 (64-bit, prefetchable) [size=2M] I/O ports at e000 [size=256] Memory at fe600000 (32-bit, non-prefetchable) [size=512K] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/4 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable- Count=3 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [200] #15 Capabilities: [270] #19 Capabilities: [2a0] Access Control Services Capabilities: [2b0] Address Translation Service (ATS) Capabilities: [2c0] Page Request Interface (PRI) Capabilities: [2d0] Process Address Space ID (PASID) Capabilities: [320] Latency Tolerance Reporting Kernel modules: amdgpu 00: 02 10 dd 15 07 00 10 08 c8 00 00 03 10 00 80 00 10: 0c 00 00 e0 00 00 00 00 0c 00 00 f0 00 00 00 00 20: 01 e0 00 00 00 00 60 fe 00 00 00 00 02 10 dd 15 30: 00 00 00 00 48 00 00 00 00 00 00 00 0b 01 00 00 38:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller [1002:15de] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller [1002:15de] Flags: bus master, fast devsel, latency 0, IRQ 55 Memory at fe680000 (32-bit, non-prefetchable) [size=16K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00: 02 10 de 15 07 04 10 00 00 00 03 04 10 00 80 00 10: 00 00 68 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 02 10 de 15 30: 00 00 00 00 48 00 00 00 00 00 00 00 0a 02 00 00 38:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df] Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df] Flags: bus master, fast devsel, latency 0, IRQ 5 Memory at fe500000 (32-bit, non-prefetchable) [size=1M] Memory at fe684000 (32-bit, non-prefetchable) [size=8K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/2 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable- Count=2 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> 00: 22 10 df 15 07 00 10 00 00 00 80 10 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 50 fe 00 00 00 00 20: 00 00 00 00 00 40 68 fe 00 00 00 00 22 10 df 15 30: 00 00 00 00 48 00 00 00 00 00 00 00 05 03 00 00 38:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 [1022:15e0] (prog-if 30 [XHCI]) Subsystem: ASRock Incorporation Raven USB 3.1 [1849:7914] Flags: bus master, fast devsel, latency 0, IRQ 42 Memory at fe400000 (64-bit, non-prefetchable) [size=1M] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=8 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00: 22 10 e0 15 07 04 10 00 00 30 03 0c 10 00 80 00 10: 04 00 40 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 49 18 14 79 30: 00 00 00 00 48 00 00 00 00 00 00 00 0b 04 00 00 38:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 [1022:15e1] (prog-if 30 [XHCI]) Subsystem: ASRock Incorporation Raven USB 3.1 [1849:7914] Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at fe300000 (64-bit, non-prefetchable) [size=1M] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=8 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00: 22 10 e1 15 07 04 10 00 00 30 03 0c 10 00 80 00 10: 04 00 30 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 49 18 14 79 30: 00 00 00 00 48 00 00 00 00 00 00 00 0b 01 00 00 39:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 61) (prog-if 01 [AHCI 1.0]) Subsystem: ASRock Incorporation FCH SATA Controller [AHCI mode] [1849:7901] Flags: bus master, fast devsel, latency 0, IRQ 39 Memory at fe900000 (32-bit, non-prefetchable) [size=2K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/2 Maskable- 64bit+ Capabilities: [d0] SATA HBA v1.0 Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] #19 Kernel driver in use: ahci Kernel modules: ahci 00: 22 10 01 79 07 04 10 00 61 01 06 01 10 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 90 fe 00 00 00 00 49 18 01 79 30: 00 00 00 00 48 00 00 00 00 00 00 00 05 01 00 00 root@eureka6:~#

1 0

[Success] AAEON BOXER-6404
by thompson＠lol1093.com July 3, 2020

July 3, 2020

DMI string chassis-type: "Desktop" DMI string system-manufacturer: "AAEON" DMI string system-product-name: "BOXER-6404" DMI string system-version: "V1.0" DMI string baseboard-manufacturer: "AAEON" DMI string baseboard-product-name: "BOXER-6404" DMI string baseboard-version: "To be filled by O.E.M." Found chipset "Intel Bay Trail" with PCI ID 8086:0f1c. From BIOS Information Vendor: American Megatrends Inc. Version: B404BM10 Release Date: 07/16/2015 To BIOS Information Vendor: American Megatrends Inc. Version: B404BM14 Release Date: 02/19/2019

1 0

read_status_opaque called before register_opaque_master.
by Todd Broch June 30, 2020

June 30, 2020

Hello flashrom maintainers, I received the following warning, 'read_status_opaque called before register_opaque_master.' while using flashrom as part of the chromeos-firmwareupdate script. Full details below. Please let me know if you need more details. Best, Todd Broch -------------------- grep DESCRIP /etc/lsb-release #CHROMEOS_RELEASE_DESCRIPTION=13311.0.0 (Official Build) dev-channel caroline test /usr/share/vboot/bin/make_dev_firmware.sh chromeos-firmwareupdate --mode=autoupdate Machine Model: caroline Write Protect: HW=0 SW=0 Last Boot Version: RO=Google_Caroline.7820.263.0 ACT/B=Google_Caroline.7820.286.0 Firmware Updater: RO=Google_Caroline.7820.300.0 RW=Google_Caroline.7820.384.0 >> Starting firmware updater. >> Target image: bios.bin (RO:Google_Caroline.7820.300.0, RW/A:Google_Caroline.7820.384.0, RW/B:Google_Caroline.7820.384.0). INFO: update_firmware: Loading current system firmware... >> Current system: /tmp/fwupdater.ecQBWI (RO:Google_Caroline.7820.263.0, RW/A:Google_Caroline.7820.263.0, RW/B:Google_Caroline.7820.286.0). >> Write protection: 0 (disabled; HW=0, SW=0). WARNING: update_firmware: RO changed and no WP. Need full update. >> FULL UPDATE: Updating whole firmware image(s), RO+RW. INFO: update_whole_firmware: Checking compatibility... INFO: host_flashrom: Executing: flashrom -w /tmp/fwupdater.u35SbM -p host flashrom v0.9.9 : c093d68c : Jun 26 2020 15:10:22 UTC on Linux 3.18.0-20514-g469972f7e001 (x86_64) flashrom v0.9.9 : c093d68c : Jun 26 2020 15:10:22 UTC on Linux 3.18.0-20514-g469972f7e001 (x86_64) Calibrating delay loop... OK. coreboot table found at 0x7aa4c000. Found chipset "Intel Skylake". Enabling flash write... WARNING: SPI Configuration Lockdown activated. OK. Erasing and writing flash chip... Verifying flash... VERIFIED. SUCCESS INFO: host_flashrom: Executing: flashrom -w /tmp/fwupdater.OdguzF -p ec flashrom v0.9.9 : c093d68c : Jun 26 2020 15:10:22 UTC on Linux 3.18.0-20514-g469972f7e001 (x86_64) flashrom v0.9.9 : c093d68c : Jun 26 2020 15:10:22 UTC on Linux 3.18.0-20514-g469972f7e001 (x86_64) Calibrating delay loop... OK. coreboot table found at 0x7aa4c000. Found chipset "Intel Skylake". Enabling flash write... WARNING: SPI Configuration Lockdown activated. OK. read_status_opaque called before register_opaque_master. Please report a bug at flashrom(a)flashrom.org Erasing and writing flash chip... Erasing and writing flash chip... Verifying flash... VERIFIED. SUCCESS INFO: host_flashrom: Executing: flashrom -w /tmp/fwupdater.ybATJ6 -p ec:type=pd flashrom v0.9.9 : c093d68c : Jun 26 2020 15:10:22 UTC on Linux 3.18.0-20514-g469972f7e001 (x86_64) flashrom v0.9.9 : c093d68c : Jun 26 2020 15:10:22 UTC on Linux 3.18.0-20514-g469972f7e001 (x86_64) Calibrating delay loop... OK. coreboot table found at 0x7aa4c000. Found chipset "Intel Skylake". Enabling flash write... WARNING: SPI Configuration Lockdown activated. OK. read_status_opaque called before register_opaque_master. Please report a bug at flashrom(a)flashrom.org Erasing and writing flash chip... Erasing and writing flash chip... Verifying flash... VERIFIED. SUCCESS >> DONE: Firmware updater exits successfully.

1 0

Re: Do you have support for W25Q128FW and W25Q256.W?
by kcshekar＠winbond.com June 19, 2020

June 19, 2020

Resending this message with datasheet links below https://www.winbond.com/resource-files/W25Q256JW%20SPI%20RevG%2011252019%20… https://www.winbond.com/resource-files/W25Q128JW_RevD_03132020%20Plus.pdf From: US00 Krishna Shekar Sent: Thursday, May 7, 2020 12:14 PM To: Mike Banon <mikebdp2(a)gmail.com> Cc: US40 Jack Lee <JLee2(a)winbond.com>; SM10 YLLi5 <YLLi5(a)winbond.com>; Wu, Amin <Amin.Wu(a)amd.com>; flashrom(a)flashrom.org Subject: RE: [flashrom] Re: Do you have support for W25Q128FW and W25Q256.W? W25Q128FW and W25Q256FW are older products and have been replaced by the latest W25Q128JW and W25Q256JW serial flash products. These newer datasheets are publicly available on the Winbond web site www.winbond.com<http://www.winbond.com>. Please see these datasheets attached. Thanks. Regards, Shekar From: Mike Banon [mailto:mikebdp2@gmail.com] Sent: Thursday, May 7, 2020 12:01 PM To: US00 Krishna Shekar <kcshekar(a)winbond.com<mailto:kcshekar@winbond.com>> Cc: US40 Jack Lee <JLee2(a)winbond.com<mailto:JLee2@winbond.com>>; SM10 YLLi5 <YLLi5(a)winbond.com<mailto:YLLi5@winbond.com>>; Wu, Amin <Amin.Wu(a)amd.com<mailto:Amin.Wu@amd.com>>; flashrom(a)flashrom.org<mailto:flashrom@flashrom.org> Subject: Re: [flashrom] Re: Do you have support for W25Q128FW and W25Q256.W? flashrom is really preferable: it's the open source (important!) software that supports a lot of programmers, including the inexpensive ones like CH341A which costs just $2. To add a support for W25Q128FW and W25Q256FW to flashrom - hopefully would be enough to create the correct chip definitions in flashchips.c / flashchips.h files using the datasheets for W25Q128FW and W25Q256FW. If these datasheets aren't publicly available yet, please provide them. On Thu, May 7, 2020 at 4:23 PM kcshekar(a)winbond.com<mailto:kcshekar@winbond.com> <kcshekar(a)winbond.com<mailto:kcshekar@winbond.com>> wrote: Hi Everyone, The latest part numbers I would recommend your using are W25Q128JWSSIQ or W25Q128JWEIQ (128Mb serial flash) and W25Q256JWEIQ (256Mb serial flash) on your designs. The part numbers mentioned below are old parts and the part numbers are incomplete. The part numbers I have mentioned are supported on the AMD Renoir reference boards, and in turn supports all the CPUs that AMD offers today. If you have further questions about support for AMD products, please contact Jason Hawken at AMD, Toronto. I am not sure if these are supported on Raspberry. Please take a look at the link below to look at the support provided by several programmer vendors for Winbond flash parts. https://www.winbond.com/resource-files/AN0000012%20CodeStorageMemoryProgram… I would recommend using Dediprog programmers - You are likely to find good support on Dediprog programmers for Winbond parts. If you already have the W25Q128FW and W25Q256FW parts with you now, they are supported on the Dediprog programmers as well. Trust this information is helpful. Let us know if you need any further help. Thanks. Regards, Shekar From: US40 Jack Lee Sent: Wednesday, May 6, 2020 7:42 PM To: SM10 YLLi5 <YLLi5(a)winbond.com<mailto:YLLi5@winbond.com>>; Wu, Amin <Amin.Wu(a)amd.com<mailto:Amin.Wu@amd.com>>; US00 Krishna Shekar <kcshekar(a)winbond.com<mailto:kcshekar@winbond.com>> Cc: David Hendricks <david.hendricks(a)gmail.com<mailto:david.hendricks@gmail.com>>; flashrom(a)flashrom.org<mailto:flashrom@flashrom.org> Subject: Re: [flashrom] Do you have support for W25Q128FW and W25Q256.W? Hi Shekar, Please help and feedback. Thx. Jack ________________________________ From: SM10 YLLi5 <YLLi5(a)winbond.com<mailto:YLLi5@winbond.com>> Sent: Wednesday, May 6, 2020 7:40 PM To: Wu, Amin; US40 Jack Lee Cc: David Hendricks; flashrom(a)flashrom.org<mailto:flashrom@flashrom.org> Subject: FW: [flashrom] Do you have support for W25Q128FW and W25Q256.W? Hi Jack, Here we have the question below. do you mind to answer for this? Thanks. Do you have a plan to support flash bios for W25Q128FW and W25Q256.W via flashrom in Raspberry? Regards, Yulia From: Wu, Amin [mailto:Amin.Wu@amd.com] Sent: Thursday, May 07, 2020 10:38 AM To: SM10 YLLi5; David Hendricks Cc: flashrom(a)flashrom.org<mailto:flashrom@flashrom.org> Subject: RE: [flashrom] Do you have support for W25Q128FW and W25Q256.W? [AMD Official Use Only - Internal Distribution Only] Thanks David. I tried flashrom1.2 , W25Q128FW and W25Q256.W are not in the support list. I want use Raspberry only to flash W25Q128FW and W25Q256.W. Hi Yulia, Can you add W25Q128FW and W25Q256.W to flashrom support list to use Raspberry only? Thanks for your responding. BR AMIN From: Yulia Li <YLLi5(a)winbond.com<mailto:YLLi5@winbond.com>> Sent: Thursday, May 7, 2020 10:22 AM To: David Hendricks <david.hendricks(a)gmail.com<mailto:david.hendricks@gmail.com>>; Wu, Amin <Amin.Wu(a)amd.com<mailto:Amin.Wu@amd.com>> Cc: flashrom(a)flashrom.org<mailto:flashrom@flashrom.org> Subject: RE: [flashrom] Do you have support for W25Q128FW and W25Q256.W? [CAUTION: External Email] Hi Amin, Sorry for the late reply, do you still need any other support? Thanks. Regards, Yulia From: David Hendricks [mailto:david.hendricks@gmail.com] Sent: Saturday, April 25, 2020 12:02 PM To: Wu, Amin Cc: AP A0PH mkt_online; flashrom(a)flashrom.org<mailto:flashrom@flashrom.org> Subject: Re: [flashrom] Do you have support for W25Q128FW and W25Q256.W? Hi Amin, Please note that the W25Q128FW is a 1.8V chip, while Raspberry PI IOs are 3.3V. For Dediprog, pass in the `voltage` parameter, e.g. `flashrom -p dediprog:voltage=1.8 -r foo.bin` Also, as Mike mentioned it will help if we know the version of flashrom which you are trying to use. Some distributions provide very old versions. On Wed, Apr 22, 2020 at 1:33 AM Wu, Amin <Amin.Wu(a)amd.com<mailto:Amin.Wu@amd.com>> wrote: [AMD Official Use Only - Internal Distribution Only] Hi David Hendricks, “No EEPROM/flash device found” pop after I added below code to flashchips.c and flashchips.h to install flashrom in Raspberry 4B. pi@raspberrypi:~ $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 flashrom on Linux 4.19.57-v7l+ (armv7l) flashrom is free software, get the source code at https://flashrom.org<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fflashrom.…> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. Do you have any suggestions? Thanks 😊 flashchips.h #define WINBOND_NEX_W25Q128FW 0xef6018 /*W25Q128FW */ flashchips.c { .vendor = "Winbond", .name = "W25Q128FW", .bustype = BUS_SPI, .manufacture_id = WINBOND_NEX_ID, .model_id = WINBOND_NEX_W25Q128FW, .total_size = 16384, .page_size = 256, /* supports SFDP */ /* OTP: 1024B total, 256B reserved; read 0x48; write 0x42, erase 0x44, read ID 0x4B */ .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP | FEATURE_QPI, .tested = TEST_OK_PREW, .probe = probe_spi_rdid, .probe_timing = TIMING_ZERO, .block_erasers = { { .eraseblocks = { {4 * 1024, 4096} }, .block_erase = spi_block_erase_20, }, { .eraseblocks = { {32 * 1024, 512} }, .block_erase = spi_block_erase_52, }, { .eraseblocks = { {64 * 1024, 256} }, .block_erase = spi_block_erase_d8, }, { .eraseblocks = { {16 * 1024 * 1024, 1} }, .block_erase = spi_block_erase_60, }, { .eraseblocks = { {16 * 1024 * 1024, 1} }, .block_erase = spi_block_erase_c7, } }, .printlock = spi_prettyprint_status_register_plain, /* TODO: improve */ .unlock = spi_disable_blockprotect, .write = spi_chip_write_256, .read = spi_chip_read, .voltage = {1650, 1950}, }, BR AMIN From: Wu, Amin Sent: Wednesday, April 22, 2020 2:55 PM To: 'David Hendricks' <david.hendricks(a)gmail.com<mailto:david.hendricks@gmail.com>>; 'mkt_online(a)winbond.com<mailto:mkt_online@winbond.com>' <mkt_online(a)winbond.com<mailto:mkt_online@winbond.com>> Cc: 'flashrom(a)flashrom.org<mailto:flashrom@flashrom.org>' <flashrom(a)flashrom.org<mailto:flashrom@flashrom.org>> Subject: RE: [flashrom] Do you have support for W25Q128FW and W25Q256.W? [AMD Official Use Only - Internal Distribution Only] Hi Winbond, Do you have a plan to support flash bios for W25Q128FW and W25Q256.W via flashrom in Raspberry? BR AMIN From: Wu, Amin Sent: Tuesday, April 21, 2020 1:32 PM To: David Hendricks <david.hendricks(a)gmail.com<mailto:david.hendricks@gmail.com>> Cc: flashrom(a)flashrom.org<mailto:flashrom@flashrom.org> Subject: RE: [flashrom] Do you have support for W25Q128FW and W25Q256.W? [AMD Official Use Only - Internal Distribution Only] Hi David, Hendricks, Can you share the flashrom link to download which support W25Q128FW and W25Q256.W? Now I used DediProg to flash these bioschip. I can try with raspberry to flash when I get the flashrom from you. 😊 It is great help for me if flashrom support W25Q128FW and W25Q256.W. I tried edit flashchip.c and flashchip.h, but flash fail and fail. ☹ Thank you flashrom developer. Good job! Flashrom~Yes~ BR AMIN From: David Hendricks <david.hendricks(a)gmail.com<mailto:david.hendricks@gmail.com>> Sent: Tuesday, April 21, 2020 1:06 PM To: Wu, Amin <Amin.Wu(a)amd.com<mailto:Amin.Wu@amd.com>> Cc: flashrom(a)flashrom.org<mailto:flashrom@flashrom.org> Subject: Re: [flashrom] Do you have support for W25Q128FW and W25Q256.W? [CAUTION: External Email] Yes and yes :-) On Mon, Apr 20, 2020 at 10:05 PM Wu, Amin <Amin.Wu(a)amd.com<mailto:Amin.Wu@amd.com>> wrote: [AMD Official Use Only - Internal Distribution Only] Hi Do you have support for W25Q128FW and W25Q256.W? Thanks BR AMIN _______________________________________________ flashrom mailing list -- flashrom(a)flashrom.org<mailto:flashrom@flashrom.org> To unsubscribe send an email to flashrom-leave(a)flashrom.org<mailto:flashrom-leave@flashrom.org> ________________________________ The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond. ________________________________ The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond. _______________________________________________ flashrom mailing list -- flashrom(a)flashrom.org<mailto:flashrom@flashrom.org> To unsubscribe send an email to flashrom-leave(a)flashrom.org<mailto:flashrom-leave@flashrom.org> ________________________________ The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.

4 7

Unable to flash AT25DF641(A)
by GIRAUDEAU-BOCQUET, LIONEL June 18, 2020

June 18, 2020

Hello from France, I have been trying to perform Bios updates on many (old) computers this last days and I am facing an issue with the AT25DF641(A) chip (like in this intersting post https://www.mail-archive.com/flashrom@flashrom.org/msg07475.html but I did not find the answer I was looking for). The full story : I am replacing some very old blades by some others (very old too) I had as spare parts. As they are spare parts, they have never been used, and so they come with a very very old Bios version (which has known bugs). These blades are : System Information Manufacturer: INSYDE Product Name: Thurley Version: Thurley.3.59.48.0028_BUILD_NCB_N0016 Back in 2011, when they have been shipped, they were used with RedHat 5.x and we were using a closed source software from Insyde to update the Bios. This software used a kernel module, so, as you have already understood, it is not working any more on modern Linux sources. So, I have two choices here : - use a recent flash tool, like flashrom - create a Redhat 5 PXE Boot image and try to use the old software The easy way is the first one of course. So I downloaded the source from git, extracted a tar.gz file, compile and tried it. It worked very well on the first blade (reading try) : [root@compute67 flashrom]# ./flashrom --programmer internal -r /dev/null flashrom v1.2-57-g6f793e4 on Linux 3.10.0-1062.12.1.el7.x86_64 (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 chipset "Intel ICH10". Enabling flash write... OK. Found Atmel flash chip "AT25DF321" (4096 kB, SPI) mapped at physical address 0x00000000ffc00000. Reading flash... done. [root@compute67 flashrom]# The write part went fine too, and the blade rebooted properly with the latest Bios version. Second blade's flash try was different. It uses a AT25DF641(A) chip instead of a AT25DF321. The image size is 8MB instead of 4MB. Looking at flashrom Wiki both are handled well and should be able to be flashed. Reading test : [root@compute63 flashrom]# ./flashrom --programmer internal -r /dev/null flashrom v1.2-57-g6f793e4 on Linux 3.10.0-1062.18.1.el7.x86_64 (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 chipset "Intel ICH10". Enabling flash write... Warning: Setting BIOS Control at 0xdc from 0x02 to 0x01 failed. New value is 0x02. OK. Found Atmel flash chip "AT25DF641(A)" (8192 kB, SPI) mapped at physical address 0x00000000ff800000. Ignoring security lockdown (if present) Reading flash... done. [root@compute63 flashrom]# I decided to flash it any way (because I have spare parts), and got a nice Brick (black screen after power on, nothing to do). So, as I have a lot of blades using this AT25DF641A chip, is there a way to flash it properly (because it is reported to be working in the wiki) or should I carry on trying to create a RHEL5 PXE image and use the old tool ? Thanks for your answers, Lionel

2 2

Uprgrae SPIROM for Skylake-D platform
by HubertLin June 17, 2020

June 17, 2020

Hi, I would like to use flashrom to upgrade BIOS on Skylake-D platform. I have done some work to unlock ME and fill W25Q256JVFIQ table in flashschips.c. But there still have some opcode problem. Have you try flashrom on Skylake-D platform before? Is there any temporary patch for Skylake-D platform after v1.2 version. I would like to try it, may you please help me? The problem I meet as below, 1. ich_spi_send_command: Internal command size error for opcode 0xe9, got writecnt=1, want >=4 2. Probing for Winbond W25Q256JVFIQ, 32768 kB: Invalid OPCODE 0x9f, will not execut 3. Probing for Winbond W25Q256JVFIQ, 32768 kB: probe_spi_rdid_generic: id1 0xf7, id Thank you BR, Hubert.lin

2 8