A supposedly off board may show a small supply voltage, illuminated LED or erratic startup because an external signal feeds an unpowered domain. The source can be a debugger, communications adapter or another board that remains active. Treat every cross-domain signal as a possible power path until its behavior is established.
Map the power combinations
List the independently powered domains and connected interfaces. For each supported combination, identify outputs that may remain high while their destination supply is absent. Include pullups and control lines, not only the main data signals. A weak-looking pullup can still alter an unloaded rail.
Texas Instruments’ powered-off protection brief describes how signal switches with suitable protection prevent back-power conditions that can occur in unprotected arrangements. The relevant feature and limits must be verified for the selected component and pins; a general label such as ‘level shifter’ does not establish powered-off isolation.
Read limits under the actual supply condition
Check input voltage limits when supply is zero, leakage specifications, output behavior and any required enable state. Distinguish partial-power-down support from ordinary high impedance while powered. A disabled device can behave differently after its own supply disappears.
Follow the destination of any injected current. It may charge a supply capacitor or energize other devices on the rail. A regulator that normally supplies current may not control the rail when current enters from another source. Avoid assuming that a regulator’s off state provides a discharge path.
Measure without creating the symptom
Remove optional connections and add them back systematically while monitoring the affected rail. Record which signal state produces the voltage and whether the source is current limited. Instrument and debugger connections can change the result, so preserve the exact setup.
A high impedance meter reading alone does not quantify the available current. Use an appropriate controlled measurement method to characterize the path without exceeding component limits. Compare observations with the documented I/O structure and leakage expectations.
Choose a defined isolation strategy
Possible approaches include coordinated sequencing, a buffer or switch with appropriate powered-off behavior, or redesigning pullup ownership. A series resistor can limit current but does not necessarily prevent the destination rail from rising. Verify both electrical limits and the required system state.
Test startup, shutdown, hot connection where supported and recovery after one domain loses power. Confirm that the fix does not break signal thresholds or timing during normal operation. Keep the power-state matrix and measured rail behavior with the schematic review so future interface changes do not quietly reintroduce the path.
Move from reading to a build-ready project
Use the fabrication and assembly checklists to prepare drawings, production files and test requirements.
Open the DFM checklist