I have a PC Engines apu2d4 running NetBSD 8 (amd64), and would like to
update coreboot/etc. on it. I searched the list (perhaps not well) and
didn't find any reports of success, although I realize things are
generally expected to work so success might well go unreported.
I am using flashrom 1.1 as built from pkgsrc.
I was able to read the existing bios without issues as:
flashrom --programmer internal -r 20200301-readflash.rom
Before I try to write, I am wondering if anyone has successfully done an
apu2 bios update with flashrom under NetBSD 8 amd64?
(I have a debricking adaptor (spi1a) and will prepare a Linux flashing
image on USB before trying myself, whether I not a get a report of
success.)
Thanks,
Greg
By the way, once I discovered the basic path to install flashrom from git,
it works for me on Fedora too, in addition to Ubuntu.
One more question: Which flavor of Linux works the best for
flashrom/coreboot?
Clay
Hello. I would like an account on the wiki. I was going to edit the
flashrom setup page on the bbb, and reference libreboot's documentation
somewhere, as they have more up to date guides. Though flashrom's bbb
guide is a good place to have links, and an older reference.
Thanks,
-------------------------------------------------
This free account was provided by VFEmail.net - report spam to abuse(a)vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
Hi everybody,
I just pushed https://review.coreboot.org/c/flashrom/+/46875 for
review which replaces the make based build process with a call to
use meson instead. The rationale is that the project is too small to
warrant having two build systems.
There are likely reasons left to use make (e.g. build configurations
not yet supported by meson), so please consider this mainly an
opportunity to discuss where flashrom's build process is headed,
a warning that make _may_ be on the way out and a call to action
to improve the meson build system to the point where it covers all
build configurations.
Comments, thoughts, counter proposals, patches welcome!
Patrick
--
Google Germany GmbH, ABC-Str. 19, 20354 Hamburg
Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
After successfully reading from W25Q128FV, I wanted to write data
back. But I get the error "ERASE FAILED!". Is there something I can do
to make writing successful?
The chip is located on the mainboard of an HP Elitebook notebook. The
pins CS, DO, GND, VCC, CLK and DI are connected to a Raspberry Pi.
pi@raspberrypi:~ $ flashrom -c "W25Q128.V" -w
/home/pi/Desktop/bios.bin -VVV -p
linux_spi:dev=/dev/spidev0.0,spispeed=16000
flashrom on Linux 5.4.51+ (armv6l)
flashrom is free software, get the source code at https://flashrom.org
flashrom was built with libpci 3.5.2, GCC 8.2.0, little endian
Command line (7 args): flashrom -c W25Q128.V -w
/home/pi/Desktop/bios.bin -VVV -p
linux_spi:dev=/dev/spidev0.0,spispeed=16000
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Initializing linux_spi programmer
Using device /dev/spidev0.0
Using 16000 kHz clock
The following protocols are supported: SPI.
Probing for Winbond W25Q128.V, 16384 kB: programmer_map_flash_region:
mapping W25Q128.V from 0xff000000 to 0x00000000
RDID returned 0xef 0x40 0x18. probe_spi_rdid_generic: id1 0xef, id2 0x4018
Found Winbond flash chip "W25Q128.V" (16384 kB, SPI) on linux_spi.
Chip status register is 0xfc.
programmer_unmap_flash_region: unmapped 0x00000000
This chip may contain one-time programmable memory. flashrom cannot read
and may never be able to write it, hence it may not be able to completely
clone the contents of this chip (see man page for details).
programmer_map_flash_region: mapping W25Q128.V from 0xff000000 to 0x00000000
Some block protection in effect, disabling... Block protection could
not be disabled!
Chip status register is 0xfc.
Reading old flash chip contents... done.
Erasing and writing flash chip... Trying erase function 0...
0x000000-0x000fff:EFAILED at 0x00000000! Expected=0xff, Found=0x00,
failed byte count from 0x00000000-0x00000fff: 0xffc
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Trying erase function 1... 0x000000-0x007fff:EFAILED at 0x00000000!
Expected=0xff, Found=0x00, failed byte count from
0x00000000-0x00007fff: 0x8000
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Trying erase function 2... 0x000000-0x00ffff:EFAILED at 0x00000000!
Expected=0xff, Found=0x00, failed byte count from
0x00000000-0x0000ffff: 0x10000
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Trying erase function 3... 0x000000-0xffffff:EFAILED at 0x00000000!
Expected=0xff, Found=0x00, failed byte count from
0x00000000-0x00ffffff: 0xffffd5
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Trying erase function 4... 0x000000-0xffffff:EFAILED at 0x00000000!
Expected=0xff, Found=0x00, failed byte count from
0x00000000-0x00ffffff: 0xfffd3e
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!
programmer_unmap_flash_region: unmapped 0x00000000
sudo flashrom --programmer internal
flashrom v1.2 on Linux 5.8.0-23-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).
Found chipset "AMD FP4".
Enabling flash write... FCH device found but SMBus revision 0x61 does
not match known values.
Please report this to flashrom(a)flashrom.org and include this log and
the output of lspci -nnvx, thanks!.
Could not determine chipset generation.PROBLEMS, continuing anyway
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found
automatically.
please check
Hey Clay,
> On 14. Oct 2020, at 21:10, Clay Daniels <clay.daniels.jr(a)gmail.com> wrote:
>
> I think this patch may fix the same problem on my MSI X570 motherboard. I need some help in applying the patch. Although I installed Ubuntu when I got involved with Flashrom, etc., I am going to revert to trusty FreeBSD which has a user "port" to install flashrom, not as a binary large object (BLOB) but simply navigating to the port directory and doing "make install && make clean". Sometimes I see patches in the ports directory, but there is none in the current flashrom directory (yet). So I think I need to create a diff file from the text below named "patch-sb600spi.c", place it in the main /usr/ports/sysutils/flashrom directory, use "make makepatch", then "make install". I can use "make clean" afterwards if I like. Does this procedure sound like I'm on the right path? Any & all help appreciated
I’m not using BSD, maybe you need to add the patch to a Makefile or so.
In any case you need a newer git checkout, and you can simply build it anywhere you want for a test with the patch applied.
It sounds like you might find my YT channel helpful, for were I do all this OpenSource work:
https://www.youtube.com/watch?v=roSoKQWIJdE <https://www.youtube.com/watch?v=roSoKQWIJdE>
René
> Clay
>
>
> On Mon, Oct 12, 2020 at 1:26 AM Rene Rebe <rene(a)exactcode.com <mailto:rene@exactcode.com>> wrote:
> Added AMD Ryzen 3950x X570 and AMD Ryzen 4000 Mobile PCI revisions
> to AMD FP4 / AM4 sb600spi.c.
>
> Trying to use flashrom to downgrade my Asus WS X570 ACE bios to a
> previous, more stable and performant version I just got this output:
>
> flashrom -p internal
> flashrom v1.2 on Linux 5.8.13-dist (x86_64)
> flashrom is free software, get the source code at https://flashrom.org <https://flashrom.org/>
>
> 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.
>
> So I patched mine and a friends MSI Modern 14 Ryzen 4700 laptop
> revisions in and we could both read the BIOS and I also tested
> flashing the Asus WS X570 ACE succesfully.
>
> Signed-of-by: René Rebe <rene(a)exactcode.de <mailto:rene@exactcode.de>>
>
> diff --git a/sb600spi.c b/sb600spi.c
> index 5892d57..8a3c87d 100644
> --- a/sb600spi.c
> +++ b/sb600spi.c
> @@ -143,7 +143,7 @@ static int determine_generation(struct pci_dev *dev)
> if (rev == 0x4a) {
> amd_gen = CHIPSET_YANGTZE;
> msg_pdbg("Yangtze detected.\n");
> - } else if (rev == 0x4b) {
> + } else if (rev == 0x4b || rev == 0x51 || rev == 0x61) {
> amd_gen = CHIPSET_PROMONTORY;
> msg_pdbg("Promontory detected.\n");
> } else {
>
>
> --
> René Rebe, ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
> https://exactcode.com <https://exactcode.com/> | https://t2sde.org <https://t2sde.org/> | https://rene.rebe.de <https://rene.rebe.de/>
> _______________________________________________
> flashrom mailing list -- flashrom(a)flashrom.org <mailto:flashrom@flashrom.org>
> To unsubscribe send an email to flashrom-leave(a)flashrom.org <mailto:flashrom-leave@flashrom.org>
--
ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin, https://exactcode.comhttps://exactscan.com | https://ocrkit.com | https://t2sde.org | https://rene.rebe.de