SI/PI Foundations — The Physics Behind Every Engineering Decision

Standalone SI/PI Learning Path · Physics → Evidence → Diagnosis → Decision

SELF-PACED
Standalone Async · Module 0 · Foundation · Before You Choose Any Analysis

SI/PI starts with one question:
where does current flow, and what impedance does it encounter?

On a real PCB, signals and power do not move through ideal wires. Time-varying current propagates through distributed geometry, return paths, packages, vias, planes and dielectric materials. Those structures create resistance, inductance, capacitance, coupling and delay. SI/PI engineering is the process of predicting when those physical effects become large enough to consume voltage, timing or noise margin — and deciding what evidence is needed before changing the design.

The Foundation PrincipleA PCB is a distributed electromagnetic structure, not an ideal schematic connection. The useful mental model is: excitation → physical structure → impedance/coupling → observable signature → engineering decision.
ExcitationEdge rate, current step, pattern, aggressor activity
StructureTrace, via, plane, package, connector, PDN
PhysicsR/L/C, fields, delay, loss, coupling, resonance
EvidenceWaveform, TDR, Z(f), S-parameters, eye, rail noise
DecisionAccept, investigate, change geometry, damping or PDN
What you will be able to decide
1
When interconnect geometry matters
Use edge time, flight time and electrical length rather than clock frequency alone.
2
Which physical mechanism fits a symptom
Separate reflection, loss, crosstalk, shared return, PDN droop and measurement artefacts using discriminating evidence.
3
What an analysis can actually prove
State model boundary, stimulus, corner, observation point and assumptions before trusting the result.
4
How to verify a fix
Predict which measurable feature should move when the suspected mechanism is changed.
What this module is not
NOT A TOOL TUTORIALDecision framework first

You are not learning a sequence of buttons in one simulator. The same physical reasoning applies whether the analysis is performed in HyperLynx, SIwave, Sigrity, ADS, a field solver, SPICE, or a measurement environment.

SELF-PACED METHODPredict before reveal

For every worked case, write the result you expect before revealing the explanation. If the observed evidence does not match the prediction, the correct engineering response is to revisit the hypothesis or model — not to force the conclusion.

Why boards fail when schematics are correct — the gap between logical connectivity and physical behaviour

A schematic answers what is connected. SI/PI asks how that connection behaves in space and time. Many prototype failures appear only after geometry, package, return path, material and switching conditions are included.

IDEAL CONNECTIONUseful abstraction, incomplete physics

A schematic wire has no delay, impedance discontinuity, mutual coupling or distributed loss. A real PCB interconnect has all of them. At sufficiently slow transitions the ideal-wire approximation is excellent; as electrical length grows, the approximation loses information that the receiver actually sees.

DISTRIBUTED PARASITICSGeometry creates the circuit

Vias, pads, antipads, planes, packages and connectors contribute distributed R, L and C. Their values are not universal constants: they depend on geometry and the return path. Treat handbook numbers only as rough screening estimates; use extracted or measured models when the structure is electrically significant.

RETURN CURRENTThe signal path is a loop

At high frequency, return current tends to follow the route that minimises loop inductance, normally close to the signal on its reference conductor. Plane splits, layer changes without a nearby return transition, voids and connector discontinuities can force a larger loop and increase reference movement, coupling and radiation.

ELECTRICAL LENGTHThere is no single frequency where “SI starts”

Distributed behaviour depends on the relationship between interconnect flight time and signal transition time. A useful screening method is to estimate the edge knee frequency and wavelength, but λ/10 is a heuristic — not a physical cliff. Near the boundary, the correct decision depends on allowable reflection, topology and noise/timing margin.

/* Screening estimates */ f_knee ≈ 0.35 / t_r v_p ≈ c / √ε_eff λ_knee = v_p / f_knee t_flight = L / v_p Example: t_r = 1 ns, ε_eff = 4 f_knee ≈ 350 MHz v_p ≈ 150 mm/ns λ_knee ≈ 429 mm λ/10 ≈ 43 mm If L is comparable with λ/10 — or t_flight is a meaningful fraction of t_r — investigate distributed effects.
Decision, not commandmentDo not write “all traces longer than X must be simulated.” Write: “this trace is electrically long enough that reflection and return-path behaviour may consume the available margin; therefore I need distributed analysis or measurement.”
Transmission-line intuition — waves, impedance, reflections and delay

