On 3/10/26 12:54 PM, Simona Toaca (OSS) wrote:
From: Simona Toaca <[email protected]>
This patch series adds support for saving DDR training
data to non-volatile memory on iMX94 and iMX95 platforms.
The purpose is running DDR Quickboot flow on next reboot.
The process is as follows:
- OEI runs Training flow for the DDRPHY
- OEI saves the data from training to volatile memory
- U-Boot can then save it to non-volatile memory (e.g. SD)
- OEI loads the data from NVM at cold reboot and runs Quickboot flow
By skipping training, a much lower boot time is achieved.
How does this interact with authenticated boot ? I wonder if, in case
the entire bootloader stack is authenticated, the attacker can tamper
with the saved QB data (which do not seem to be authenticated) and cause
bitflips to occur in DRAM, which could then allow them to bypass
authentication in follow up stages which execute from DRAM ?
Are the QB data protected/authenticated in any way against tampering ?
