NOR/QSPI boot failure impact on select i.MX device Silicon Revisions

[#1]

Background:

Certain i.MX device silicon revisions are affected by boot failures, when the boot device selected is External Interface Module (EIM) NOR or QSPI and the boot image targets internal OCRAM. The proposed workaround is for the boot image to not target OCRAM. These errata do not have any security implications.

Impacted i.MX devices:

	Silicon Rev	ERR011121	ERR011112	Comments
i.MX 6DualPlus/QuadPlus	1.1	Impacted*	Not Impacted	QSPI boot not supported
i.MX 6Dual/Quad	1.6	Impacted*	Not Impacted	QSPI boot not supported
i.MX 6DualLite/Solo	1.4	Impacted*	Not Impacted	QSPI boot not supported
i.MX 6SoloX	1.4	Not Impacted	Impacted*	Both QSPI + EIM NOR impacted
i.MX 6SoloLite	1.4	Impacted*	Not Impacted	QSPI boot not supported
i.MX 6UltraLite	1.2	Impacted*	Impacted*	Included in Latest Chip Errata Document
i.MX 6ULL	1.1	Impacted*	Not Impacted	Included in Latest Chip Errata Document
i.MX 7D/Solo	1.3	Not Impacted	Impacted*	Both QSPI + EIM NOR impacted

*Only Silicon Revisions listed are impacted by this errata

Errata:

The following errata will be included in the next revisions of the respective Chip errata documents.

ERR011121: System Boot: EIM NOR boot failure when the boot image targets OCRAM

Description:

A boot image corruption can result in a boot failure for a EIM NOR boot device under specific conditions as described below. The boot failure only occurs if all conditions below are satisfied.

Conditions:

There are four specific conditions that result in this boot failure:

1. i.MX device with the exact Silicon Revision listed in the impacted table above

2. A EIM NOR boot device is used

3. The device is in a security enabled configuration (SEC_CONFIG[1] eFUSE is programmed)

4. The boot image start address (specified in boot data) targets internal memory on Chip RAM (OCRAM) space.

Projected Impact:

EIM NOR  boot failure and possible entry into Serial Downloader mode.

Workarounds:

Since the boot failure only occurs when the boot image start address targets OCRAM space the recommended workarounds are for users to ensure the EIM NOR boot image runs from DDR or executes in place (XIP) and not target OCRAM.

Proposed Solution:

No fix planned.

Linux BSP Status:

Workaround not implemented in BSP: functionality where the erratum may manifest itself is not used. 

Users will need to apply the proposed workaround when creating the boot image.

_____________________________________________________________________________________________________________________

ERR011112: System Boot: QSPI/EIM NOR boot failure when the boot image targets OCRAM

Description:

A boot image corruption can result in a boot failure for a QSPI/EIM NOR boot device under specific conditions as described below. The boot failure only occurs if all conditions below are satisfied.

Conditions:

There are four specific conditions that result in this boot failure:

1. i.MX device with the exact Silicon Revision listed in the impacted table above

2. A QSPI/EIM NOR boot device is used

3. The device is in a security enabled configuration (SEC_CONFIG[1] eFUSE is programmed)

4. The boot image start address (specified in boot data) targets internal memory on Chip RAM (OCRAM) space

Projected Impact:

QSPI/EIM boot failure and possible entry into Serial Downloader mode.

Workarounds:

Since the boot failure only occurs when the boot image start address targets OCRAM space the recommended workarounds are for users to ensure the QSPI/EIM NOR boot image runs from DDR or execute in place (XIP) and not target OCRAM.

Proposed Solution:

No fix planned.

Linux BSP Status:

Workaround not implemented in BSP: functionality where the erratum may manifest itself is not used.

Users will need to apply the proposed workaround when creating the boot image.