A useful transmission-line model should let you predict the sign, timing and approximate cause of a waveform disturbance before a solver shows it.

WAVEGUIDE VIEWEnergy is guided by the conductor/reference geometry

The signal is an electromagnetic wave guided by the trace and its return conductor. The field occupies the dielectric around the conductors; copper loss, dielectric loss, reference discontinuities and nearby conductors all modify that guided wave.

CHARACTERISTIC IMPEDANCEV/I ratio of a travelling wave

Z₀ is a property of the cross-section and materials, not the receiver resistance. Width, copper thickness, height to reference, dielectric properties and solder mask can all shift it. A closed-form equation is useful for intuition; fabrication field-solver values are preferred for final geometry.

Example screening equation for microstrip: Z₀ ≈ (87/√(εr+1.41))·ln(5.98H/(0.8W+T)). With H=100 µm, W=150 µm, T=35 µm and εr=4.2, the estimate is ≈50 Ω. Treat the equation as an approximation, not a fabrication guarantee.

REFLECTION COEFFICIENTPredict polarity from impedance change

At a boundary, Γ=(Z₂−Z₁)/(Z₂+Z₁). Γ>0 gives a same-polarity reflected voltage; Γ<0 gives opposite polarity; Γ=0 gives no reflection at that boundary. Open and short are useful limiting cases, while real CMOS inputs and packages are frequency dependent.

/* Reflection limits */ Matched load: ZL = Z0 → Γ = 0 Open load: ZL → ∞ → Γ → +1 Short load: ZL = 0 → Γ = −1 /* Timing */ t_flight = L / v_p t_rt = 2·t_flight
DELAYED REFLECTIONSUse timing to locate the mechanism

At the receiver, the first reflection occurs when the incident wave reaches the load. At the source, the reflected wave returns after the round-trip delay. Multiple impedance changes produce multiple echoes. This is why transient waveform timing and TDR location can be combined to isolate a discontinuity.

Important distinctionA repeated step/edge “bounce” has spacing set by propagation delay. A physical structure can also have resonant frequencies. These are related views of the same distributed system, but do not assume every ringing waveform is a simple lumped RLC resonance or every resonance is visible as equally spaced bounces.
PDN intuition — DC resistance, dynamic impedance and shared inductance

Power integrity is not “does the regulator output the right voltage?” It is whether the voltage at the device pins stays inside its allowed window for the actual current waveform and current-return geometry.

DC VIEWSource-to-load resistance budget

At steady load, ΔV≈I·R. The resistance includes planes, neck-downs, vias, connectors, package paths and return current. Allocate source tolerance, board drop and load tolerance explicitly; do not assume the entire datasheet voltage range belongs to the PCB.

DYNAMIC VIEWCurrent must come from the lowest-impedance path available at that timescale

Fast load change is limited by inductance: V=L·dI/dt. The effective source of current changes with frequency among regulator/output network, bulk storage, board capacitors, plane/package paths and on-die capacitance. The crossover frequencies are design-specific — not fixed decade boundaries.

TARGET IMPEDANCEA screening bound derived from allowed ripple

Z_target≈ΔV_allowed/ΔI is useful for designing and reviewing a PDN. Keep the load-point impedance below the target over the frequency range where the relevant current spectrum has energy. A peak above target is a risk only if the load event excites that frequency strongly enough.

/* PDN screening relations */ R_budget ≈ ΔV_DC / I_DC Z_target ≈ ΔV_dynamic / ΔI_transient V_L = L_shared · dI/dt Example: allowed transient deviation = 30 mV current step = 6 A Z_target ≈ 5 mΩ Always state where ΔV and ΔI were defined.
SSN / GROUND BOUNCEShared current path converts di/dt into reference movement

