> Note: hardware status register protection is enabled. The chip's WP# pin
must be set to an inactive voltage level to be able to change the WP
settings.
You need to disable hardware write protect:
https://chromium.googlesource.com/chromiumos/docs/+/master/write_protection.md
On Tue, Aug 8, 2023
ardware tech with 40 yrs experience, so no issue. Just
> unfamiliar with ChromeOS.
> Need to remove the board. But it's the only IT platform I have.
> Learned ChromeOS, Time to go back to linux.
>
>
> On Thu, 10 Aug 2023 at 13:01, Peter Marheine
> wrote:
>
>>
For completeness, the proposed change is at
https://review.coreboot.org/c/flashrom/+/81545
I've tested it myself (and added a unit test) and am fairly confident
everything works well, but if anybody has a "weirder" machine than an x86
PC to test on, additional coverage would be helpful.
On Fri, A
I found this patch by searching gerrit for the part number:
https://review.coreboot.org/c/flashrom/+/58025
On Tue, Apr 30, 2024 at 6:54 PM Munduru, Avinash via flashrom <
flashrom@flashrom.org> wrote:
> [AMD Official Use Only - General]
>
> + attaching the output log
>
> -
I would expect this system should already work, since ChromeOS uses
flashrom itself. Have you tried it? If it failed, what did it say?
On Tue, Jul 2, 2024 at 11:02 PM Jason Whitaker
wrote:
> Unsure of board URL, this is an Asus Chromebox for Google Meet:
>
> https://www.asus.com/displays-desktop
Hi everyone,
As was described in the release notes for version 1.4, I plan to remove the
Makefile soon and make Meson the only supported buildsystem for flashrom:
the proposed change is https://review.coreboot.org/c/flashrom/+/83673
If you haven't tried using meson before, now would be a good tim
Are you able to share a core dump with us to be able to see where it's
crashing? It looks like if you do `ulimit -c unlimited` in your shell
before running flashrom, you should get a core dump in `/cores/core.PID`
(where PID is the PID of the flashrom process) when it crashes. If you can
share that
You misspelled the chip name in the command to write. Your log shows you
correctly said "MT25QL128" when reading the chip initially (which worked),
but then wrote "MT25Q128" (missing the 'L') in the command to write.
On Sun, Jan 19, 2025 at 11:41 PM Manuel del Rey Carral <
manuel.delreycar...@gmai
It looks to me like the library only looks for up to two matches because it
returns an error if there's more than one match. I agree that it would be
good to make it able to report which chips matched (making
flashrom_flash_probe() suitable for CLI use) in addition to returning an
error, but the AP
That's probably because you have hardware that's known not to be supported
currently: https://flashrom.org/release_notes/v_1_5.html#known-issues
On Sat, Jan 4, 2025 at 12:13 AM Markus Rudolf via flashrom <
flashrom@flashrom.org> wrote:
> Hi,
>
> I have an ASUS PRIME X370-A and wanted to make a ra
What version of flashrom do you have? It looks like this might be the bug
that was introduced in 1.5.0 and fixed in 1.5.1.
On Fri, Dec 13, 2024 at 2:46 AM Chris Andrew wrote:
> Hi, guys.
>
> I'm trying to update the firmware for my Toshiba Swanky. I've done this
> several times before, without i
It looks to me like your communication isn't working at all, since your log
looks like you're reading all ones: "id1 0xff, id2 0xff, id1 parity
violation" appears for every chip that it's probing for, and the "parity
violation" part in particular looks like a communication error.
On Tue, Feb 18, 2
Hey Dmitry,
Thanks for the notes! There aren't many general-purpose users of the
library API so I'm sure it does currently have some rough edges- it's nice
to have somebody interested in improving it.
- how to obtain the list of programmers , as far as I see there is no any
> way to do it for no
13 matches
Mail list logo
