Garrett,
The 10,000 foot view of the concept behind the code is to work around the
limitation of NOR flash. Basically one of the bit state transitions for a bit
(usually setting 0 to 1) requires erasing an entire block.
So to flip one bit in the block could require you to erase the entire bl
Is there any good documentation for how the Fault Tolerant Write is supposed to
work?
I understand that NV storage, FTW working space and FTW spare space are
supposed to be in the same Firmware Volume.
I'm having trouble deciphering how big the FTW working and spare areas should
be in relation
Hi Michael,
Thanks for catching this.
While we re-checked the spec, and realized there're some inconsistency in the
UEFI Spec about the Override Data definition. As we know, 0.0.0.0 is clearly
not a valid unicast address.
In "Related Definitions" under EFI_MTFTP4_PROTOCOL.GetInfo():
ServerIp
I'm stored the value in the PCR8, which is left empty at boot time by the
UEFI. In my understanding, since the register is initially empty, the
value I should see when the OS has booted should be the one I'm computing,
shouldn't it ?
Best regards & Thanks,
Eric Viseur
Etudiant Ingénieur Civil El
Hi again,
Sorry to bring back this topic from the dead, but I had to work on another
project for little while. So, I switched to UDK2014/VS2010 and used
DxeTpmMeasureBootLib as a reference for my PCR extend.
Good news is, I can now actually send data to the PCR8. I precompute my
hash using SHA-
