sign_gsc_firmware: update generated file name

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

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 <>
Tested-by: Vadim Bendebury <>
Auto-Submit: Vadim Bendebury <>
Reviewed-by: George Engelbrecht <>
Commit-Queue: Vadim Bendebury <>
1 file changed