When many I/Os switch, their current waveforms add through shared package, via and plane inductance/resistance. The resulting rail/ground movement depends on edge rate, simultaneous activity, package topology and return path. The general relation is frequency-domain ΔV(f)=Z_PDN(f)·ΔI(f), plus local shared-inductance effects. A single “N×I×Z at f_switch” number is only a rough toy model.

Frequency ownership — think qualitatively, verify quantitatively
RegionLikely dominant path
LowRegulator control and bulk network
MidBoard capacitors + mounting/plane inductance
HighPackage and on-die network increasingly dominate
Actual crossovers can differ by orders of magnitude. Use the impedance plot and physical model rather than fixed frequency bands.
Electromagnetic coupling — distinguish field coupling from shared-return and PDN coupling

Crosstalk is a distributed field-coupling problem. The most useful design variables are spacing, coupled length, reference-plane distance, layer relationship, edge rate and termination. There is no universal “3W solves it” rule.

CAPACITIVE COUPLINGMutual electric field

A changing aggressor voltage drives current through mutual capacitance: i≈C_m·dV/dt. More field intercepted by the victim means more coupling. Bringing the reference plane closer can confine more field to the aggressor-reference pair and reduce victim coupling.

INDUCTIVE COUPLINGMutual magnetic field

A changing aggressor current couples through mutual inductance: v≈M·dI/dt. Geometry, return paths and coupled length set the mutual coupling. Faster edges generally increase both capacitive and inductive excitation.

NEXT & FEXTEven/odd-mode propagation determines the details

Near-end crosstalk is present in both microstrip and stripline. Far-end crosstalk depends on the difference between even- and odd-mode propagation. In an ideal homogeneous symmetric stripline, first-order FEXT can cancel; real asymmetry, loss and discontinuities make non-zero FEXT possible. In microstrip, differing modal velocities generally make FEXT more visible.

SPACING & COUPLED LENGTHNo universal inverse-square law

Crosstalk falls as spacing increases and rises as parallel coupled length grows, but the exact relationship depends on trace width, height to reference, stackup and termination. Rules such as 3W are screening heuristics. For a critical victim, extract or simulate the actual geometry and compare induced voltage/timing against the receiver margin.

GUARD TRACE / VIA FENCEUseful only when its return connection is electrically effective

A guard conductor that is poorly tied to reference can itself become a coupled resonant structure. Stitching pitch should be electrically small over the relevant bandwidth and selected from the geometry/field problem — not from a universal λ/4 rule. Often, simply increasing spacing or using a closer solid reference is cleaner than inserting a guard trace.

Do not diagnose “crosstalk” from activity correlation aloneIf a victim fails only when a neighbouring bus switches, direct field coupling is one hypothesis. Shared return impedance, ground bounce and supply modulation can produce the same activity correlation. Use an aggressor on/off comparison together with rail/ground observation to separate them.
Signal loss mechanisms — conductor loss, dielectric loss, dispersion and channel memory

Loss is frequency dependent, so it does more than reduce amplitude. When higher-frequency components are attenuated or delayed differently from lower-frequency components, the received edge changes shape and one symbol can influence the next.

CONDUCTOR LOSSSkin effect and current crowding

For copper, skin depth δ≈√(ρ/(πfµ)). Once skin depth is small compared with conductor thickness, AC resistance rises roughly with √f. Surface roughness and current crowding can further increase high-frequency loss. Exact attenuation depends strongly on trace geometry and roughness model, so avoid generic dB/cm numbers.

DIELECTRIC LOSSLoss tangent converts field energy to heat

For a low-loss TEM-like line in a homogeneous dielectric, a useful estimate is α_d≈πf√ε_r·tanδ/c Np/m. Microstrip uses an effective dielectric participation, and real laminate Dk/Df vary with frequency and test method. Use vendor frequency-dependent data for sign-off.

Worked estimate · dielectric loss only

At 5 GHz with εr=4.2 and Df=0.020: α_d≈2.14 Np/m≈18.6 dB/m≈0.186 dB/cm. Over 100 mm, dielectric loss alone is therefore ≈1.86 dB — not 18.6 or 37 dB. Total channel loss must still include conductor/roughness, vias, connectors, packages and other discontinuities.

