<div dir="ltr"><div class="gmail_extra"><br>
<br><br><div class="gmail_quote">On Thu, Oct 31, 2013 at 7:05 AM, David Hendricks <span dir="ltr"><<a href="mailto:dhendrix@google.com" target="_blank">dhendrix@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div><div class="h5">On Wed, Oct 30, 2013 at 12:08 AM, marc pascual <span dir="ltr"><<a href="mailto:marcmpascual@gmail.com" target="_blank">marcmpascual@gmail.com</a>></span> wrote:<br></div></div><div class="gmail_extra">
<div class="gmail_quote"><div><div class="h5">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hello,<div><br></div><div>I have an HP DL165 G7 and I applied the latest BIOS image from HP.</div>
<div><br></div><div>root# flashrom -p internal:amd_imc_force=yes -w /var/tmp/2012.07.27.A-O37_0727.ROM -c MX25L3206E</div>
<div><br></div><div>flashrom v0.9.7-r1711 on Linux 2.6.32-358.2.1.el6.x86_64 (x86_64)</div><div>flashrom is free software, get the source code at <a href="http://www.flashrom.org" target="_blank">http://www.flashrom.org</a></div>
<div><br>
</div><div>Calibrating delay loop... OK.</div><div>Found chipset "AMD SB7x0/SB8x0/SB9x0". Enabling flash write... Writes have been disabled for safety reasons because the presence of the IMC</div><div>was detected and it could interfere with accessing flash memory. Flashrom will</div>
<div>try to disable it temporarily but even then this might not be safe:</div><div>when it is reenabled and after a reboot it expects to find working code</div><div>in the flash and it is unpredictable what happens if there is none.</div>
<div><br></div><div>To be safe make sure that there is a working IMC firmware at the right</div><div>location in the image you intend to write and do not attempt to erase.</div><div><br></div><div>You can enforce write support with the amd_imc_force programmer option.</div>
<div>Continuing with write support because the user forced us to!</div><div>OK.</div><div>Found Macronix flash chip "MX25L3206E" (4096 kB, SPI) at physical address 0xffc00000.</div><div>Reading old flash chip contents... done.</div>
<div>Erasing and writing flash chip... Erase/write done.</div><div>Verifying flash... VERIFIED.</div><div><br></div><div>However after rebooting the machine once, I'm getting this message:<br></div><div>
<br></div><div><div>Detect a Unsame SDRR/Configuration Image in Current BIOS</div><div>BMC SDRR Version : 2.37.0.98 --> 2.33.1.226</div><div>Loading updated SDRR/CONFIGURATION to BMC -- DO NOT POWER OFF</div>
<div>Erasing Sectors Done!</div><div>Uploading SDRR: 100%</div><div>Uploading Configuration: 100%</div><div>Update SDRR/Configuration Image successfully</div><div>Resetting BMC....</div><div><br></div><div>The machine reboots itself again, and I see the same message the second time around. It reboots itself again.</div>
<div><br></div><div>This time, it can't find my local disk:</div><div><br></div><div><div>Reboot and Select proper Boot device</div><div>or Insert Boot Media in selected Boot device and press a key</div>
<div><br></div><div>I issue a reset, then everything seems to be fine from here.</div><div><br></div><div><div>/./-> reset /system1/console1</div><div>System1 reset.</div><div><br></div><div><div>/./-> start /system1/console1</div>
<div>...</div></div><div>(boots to the OS)</div><div><br></div><div><br></div><div>Is this normal, or is this related to the warning about IMC being detected?</div></div></div></div></div></blockquote><div><br></div></div>
</div><div>
This seems normal for the HP DL165 G7. In general, Flashrom does not know about vendor-specific BMCs. I guess that the BMC configuration is stored on the same ROM as the BIOS, so flashing the .ROM file provided by HP wipes it out and the BMC must be re-configured.</div>
<span class=""><font color="#888888">
<div><br></div></font></span></div><span class=""><font color="#888888">-- <br>David Hendricks (dhendrix)<br>Systems Software Engineer, Google Inc.
</font></span></div></div>
</blockquote></div><br></div><div class="gmail_extra"><br></div><div class="gmail_extra" style>Thanks for your response. It does seem normal. I was able to replicate this consistently -- only happens when downgrading from a higher ROM version. I don't know what's exactly going on, but what happens is that after a reboot, it downgrades the "BMC SDRR", resets the BMC, updates it again to the previous version (what it was before), and finally resets the BMC for the second time. </div>
<div class="gmail_extra"><br></div><div class="gmail_extra">root# dmidecode -t bios</div><div class="gmail_extra"><br></div><div class="gmail_extra"># dmidecode 2.11</div><div class="gmail_extra">SMBIOS 2.7 present.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Handle 0x0000, DMI type 0, 24 bytes</div><div class="gmail_extra">BIOS Information</div><div class="gmail_extra"> Vendor: HP</div><div class="gmail_extra">
Version: O37</div><div class="gmail_extra"> Release Date: 10/17/2012</div><div class="gmail_extra"> Address: 0xF0000</div><div class="gmail_extra"> Runtime Size: 64 kB</div><div class="gmail_extra">
ROM Size: 4096 kB</div><div class="gmail_extra"><br></div><div class="gmail_extra">root# flashrom -p internal:amd_imc_force=yes -w /var/tmp/2012.07.27.A-O37_0727.ROM -c MX25L3206E</div><div class="gmail_extra"><br>
</div><div class="gmail_extra">(reboot)</div><div class="gmail_extra"><br></div><div class="gmail_extra">Detect a Unsame SDRR/Configuration Image in Current BIOS</div><div class="gmail_extra">BMC SDRR Version : 2.37.0.98 --> 2.33.1.226</div>
<div class="gmail_extra">Loading updated SDRR/CONFIGURATION to BMC -- DO NOT POWER OFF</div><div class="gmail_extra">Erasing Sectors Done!</div><div class="gmail_extra">Uploading SDRR: 100%</div><div class="gmail_extra">
Uploading Configuration: 100%</div><div class="gmail_extra">Update SDRR/Configuration Image successfully</div><div class="gmail_extra">Resetting BMC.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Detect a Unsame SDRR/Configuration Image in Current BIOS</div>
<div class="gmail_extra">BMC SDRR Version : 2.33.1.226 --> 2.37.0.98</div><div class="gmail_extra">Loading updated SDRR/CONFIGURATION to BMC -- DO NOT POWER OFF</div><div class="gmail_extra">Erasing Sectors Done!</div>
<div class="gmail_extra">Uploading SDRR: 100%</div><div class="gmail_extra">Uploading Configuration: 100%</div><div class="gmail_extra">Update SDRR/Configuration Image successfully</div><div class="gmail_extra">Resetting BMC.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">(... normal boot up follows) </div><div class="gmail_extra"><br></div><div class="gmail_extra" style>I don't know why it does this, but I think I should be asking HP. </div>
<div class="gmail_extra"><br></div><div class="gmail_extra" style>Regards,</div><div class="gmail_extra" style>Marc</div></div>