elly on Nostr: nprofile1q…385f4 nprofile1q…u08ps nprofile1q…mx4u4 nprofile1q…c24yc Seconding ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqk2pk25uqk7698nw6klprr73dr7s9fwhn8vugpcdxav9x20vpn26qc385f4 (nprofile…85f4) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqe95tvhl4h7tstxhfe9fe9kmgkphqdm79aw0rtasgqrr8gs9qqpjs4u08ps (nprofile…08ps) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqc3xpzthhtnnewsqnfq94ayle2vxhda85x687xd49q6s2kkxf6g7q5mx4u4 (nprofile…x4u4) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqwlqn9lykk9w6drh3gu2gvm5rm6k2pwca7u6apsnrutzz2fgmavgsdc24yc (nprofile…24yc) Seconding flashprog.
It’s a fork of flashrom that’s maintained a lot better. Current maintainers of flashrom have no idea what they’re doing, resulting in failed flashes, bricked devices and weird errors all around.
I wanted to add support for flash chip on one of mainboards I was REing to port coreboot to, but had issues with flashrom detecting and flashing the chip reliably. I went on their IRC, waited 3 days and got no response. Then I applied the same patch to flashrom and it just worked.
Another example with FW I ported:
flashrom v1.4.0 on Linux 6.12.3-0-edge (x86_64)
flashrom is free software, get the source code at https://flashrom.org
coreboot table found at 0x7aa16000.
Found chipset "Intel Alder Lake-N".
Enabling flash write... Warning: Setting BIOS Control at 0xdc from 0x8b to 0x89 failed.
New value is 0x8b.
SPI Configuration is locked down.
FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-write.
FREG1: BIOS region (0x00600000-0x00ffffff) is read-write.
FREG2: Management Engine region (0x00001000-0x00413fff) is read-write.
OK.
Found Winbond flash chip "W25Q128.V" (16384 kB, Programmer-specific) on internal.
Reading old flash chip contents... done.
Erase/write done from 0 to ffffff
Verifying flash... FAILED at 0x001c504e! Expected=0xfb, Found=0xc0, failed byte count from 0x00000000-0x00ffffff: 0x465
Your flash chip is in an unknown state.
Get help on IRC (see https://www.flashrom.org/Contact) or mailflashrom@flashrom.org with the subject "FAILED: <your board name>"!-------------------------------------------------------------------------------
DO NOT REBOOT OR POWEROFF!
Then tried with flashprog:
flashprog v1.3 on Linux 6.12.3-0-edge (x86_64)
flashprog is free software, get the source code at https://flashprog.org
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
coreboot table found at 0x7aa16000.
Found chipset "Intel Alder Lake-N".
Enabling flash write... Warning: Setting BIOS Control at 0xdc from 0x8b to 0x89 failed.
New value is 0x8b.
SPI Configuration is locked down.
OK.
Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) on internal.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... VERIFIED.
It’s a fork of flashrom that’s maintained a lot better. Current maintainers of flashrom have no idea what they’re doing, resulting in failed flashes, bricked devices and weird errors all around.
I wanted to add support for flash chip on one of mainboards I was REing to port coreboot to, but had issues with flashrom detecting and flashing the chip reliably. I went on their IRC, waited 3 days and got no response. Then I applied the same patch to flashrom and it just worked.
Another example with FW I ported:
flashrom v1.4.0 on Linux 6.12.3-0-edge (x86_64)
flashrom is free software, get the source code at https://flashrom.org
coreboot table found at 0x7aa16000.
Found chipset "Intel Alder Lake-N".
Enabling flash write... Warning: Setting BIOS Control at 0xdc from 0x8b to 0x89 failed.
New value is 0x8b.
SPI Configuration is locked down.
FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-write.
FREG1: BIOS region (0x00600000-0x00ffffff) is read-write.
FREG2: Management Engine region (0x00001000-0x00413fff) is read-write.
OK.
Found Winbond flash chip "W25Q128.V" (16384 kB, Programmer-specific) on internal.
Reading old flash chip contents... done.
Erase/write done from 0 to ffffff
Verifying flash... FAILED at 0x001c504e! Expected=0xfb, Found=0xc0, failed byte count from 0x00000000-0x00ffffff: 0x465
Your flash chip is in an unknown state.
Get help on IRC (see https://www.flashrom.org/Contact) or mailflashrom@flashrom.org with the subject "FAILED: <your board name>"!-------------------------------------------------------------------------------
DO NOT REBOOT OR POWEROFF!
Then tried with flashprog:
flashprog v1.3 on Linux 6.12.3-0-edge (x86_64)
flashprog is free software, get the source code at https://flashprog.org
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
coreboot table found at 0x7aa16000.
Found chipset "Intel Alder Lake-N".
Enabling flash write... Warning: Setting BIOS Control at 0xdc from 0x8b to 0x89 failed.
New value is 0x8b.
SPI Configuration is locked down.
OK.
Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) on internal.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... VERIFIED.