| commit | c2baac9661a6d70d46811f14868a65fb41077f99 | [log] [tgz] |
|---|---|---|
| author | Patrick Venture <venture@google.com> | Mon Aug 05 13:30:38 2019 -0700 |
| committer | Patrick Venture <venture@google.com> | Mon Aug 05 13:34:37 2019 -0700 |
| tree | 1c5b0d57bb57eec46f3abcc8d0f8a4c9074b6066 | |
| parent | 984d94d6cd4aa3e671156d00cfd7fa6b29229532 [diff] |
bmc: allow update to use systemd with path Verification provides a mechanism that has a systemd unit and mode, and also a path to check the result. This object can be used for updates, and will be renamed in a later patchset to be more generically named. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I0a995af0aefff76592247775f22fc84189d14903
This document describes the OpenBmc software implementing the secure flash update mechanism.
The primary details are here.
This repo contains a host-tool implementation for talking to the corresponding BMC blob handler.
The host-tool depends on ipmi-blob-tool and pciutils.
Check out the pciutils source.
Then run these commands in the source directory.
make SHARED=yes make SHARED=yes install make install-lib
Check out the ipmi-blob-tool source.
Then run these commands in the source directory.
./bootstrap.sh ./configure make make install
Check out the phosphor-ipmi-flash source.
Then run these commands in the source directory.
./bootstrap.sh ./configure --disable-build-bmc-blob-handler make make install
NOTE: When building from the OpenBMC SDK your configuration call will be:
./configure --enable-oe-sdk --host "$(uname -m)" --disable-build-bmc-blob-handler AR=x86_64-openbmc-linux-gcc-ar RANLIB=x86_64-openbmc-linux-gcc-ranlib
The host-tool has parameters that let the caller specify every required detail.
The required parameters are:
| Parameter | Options | Meaning |
|---|---|---|
command | update | The tool should try to update the BMC firmware. |
interface | ipmibt, ipmilpc, ipmipci | The data transport mechanism, typically ipmilpc |
image | path | The BMC firmware image file (or tarball) |
sig | path | The path to a signature file to send to the BMC along with the image file. |
type | static, ubitar | Whether we're updating via the static layout or UBI tarball. |
If you're using an LPC data transfer mechanism, you'll need two additional parameters: address and length. These values indicate where on the host you've reserved memory to be used for the transfer window.
This supports two methods of providing the image to stage. You can send the file over IPMI packets, which is a very slow process. A 32-MiB image can take ~3 hours to send via this method. This can be done in <1 minutes via the PCI bridge, or just a few minutes via LPC depending on the size of the mapped area.
This is implemented as a phosphor blob handler.
The image must be signed via the production or development keys, the former being required for production builds. The image itself and the image signature are separately sent to the BMC for verification. The verification package source is beyond the scope of this design.
Basically the IPMI OEM handler receives the image in one fashion or another and then triggers the verify_image service. Then, the user polls until the result is reported. This is because the image verification process can exceed 10 seconds.
The image flashing mechanism itself is the initramfs stage during reboot. It will check for files named "image-*" and flash them appropriately for each name to section. The IPMI command creates a file /run/initramfs/bmc-image and writes the contents there. It was found that writing it in /tmp could cause OOM errors moving it on low memory systems, whereas renaming a file within the same folder seems to only update the directory inode's contents.
The staging file path can be controlled via software configuration. The image is assumed to be the tarball contents and is written into /tmp/{tarball_name}.gz
TODO: Flesh out the UBI approach.
To use phosphor-ipmi-flash a platform must provide a configuration. A platform can configure multiple interfaces, such as both lpc and pci. However, a platform should only configure either static layout updates, or ubi. If enabling lpc, the platform must specify either aspeed or nuvoton. The system also supports receiving BIOS updates.
The following are the two primary configuration options, which control how the update is treated.
| Option | Meaning |
|---|---|
--enable-static-layout | Enable treating the update as a static layout update. |
--enable-tarball-ubi | Enable treating the update as a tarball for UBI update. |
--enable-host-bios | Enable receiving the update for a host bios update. |
The following are configuration options for how the host and BMC are meant to transfer the data. By default, the data-in-IPMI mechanism is enabled.
There are two configurable data transport mechanisms, either staging the bytes via the LPC memory region, or the PCI-to-AHB memory region. Because there is only one MAPPED_ADDRESS variable at present, a platform should only configure one. The platform's device-tree may have the region locked to a specific driver (lpc-aspeed-ctrl), preventing the region from other use.
NOTE: It will likely be possible to configure both in the near future.
| Variable | Default | Meaning |
|---|---|---|
MAPPED_ADDRESS | 0 | The address used for mapping P2A or LPC into the BMC's memory-space. |
If a platform enables p2a as the transport mechanism, a specific vendor must be selected via the following configuration option. Currently, only one is supported.
| Option | Meaning |
|---|---|
--enable-aspeed-p2a | Use with ASPEED parts. |
If a platform enables lpc as the transport mechanism, a specific vendor must be selected via the following configuration option. Currently, only two are supported.
| Option | Meaning |
|---|---|
--enable-aspeed-lpc | Use with ASPEED parts. |
--enable-nuvoton-lpc | Use with Nuvoton parts. |
There are also options to control an optional clean up mechanism.
| Option | Meaning |
|---|---|
--enable-cleanup-delete | Provide a simple blob id that deletes artifacts. |
If the update mechanism desired is simply a BMC reboot, a platform can just enable that directly.
| Option | Meaning |
|---|---|
--enable-reboot-update | Enable use of reboot update mechanism. |
The following variables can be set to whatever you wish, however they have usable default values.
| Variable | Default | Meaning |
|---|---|---|
STATIC_HANDLER_STAGED_NAME | /run/initramfs/bmc-image | The filename where to write the staged firmware image for static updates. |
TARBALL_STAGED_NAME | /tmp/image-update.tar | The filename where to write the UBI update tarball. |
HASH_FILENAME | /tmp/bmc.sig | The file to use for the hash provided. |
PREPARATION_DBUS_SERVICE | phosphor-ipmi-flash-bmc-prepare.target | The systemd target started when the host starts to send an update. |
VERIFY_STATUS_FILENAME | /tmp/bmc.verify | The file checked for the verification status. |
VERIFY_DBUS_SERVICE | phosphor-ipmi-flash-bmc-verify.target | The systemd target started for verification. |
UPDATE_DBUS_SERVICE | phosphor-ipmi-flash-bmc-update.target | The systemd target started for updating the BMC. |
BIOS_STAGED_NAME | /tmp/bios-image | The file to use for staging the bios firmware update. |
BIOS_VERIFY_STATUS_FILENAME | /tmp/bios.verify | The file checked for the verification status. |
PREPARATION_BIOS_TARGET | phosphor-ipmi-flash-bios-prepare.target | The systemd target when the host starts to send an update. |
VERIFY_BIOS_TARGET | phosphor-ipmi-flash-bios-verify.target | The systemd target started for verification. |
UPDATE_BIOS_TARGET | phosphor-ipmi-flash-bios-update.target | The systemd target started for updating the BIOS. |
This document describes the details of the state machine implemented and how different interactions with it will respond. This also describes how a host-side tool is expected to talk to it (triggering different states and actions).