| commit | 695ebdbcd01a51381daeec719c7c4e1cca907a35 | [log] [tgz] |
|---|---|---|
| author | Hung-Te Lin <hungte@chromium.org> | Mon Mar 27 07:44:10 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Sat Apr 29 09:42:48 2017 |
| tree | b897b13579891b7adb359332ebb6fa01dc7e08d5 | |
| parent | 3def9376cf31b5c9a0a7efa18cee81f5480fc8fa [diff] |
Change updater 5 to be symlink of updater4.
Vboot2 logic has been migrated to V4 updater because many projects
choose to migrate silently. As a result, we should make V5 a symlink of
V4 to reduce maintenance effort, also to prevent the bugs like "PD is
only supported in V4" when people are trying to add new features to a
particular platform.
BUG=chromium:705414
TEST=emerge-$BOARD chromeos-firmware-$BOARD (use a board with v5 updater)
chromeos-firmwareupdate --mode=recovery # success.
Change-Id: I057d63647218cc626c0c123334a5554e5ad6e0c9
Reviewed-on: https://chromium-review.googlesource.com/479182
Commit-Ready: Hung-Te Lin <hungte@chromium.org>
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
This repository contains the firmware updater (chromeos-firmwareupdate) that will update firmware images related to verified boot, usually AP (also known as BIOS or MAIN) and EC.
Auto update is one of the most important feature in Chrome OS. Updating firmware is one of the most complicated process, since all Chromebooks come with firmware that implemented verified boot and must be able to update in background silently.
The firmware updater was made as a “shellball”, a self-executable file containing updater logic (shell scripts), utility programs, and firmware images.
Usually you can find the updater in /usr/sbin/chromeos-firmwareupdate on a ChromeOS device (or the rootfs partition of a disk image).
To look at its contents (firmware images and versions):
chromeos-firmwareupdate -V
Usually for people who wants to “update all my firmware to right states”, do:
chromeos-firmwareupdate --mode=recovery
The
recoverymode will try to update RO+RW if your write protection is not enabled, otherwise on RW.
If your are not sure about write protection status but you only want RW to be updated, run:
chromeos-firmwareupdate --mode=recovery --wp=1
The
--wpargument will override you real write protection status.
The ChromeOS Auto Update (update_engine) runs updater in a different way - a two-step trial process.
If you want to simulate and test that, do:
chromeos-firmwareupdate --mode=autoupdate
autoupdatemay automatically switch torecoverymode under certain conditions, especially if your write protection is not enabled. To really simuate the 2-step update process, add--wp=1 --nocheck_rw_compatible.
The updater is provided by the virtual/chromeos-firmware package in Chromium OS source tree, which will be replaced and includes the chromeos-base/chromeos-firmware-${BOARD} package in private board overlays.
To build an updater locally, in chroot run:
emerge-${BOARD} chromeos-firmware-${BOARD}
If your board overlay has defined USE flags bootimage or cros_ec, chromeos-firwmare-${BOARD} package will add dependency to firmware and EC source packages (chromeos-bootimage and chromeos-ec), and have the firmware images in /build/${BOARD}/firmware/{image,ec}.bin. A “local” updater will be also generated in /build/${BOARD}/firmware/updater.sh so you can run it to test the locally built firmware images.
In other words, you can remove
bootimageandcros_ecin branches that you don't need firmware from source, for example the factory branches or ToT, especially if there are external partners who only has access to particular board private overlays.
The firmware updater packages lives in private board overlays: src/private-overlays/overlay-${BOARD}-private/chromeos-base/chromeos-firmware-${BOARD}/chromeos-firmware-${BOARD}-9999.ebuild.
Usually there are few fields you have to fill:
A reference to the Main (AP) firmware image, which usually comes from emerge-${BOARD} chromeos-booimage then /build/${BOARD}/firmware/image.bin.
Usually this implies both RO and RW. See CROS_FIRMWARE_MAIN_RW_IMAGE below for more information.
You have to run
ebuild-${BOARD} chromeos-firmware-${BOARD}.ebuild manifestwhenever you've changed the image files (CROS_FIRMWARE_*_IMAGE).
A reference to the Main (AP) firmware image and only used for RW sections.
If this value is set, CROS_FIRMWARE_MAIN_IMAGE will be used for RO and this will be used for RW.
A reference to the Embedded Controller (EC) firmware image, which usually comes from emerge-${BOARD} chromeos-ec then /build/${BOARD}/firmware/ec.bin.
Similar to CROS_FIRMWARE_MAIN_RW_IMAGE - just for EC.
A version number to indicate “the expected stable (RO) main firmware version”. Devices with firmware version smaller than stable (or if the stable was set to empty) will get RO+RW update if write protection is not enabled; otherwise only RW update.
This can be considered as a setting for “which RO version I want to keep for dogfood devices when they receive AU”.
Devices without write protection will always get RO+RW updated by recovery, that‘s why this option is not called
RO_VERSION. It’s named “stable” to indicate that the version here is simply a suggestion for updating or not.
Ideally, this should be used as:
In other words, STABLE should be the “first shipped RO”.
However, we do see the need of “pushing AU to dogfooders to test new RW or new RO”. STABLE can be used to control this:
When STABLE is not empty, implicit key changing is not allowed in AU mode, so you if you want to push key changes, for example PreMP to MP, you have to uprev
CROS_FIRMWARE_MAIN_IMAGEas well, or temporarily set STABLE to empty.
Same as CROS_FIRMWARE_MAIN_IMAGE, except that this is for EC.
The firmware updater is built by running pack_firmware.py, which collects firmware image and extra files, all files under pack_dist folder, archived by running shar, with a special bootstrap stub pack_stub.
Since the verified boot has been evolved with so much differences, we put the updating logic in different files according to the generation of firmware: pack_dist/updater*.sh. Most Chromebooks today should use updater4.sh.
Usually we will increase a “logic version” when the verified boot has been changed so much that the updater code for previous versions would almost won't work. Currently we have defined these versions (Use Developer Info page to find the mapping from board names to product names):
This will be mapped to what you should set in the CROS_FIRMWARE_SCRIPT value in ebuild files.