Hi all,
I would like to see the following feature added to flashrom:
https://github.com/flashrom/flashrom/issues/185
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.
Hi, I'm attempting to install libreboot on my thinkpad x200 (soic16) with a green ch341a programmer. The reading of the flash chip works fine, but when attempting to write to the flash chip, it fails and spits out these errors: https://pastebin.com/G17JWGfQ
Hoping for any help on what's going wrong. I've checked the connections are right.
Thanks in advance!
Any reason for this? Any guidance will be greatly appreciated.
On Fri, May 21, 2021 at 4:33 PM Hermann Thomas A. Calero <
hermanncalero(a)gmail.com> wrote:
> Hello,
>
> I tried to change the flash chip of my old Toshiba satellite pro a50 a
> series with previous bios chip Winbond 25Q64CVSIG with a new Winbond
> 25Q64FWSIG and i am getting the error "No usable erase functions left.
> FAILED!
> 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!"
>
> Error screenshot here <https://prnt.sc/138oacn>and below.
>
> [image: image.png]
> Hope you can enlighten me on this as i have used the latest flashrom
> version. Thank you!
>
>
Am 27.05.21 um 11:22 schrieb Urja Rannikko:
>>> Currently, on libera there are 46 people and on OFTC 2 people (me included).
>>>
>>> So I would say let's move to libera.
>> Agreed. Let’s do what most members in #coreboot users already did.
> +1
>
> I know I'm not a regular contributor or anything, but fwiw currently
> the only channels keeping me connected to freenode are #coreboot and
> #flashrom (I assume flashrom will just tag along where coreboot goes),
> so .. let's go, we've watched this long enough.
The shipped flashrom binaries, the man page and the README mention IRC
directly.
I think we should start with pointing users to a flashrom.org web page
instead of mentioning IRC in case another move (Matrix, IRC, Discord,
whatever) is needed or desired. Once such a patch is committed, we would
have to get all the distribution packages updated to point to the new
location. Doable, but it's a lot of work.
Regards,
Carl-Daniel
---------- Forwarded message ---------
From: Hermann Thomas A. Calero <hermanncalero(a)gmail.com>
Date: Fri, May 21, 2021 at 4:33 PM
Subject: Your flash chip is in an unknown state
To: <flashrom(a)flashrom.org>
Hello,
I tried to change the flash chip of my old Toshiba satellite pro a50 a
series with previous bios chip Winbond 25Q64CVSIG with a new Winbond
25Q64FWSIG and i am getting the error "No usable erase functions left.
FAILED!
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!"
Error screenshot here <https://prnt.sc/138oacn>and below.
[image: image.png]
Hope you can enlighten me on this as i have used the latest flashrom
version. Thank you!
"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."
Thanks
--
*Conhecimento não tem dono. É patrimônio de toda a humanidade. Assim como o
GNU/Linux.*
“*Os idiotas vão tomar conta do mundo; não pela capacidade, mas pela
quantidade. Eles são muitos*”. *Nelson Rodrigues*
Hi, hoping to get some help on this as I believe the BIOS is the issue on this box.
I am able to see and pull down a copy of the existing code but I cannot write back as it says it is unable to unset the lock bits. I see in the documentation for the chip that it expects manipulation of the CS pin which I do not know if that is occurring but it is wired (when not wired it will not detect the chip).
Chip is AT25DF641-S3H
Using a Raspberry Pi (Original) with a stand-alone DC power supply to power the chip, requiring 3.5V or is not seen.
Last portion of the log:
Found Atmel flash chip "AT25DF641(A)" (8192 kB, SPI).
Ignoring security lockdown (if present)
Some block protection in effect, disabling...
Need to disable the register lock first... Unsetting lock bit(s) failed.
Reading old flash chip contents... done.
Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x00000fff: 0xb4
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Trying erase function 1... 0x000000-0x007fff:S, 0x008000-0x00ffff:S, 0x010000-0x017fff:EFAILED at 0x00010000! Expected=0xff, Found=0x20, failed byte count from 0x00010000-0x00017fff: 0xa5
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Trying erase function 2... 0x000000-0x00ffff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x0000ffff: 0xb6
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Trying erase function 3... 0x000000-0x7fffff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x007fffff: 0x3f606d
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Trying erase function 4... 0x000000-0x7fffff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x007fffff: 0x3f2b1c
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Trying erase function 5... not defined. No usable erase functions left.
FAILED!
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!
Thank you,
Eric
---------- Forwarded message ---------
From: Tim Tech <agitimtim(a)gmail.com>
Date: Thu, May 20, 2021 at 12:07 PM
Subject: Re: [flashrom] Dell 3100 Chromebook
To: Mike Banon <mikebdp2(a)gmail.com>
The flashing setup seems to work fine with any other chip. The chip in
question is a Winbond 25Q128FWPF. This chip is on the Dell 3100 and HP 11
G6 EE chromebooks and is the only chip we've had an issue with so far. I
attached an image of the chip itself, in case there is any other info on
there you need. I don't see this chip on the supported hardware, so maybe
it is not yet supported?
Thank you for any help
Tim
On Mon, May 17, 2021 at 1:17 PM Mike Banon <mikebdp2(a)gmail.com> wrote:
> Are you doing the ISP (In-System Programming) ? Maybe there are
> problems with the reliability of your flashing setup (i.e. too long
> wires between a programmer and test clip)
>
> On Thu, May 13, 2021 at 2:39 AM Tim Tech <agitimtim(a)gmail.com> wrote:
> >
> > Are you able to help with the following issue? Thank you
> >
> > Calibrating delay loop... OK.
> > Found Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB,
> SPI) on ch341a_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.
> > _______________________________________________
> > flashrom mailing list -- flashrom(a)flashrom.org
> > To unsubscribe send an email to flashrom-leave(a)flashrom.org
>
>
>
> --
> Best regards, Mike Banon
> Open Source Community Manager of 3mdeb - https://3mdeb.com/
>