/* Copper skin depth */ δ ≈ √(ρ/(πfµ₀)) 100 MHz → ≈ 6.6 µm 1 GHz → ≈ 2.1 µm 10 GHz → ≈ 0.66 µm /* Dielectric-loss screening estimate */ α_d ≈ πf√ε_r·Df/c [Np/m] dB/m = α_d × 8.686
ISILoss creates channel memory

If the channel attenuates high-frequency content more strongly, transitions become slower and the received level depends on previous symbols. That is inter-symbol interference. Long-run and pseudo-random patterns can reveal different channel memory than a simple 1010 pattern; the correct stress pattern is interface-specific.

Material choice is a budget decisionDo not declare “FR-4 cannot do X Gb/s” from data rate alone. Decide from total insertion-loss/return-loss budget, channel length, geometry, copper roughness, connectors/vias, transmitter/receiver capability and any supported equalization.
Models, solvers and boundaries — what an analysis actually computes

The decision framework is tool-independent. A solver answers the mathematical problem you give it; it does not know whether your stackup, package, load, corner or observation point matches the hardware.

TRANSIENT / TIME DOMAINUse when waveform shape and event timing matter

Combines active I/O models with distributed interconnect/network models to calculate voltage/current versus time. Useful evidence includes overshoot, settling, threshold crossings, propagation delay, pattern dependence and eye construction.

FREQUENCY DOMAINUse when transfer, reflection or impedance versus frequency matters

Computes quantities such as Z(f), S11/S21, resonances and coupling across frequency. It is the natural view for PDN impedance and broadband channel/discontinuity characterisation.

2.5D / 3D EMUse when geometry determines fields in ways simple circuit models miss

Useful for via fields, connector launches, packages, cavities and other complex transitions. Higher fidelity is only useful if port definitions, material data, meshing and boundary conditions are correct.

MODEL-BOUNDARY HIERARCHYRecord what is inside and outside

Materials: Dk/Df, copper conductivity/roughness and frequency dependence.

Geometry: as-built widths, heights, vias, reference planes, connector/fixture.

Device models: correct pin, I/O standard, package, PVT/IBIS corner, receiver load.

Experiment: stimulus, activity, termination, observation point, thresholds, bandwidth and environmental condition.

Before reading any resultWrite the three assumptions most likely to change the conclusion. If you cannot identify them, you are not yet ready to use the result as design evidence.
Analysis and evidence matrix — ask the environment for the quantity it can actually provide

This bootcamp does not teach button sequences. It teaches the analysis category, model boundary and evidence required for the engineering question.

Engineering questionAnalysis / evidence typeWhat the result can support
Will a topology ring or violate threshold?Pre-layout distributed transient analysisReflection timing, overshoot/undershoot, termination sensitivity and topology trade-off.
What does the routed board do?Post-layout extracted interconnect + transient/frequency analysisEffect of actual lengths, layers, coupling, vias and transitions.
Where is steady-state rail voltage lost?DC drop / current-density analysisIR drop, current crowding and resistive bottlenecks.
At which frequencies is the PDN vulnerable?Frequency-domain impedance analysisZ(f), resonance/anti-resonance and target-impedance margin.
How does a connector/via/channel transmit and reflect energy?S-parameter / EM extractionS11/S21/coupling and broadband discontinuity behaviour at defined ports.
What sampling margin does a model predict?Transient/statistical eye or timing analysisModel-based voltage/time margin under stated stimulus, corner and jitter assumptions.
What did the physical board produce?Oscilloscope / VNA / TDR / rail measurement as appropriateMeasured waveform, network response, impedance or timing at a defined physical reference plane.
Is the model credible for this decision?Simulation-to-measurement correlationAgreement of features and sensitivity under matched conditions; residual mismatch and uncertainty documented.
Before accepting simulation evidence
Model boundary is explicit
Observation point is electrically defined
As-built geometry/material assumptions are known
Stimulus, corner and loading match the question
Before accepting measurement evidence
Probe/fixture/loading are characterised
Bandwidth, filtering and thresholds are recorded
Stimulus and operating condition are reproducible
Reference plane matches the intended comparison
Worked engineering case · Model → evidence → root cause → correction
The simulated eye passes, but the measured eye fails
A 1.6 Gb/s single-ended interface is simulated after layout. The model predicts comfortable eye margin at the receiver. The first board, measured at the same nominal receiver location, shows reduced eye height, narrower eye width and intermittent mask hits. The wrong response is to change termination immediately. The correct response is to establish whether simulation and measurement are describing the same electrical system.
Simulation resultPost-layout eye passes with margin. Nominal stackup, ideal connector transition and the selected IBIS corner were used.
Measurement resultMeasured eye is visibly smaller and intermittently violates the mask. TIE spread is wider than expected.
Initial symptom

