e42731603e
Wile historically there was a unique recovery image for each Chrome OS board/HWID (with matching names), this is no longer the case. Now, multiple boards share a single recovery image, so adjust how the proper recovery image is determined, and how the coreboot image is extracted from it. Test: successfully extract coreboot images for older 1:1 boards (e.g. CAVE) and newer 1:N boards (e.g. DROBIT) Change-Id: If478aa6eadea3acf3ee9d4c5fa266acd72c99b7a Signed-off-by: Matt DeVillier <matt.devillier@gmail.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/61615 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Martin Roth <martinroth@google.com> |
||
|---|---|---|
| .. | ||
| crosfirmware.sh | ||
| description.md | ||
| extract_blobs.sh | ||
| gen_test_hwid.sh | ||
| README.md | ||
Chrome OS Scripts
These scripts can be used to access or generate Chrome OS resources, for example
to extract System Agent reference code and other blobs (e.g. mrc.bin, refcode,
VGA option roms) from a Chrome OS recovery image.
crosfirmware.sh
crosfirmware.sh downloads a Chrome OS recovery image from the recovery
image server, unpacks it, extracts the firmware update shell archive,
extracts the firmware images from the shell archive.
To download all Chrome OS firmware images, run
$ ./crosfirmware.sh
To download, e.g. the Panther firmware image, run
$ ./crosfirmware.sh panther
extract_blobs.sh
extract_blobs.sh extracts the blobs from a Chrome OS firmware image.
Right now it will produce the ME firmware blob, IFD, VGA option rom,
and mrc.bin.
gen_test_hwid.sh
gen_test_hwid.sh generates a test-only identifier in Chrome OS HWID v2
compatible format.
Usage:
$ ./gen_test_hwid.sh BOARD_NAME
Example:
$ ./gen_test_hwid.sh Kukui
KUKUI TEST 9847