summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVadim Bendebury <vbendeb@google.com>2020-12-16 19:49:29 -0800
committerCommit Bot <commit-bot@chromium.org>2020-12-18 18:08:14 +0000
commitbc2317695965bb92b8809d9c06327adedcb0653c (patch)
treeb06a9d15be28fc8ddd4439d7dc7b3c65b2a0ebf9
parentaf02768dace900e7e62d6788b4ff81b57b3e0a79 (diff)
downloadvboot-factory-test-13683.B.tar.gz
sign_gsc_firmware: update generated file namefactory-test-13683.Bfactory-dedede-13683.B
When processing Gsc image singing request the signing server is not aware of which chip the image is being signed for, the output file name includes the string @CHIP@ and it is the responsibility of the actual signing scripts to figure out if the image is for Cr50 or Ti50. The destination image type is determined based no the signing manifest contents, this patch add code to replace @CHIP@ with the actual image type. BRANCH=none BUG=b:173049030 TEST=invoked the script to sign a Ti50 image locally, verified that the produced signed image file had the expected name. Change-Id: Ib1534ce50e0a44d0ec014e8dbee4e4d85c2082c9 Signed-off-by: Vadim Bendebury <vbendeb@google.com> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/vboot_reference/+/2596695 Tested-by: Vadim Bendebury <vbendeb@chromium.org> Auto-Submit: Vadim Bendebury <vbendeb@chromium.org> Reviewed-by: George Engelbrecht <engeg@google.com> Commit-Queue: Vadim Bendebury <vbendeb@chromium.org>
-rwxr-xr-xscripts/image_signing/sign_gsc_firmware.sh2
1 files changed, 2 insertions, 0 deletions
diff --git a/scripts/image_signing/sign_gsc_firmware.sh b/scripts/image_signing/sign_gsc_firmware.sh
index 30e27950..6c0903a7 100755
--- a/scripts/image_signing/sign_gsc_firmware.sh
+++ b/scripts/image_signing/sign_gsc_firmware.sh
@@ -598,6 +598,8 @@ sign_gsc_firmware_dir() {
if [[ -d "${output}" ]]; then
output="${output}/${base_name}.bin.prod"
+ else
+ output="${output/@CHIP@/${base_name}}"
fi
sign_gsc_firmware \