Some ChromeOS recovery images, such as for GRUNT, support multiple boards / multiple bios/ec images, but do not break them out in a 'models' subdirectory like modern recovery images do. Instead, they use a manifest.json to map the board name to the correct bios/ec images. Add support for parsing out the info from here. TEST=run `util/chromeos/crosfirmware.sh kasumi` and verify that the correct shellball firmware is extracted from the recovery image. Change-Id: I64153ba16cb8328d65a0f088d05f04a969f6810f Signed-off-by: Matt DeVillier <matt.devillier@gmail.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/85024 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Felix Singer <service+coreboot-gerrit@felixsinger.de> |
||
|---|---|---|
| .. | ||
| crosfirmware.sh | ||
| description.md | ||
| extract_blobs.sh | ||
| gen_test_hwid.sh | ||
| README.md | ||
| update_ec_headers.sh | ||
ChromeOS Scripts
These scripts can be used to access or generate ChromeOS resources, for example
to extract System Agent reference code and other blobs (e.g. mrc.bin, refcode,
VGA option roms) from a ChromeOS recovery image.
crosfirmware.sh
crosfirmware.sh downloads a ChromeOS 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 ChromeOS 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 ChromeOS 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 ChromeOS HWID v2
compatible format.
Usage:
$ ./gen_test_hwid.sh BOARD_NAME
Example:
$ ./gen_test_hwid.sh Kukui
KUKUI TEST 9847