OpenBMC Image Management - Witherspoon

[Adriana Kobylak]

Today, the support for UBI on BMC will be turned on for the Witherspoon platform. This support (that can be enabled on any system via the machine feature "obmc-ubi-fs”) allows for the storage of the BMC image files in UBI volumes and takes advantage of the 2nd BMC chip on the system to support dual images.

The method for updating the BMC are the same as updating the virtual PNOR where the BMC tarfile is uploaded to the BMC, followed by setting the RequestedActivation property to Active. After the activation is successful, the BMC can be rebooted.

The openbmc-sfw tool located here helps with the querying and updating process: https://github.com/geissonator/openbmc-events <https://github.com/geissonator/openbmc-events>

To move from the existing static layout for the first time, this script can be used (this will reformat the BMC chip clearing all user settings): https://gist.github.com/charleshofer/e753f88deff0c75eda196eb24877fa0c <https://gist.github.com/charleshofer/e753f88deff0c75eda196eb24877fa0c>

I’ll be updating the docs/code-update.md file to reflect this change.



> On Aug 2, 2017, at 12:23 PM, Adriana Kobylak <anoo at linux.vnet.ibm.com> wrote:
> 
> This week, the support for virtual pnor on witherspoon (which reformats the pnor chip to ubi) will be turned on.
> REST interfaces and copying partition files for patching replace pflash for updating and patching the pnor.
> 
> Additional details of the implementation and instructions are documented here:
> https://gerrit.openbmc-project.xyz/#/c/4756/ <https://gerrit.openbmc-project.xyz/#/c/4756/>
> https://gerrit.openbmc-project.xyz/#/c/5433/ <https://gerrit.openbmc-project.xyz/#/c/5433/>
> 
> 
>> On Jun 13, 2017, at 1:10 PM, Adriana Kobylak <anoo at linux.vnet.ibm.com <mailto:anoo at linux.vnet.ibm.com>> wrote:
>> 
>> In the next coming days, the changes to the host bios update procedure will be available for use.
>> 
>> Notable changes are using a squashfs image that includes individual pnor partition files instead of the ffs (.pnor) image, formatting the pnor chip as ubi to store these files (allowing for the storage of more than one image), and mailbox daemon updates to support these changes (new phosphor-mboxd repo).
>> 
>> Regarding the mailbox daemon, the mboxbridge repository is staying as a reference implementation and has been cloned into phosphor-mboxd. Any system using mailbox and running with a flashed ffs pnor image (instead of updating to the ubi layout) would still need the reference mboxbridge implementation. The openbmc build is being updated to build phosphor-mboxd as the default.
>> 
>> A system can be updated transparently from running with an ffs pnor image to the squashfs image via the Software dbus interfaces. In a similar way, a system with a ubi-formatted pnor can be flashed with an ffs pnor image using pflash.
>> 
>> The first round of documentation updates are here: https://gerrit.openbmc-project.xyz/#/c/4756/ <https://gerrit.openbmc-project.xyz/#/c/4756/>
>> Reviewers welcome :)
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170921/e78e571c/attachment-0001.html>