under Linux : as root: flashrom -r bios-bak.romto all who bought this motherboard:
save BIOS settings with unstable CPU can corrupt BIOS, make a backup before doing experiments. BIOS chip is in socket.
there is no fresh file to restore BIOS out there.
hope this works for AMD, but at Intel system you can not get full flashable dump with this.under Linux : as root: flashrom -r bios-bak.rom
Decided not to wait....
Fire the one (the right one looking from the back)
![]()
3.64 MB file on MEGA
mega.nz
BIOS Date: 04/23/2020 10:19:02 Ver: T6U_3A25
Olympus Epyc W25Q256FV(OTP)@SOIC16 (right).BIN (1/1)
╔════════════════════════════════════════════════════════════════╗
║ AMD ║
╟───┬──────────┬──────────┬────────────┬───────┬──────────┬──────╢
║ # │ CPUID │ Revision │ Date │ Size │ Offset │ Last ║
╟───┼──────────┼──────────┼────────────┼───────┼──────────┼──────╢
║ 1 │ 00800F12 │ 08001230 │ 2018-08-04 │ 0xC80 │ 0x26FE00 │ No ║
╟───┼──────────┼──────────┼────────────┼───────┼──────────┼──────╢
║ 2 │ 00800F11 │ 08001129 │ 2017-07-14 │ 0xC80 │ 0x270B00 │ No ║
╚═══╧══════════╧══════════╧════════════╧═══════╧══════════╧══════╝
BIOS Date: 05/15/2018 16:09:29 Ver: T6U_3A15
Olympus Epyc W25Q256FV(OTP)@SOIC16 (left).BIN (1/1)
╔════════════════════════════════════════════════════════════════╗
║ AMD ║
╟───┬──────────┬──────────┬────────────┬───────┬──────────┬──────╢
║ # │ CPUID │ Revision │ Date │ Size │ Offset │ Last ║
╟───┼──────────┼──────────┼────────────┼───────┼──────────┼──────╢
║ 1 │ 00800F12 │ 08001227 │ 2018-02-09 │ 0xC80 │ 0x26FE00 │ No ║
╟───┼──────────┼──────────┼────────────┼───────┼──────────┼──────╢
║ 2 │ 00800F11 │ 08001129 │ 2017-07-14 │ 0xC80 │ 0x270B00 │ No ║
╚═══╧══════════╧══════════╧════════════╧═══════╧══════════╧══════╝
better is.Now dumping the BMC (?)
is this compatible?don't waste your time to get the orginal chip w25q256FV (EOL)
the replacement is w25q256JV
You mean only naples is supported? I'm too tired to dig into it.better is.
i guess they replaced the the BIOS with the initial Naples only before decommissioning...
My guess -Got the server with case. Tried to connect power to the power supply for testing by connecting the individual pins using connector like this (not these exact ones need to use connectors which are flat enough that the can fit next to each other) "https://www.reichelt.de/de/de/shop/...MI28vWxN_ekAMVj7CDBx27fT1vEAQYAiABEgKf6_D_BwE" The connectors need to be compressed a little bit using thongs to fit the quite thin Pins (the are designed for 0.8mm thickness pins, but psu pins are more like 0.3-0.4mm). I connected all three phases (only feed A not backup so 3* 2 Pins) of the power supply to a single phase plus the GND. However I can not get 12V output on the powersupply. There is something happening (Relais clicking) after plugging and unplugging and it is drawing some power and warming up slightly (ca. 45 Watts) but there is no 12V on the output. Anyone tried something similar or got the PSUs to power on?
My guess -
You might be on the right track, there's just more to do.
The 45w is probably ~30w for battery charging + other "always on" components.
You'll get more data after several hours of charging I think.
I think we'll have to figure out the data pins on the PSU connector as well - I suspect the node needs to be told to turn on as it would have been told to turn off before being decomissioned (otherwise, how would the batteries arrive with a good charge?)
i simply grep'd strings from the binaries, and could only find a reference to Naplesthis BIOS supports Naples.Code:BIOS Date: 04/23/2020 10:19:02 Ver: T6U_3A25 Olympus Epyc W25Q256FV(OTP)@SOIC16 (right).BIN (1/1) ╔════════════════════════════════════════════════════════════════╗ ║ AMD ║ ╟───┬──────────┬──────────┬────────────┬───────┬──────────┬──────╢ ║ # │ CPUID │ Revision │ Date │ Size │ Offset │ Last ║ ╟───┼──────────┼──────────┼────────────┼───────┼──────────┼──────╢ ║ 1 │ 00800F12 │ 08001230 │ 2018-08-04 │ 0xC80 │ 0x26FE00 │ No ║ ╟───┼──────────┼──────────┼────────────┼───────┼──────────┼──────╢ ║ 2 │ 00800F11 │ 08001129 │ 2017-07-14 │ 0xC80 │ 0x270B00 │ No ║ ╚═══╧══════════╧══════════╧════════════╧═══════╧══════════╧══════╝ Olympus Epyc W25Q256FV(OTP)@SOIC16 (left).BIN (1/1) ╔════════════════════════════════════════════════════════════════╗ ║ AMD ║ ╟───┬──────────┬──────────┬────────────┬───────┬──────────┬──────╢ ║ # │ CPUID │ Revision │ Date │ Size │ Offset │ Last ║ ╟───┼──────────┼──────────┼────────────┼───────┼──────────┼──────╢ ║ 1 │ 00800F12 │ 08001227 │ 2018-02-09 │ 0xC80 │ 0x26FE00 │ No ║ ╟───┼──────────┼──────────┼────────────┼───────┼──────────┼──────╢ ║ 2 │ 00800F11 │ 08001129 │ 2017-07-14 │ 0xC80 │ 0x270B00 │ No ║ ╚═══╧══════════╧══════════╧════════════╧═══════╧══════════╧══════╝
revision is microcode.out of interest, what tool did you use to get those tables?
btw, there are three revisions / dates on the tables. Are those three different AGESA versions or how should I read those things?
they also state VGA onboard which is wrong.tbh, we also should be able to ask pio? They tested the boards and advertised them as 7003 Milan boards.
Maybe they got a different bios at hands?