How Do i.MX8DualX Low-Power Isolation Settings Work?

Before anything else, confirm that the setting under review belongs to the i.MX8DualX System Controller Firmware (SCFW) pad configuration service. The four low-power isolation choices—OFF, EARLY, LATE, and ON—select an isolation policy; they are not alternate pad logic levels. Choose among them only after identifying the pad’s power domain, the external circuit’s powered state, and the required behavior during low-power entry and exit.

Initial Configuration Classification

1. Read the complete pad configuration applied by SCFW. Confirm that the targeted pad and its low-power isolation field are the ones actually programmed.
2. Determine whether the pad crosses a power boundary. Record which supply powers the i.MX8DualX pad and which supply powers the connected device.
3. Record whether each side remains powered, loses power, or changes state during the target low-power mode.
4. Identify the required pad condition during entry, the steady low-power interval, and exit. Do not move on until all three intervals have defined acceptance criteria.

Power-Boundary Timing

Isolation separates pad behavior from a domain that is entering or leaving a low-power state. Its purpose is to prevent an active side of an interface from interacting incorrectly with a side that is unpowered, unstable, or not yet restored. The required policy therefore follows the power sequence, not the signal’s normal active-high or active-low meaning.

EARLY and LATE are sequenced policies associated with different points in the SCFW-managed low-power transition. The labels alone do not define the electrical instant at the pin. Read the applicable SCFW pad-setting description and the platform power sequence to identify which transition boundary each label represents. Select the policy whose isolation interval covers the unsafe supply overlap.

OFF and ON represent the non-sequenced endpoints of the policy choice: isolation disabled or enabled. Before using either, confirm how the documented state affects the pad across entry, residency, and exit. A permanently enabled isolation choice can block required communication; a disabled choice can expose an unpowered boundary.

Applied-Setting Checks

1. Inspect the pad entry used by the running SCFW build. Record the selected value exactly as OFF, EARLY, LATE, or ON.
2. Check for another initialization path that reconfigures the same pad. The last applied configuration governs the observed behavior, so a correct source entry does not prove the running state.
3. Confirm that the tested power transition is controlled by SCFW and that the pad’s domain actually changes state. If the domain never enters the expected low-power condition, the isolation branch may not execute.
4. Compare the running SCFW build with the configuration source used for the test. Do not move on until the loaded image and reviewed configuration belong to the same build.

Controlled Transition Test

1. Attach measurement channels to the pad supply, the external-device supply, and the affected pad signal. Add a low-power entry or firmware event marker if the platform exposes one.
2. Capture normal operation first. Confirm the expected pad level and that neither endpoint is already unpowered.
3. Command the target low-power transition and record the order in which the supplies change, the pad becomes isolated, and the interface stops responding.
4. Capture wake-up in the same acquisition. Record when supplies stabilize, isolation releases, and valid signaling resumes.
5. If the waveform shows the pad driven while either endpoint is unpowered, choose the policy that moves isolation ahead of that interval. If isolation blocks a signal needed to complete entry, move it to the later documented phase.

A supply waveform decides whether the problem is sequencing or configuration. A pad that changes at the intended phase while the external supply remains unsafe points to the wrong isolation policy. A pad that never changes despite a confirmed domain transition points to an unapplied setting, a later rewrite, or testing the wrong pad.

Resolving Configuration Procedure

1. Use OFF only when the interface may remain connected throughout the transition and measurements show no unpowered-side drive, contention, or unwanted current path.
2. Use EARLY when the documented early phase must isolate the pad before the unsafe power overlap begins. Confirm on the waveform that isolation precedes the first supply boundary.
3. Use LATE when the interface must remain available through the early phase but must be isolated before the later boundary. Confirm that required entry signaling completes before isolation.
4. Use ON when the pad must remain isolated for the configured operating context. Confirm that the interface is not required while this policy is active.
5. Rebuild and load SCFW, then read back or otherwise verify the applied pad configuration before repeating the power transition.

Verification Criteria

Run repeated entry and wake cycles while observing the same channels. A passing result has no driven interval into an unpowered endpoint, no conflicting pad drive, no unexpected supply current change, and no required transaction cut off by isolation. On wake, the pad must remain isolated until both sides are ready, then return to valid signaling without a false transition that affects the connected circuit.

Repeat the test from every operating state that can precede the target low-power mode. Pad direction, output value, and external pull networks can change the electrical result even when the isolation policy is unchanged. Treat a single successful waveform as validation of that initial state only.

Frequently Asked Questions