Not a problem, I appreciate your help immensely
Yeah it isn't even possible to write to the BIOS, BMC or ME recovery controllers, and they should overwrite whatever is actually stored in the firmware. So I fail to see how you could properly brick one of these even if you were trying! That said, this has me stumped...
It is getting stuck at 01h - First post code after CPU reset. The System Status LED goes amber (fatal error), the System ID LED is off and LSB (LED#0) is green. All other progress code LEDs are off.
There were no PCI-Express devices connected to the board last night, only SATA drives. I have disconnected those as well tonight so the only things plugged into the board are CPUs, RAM, fans and PSU.
I must apologise for my manic-sounding posts last night. I was not handling the stress at all well. Fortunately everyone has been very understanding thus far - sometimes stuff just happens. I need to get it sorted ASAP though!
My thoughts at this stage:
1) The flash MUST have worked initially or it would have thrown up an error when I tried to write 1.06.0001, wouldn't it? I was previously on 02.06.0002, so that should have had the security bit enabled which would have stopped 1.06.0001 from writing, right? So the fact that it successfully wrote 1.06.0001 should mean that the recovery to 02.05.0004 must have been successful...
2) Would a BMC or ME conflict be causing this? Should I try the recovery process for those, too?
3) My USB flash drives are reliable and work fine - every USB 2.0 one I've tried has been detected and been able to flash firmware successfully to the board. However, I can't see what it's doing when it is using BIOS recovery - surely if the drive is detected correctly it should simply follow the process when the jumper is set in recovery mode position?