OpenBMC Image Management - Witherspoon
Andrew Geissler
geissonator at gmail.com
Thu Aug 3 11:53:04 AEST 2017
This went live tonight in master with commit 0bf11809a80f88
(https://github.com/openbmc/openbmc/commit/0bf11809a80f8829ffc47fd0ea06ffab93199638).
This commit and any after it will now require the new PNOR update
images and process documented by Adriana below.
To make it all work well, first upgrade the BMC to the new level, then
upgrade the PNOR using the new squashfs.tar file (see directions in
doc updates on getting this). The first time you update to using this
new PNOR image type you need to reboot the BMC after you've done the
bmc and pnor update. After that, just boot the system up like normal.
PNOR updates now take on the order of 30s vs. 4.5 minutes! You can
have multiple versions of PNOR loaded, with the ability to choose
which one you want at boot time, and the ability to easily patch any
of the partitions in PNOR via simple filesystem operations.
This robot test can be used directly to do the updates, or as a
reference - https://github.com/openbmc/openbmc-test-automation/blob/master/extended/code_update/code_update.robot
Switching back to older BMC code is pretty painless. Just flash the
old BMC level then pflash your PNOR like the old days.
On Wed, 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/5433/
>
>
> On Jun 13, 2017, at 1:10 PM, Adriana Kobylak <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/
> Reviewers welcome :)
>
>
More information about the openbmc
mailing list