Hi !
I have a common question
[root@ipfire ~]# firmware-update update
Detected PC Engines apu2 running BIOS version 88a4f96
New firmware version available: v4.19.0.1
Why i have there such a number ?
Ciao Gerd
I haven’t got the faintest idea. I have not seen anything like that with the three updates that I have done with my apu4.
Mine is already at v4.19.0.1 but if I run the same command I get
firmware-update update
Detected PC Engines apu4 running BIOS version v4.19.0.1
We have v4.19.0.1 and this board is already on v4.19.0.1
No new firmware available. Aborting.
Do you get the same number if you run firmware-update info.
firmware-update info
Board : PC Engines apu4
HW Version : 1.0
Serial : 1550967
BIOS Version: v4.19.0.1 (01/31/2023)
What version number was the last update done with?
I found that bios number mentioned at the following URL.
https://bsd-hardware.info/?id=bios:coreboot-88a4f96-03-07-2016
The date for that version is 03/07/2016
The earliest version listed on the PC Engines website is v4.0.9 from 30/05/2017
1 Like
Board : PC Engines apu2
HW Version : 1.0
Serial : 123456789
BIOS Version: 88a4f96 (03/07/2016)
Then that bios version is the one from 2016.
1 Like
Can i flash the actual one ?
btw: serial is interesting… 
Ciao Gerd
I don’t know. That is a long delta between 2016 and 2023. As there is an apu2 update available, the answer would be expected to be yes but I would suggest that you contact the PC Engines or Dasharo people and ask the question about updating from that bios version, to get confirmation from the people who have created the bios updates.
1 Like
I asked pc engines support and he told me that i can flash newest FW Version to my board… but it fails
Flashing process is starting now...
PLEASE DO NOT TURN OFF THE SYSTEM WHILE FLASHING!
flashrom v1.2 on Linux 6.1.30-ipfire (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).
coreboot table found at 0xdffae000.
Found chipset "AMD FCH".
Enabling flash write... OK.
Error accessing GD25Q256D, 0x2000000 bytes at 0x00000000fe000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip GD25Q256D at 0x00000000fe000000.
Error accessing IS25LP256, 0x2000000 bytes at 0x00000000fe000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip IS25LP256 at 0x00000000fe000000.
Error accessing IS25WP256, 0x2000000 bytes at 0x00000000fe000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip IS25WP256 at 0x00000000fe000000.
Error accessing MX25L25635F/MX25L25645G, 0x2000000 bytes at 0x00000000fe000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip MX25L25635F/MX25L25645G at 0x00000000fe000000.
Error accessing MX25U25635F, 0x2000000 bytes at 0x00000000fe000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip MX25U25635F at 0x00000000fe000000.
Error accessing MX25U51245G, 0x4000000 bytes at 0x00000000fc000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip MX25U51245G at 0x00000000fc000000.
Error accessing MX66L51235F/MX25L51245G, 0x4000000 bytes at 0x00000000fc000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip MX66L51235F/MX25L51245G at 0x00000000fc000000.
Error accessing N25Q00A..1G, 0x8000000 bytes at 0x00000000f8000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip N25Q00A..1G at 0x00000000f8000000.
Error accessing N25Q00A..3G, 0x8000000 bytes at 0x00000000f8000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip N25Q00A..3G at 0x00000000f8000000.
Error accessing N25Q256..1E, 0x2000000 bytes at 0x00000000fe000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip N25Q256..1E at 0x00000000fe000000.
Error accessing N25Q256..3E, 0x2000000 bytes at 0x00000000fe000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip N25Q256..3E at 0x00000000fe000000.
Error accessing N25Q512..1G, 0x4000000 bytes at 0x00000000fc000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip N25Q512..1G at 0x00000000fc000000.
Error accessing N25Q512..3G, 0x4000000 bytes at 0x00000000fc000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip N25Q512..3G at 0x00000000fc000000.
Error accessing MT25QL01G, 0x8000000 bytes at 0x00000000f8000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip MT25QL01G at 0x00000000f8000000.
Error accessing MT25QU01G, 0x8000000 bytes at 0x00000000f8000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip MT25QU01G at 0x00000000f8000000.
Error accessing MT25QL02G, 0x10000000 bytes at 0x00000000f0000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip MT25QL02G at 0x00000000f0000000.
Error accessing MT25QU02G, 0x10000000 bytes at 0x00000000f0000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip MT25QU02G at 0x00000000f0000000.
Error accessing MT25QL256, 0x2000000 bytes at 0x00000000fe000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip MT25QL256 at 0x00000000fe000000.
Error accessing MT25QU256, 0x2000000 bytes at 0x00000000fe000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip MT25QU256 at 0x00000000fe000000.
Error accessing MT25QL512, 0x4000000 bytes at 0x00000000fc000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip MT25QL512 at 0x00000000fc000000.
Error accessing MT25QU512, 0x4000000 bytes at 0x00000000fc000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip MT25QU512 at 0x00000000fc000000.
Error accessing S25FL256S......0, 0x2000000 bytes at 0x00000000fe000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip S25FL256S......0 at 0x00000000fe000000.
Error accessing S25FL512S, 0x4000000 bytes at 0x00000000fc000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip S25FL512S at 0x00000000fc000000.
Error accessing W25Q256.V, 0x2000000 bytes at 0x00000000fe000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip W25Q256.V at 0x00000000fe000000.
Error accessing W25Q256JV_M, 0x2000000 bytes at 0x00000000fe000000
/dev/mem mmap failed: Operation not permitted
Could not map flash chip W25Q256JV_M at 0x00000000fe000000.
Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0x00000000ff800000.
This coreboot image (PC Engines:apu2) does not appear to
be correct for the detected mainboard (PC Engines:PCEngines apu2).
Aborting. You can override this with -p internal:boardmismatch=force.
Error: Flashing the firmware was not successful
Ciao Gerd
Hi @goerdi.
You can override this error with “-p internal:boardmismatch=force” parameter.
The command complete ist this:
flashrom -p internal:boardmismatch=force -w apu2_v4.19.0.1.rom
Try this and say us.
Regards.
1 Like
Hi bbitsch !
The output was from this tool
Ciao Gerd
Sorry, didn’t read the thread exactly. 
The problem are the different board names in the firmware. Therefore the suggestion of @roberto should work.
Bernhard
On very old apu2 boards you have to ignore the board mismatch once because the bios makers has changed the identification strings.
https://pcengines.github.io/apu2-documentation/firmware_flashing/
5 Likes
OK finally it worked…
Ciao Gerd
2 Likes