Functional errors appear only at the highest data rate. Lowering the rate removes the failure.

Competing explanations

Wrong stackup, omitted connector loss, probe loading, stimulus mismatch, fabrication variation or an incomplete driver / receiver model.

Decision objective

Identify which mismatch is large enough to explain the measured eye closure before modifying the board.

1

Freeze the comparison conditions

Write down the conditions for both results. The team aligns the observation point, data rate, bit pattern, output drive, slew setting, termination, supply voltage, temperature, scope bandwidth, filtering and reference threshold. The measured TIE histogram is generated in the oscilloscope analysis software from acquired edge timing.

2

Check the measurement path before blaming the board

  • Repeat the capture with the specified low-capacitance active probe.
  • Apply the characterised fixture / cable de-embedding file.
  • Confirm that bandwidth limiting and clock-recovery settings match the intended compliance or engineering method.
  • Move the probe only after recording the exact physical observation point.

The eye improves slightly, but the failure remains. Probe loading is a contributor, not the root cause.

3

Audit the model against the as-built board

  • The simulation used the release stackup; the fabricator's as-built report shows a larger dielectric height on the signal layer.
  • The connector was represented as an ideal through-connection; its launch and via field were not included as an S-parameter block.
  • The receiver observation point in simulation was at the PCB pad, while measurement included the connector, fixture and probe path.
4

Use independent evidence to isolate the root cause

TDR shows a local impedance discontinuity at the connector launch. The as-built stackup recalculation shows that the routed trace is below the intended impedance. A VNA or validated connector model shows additional insertion loss and return loss that the original simulation never included.

Actual root cause The passing simulation represented a different channel from the fabricated and measured channel. The primary mismatch was the omitted connector launch model, compounded by an as-built stackup change that shifted trace impedance. The measurement setup added a smaller, secondary loading effect.
5

Correct the model, then correct the design

  • Replace nominal geometry with the as-built stackup and actual routed dimensions.
  • Insert the connector / launch S-parameter model at the correct reference planes.
  • Include package and receiver loading at the intended observation point.
  • Use the same stimulus and corner conditions as the bench test.
  • For the next board spin, retune the trace geometry and improve the connector launch / return-via structure.
6

Verify correlation instead of declaring victory from one screenshot

The updated simulation now reproduces the measured eye shape and the location of the dominant degradation. After the layout correction, both simulation and measurement show improved eye height and width, and the intermittent mask hits disappear under the matched test conditions.

Before correctionModel passes; board fails. The two results use different channel boundaries and incomplete physical data.
After correctionModel and measurement describe the same channel. The corrected design passes in both environments with traceable margin.
Reusable correlation checklist

Before comparing any simulated and measured waveform, confirm all of the following:

Same electrical observation point and reference plane
Same data rate, pattern and edge / slew setting
Same termination and receiver loading
As-built stackup and routed dimensions
Connector, via, package and fixture included or de-embedded
Same voltage, temperature and process / model corner
Known scope bandwidth, filtering and clock recovery
Result uncertainty and residual mismatch documented
The engineering lesson Correlation is not forcing simulation and measurement to look identical. It is making their boundaries and assumptions explicit, explaining the remaining difference, and proving that the model is accurate enough for the decision being made.
Failure pattern diagnosis — signatures generate hypotheses, not verdicts

Real hardware symptoms are rarely unique to one mechanism. Use the pattern to rank hypotheses, then choose a controlled experiment that makes those hypotheses predict different outcomes.

