[PATCH v3 5/6] doc: board: nxp: Add Quickboot documentation

[Marek Vasut]

On 4/2/26 11:40 AM, Simona Toaca (OSS) wrote:

[...]

> +DDR QuickBoot flow
> +------------------
> +
> +Some NXP boards (which use OEI - iMX943, iMX95, iMX952 etc.) support saving

boards or SoCs ? I think SoCs ?

> +DDR training data (collected by OEI during Training flow) from volatile
> +to non-volatile memory, which is then available to OEI at next cold reboot.
> +OEI uses the saved data to run Quickboot flow and avoid training the DDR again.
> +This significantly reduces the boot time.
> +
> +The location of the qb data in NVM is a space left in the bootloader by
> +mkimage, with the size of 64K. The qb command searches for this space to
> +save the data. Thus, the NVM should also be a boot device.
> +
> +U-Boot provides no authentication for qb data, only its integrity
> +is verified via the CRC32. The authentication is done in OEI. With
> +the exception of iMX95 A0/A1, which use CRC32 as well for verifying
> +the data, the rest of the boards use ELE to verify the MAC stored

SoCs or SoC revisions ?

[...]

> +2. using qb command in U-Boot console (by enabling CONFIG_CMD_IMX_QB)
> +
> +- supports saving on the current boot device, or on another, specified device.
> +- if flashing via uuu, the command can be added in an uuu script (boot device needs to be specified)
> +- use 'qb erase' to force DDR re-training
> +- use for: saving qb data during flashing / controlling the NVM to save to / forcing re-training
> +
> +::
> +
> +        # To save/erase on current boot device
> +        => qb save/erase
> +
> +        # To save/erase on other boot device
> +        => qb save/erase mmc 0 # eMMC
> +        => qb save/erase mmc 1 # SD
> +        => qb save/erase spi   # NOR SPI

It would be good to have a way to instruct QB to save the data into 
backup location.