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

[Marek Vasut]

On 3/16/26 9:15 AM, Simona Toaca (OSS) wrote:

> +After successful saving, U-Boot clears the data in volatile memory so
> +that qb check fails at next reboot and the NVM isn't accessed again.
> +
> +There are 2 ways to save this data (both can be enabled):

Replace () with , .

> +1. automatically, in SPL (by enabling CONFIG_SPL_IMX_QB)
> +
> +- this will save the data on the current boot device (e.g. SD)
> +- other configs specific to the boot device need to be enabled (CONFIG_SPL_MMC_WRITE for saving to eMMC/SD)
> +- use for: automating qb save / saving qb data if using Falcon mode (skipping U-Boot proper)
> +
> +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 for: saving the qb data during flashing / controlling the NVM to save to
> +
> +::
> +
> +        # 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

Can QB data be saved to arbitrary SPI NOR ?

Looking at this, why can this QB not use the same interface to select 
arbitrary block storage device/partition/... that e.g. FS_GENERIC does use ?