On Mon, 9 May 2016 20:46:18 -0700
David Hendricks <dhendrix(a)google.com> wrote:
> Hi Victor,
> From Flashrom's software perspective all chips with the same ID are
> indistinguishable.
>
> Part number often includes characteristics such as package and thermal
> tolerance which do not affect software compatibility.
However, we will add the new names to the in-program (and hence
wiki) database so that this new information becomes public. Thanks for
the heads up, Victor.
--
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -r romread_v1.rom
./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w
x200_8mb_ukqwerty_txtmode.rom
flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org
Calibrating delay loop... OK.
Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.
Error: WIP bit after WRSR never cleared
spi_write_status_register failed.
Reading old flash chip contents...
Calibrating delay loop... OK.
Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.
Error: WIP bit after WRSR never cleared
spi_write_status_register failed.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... FAILED at 0x00000000! Expected=0x5a, Found=0x00,
failed byte count from 0x00000000-0x007fffff: 0x1d1
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!
.//flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w x200_8mac.rom
flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org
Calibrating delay loop... OK.
Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.
Error: WIP bit after WRSR never cleared
spi_write_status_register failed.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... FAILED at 0x00000000! Expected=0x5a, Found=0x00,
failed byte count from 0x00000000-0x007fffff: 0x2d1
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!
./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w x200_8mac.rom
flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org
Calibrating delay loop... OK.
Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.
Error: WIP bit after WRSR never cleared
spi_write_status_register failed.
Reading old flash chip contents... done.
Erasing and writing flash chip... FAILED at 0x00000100! Expected=0xff,
Found=0x89, failed byte count from 0x00000000-0x00000fff: 0x2d
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase
function.
Erase/write done.
Verifying flash... FAILED at 0x00000000! Expected=0x5a, Found=0x00,
failed byte count from 0x00000000-0x007fffff: 0x1d1
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!
./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w x200_8mac.rom
flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org
Calibrating delay loop... OK.
Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff,
Found=0x5a, failed byte count from 0x00000000-0x00000fff: 0x66
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase
function.
Erase/write done.
Verifying flash... FAILED at 0x00000000! Expected=0x5a, Found=0x00,
failed byte count from 0x00000000-0x007fffff: 0x3d1
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!
./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w
x200_8mb_ukqwerty_vesafb.rom
flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org
Calibrating delay loop... OK.
Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.
Error: WIP bit after WRSR never cleared
spi_write_status_register failed.
Reading old flash chip contents... done.
Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff,
Found=0x00, failed byte count from 0x00001000-0x00001fff: 0x62
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase
function.
FAILED at 0x00000000! Expected=0xff, Found=0x5a, failed byte count from
0x00000000-0x0000ffff: 0x6829
ERASE FAILED!
ading current flash chip contents... done. Looking for another erase
function.
FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from
0x00000000-0x007fffff: 0xf84ce
ERASE FAILED!
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase
function.
FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from
0x00000000-0x007fffff: 0xf83cf
ERASE FAILED!
Looking for another erase function.
No usable erase functions left.
FAILED!
Uh oh. Erase/write failed. Checking if anything has changed.
Uh oh. Erase/write failed. Checking if anything has changed.
Reading current flash chip contents... done.
Apparently at least some data has changed.
Your flash chip is in an unknown state.
Please report this on IRC at chat.freenode.net (channel #flashrom) or
mail flashrom(a)flashrom.org, thanks!
# ./flashrom -p internal -r test.out
flashrom v1.0.1 on Linux 4.4.0-142-generic (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 B150".
This chipset is marked as untested. If you are using an up-to-date version
of flashrom *and* were (not) able to successfully update your firmware with it,
then please email a report to flashrom(a)flashrom.org including a verbose (-V) log.
Thank you!
Enabling flash write... Warning: BIOS region SMM protection is enabled!
Warning: Setting Bios Control at 0xdc from 0xaa to 0x89 failed.
New value is 0xaa.
Warning: SPI Configuration Lockdown activated.
FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
FREG2: Warning: Management Engine region (0x00003000-0x007fffff) is locked.
Not all flash regions are freely accessible by flashrom. This is most likely
due to an active ME. Please see https://flashrom.org/ME for details.
Writes have been disabled for safety reasons. You can enforce write
support with the ich_spi_force programmer option, but you will most likely
harm your hardware! If you force flashrom you will get no support if
something breaks. On a few mainboards it is possible to enable write
access by setting a jumper (see its documentation or the board itself).
Enabling hardware sequencing because some important opcode is locked.
PROBLEMS, continuing anyway
Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000.
Reading flash... Transaction error between offset 0x00003000 and 0x0000303f (= 0x00003000 + 63)!
Read operation failed!
FAILED.
flashrom-v1.0.1 # ./flashrom -p internal -V -r test.out
flashrom v1.0.1 on Linux 4.4.0-142-generic (x86_64)
flashrom is free software, get the source code at https://flashrom.org
flashrom was built with libpci 3.2.1, GCC 4.8.4, little endian
Command line (5 args): ./flashrom -p internal -V -r test.out
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Initializing internal programmer
No coreboot table found.
Using Internal DMI decoder.
DMI string chassis-type: "Desktop"
DMI string system-manufacturer: "FUJITSU"
DMI string system-product-name: " "
DMI string system-version: " "
DMI string baseboard-manufacturer: "FUJITSU"
DMI string baseboard-product-name: "D3401-H2"
DMI string baseboard-version: "S26361-D3401-H2 "
Found chipset "Intel B150" with PCI ID 8086:a148.
This chipset is marked as untested. If you are using an up-to-date version
of flashrom *and* were (not) able to successfully update your firmware with it,
then please email a report to flashrom(a)flashrom.org including a verbose (-V) log.
Thank you!
Enabling flash write... BIOS_SPI_BC = 0xaaa: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x0 (SPI)
Top Swap: not enabled
SPI Read Configuration: prefetching enabled, caching enabled,
BIOS_CNTL = 0xaa: BIOS Lock Enable: enabled, BIOS Write Enable: disabled
Warning: BIOS region SMM protection is enabled!
Warning: Setting Bios Control at 0xdc from 0xaa to 0x89 failed.
New value is 0xaa.
SPIBAR = 0x00007fccfaa47000 (phys = 0xfe010000)
0x04: 0xe800 (HSFS)
HSFS: FDONE=0, FCERR=0, AEL=0, SCIP=0, PRR34_LOCKDN=0, WRSDIS=1, FDOPSS=1, FDV=1, FLOCKDN=1
Warning: SPI Configuration Lockdown activated.
Reading OPCODES... done
0x06: 0x3f00 (HSFC)
HSFC: FGO=0, HSFC=0, WET=0, FDBC=63, SME=0
0x0c: 0x00000000 (DLOCK)
DLOCK: BMWAG_LOCKDN=0, BMRAG_LOCKDN=0, SBMWAG_LOCKDN=0, SBMRAG_LOCKDN=0,
PR0_LOCKDN=0, PR1_LOCKDN=0, PR2_LOCKDN=0, PR3_LOCKDN=0, PR4_LOCKDN=0,
SSEQ_LOCKDN=0
0x50: 0x00004acb (FRAP)
BMWAG 0x00, BMRAG 0x00, BRWA 0x4a, BRRA 0xcb
0x54: 0x00000000 FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
0x58: 0x0fff0800 FREG1: BIOS region (0x00800000-0x00ffffff) is read-write.
0x5C: 0x07ff0003 FREG2: Warning: Management Engine region (0x00003000-0x007fffff) is locked.
0x60: 0x00020001 FREG3: Gigabit Ethernet region (0x00001000-0x00002fff) is read-write.
Not all flash regions are freely accessible by flashrom. This is most likely
due to an active ME. Please see https://flashrom.org/ME for details.
Writes have been disabled for safety reasons. You can enforce write
support with the ich_spi_force programmer option, but you will most likely
harm your hardware! If you force flashrom you will get no support if
something breaks. On a few mainboards it is possible to enable write
access by setting a jumper (see its documentation or the board itself).
0xa0: 0x80 (SSFS)
SSFS: SCIP=0, FDONE=0, FCERR=0, AEL=0
0xa1: 0xfe0000 (SSFC)
SSFC: SCGO=0, ACS=0, SPOP=0, COP=0, DBC=0, SME=0, SCF=6
0xa4: 0x0000 (PREOP)
0xa6: 0x0000 (OPTYPE)
0xa8: 0x00000000 (OPMENU)
0xac: 0x00000000 (OPMENU+4)
Enabling hardware sequencing because some important opcode is locked.
PROBLEMS, continuing anyway
The following protocols are supported: Parallel, LPC, FWH, Programmer-specific.
Probing for Programmer Opaque flash chip, 0 kB: Hardware sequencing reports 1 attached SPI flash chip with a density of 16384 kB.
Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000.
Probing for AMD Am29F010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F010A/B, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F002(N)BB, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F002(N)BT, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F016D, 2048 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F040, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F040B, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F080, 1024 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F080B, 1024 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV001BB, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV001BT, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV002BB, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV002BT, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV004BB, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV004BT, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV008BB, 1024 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV008BT, 1024 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV040B, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV081B, 1024 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMIC A29002B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMIC A29002T, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMIC A29040B, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT29C512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT29C010A, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT29C020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT29C040A, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49BV512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49F002(N), 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49F002(N)T, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49(H)F010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49F020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49F040, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49F080, 1024 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49F080T, 1024 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Catalyst CAT28F512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Bright BM29F040, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for ESMT F49B002UA, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Eon EN29F010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Eon EN29F002(A)(N)B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Eon EN29F002(A)(N)T, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Eon EN29LV040(A), 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Eon EN29LV640B, 8192 kB: probe_en29lv640b: id1 0x0000, id2 0x0000
Probing for Eon EN29GL064(A)B, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Eon EN29GL064(A)T, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Eon EN29GL064H/L, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Eon EN29GL128, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Fujitsu MBM29F004BC, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Fujitsu MBM29F004TC, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Fujitsu MBM29F400BC, 512 kB: probe_jedec_common: id1 0x45, id2 0x89, id1 is normal flash content, id2 is normal flash content
Probing for Fujitsu MBM29F400TC, 512 kB: probe_jedec_common: id1 0x45, id2 0x89, id1 is normal flash content, id2 is normal flash content
Probing for Fujitsu MBM29LV160BE, 2048 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Fujitsu MBM29LV160TE, 2048 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Hyundai HY29F002T, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Hyundai HY29F002B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Hyundai HY29F040A, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Intel 28F001BN/BX-B, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Intel 28F001BN/BX-T, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Intel 28F002BC/BL/BV/BX-T, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Intel 28F008S3/S5/SC, 512 kB: probe_82802ab: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Intel 28F004B5/BE/BV/BX-B, 512 kB: probe_82802ab: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Intel 28F004B5/BE/BV/BX-T, 512 kB: probe_82802ab: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Intel 28F400BV/BX/CE/CV-B, 512 kB: probe_82802ab: id1 0x45, id2 0x89, id1 is normal flash content, id2 is normal flash content
Probing for Intel 28F400BV/BX/CE/CV-T, 512 kB: probe_82802ab: id1 0x45, id2 0x89, id1 is normal flash content, id2 is normal flash content
Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ISSI IS29GL064B, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for ISSI IS29GL064T, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for ISSI IS29GL064H/L, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for ISSI IS29GL128H/L, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Macronix MX29F001B, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX29F001T, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX29F002(N)B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX29F002(N)T, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX29F022(N)B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX29F022(N)T, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX29F040, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX29GL320EB, 4096 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Macronix MX29GL320ET, 4096 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Macronix MX29GL320EH/L, 4096 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Macronix MX29GL640EB, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Macronix MX29GL640ET, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Macronix MX29GL640EH/L, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Macronix MX29GL128F, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Macronix MX29LV040, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for MoselVitelic V29C51000B, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for MoselVitelic V29C51000T, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for MoselVitelic V29C51400B, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for MoselVitelic V29C51400T, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for MoselVitelic V29LC51000, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for MoselVitelic V29LC51001, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for MoselVitelic V29LC51002, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm29F002T, 256 kB: Chip lacks correct probe timing information, using default 10ms/40us. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm29F002B, 256 kB: Chip lacks correct probe timing information, using default 10ms/40us. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm39LV010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm39LV020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm39LV040, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm39LV512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Sharp LH28F008BJT-BTLZ1, 1024 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST28SF040A, 512 kB: probe_82802ab: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for SST SST29EE010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST29LE010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST29EE020A, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST29LE020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST39SF512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST39SF010A, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST39SF020A, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST39SF040, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for SST SST39VF512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST39VF010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST39VF020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST39VF040, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for SST SST39VF080, 1024 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10ms/40us. probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M29F002B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M29F002T/NT, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M29F040B, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for ST M29F400BB, 512 kB: probe_jedec_common: id1 0x45, id2 0x89, id1 is normal flash content, id2 is normal flash content
Probing for ST M29F400BT, 512 kB: probe_jedec_common: id1 0x45, id2 0x89, id1 is normal flash content, id2 is normal flash content
Probing for ST M29W010B, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M29W040B, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for ST M29W512B, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50LPW080, 1024 kB: probe_82802ab: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SyncMOS/MoselVitelic {F,S,V}29C51001B, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SyncMOS/MoselVitelic {F,S,V}29C51001T, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SyncMOS/MoselVitelic {F,S,V}29C51002B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SyncMOS/MoselVitelic {F,S,V}29C51004B, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for SyncMOS/MoselVitelic {F,S,V}29C51004T, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for SyncMOS/MoselVitelic {S,V}29C31004B, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for SyncMOS/MoselVitelic {S,V}29C31004T, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for TI TMS29F002RB, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for TI TMS29F002RT, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W29C512A/W29EE512, 64 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012-old, 128 kB: Old Winbond W29* probe method disabled because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29C010(M)/W29C011A/W29EE011/W29EE012-old' if you have a board with such a chip.
Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W29C020(C)/W29C022, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W29C040/P, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W29GL032CB, 4096 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Winbond W29GL032CT, 4096 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Winbond W29GL032CH/L, 4096 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Winbond W29GL064CB, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Winbond W29GL064CT, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Winbond W29GL064CH/L, 8192 kB: probe_jedec_29gl: man_id 0x00, dev_id 0x000000, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Winbond W29GL128C, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash content, dev_id seems to be normal flash content
Probing for Winbond W39F010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39L010, 128 kB: probe_jedec_common: id1 0xeb, id2 0x2e, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39L020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39L040, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W49F002U/N, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W49F020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0x00, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0x45, id2 0xf8, id1 is normal flash content, id2 is normal flash content
Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific).
Reading flash... Reading 16777216 bytes starting at 0x000000.
Transaction error between offset 0x00003000 and 0x0000303f (= 0x00003000 + 63)!
HSFS: FDONE=1, FCERR=1, AEL=0, SCIP=0, PRR34_LOCKDN=0, WRSDIS=1, FDOPSS=1, FDV=1, FLOCKDN=1
HSFC: FGO=0, HSFC=0, WET=0, FDBC=63, SME=0
Read operation failed!
FAILED.
Restoring PCI config space for 00:1f:5 reg 0xdc
Hi,
Flashrom can't read my bios. So, I transmit the log file.
Nota :
I build myself flashrom and its dependencies from git repositories.
I hope this log file can help you.
Sincerely yours
Philippe
Hey, found your site while researching programming EC chips. Brief background: I have an old 2013 Alienware m17xr4 laptop. Was upgrading RAM/GPU/Display/SSDs mostly just for fun. In the process of adjusting bios, the computer failed to post. Attempted a blind flash which failed and left he laptop totally unresponsive.
Using a CH341A Hardware programmer with cable clip, I have been able to repair the BIOS. But the computer remains unresponsive leading me to believe the EC chip is also corrupted. I have a viable .bin to use with the EC chip, but I cannot seem to make the upload stick. I can clip and detect the EC chip (which appears wiped). I can program with my .bin. But then verification fails and it still looks like the chip is wiped.
Appreciate any advice. I don’t have the expertise to solder/desolder the chip, and I know a new motherboard may be in my future. But is there any other last ditch effort I should try with the programmer?
Thanks,
Zac
Sent from my iPad
Best Regards,
Allen Analian | President & Senior Electrical Engineer
Allen Productions Inc. / Engineering
1200 E Mission Blvd
Pomona, CA 91766
Website: http://www.allen.dj
Mobile: (562) 242-8479 - Available 24/7/365 (Emergencies Only)
*CONFIDENTIALITY NOTICE:*
This transmission may be privileged and may contain confidential
information intended only for the recipient(s) named above. Any other
distribution, re-transmission, copying or disclosure of this message is
strictly prohibited. If you have received this transmission in error,
please notify me immediately by telephone or return email, and delete this
message from your servers and local system.
---------- Forwarded message ---------
From: Allen <allen(a)allen.dj>
Date: Tue, Apr 9, 2019 at 12:46 AM
Subject: Re: confirm a56f2da945a80ad7b5155fd90206ef7a9609ae37
To: <flashrom-confirm+a56f2da945a80ad7b5155fd90206ef7a9609ae37(a)flashrom.org>
Flashrom works with Alienware Aurora R4 motherboard, with winbond ic:
W25Q64.V
Had a successful flash using rpi environment! The flash image was A11.bin -
latest version
Best Regards,
Allen Analian | President & Senior Electrical Engineer
Allen Productions Inc. / Engineering
1200 E Mission Blvd
Pomona, CA 91766
Website: http://www.allen.dj
Mobile: (562) 242-8479 - Available 24/7/365 (Emergencies Only)
*CONFIDENTIALITY NOTICE:*
This transmission may be privileged and may contain confidential
information intended only for the recipient(s) named above. Any other
distribution, re-transmission, copying or disclosure of this message is
strictly prohibited. If you have received this transmission in error,
please notify me immediately by telephone or return email, and delete this
message from your servers and local system.
On Tue, Apr 9, 2019 at 12:41 AM <
flashrom-confirm+a56f2da945a80ad7b5155fd90206ef7a9609ae37(a)flashrom.org>
wrote:
> Email Address Registration Confirmation
>
> Hello, this is the GNU Mailman server at flashrom.org.
>
> We have received a registration request for the email address
>
> allen(a)allen.dj
>
> Before you can start using GNU Mailman at this site, you must first confirm
> that this is your email address. You can do this by replying to this
> message,
> keeping the Subject header intact.
>
> If you do not wish to register this email address, simply disregard this
> message. If you think you are being maliciously subscribed to the list, or
> have any other questions, you may contact
>
> flashrom-owner(a)flashrom.org
>
Hi all,
I'm trying to dump a chip using the following command:
sudo flashrom -p ft2232_spi:type=232H,port=A,divisor=16 -r dump.rom -V
For some reason I'm getting an error. Can anybody help me?
"Initializing ft2232_spi programmer
Error: Invalid device type specified.
Unhandled programmer parameters: port=A,divisor=16
Error: Programmer initialization failed."
I also tried: sudo flashrom -p ft2232_spi:type=232H -r dump.rom -V
got the same error.
help :)
Thanks!
Dan
Hello Dominique,
you should always keep the mailing list in the loop. This way you
wouldn't rely on a single person giving the answers :)
On 05.04.19 22:35, Dominique Wille wrote:
> What is strange is we can flash from DOS with the oem flashing software
> without touching BIOS.
> So we guess there is maybe something missing in flashrom ?
Possible, but not necessarily. Flashrom is a simple tool to write
data to a flash chip. It doesn't care about the contents, just that
they are written correctly.
Updating the firmware of a modern mainboard, however, is a complex
process that may involve more than just writing data to the flash.
There are roughly three ways how the update process of that DOS tool
might look like:
a) The tool "asks" the firmware to allow write access to the
flash chip (then does what flashrom would do).
- This is rather old school, but who knows? *shrug*
b) The tool hands the data over to a program running in the firmware
(usually involves SMM; that's also where the write protection is
implemented).
c) The tool writes the data to a specific memory location, and the
update is done during the next reboot/resume (when the firmware
is the only process running on the computer).
( d) A combination of b) and c) )
Only for case a), flashrom would be the correct program to use. But
that would still need a piece of code to talk to the running firmware
(what we call a board-enable).
I guess the best option would be to talk to the manufacturer of your
devices. And there is also LVFS [1]. The people there might even know
already how it works for your device.
Nico
[1] https://fwupd.org/
Hello I have a hp dv6z-6c00 laptop and flashed bios now it won't turn on
and can't do emergency recover I have a ardino uno and use blaster I was
wondering if u could help me fix it I really need some help I'm good at
soldering so also know some what how to hook it up just need some help
