U-Boot Bootflow Arguments: A Bare Flag, an Empty Value and a Deleted Parameter Differ
Distinguish bare flags, empty values and deletion, then inspect duplicate parameters and synchronized bootargs state.
-
-
U-Boot ADC Single: The Same Environment Variable Can Contain Raw Counts or Microvolts
Prevent a voltage threshold from consuming raw ADC counts after the command silently falls back from conversion.
-
U-Boot Environment Callbacks: Verify the Bound Function, Not Just the Association String
Separate linked callback availability, existing-variable three-pass rebinding and acceptance of a later overwrite.
-
U-Boot Event Spies: A Static Handler Error Can Hide an Event from Dynamic Observers
Explain synchronous static-before-dynamic dispatch, short-circuit errors and visibility boundaries for missing event observations.
-
U-Boot Bloblist Handoff: Successful Initialization Can Replace Rejected State
Separate successful bloblist container initialization from preservation and provenance of incoming tagged records.
-
U-Boot I2C Offset Width: An Explicit Suffix Changes the Next Unsuffixed Read
Track address-length suffixes as persistent per-chip driver-model state rather than per-transfer temporary formatting.
-
U-Boot DFU: The Flush Callback Is Not a Successful-Commit Notification
Keep DFU lifecycle callback occurrence separate from the medium-flush return value and update acceptance decision.
-
U-Boot Environment Flags: Write-Once and Change-Default Check Different State
Choose environment access policy according to absent creation versus replacement of a compiled default, without inferring a write counter.
-
U-Boot dtoc: A Second Node Can Change the First Node’s Generated Platform Data
Explain cross-node generated-structure widening and why padded or omitted fields cannot recover original property presence or counts.
-
U-Boot mtest: Check the Accumulated Error Count as Well as the Final Status
Prevent a later clean RAM-test pass from hiding accumulated errors when automation uses only the final command status.
