Flashing DCU-modified (smbios area) btg_provisioned firmware image bricks the laptop.
Component
Dasharo firmware
Device
NovaCustom V56 14th Gen
Dasharo version
1.0.0-rc6
Dasharo Tools Suite version
2.6.0
Test case ID
CUP170.201, CUP170.301, CUP180.201, CUP180.301
Brief summary
V560TNE, v1.0.0-rc6: brick after dcu smbios modification of btg_provisioned flash image.
How reproducible
2/2
How to reproduce
- Modify btg_provisioned Dasharo image by setting UUID & serial number with DCU.
- Flash it using flashrom -p internal --ifd -i fd -i bios -i me.
- After successful verification, power off DUT.
- Try to power on DUT.
Expected behavior
DUT starts, UUID & serial number modified as expected.
Actual behavior
Platform does not start, power LED off after a while.
Screenshots
No response
Additional context
No response
Solutions you've tried
No response
Can you specify if it only happens on bootguard provisioned firmware? I doubt changing the UUID/Serial number via DCU could affect the IBB and make boot guard fail. Do you have an idea @mkopec ?
We use CBFS verification which verifies the hashes of all files in CBFS and puts the trust anchor in the bootblock, so all files in CBFS are effectively tied to the boot guard signature.
We use CBFS verification which verifies the hashes of all files in CBFS and puts the trust anchor in the bootblock, so all files in CBFS are effectively tied to the boot guard signature.
In that case, all that we can do is to only run these DCU test suite only on firmware without provisioned BTG, right? I wonder how that should be reflected in the test scope of BTG releases. Maybe the tests for modifying UUID and serial number should be left out for platforms supporting BTG?