Bios upgrade from BMC
vijaykhemka at fb.com
Wed Jan 22 05:56:53 AEDT 2020
On 1/20/20, 10:54 PM, "Neeraj Ladkani" <neladk at microsoft.com> wrote:
- How are you able to determine flash ranges used by UEFI in case we may not want to update ME but only UEFI regions?
I am not defining any range in flash. Currently it is just going to use flashcp command to flash image. I can accept this final stage of flashing as system unit file or command through config option.
- How is this interfaced from redfish/IPMI ?
It will interface same as BMC upgrade. Considering redfish/IPMI only, I am considering this this as a part of same image updater.
Is there any design document for this feature that we can review?
No, There is no design document just below steps and wanted to check if it is a common sequence everyone use or we need some flexibility.
From: openbmc <openbmc-bounces+neladk=microsoft.com at lists.ozlabs.org> On Behalf Of Lawniczak, Maciej
Sent: Sunday, January 19, 2020 11:35 PM
To: CS20 CTCchien <CTCCHIEN at nuvoton.com>; openbmc at lists.ozlabs.org; Vijay Khemka <vijaykhemka at fb.com>
Subject: [EXTERNAL] RE: Bios upgrade from BMC
To set up ME in Recovery mode use IPMI command “Force ME Recovery” – DFh (byte4=01h)
To set up ME in Operational again use IPMI “Cold Reset” command” – 02h
For more details check: https://urldefense.proofpoint.com/v2/url?u=https-3A__nam06.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.intel.com-252Fcontent-252Fdam-252Fwww-252Fpublic-252Fus-252Fen-252Fdocuments-252Ftechnical-2Dspecifications-252Fintel-2Dpower-2Dnode-2Dmanager-2Dv3-2Dspec.pdf-26data-3D02-257C01-257Cneladk-2540microsoft.com-257Cadc15cf0148e432110b508d79d7b6a38-257C72f988bf86f141af91ab2d7cd011db47-257C1-257C0-257C637151026289126945-26sdata-3D2TLHwCsXMK2vg-252FfBMrKIPyNoPUG52RjYq33prp9xpsc-253D-26reserved-3D0&d=DwIGaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=v9MU0Ki9pWnTXCWwjHPVgpnCR80vXkkcrIaqU7USl5g&m=5Pb3J8Ryu1wP_3jCzVlxAbutqUd0mniJjRC5jlcl0mg&s=e4TQhEF7P9P3pjD1qc8cZ4G4_gqi-yAiGee9pTHUuNs&e=
I try to upgrade BIOS from BMC, but I do not know how to set the mode of ME/NM.
Can you share the process how you set ME/NM to recovery mode and operation mode?
From: Vijay Khemka <mailto:vijaykhemka at fb.com>
To: OpenBMC Maillist <mailto:openbmc at lists.ozlabs.org>
Subject: Bios upgrade from BMC
I am writing an application for Bios upgrade. Currently I have created a hook to our bmc updater which expects a systemd unit file to be run at the time of activating update. But I am thinking of adding some of this unit file functionality in updater itself and wanted to run by you all if it is common procedure used by every platform. Below are the process we use in our platform as a part of bios upgrade.
1. Power off host server.
2. Set ME/NM (Management engine or Node manager in x86) to recovery mode
3. Flip GPIO to access SPI flash used by host.
4. Bind spi driver to access flash
5. Flashcp image to device.
6. Unbind spi driver
7. Flip GPIO back for host to access SPI flash
8. Set ME/NM to operational mode
9. Power on server.
I can have some flexibility in this sequence based on each platform configuration. Looking forward to your suggestions.
The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.
Intel Technology Poland sp. z o.o.
ul. Słowackiego 173 | 80-298 Gdańsk | Sąd Rejonowy Gdańsk Północ | VII Wydział Gospodarczy Krajowego Rejestru Sądowego - KRS 101882 | NIP 957-07-52-316 | Kapitał zakładowy 200.000 PLN.
Ta wiadomość wraz z załącznikami jest przeznaczona dla określonego adresata i może zawierać informacje poufne. W razie przypadkowego otrzymania tej wiadomości, prosimy o powiadomienie nadawcy oraz trwałe jej usunięcie; jakiekolwiek przeglądanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited.
More information about the openbmc