I would like to see the following feature added to flashrom:
If someone implemented it, would the idea (at least) be accepted?
Is anyone interested in implementing it and claiming the $100 bounty?
Text of the issue, for people too lazy to click:
Some chips require certain bits (and similar features) be set before the hardware write-protect pins can be used. Flashrom doesn't currently support setting these bits, which makes it impossible to e.g hardware write-protect a BIOS chip after flashing Coreboot. I would like to see Flashrom add support for this.
Attached is a patch which was written by someone else (they can identify themselves if they like) to toggle the relevant bits for a particular flash chip, each time flashrom is run, and tell the user what's going on.
Your task, if you want to claim the bounty, is to:
1- Add some UI sugar so that the user can choose to set the appropriate bits (or not), and any other "features" needed to enable hardware write-protect, via the command line
2- Ensure the necessary bits and features can be set for a specified set of chips (see below), so Flashrom supports hardware write protect for at least all of the listed chips, and
3- Get your patch accepted and merged (it may be wise to first check with the maintainers that they are willing to add this feature) using Gerrit or the mailing list as per the official process
If $100 isn't enough to make this attractive, I am open to increasing the bounty. I am also happy to escrow it if need be. Payment will be in Bitcoin.
Received the following message: "Read is not working on this chip.
Aborting." while trying to read a "PM25LQ010"
Here is the exact programmer I have:
SOIC8 SOP8 Flash Chip/IC Test Clip with Adapters and CH341A 24 25 Series
EEPROM Flash BIOS USB Programmer
The PM25LQ010 I would like to read/write is on a Nvidia GTS 450 Video
Card. Flashrom Version 1.2 has detected my CH341A USB device but unable to
detect the Bios Chip. Included a picture of the physical Bios. If there
is more information I can provide please let me know.
Hello, I was wondering if anyone would mind helping me with an issue I'm running into with flashrom on a dell xps 15 9550. The dell has a 16 mbyte Winbond W25Q128.V bios chip on it. I'm using flash rom on a raspberry pi 4 but when I read this chip with a soic8 test clip, it seems to read successfully. However, when checking to see if the checksum of the reads I do are identical, they always come up as different values. The other two bios chips however read with the same checksums every time. I am attempting to use intel me cleaner to set the hap bit and disable intel me without repartitioning or cleaning anything on the chip as intel boot guard is enabled. ME Cleaner is able to read the file and say the hap bit has been successfully set. However, when writing the modified image, I get the error through flash rom verifying flash...failed, your flash chip is in an unknown state. The laptop will no longer boot and the power light comes on for a moment before turning on. I suspect either flash rom is not compatible with this chip or something about this chip prevents it from being read by flash rom. Using this guide: darajnish/dell5577medisable it seems as though a select few people have been able to set the hap bit by using the command soft-disable-only. Even when I try re-flashing the original read bios image however, the laptop still does not boot. I read somewhere that my chip has flash descriptors locked, but since other people have had success I'm not sure why I can't get it to work properly. Any advice would be much appreciated!
On Wed, 16 Aug 2017 at 22:02, David Hendricks <david.hendricks(a)gmail.com> wrote:
> The short answer is yes. Nico also briefly mentioned an idea on IRC to use a mechanism similar to flashrom_set_log_callback() to avoid complicating function signatures for the read, write, and verify functions.
Dragging up an email thread from a long time ago, apologies. We're
finally using libflashrom via fwupd "in production" so to speak. One
glaring problem is that the UI "freezes" when we're doing operations
with libflashrom, which we've worked around with just making the
progress bar spin up and down so at least it looks like the program
has not crashed. Of course, the correct thing to do is return the
progress information because, as David says, some flash chips take a
looong time to write.
I've attached a patch for some initial comments, if this looks
acceptable I can add some more callbacks in other flash
implementations (as at the moment I've only covered SPI stuff) but I
didn't want to spend time on a mega patch before I had some kind of
initial thumbs-up. Comments welcome. Thanks.
I successfully read/wrote a BIOS image file to a MSI Z390-A PRO (MS-7B98)
motherboard via both Linux and DOS builds of flashrom based on the master
branch on Jan. 1, 2021. Attached are reports/logs.
Also, I would like to report that the "buildbot archive" link for finding
DOS bulids of flashrom linked on https://flashrom.org/Downloads is not
working for me as I am not able to connect to that site (seems like
https://buildbot.flashrom.org/ is no longer online).
So I built for myself a copy of flashrom for DOS. After making some changes
to the code, I was able to cross-compile for DOS on Linux. I used pciutils
3.6.4, which did not require the patch to cross-compile the pciutils
library for DOS. I put my build steps as well as my tested PC findings at