Hi there Angel, thank you for your reply and clarification! Please
tell, is this command
> sudo flashrom -p internal:laptop=force_I_want_a_brick,amd_imc_force=yes -r
> ./build/coreflop.rom
- dangerous to run, even if it's only trying to read (-r) and not
write? (aside from "irritating the EC" po
Please describe your flashing setup in more details. We don't even
know which programmer you're trying to use, and in what mode?
(In-System Programming with a test clip?)
On Mon, Jan 24, 2022 at 12:55 AM John Evacristo wrote:
>
> flashrom v1.2 on Linux 5.11.0-27-generic (x86_64)
> flashrom is fre
Hello
I tried today to back up my actual bios and got a result as you can see
below:
tianlou@avocette:~$ sudo flashrom --programmer internal --read bios.backup
flashrom v1.2 on Linux 5.10.0-11-amd64 (x86_64)
flashrom is free software, get the source code at https://flashrom.org
Using clock_gettim
1) Try the shorter cables between a test clip and a programmer. See my
notes here at
http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate#Standard_SOIC8_clip
2) Make sure that your ch341a programmer is good enough. I had to
repair a couple of dead-on-arrival ch341a:
https://www
Hi Mike,
On 29.01.22 15:50, Mike Banon wrote:
> Hi there Angel, thank you for your reply and clarification! Please
> tell, is this command
>
>> sudo flashrom -p internal:laptop=force_I_want_a_brick,amd_imc_force=yes -r
>> ./build/coreflop.rom
>
> - dangerous to run, even if it's only trying to re