PCENGINES APU[1-7] Coreboot SeaBIOS Open Source Firmware

[iam]

What's APU[5-6]?

[marcelmah]

What's APU[5-6]?

I'm wondering the same...

[katamadone [CH]]

http://www.pcengines.info/forums/?page=post&id=7D919FB8-C4BB-4C33-B47B-F8F53E01600D&fid=DF5ACB70-99C4-4C61-AFA6-4C0E0DB05B2A

[pmhausen]

Has anyone successfully flashed 4.13.0.1?

Action:

Code: [Select]

root@opnsense:/tmp # flashrom -p internal -w apu4_v4.13.0.1.rom
flashrom v1.2 on FreeBSD 12.1-RELEASE-p11-HBSD (amd64)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 4, resolution: 2ns).
coreboot table found at 0xcfec2000.
Found chipset "AMD FCH".
Enabling flash write... OK.
Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) mapped at physical address 0x00000000ff800000.
Reading old flash chip contents... done.
Erasing and writing flash chip...
Warning: Chip content is identical to the requested image.
Erase/write done.
Result after reboot in screenshot.

apu4_v4.12.0.6.rom and apu4_v4.13.0.1.rom do have different sha256 checksums.

Puzzled ...
Patrick

[iam]

Yes a APU1 and a APU2.

[miroco]

I'm on the v4.13.01, but I have an APU2C4. The upgrade was uneventful.

Did you perform a cold boot after the firmware upgrade?

The fact that two dissimilar files have different checksums is of cause expected.

"Warning: Chip content is identical to the requested image."

It's as if you ran the same upgrade twice.

miroco

[iam]

No I've performed a normal reboot only. And I haven't observed such message. I can't remember at least.

[pmhausen]

Did you perform a cold boot after the firmware upgrade?

Yes.

"Warning: Chip content is identical to the requested image."
It's as if you ran the same upgrade twice.

Yes, I did, because the first attempt did not succeed. Now after two failures I am asking here

This is part of the output of kenv:

Code: [Select]

smbios.bios.reldate="10/29/2020"
smbios.bios.vendor="coreboot"
smbios.bios.version="v4.12.0.6"

So flashed the supposedly 4.13.0.1 file, system reports it was 4.12.0.6 ...

[tillsense]

@all

v4.13.0.2 was released.

https://pcengines.github.io/firmware/2020/12/30/PC-Engines-Firmware-v4-13-0-2.html

https://pcengines.github.io/#mr-42

Please read the announcements.
(small tip: the serial number of the apu1 is displayed again)


cheers
till

[mayo]

Sorry tillsense, what do you mean with "read the announcements"?
I've updated as usual, is there something that I have to do from now?
Thank you and sorry again for the dummie question.
Mayo

@all

v4.13.0.2 was released.

https://pcengines.github.io/firmware/2020/12/30/PC-Engines-Firmware-v4-13-0-2.html

https://pcengines.github.io/#mr-42

Please read the announcements.
(small tip: the serial number of the apu1 is displayed again)


cheers
till

[tillsense]

Sorry tillsense, what do you mean with "read the announcements"?
I've updated as usual, is there something that I have to do from now?
Thank you and sorry again for the dummie question.
Mayo

Hi Mayo,

this is a hint that with every new firmware announcement also the further information by the manufacturer about this in the links are read and considered.

cheers
till

[Ben.]

APU1 does not support APU Core Performance Boost, is that correct?

Thanks.

[mayo]

Thank you so much!

Sorry tillsense, what do you mean with "read the announcements"?
I've updated as usual, is there something that I have to do from now?
Thank you and sorry again for the dummie question.
Mayo

Hi Mayo,

this is a hint that with every new firmware announcement also the further information by the manufacturer about this in the links are read and considered.

cheers
till

[hushcoden]

APU1 does not support APU Core Performance Boost, is that correct?

Thanks.

That's correct.

[tillsense]

v4.13.0.3 was released.

https://pcengines.github.io/firmware/2021/02/02/PC-Engines-Firmware-v4-13-0-3.html

https://pcengines.github.io/#mr-43

Please read the announcements.


cheers
till