PATTERN 1Fails only at high temperature

Possible mechanisms: slower driver/receiver timing, higher copper resistance, regulator/PDN drift, material changes or component tolerance. Discriminator: separate timing margin, steady DC rail drop and dynamic rail disturbance under the same temperature.

PATTERN 2Errors rise with bus activity

Possible mechanisms: direct crosstalk, SSN/shared return, PDN droop, clock/reference modulation or thermal loading. Discriminator: aggressor on/off plus simultaneous rail/ground/timing observation.

PATTERN 3Quiet victim glitches when neighbour switches

Strong hypothesis: crosstalk — but not proof. Shared reference movement can produce the same correlation. Change spacing/coupled length in the model or switch the aggressor while monitoring local ground/rail to separate mechanisms.

PATTERN 4Failure concentrated near one data-rate region

Possible mechanisms: via/connector resonance, channel notch, clock spur, equalization-mode boundary or protocol configuration. Discriminator: frequency response and a geometry/parameter sweep. A resonant mechanism should move when electrical length changes.

PATTERN 5Bench passes, long-term reliability fails

Repeated overstress is one possible mechanism, but do not infer it from elapsed time alone. If failure analysis shows clamp degradation, correlate measured/simulated overshoot and clamp current with absolute-maximum/transient ratings and environmental stress. Reliability conclusions require device-specific qualification evidence.

Diagnostic disciplineA useful failure signature narrows the hypothesis list. A root cause is established only when an independent change moves the predicted evidence in the expected direction.
Standalone study map — how to use this module without an instructor

This foundation module supplies the physical intuition that every later SI/PI decision depends on. Do not treat equations as isolated formulas. For each topic, connect physical mechanism → observable signature → analysis method → design lever. That chain is the core skill used throughout this learning path.

Prerequisite
Basic circuits, impedance, PCB stackup familiarity
Study mode
Read → predict → reveal → apply → quiz
Recommended depth
Concept mastery, not tool memorisation
Exit criterion
You can explain why a board fails before naming a simulator
Decide when a net is electrically long. Use edge rate and propagation delay rather than clock frequency alone.
Explain reflections physically. Predict the sign of a reflection from an impedance change.
Reason about return current. Identify where loop inductance increases and why plane discontinuities matter.
Connect SI and PI. Explain how PDN impedance and simultaneous switching can corrupt signal timing and voltage.
Study rule: Before revealing any worked answer, write one sentence predicting the waveform, impedance or timing signature you expect. The prediction is more valuable than memorising the final number.
Edge rate, electrical length and return path — three checks before choosing SI analysis
EDGE RATEWhy a slow clock can still launch a fast electromagnetic event

Repetition rate tells you how often an edge occurs. Rise/fall time tells you how quickly the voltage/current changes during each edge. The faster the transition, the wider the useful spectrum and the more strongly discontinuities and coupling are excited.

Useful edge-bandwidth estimate
f_knee ≈ 0.35 / t_r 500 ps edge → f_knee ≈ 700 MHz 200 ps edge → f_knee ≈ 1.75 GHz This is a reasoning estimate, not a compliance bandwidth.
FLIGHT TIMEAsk whether the receiver can “know” the source has finished switching

If a wave can travel a significant distance while the source transition is still occurring, voltage and current are no longer uniform along the route. The interconnect must be treated as distributed. Compare t_flight with t_r, and use λ/10 only as a screening heuristic.

Propagation estimate
v_p ≈ c / √ε_eff t_flight = L / v_p t_round-trip = 2L / v_p
RETURN PATHGeometry under the trace is part of the signal

A layer transition is not complete until the return current can transition too. Signal vias without nearby reference vias can enlarge the loop. Crossing a plane split can be worse because the return current has no local continuous path at all.

Predict before reveal · 80 mm digital line

A 3.3 V GPIO toggles at 20 MHz, but the buffer rise time is 400 ps. The route is 80 mm long and ε_eff ≈ 4. Would you screen this as lumped or distributed?

