Follow-up: we have now identified the unit from its underside label and attempted the public OEM H516 update. We need instructions for the ROM-layout warning before proceeding.
Exact machine:
- Beelink SER5 Pro, Ryzen 7 5800H
- Model code: SER5 PRO-E-16500EJ0W64PRO-DP/XB
- Serial: Y58004AG90536
- Exterior label ID: 9Y.2890830A20 (not a verified motherboard part number)
- Current BIOS: SER5H512, 09/06/2024; baseboard DMI reports AZW SER V2.0
- Proxmox/Linux; Secure Boot disabled during the attempt
Package tested: SER5H516_LK.zip from your public https://dr.bee-link.cn/?dir=uploads/SER/SER5-5850/BIOS directory (the revised package whose flash.nsh does not include /capsule).
- Archive SHA256: 43042f8c72018016e9beba2061962d54f7482baa459b6fcd4f2b6f8c1f3505c9
- SER5H516.bin SHA256: adcb54af080d09d66c3e3070507fa7cd988421d5d65b8e84cf05e737b45a5ecf
- Supplied AFU version: 5.16.05.0145
- Unmodified OEM command: AfuEfix64.efi SER5H516.bin /p /b /n /x /l /r
From the UEFI shell, the updater reported FFS checksums Pass and Check RomLayout Changed, then warned that the ROM file information does not match the system BIOS and that updating could destroy the system BIOS. It offered E (update entire BIOS region), A (no ROM update), or F (force the provided command). We selected A. It returned “4c - Error: ROM file information does not match system BIOS.” No erase/program step occurred, and the machine is running normally on H512. We also saved the original 16 MiB BIOS with the supplied AFU /O command.
For this exact unit and package:
- Is H516 the correct image, and is selecting E the intended/supported way to handle this H512-to-H516 layout change?
- Is an intermediate H515 update required, or should we use a different/corrected H516 package? Please provide the exact download and procedure if so.
- What recovery procedure is supported if the update fails to boot?
We saw your July response about H516’s “ROM Hole is redesigned” issue and the revised release. Our observed warning is the E/A/F layout-mismatch prompt described above; we do not want to assume that the H515-specific instruction to press E applies to H516.
The original question about validated 64 GB (2 × 32 GB) RAM support and compatible module part numbers also remains open. Thank you.