cros_bundle_firmware: special case rush and rush_ryu for coreboot area
The rush and rush_ryu boards have a different sized coreboot
area and location. The assumed size (1MiB) and location (end or rom)
is not correct. Therefore, use the fmap to determine the size and
location to extract out the coreboot bits.
BUG=chrome-os-partner:30569
TEST=Built bootiamge with corresponding fmap changes to size the
coreboot area correctly.
Change-Id: I5f6227295bcff12048719f22a61bc707cd8034e9
Signed-off-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/208471
Reviewed-by: Furquan Shaikh <furquan@chromium.org>
Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>
diff --git a/host/lib/bundle_firmware.py b/host/lib/bundle_firmware.py
index dbc3418..8b5ff70 100644
--- a/host/lib/bundle_firmware.py
+++ b/host/lib/bundle_firmware.py
@@ -904,7 +904,7 @@
bootstub_copy = os.path.join(self._tools.outdir, 'coreboot-8mb.rom')
self._tools.WriteFile(bootstub_copy, data)
- if self._board in ('storm', ):
+ if self._board in ('storm', 'rush', 'rush_ryu', ):
# This is a hack, as storm does not fall into any of the two
# categories of images covered by the [-0x100000:] range. Not applying
# this to all targets yet, as it is not clear that they all would fit