-
Notifications
You must be signed in to change notification settings - Fork 427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flashrom not work hp 8200 sff #230
Comments
Same problem me too |
there was a option no-verify-all or something.. but its the hp bios having hidden write protection u can come to the coreboot discord and visit us |
Yeah, ended up flashing with Ch341a everything worked
Il dom 23 apr 2023, 03:34 kocoman1 ***@***.***> ha scritto:
… there was a option no-verify-all or something.. but its the hp bios having
hidden write protection
—
Reply to this email directly, view it on GitHub
<#230 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABBV6QM3MN6QUL4ADZSW7LXCSBJ5ANCNFSM5HBNTTWQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@tizbac how did you get the ch341a to work? I'm trying without the 3.3>1.8v stepdown, but nothing seems to work. I get, Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). |
Hi i have a hp 8200 sff with hp bios. i am trying to flash coreboot on it but it fails with this log. any ideas? thanks
flashrom -p internal -c "MX25L6406E/MX25L6408E" --ifd -i bios -w build/coreboot.rom
flashrom v1.2 on Linux 5.13.0-19-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).
No DMI table found.
Found chipset "Intel Q67".
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@flashrom.org including a verbose (-V) log.
Thank you!
Enabling flash write... Warning: Setting Bios Control at 0xdc from 0x02 to 0x01 failed.
New value is 0x02.
SPI Configuration is locked down.
The Flash Descriptor Override Strap-Pin is set. Restrictions implied by
the Master Section of the flash descriptor are NOT in effect. Please note
that Protected Range (PR) restrictions still apply.
PR0: Warning: 0x007f0000-0x007fffff is read-only.
At least some flash regions are write protected. For write operations,
you should use a flash layout and include only writable regions. See
manpage for more details.
OK.
Found Macronix flash chip "MX25L6406E/MX25L6408E" (8192 kB, SPI) mapped at physical address 0x00000000ff800000.
Reading ich descriptor... done.
Peculiar firmware descriptor, assuming Ibex Peak compatibility.
Using region: "bios".
Reading old flash chip contents... done.
Erasing and writing flash chip... Transaction error!
spi_write_cmd failed during command execution at address 0x510000
Reading current flash chip contents... done. Looking for another erase function.
spi_write_cmd failed during command execution at address 0x510000
Reading current flash chip contents... done. Looking for another erase function.
spi_write_cmd failed during command execution at address 0x510000
Reading current flash chip contents... done. Looking for another erase function.
spi_simple_write_cmd failed during command execution
Reading current flash chip contents... done. Looking for another erase function.
spi_simple_write_cmd failed during command execution
Reading current flash chip contents... done. Looking for another erase function.
Looking for another erase function.
Looking for another erase function.
No usable erase functions left.
FAILED!
Uh oh. Erase/write failed. Checking if anything has changed.
Reading current flash chip contents... done.
Good, writing to the flash chip apparently didn't do anything.
This means we have to add special support for your board, programmer or flash
chip. Please report this on IRC at chat.freenode.net (channel #flashrom) or
mail flashrom@flashrom.org, thanks!
You may now reboot or simply leave the machine running.
The text was updated successfully, but these errors were encountered: