architecture/code-update/code-update.md

3 Two BMC Code layouts are available:
12 The following are the steps to update the BMC.
14 1. Get a BMC image tar: After building OpenBMC, you will end up with a set of
22 The BMC tar image contains 5 files: u-boot, kernel, ro, and rw partitions and
30 purpose=xyz.openbmc_project.Software.Version.VersionPurpose.BMC
37 2. Transfer the generated BMC image to the BMC via one of the following methods:
42 - Method 2: Via scp: Copy the generated BMC image to the `/tmp/images/`
43   directory on the BMC.
56 - Method 1: From the BMC command line, note the most recent directory name
81 …tar xfO <BMC tar image> MANIFEST | sed -ne '/version=/ {s/version=//;p}' | head -n1 | tr -d '\n' |…
86    previous step, this will write the contents of the image to the BMC chip via
89 - Method 1: From the BMC command line:
92   busctl set-property xyz.openbmc_project.Software.BMC.Updater \
119 - Method 2: From the BMC command line:
122   busctl get-property xyz.openbmc_project.Software.BMC.Updater  \
142 - Method 2: From the BMC command line:
145   busctl get-property xyz.openbmc_project.Software.BMC.Updater \
156 7. Reboot the BMC for the image to take effect.
158 - Method 1: From Redfish: If ApplyTime was set to "Immediate", the BMC will
161   To reboot the BMC manually see:
164 - Method 2: From the BMC command line:
174       -d '{"data": "xyz.openbmc_project.State.BMC.Transition.Reboot"}' \
199 1. A "functional" association to the "running" BMC and host images
201 There is only one functional association per BMC and one functional association
202 per host. The functional/running BMC image is the BMC image with the lowest
203 priority when rebooting the BMC. The functional image does not update until the
204 BMC is rebooted. The functional host image behaves the same way except that it
222 2. An "active" association to the active BMC and host images
224 Note: Several BMC images might be active, this is true for the host images as
245 This is used for identifying firmware components which are programmable via BMC
298 via TFTP, or copied to the BMC.
305   xyz.openbmc_project.Software.Version.VersionPurpose.BMC or
334 To delete all non-functional images, whether BMC or host images:
347 interface disables patching of the BMC by not mounting `/usr/local`, which in
361 user with admin privileges by running the following commands on the BMC:
376 Software factory reset resets the BMC and host firmware to its factory state by
378 command and then reboot the BMC:
386 The factory reset on the BMC side will clear `/var`, `/home`, and `/etc`. On the
398 When a BMC image is activated, each `image-<name>` is written to the BMC chip's
408 When a BMC image is activated (i.e. when "RequestedActivation" is set to
409 "Active"), UBI volumes are created on the BMC chip for the image. The alternate
410 BMC chip can also be used to store images. This is determined by "BMC_RO_MTD".
411 Using both the alternate BMC chip and the BMC chip allows for multiple BMC
412 images to be stored. By default, only the BMC chip is used. To use both, set