Hello,
I have an HP DL165 G7 and I applied the latest BIOS image from HP.
root# flashrom -p internal:amd_imc_force=yes -w /var/tmp/2012.07.27.A-O37_0727.ROM -c MX25L3206E
flashrom v0.9.7-r1711 on Linux 2.6.32-358.2.1.el6.x86_64 (x86_64)
Calibrating delay loop... OK.
Found chipset "AMD SB7x0/SB8x0/SB9x0". Enabling flash write... Writes have been disabled for safety reasons because the presence of the IMC
was detected and it could interfere with accessing flash memory. Flashrom will
try to disable it temporarily but even then this might not be safe:
when it is reenabled and after a reboot it expects to find working code
in the flash and it is unpredictable what happens if there is none.
To be safe make sure that there is a working IMC firmware at the right
location in the image you intend to write and do not attempt to erase.
You can enforce write support with the amd_imc_force programmer option.
Continuing with write support because the user forced us to!
OK.
Found Macronix flash chip "MX25L3206E" (4096 kB, SPI) at physical address 0xffc00000.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... VERIFIED.
However after rebooting the machine once, I'm getting this message:
Detect a Unsame SDRR/Configuration Image in Current BIOS
BMC SDRR Version : 2.37.0.98 --> 2.33.1.226
Loading updated SDRR/CONFIGURATION to BMC -- DO NOT POWER OFF
Erasing Sectors Done!
Uploading SDRR: 100%
Uploading Configuration: 100%
Update SDRR/Configuration Image successfully
Resetting BMC....
The machine reboots itself again, and I see the same message the second time around. It reboots itself again.
This time, it can't find my local disk:
Reboot and Select proper Boot device
or Insert Boot Media in selected Boot device and press a key
I issue a reset, then everything seems to be fine from here.
/./-> reset /system1/console1
System1 reset.
/./-> start /system1/console1
...
(boots to the OS)
Is this normal, or is this related to the warning about IMC being detected?