/
i.MX 8X Bootcontainer

i.MX 8X Bootcontainer

Owned by Collaboration Admins
Last updated: Aug 26, 2024
2 min read

A Boot image consists of a primary boot container set, or a primary boot container set
and a secondary boot container set. This section describes the structure of the boot image,
the primary and secondary boot container data structure, and what is required to be
included in each boot container. A boot image consists of:

  • Primary Boot Container Set

  • Optional Secondary Boot Container Set

Every Container Set includes two containers. One container (SECO container) for SECO
FW , and another container (SCU container) for SCU FW (necessary), AP IPL (optional),
CM4 FW (optional), and DDR initialization image (optional).

Please note that the Primary Container Set is the one with the newer "SW version" and is
not necessarily the 1st one in the boot device. Please refer to the section Terms for more
information.

Primary Boot Container Set

The images that will be loaded as part of the boot process are stored in containers. A
container can contain one or multiple images, as blocks of data specifying the load
address, target address, etc.
The Primary Boot Container Set will at the very least, contain two containers. The first
container will only contain the SECO firmware image. This container is NXP signed, and
NXP provided. The second container can contain multiple images and will typically have
the following images:

  • SCU FW Image

  • DDR Initialization Image

  • M4 FW Image(s)

  • FW Image(s) for the Cortex A processing domain

The second container, in every container Set, is signed by the customer.

Secondary Boot Container Set

The Secondary Boot Container Set is a copy of the Primary Container Set. ROM will
always try to load the Primary Container Set first and if the Primary Container Set fails
SECO authorization or other failures occur (e.g. read error), ROM will then attempt to
load the Secondary Container Set.