new_variant: allow custom fitimage usage message
For boards that use a fitimage, the command to generate the fitimage
may vary, so add the usage to the reference board variables.
BUG=None
TEST=`./new_variant.py --board=hatch --variant=sushi`
Verify that the gen_fit_image.sh usage example is
./gen_fit_image.sh sushi <path_to_fit_kit> [-b]
`./new_variant.py --board=volteer --variant=ripto`
Verify that the gen_fit_image.sh usage example is
./gen_fit_image.sh ripto <path_to_fit_kit> <path_to_inputs_folder> [-b]
Change-Id: I8433dfaa53a088c908d16cd89d2853b3ec836e3c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/dev-util/+/2025290
Tested-by: Paul Fagerburg <pfagerburg@chromium.org>
Reviewed-by: Jacob Rasmussen <jacobraz@google.com>
diff --git a/contrib/variant/new_variant.py b/contrib/variant/new_variant.py
index 8b63c36..15bb4a4 100755
--- a/contrib/variant/new_variant.py
+++ b/contrib/variant/new_variant.py
@@ -281,6 +281,7 @@
status.emerge_pkgs = module.emerge_pkgs
status.fitimage_dir = module.fitimage_dir
status.fitimage_pkg = module.fitimage_pkg
+ status.fitimage_cmd = module.fitimage_cmd
status.fsp = module.fsp
status.private_yaml_dir = module.private_yaml_dir
status.step_list = module.step_list
@@ -539,7 +540,7 @@
logging.info('The fitimage sources are ready for gen_fit_image.sh to process.')
logging.info('gen_fit_image.sh cannot run inside the chroot. Please open a new terminal')
logging.info('window, change to the directory where gen_fit_image.sh is located, and run')
- logging.info('./gen_fit_image.sh %s [location of FIT] -b', status.variant)
+ logging.info(status.fitimage_cmd, status.variant)
logging.info('Then re-start this program with --continue.')
logging.info('If your chroot is based in ~/chromiumos, then the folder you want is')
logging.info('~/chromiumos/src/%s/asset_generation', status.fitimage_dir)