| commit | 7584495b56aa202d99079b2e747c4ce760583622 | [log] [tgz] |
|---|---|---|
| author | Simon Glass <sjg@chromium.org> | Tue Aug 15 16:55:41 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu Aug 17 08:56:46 2017 |
| tree | b81c9750aa77c4507feeaab693616d9e5eb86832 | |
| parent | a0dc7a0cefc3d38a47fa111842506b7d52535cb8 [diff] |
pack_firmware: Adjust code order in _GenerateOneModel() Don't create directories until we have located the shared node. This will allow us to skip this model if we decide not to process it yet. BUG=chromium:741043 BUG=b:64117873 TEST=PYTHONPATH=~/cosarm python pack_firmware_unittest.py && \ PYTHONPATH=~/cosarm python pack_firmware_functest.py Change-Id: I775df811592cb2916900681ce8c4362810e48f80 Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/615367 Reviewed-by: Jason Clinton <jclinton@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.
In all modes, updater will try to preserve few firmware data, for example the VPD sections (
RO_VPD,RW_VPD),HWIDandGBB flags(inGBBsection).
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 only 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 --wp=1
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. To do that, find themake.confin board overlay and addUSE="-bootimage -cros_ec".
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. Find a template here in chromiumos-base/chromeos-firmware-null.
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.
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.
Here's a detailed list of how each updater mode works:
--mode=autoupdate: Invoked by update_engine when a payload is installed.
update_engine will invoke chromeos-setgoodfirmware after 60 secs, which will update or mark booted RW firmware to active.CROS_FIRMWARE_MAIN_IMAGE. If yes, go 2. Otherwise, do --mode=recovery.--mode=recovery: Invoked by recovery shim after installed.
--mode=factory_install: Used for factory initial imaging.