capsule update issue (ported from bsa-acs) #422
Description
During the capsule update test for ARM System Ready, we observed that the script keeps looping around unauth.bin since it is not deleted after the test. This causes the script to never proceed to tampered.bin and signed_capsule.bin.
We suggest adding a flag or mechanism to indicate that once the test for unauth.bin is complete (pass or fail), the script should move forward to the next capsule.
if exist FS%r:\acs_tests\app\unauth.bin then
FS%r:\acs_tests\app\CapsuleApp.efi FS%r:\acs_tests\app\unauth.bin >> FS%r:\acs_results_template\fw\capsule-update.log
else
echo "unauth.bin not present" >> FS%r:\acs_results_template\fw\capsule-update.log
endif
echo "entering tampered story"
echo "Testing tampered.bin update" >> FS%r:\acs_results_template\fw\capsule-update.log
echo "Test_Info" >> FS%r:\acs_results_template\fw\capsule-update.log
if exist FS%r:\acs_tests\app\tampered.bin then
FS%r:\acs_tests\app\CapsuleApp.efi FS%r:\acs_tests\app\tampered.bin >> FS%r:\acs_results_template\fw\capsule-update.log
else
echo "tampered.bin not present" >> FS%r:\acs_results_template\fw\capsule-update.log
endif