Distributed effects deserve analysis. f_knee ≈ 875 MHz, v_p ≈ 150 mm/ns, so λ_knee ≈ 171 mm and λ/10 ≈ 17 mm. The 80 mm line is well beyond that screening length, and its one-way delay is about 533 ps — longer than the 400 ps edge. The 20 MHz repetition rate does not remove reflection risk.
The board as one coupled electromagnetic system — where SI and PI meet

Separating SI and PI is useful for analysis, but the hardware does not know those labels. Signal current closes through the PDN, switching outputs inject current into power and ground structures, and supply motion changes transmitter/receiver behaviour.

MechanismPhysical causeWhat you may observeBest first evidence
ReflectionImpedance discontinuityOvershoot, undershoot, ringing, multiple edgesTransient + TDR
CrosstalkElectric/magnetic field couplingVictim noise correlated with aggressor activityAggressor on/off simulation or measurement
SSN / ground bounceShared return inductance × simultaneous di/dtQuiet outputs move when many outputs switchPDN/SSN transient correlation
PSIJ-like behaviourSupply variation changes edge timingEdge position correlated with rail rippleTime-correlated rail + signal measurement
Loss / ISIFrequency-dependent conductor/dielectric lossSlow settling, pattern dependence, eye closureInsertion loss + impulse/eye
Diagnostic reasoning

A receiver occasionally mis-samples only when a nearby 16-bit bus switches. The victim trace is unchanged. Name three different mechanisms that could create the correlation.

(1) Direct crosstalk from the bus into the victim. (2) Shared-return/ground-bounce noise caused by the bus switching current. (3) Supply disturbance that changes victim-driver or receiver timing. The correct next step is to design measurements/simulations that separate field coupling from shared-PDN coupling rather than assuming “crosstalk” from correlation alone.
Foundation reference sheet — what to remember and what not to oversimplify
REFLECTIONΓ = (Z_L − Z_0)/(Z_L + Z_0)

Positive Γ means the reflected voltage has the same polarity as the incident wave; negative Γ means opposite polarity. Open ≈ +1, short ≈ −1. Real drivers and loads are frequency dependent, so use this as the first mental model.

PDNZ_target = ΔV_allowed / ΔI

Target impedance is a design bound derived from allowed rail ripple and load-current change. It is not a universal number.

LOSSLoss is not just smaller amplitude

Frequency-dependent loss reshapes edges and creates memory. Different bit histories arrive at different levels/times: inter-symbol interference.

MYTH“Clock frequency tells me whether SI matters”

Use transition time and electrical length.

MYTH“Ground is always 0 V”

Real return paths have resistance and inductance. Fast current creates local reference motion.

MYTH“A passing simulation is proof”

It is proof only for the model, boundary conditions, corner, and observation point you actually simulated.

MYTH“More decoupling is always better”

Real capacitors have ESR/ESL and can interact to create anti-resonance. Placement and mounting inductance matter.

Exit test: You are ready for Module 1 when you can look at a symptom, name several plausible physical mechanisms, and choose the evidence that would distinguish them — before naming a tool.
Interactive foundation lab — change one variable and predict what the physics should do

These calculators are screening tools, not sign-off solvers. Their purpose is to train engineering intuition: if you change rise time, impedance, current step or symptom, you should know which result moves and why.

1 · Electrical-length estimator
Compare edge time with interconnect delay. λ/10 is shown as a heuristic, not a hard threshold.
f_knee
—
One-way delay
—
λ/10 at f_knee
—
t_flight / t_r
—
—
2 · Reflection coefficient explorer
Predict reflected polarity and first-arrival load voltage from a single impedance boundary.
Γ
—
Reflected V
—
First load V
—
—
3 · PDN target-impedance estimator
Translate allowed dynamic rail deviation and current step into a first-pass impedance bound.
Z_target
—
—
4 · Symptom-to-evidence triage
Choose a symptom. The output gives hypotheses and the first discriminating evidence — not an automatic root cause.
—
How to use the lab: Change one input at a time and state the direction you expect before reading the updated result. This is exactly the discipline used later for sensitivity sweeps and root-cause confirmation.
Knowledge Check — SI/PI foundations and physical intuition