Part 2 · Combinational · Senior Prep

Wired-AND / wired-OR behavior

Shared Bus Structures: Wired-AND / wired-OR behavior.

Wired-AND / wired-OR behavior

Open-drain protocols emulate wired-AND: any agent pulling low dominates. Wired-OR can be modeled similarly with active-high pull logic depending on electrical convention.

verilog

// Open-drain style (wired-AND at board level)
assign sda = drive_low ? 1'b0 : 1'bz;

Deep dive

This lesson deepens Wired-AND / wired-OR behavior within combinational. Senior reviewers expect you to connect mechanism to logic depth, latch inference, and arithmetic width — not just define terms.

Start from the spec invariant: what must always be true each cycle? Write it as a Boolean relation, timing budget, or protocol rule before coding. That invariant becomes your reference model, assertion, or waveform check.

At tape-out quality, every block needs a sign-off story: no latches, ref model matches, delay intuition documented. Treat this lesson as building one paragraph of that story for your project documentation.

Architecture and signal flow

diagram

WIRED-AND / WIRED-OR BEHAVIOR

  inputs ──► [combinational] ──► mechanism ──► outputs
                │                │
           tri-state-buses     verify in sim + lint

Worked example (Verilog/SystemVerilog)

Synthesizable pattern for this topic — simulate locally and compare against your reference.

verilog

assign bus = en ? drv : 1'bz;  // sim only; avoid in ASIC

Step-by-step design procedure

Write the spec invariant (truth table, timing, or protocol rule).
Sketch block diagram — inputs, outputs, clock/reset domains.
Code the minimal correct version (no optimizations yet).
Run self-checking TB with corners: min, max, reset, idle.
Lint and review: width, latch, clock, CDC if applicable.
Iterate for timing/area only after functionally proven.

Timing and resource trade-offs

diagram

METRIC          TYPICAL LEVER
Logic levels      algebra / pipelining
Register count    retiming / sharing
Wire fanout       duplication / pipeline
Power             clock gating / operand isolation
Debug visibility  status flags / SVA / waveform probes

Debug checklist

Compare DUT vs reference on every stimulus vector
Capture first cycle of mismatch — not last
Log seed and plusargs for random regressions
Check reset release and clock alignment in TB
If waveform is ambiguous, add temporary assertions

Interview angle

How do you prove no latch was inferred?

diagram

MODEL ANSWER SKELETON
1. MECHANISM — one-sentence technical truth
2. MOTIVATION — why this structure vs alternatives
3. WHEN TO USE / SKIP — scope and assumptions
4. PITFALL — common junior mistake
5. EXAMPLE — Verilog or waveform scenario

Practice exercise

Extend the worked example for "Wired-AND / wired-OR behavior": add one corner case, write a self-checking test, and document one intentional pitfall you avoided. Timebox: 30–45 minutes.

Key takeaways

Connect Wired-AND / wired-OR behavior to logic depth, latch inference, and arithmetic width.
Spec → diagram → code → TB → lint is the default loop.
Document assumptions at block boundaries (width, signedness, latency).
Interview answers need mechanism + trade-off + example.

Common pitfalls

Skipping reference model — passes wrong together with DUT.
Optimizing before correct — ECO cost goes up 10×.
Ignoring tool warnings — lint/CDC/STA warnings are technical debt.
Undocumented clock/reset domain — integration surprises.

Extended design scenario

Scenario for Wired-AND / wired-OR behavior : Priority mux depth is 8 levels — refactor to balanced tree or pipeline with documented latency.

Scenario resolution outline

Reproduce with minimal TB — one stimulus, one check.
Isolate failing cone (logic, FSM state, or bus beat).
Fix root cause — not symptom — in RTL or TB alignment.
Add regression test that fails without the fix.
Document invariant in comment or SVA for permanence.

Additional simulation pattern

verilog

// Exhaustive 3-input truth table
for (int a=0; a<2; a++)
  for (int b=0; b<2; b++)
    for (int c=0; c<2; c++)
      check_ref(a,b,c);

Synthesis and sign-off notes

Elaborate clean — no OOM from unconstrained generate
Constraints cover all clocks and I/O delays
Cross-check RTL parameters vs integration top
Attach sim log + seed to code review

Lab exercise (45–60 min)

Implement or extend the worked example for "Wired-AND / wired-OR behavior". Add two new test vectors that target different branches. Write a one-paragraph sign-off note covering function, corners, and what you would still verify in SoC context.

Extended design scenario

Scenario for Wired-AND / wired-OR behavior : Priority mux depth is 8 levels — refactor to balanced tree or pipeline with documented latency.

Scenario resolution outline

Reproduce with minimal TB — one stimulus, one check.
Isolate failing cone (logic, FSM state, or bus beat).
Fix root cause — not symptom — in RTL or TB alignment.
Add regression test that fails without the fix.
Document invariant in comment or SVA for permanence.

Additional simulation pattern

verilog

// Exhaustive 3-input truth table
for (int a=0; a<2; a++)
  for (int b=0; b<2; b++)
    for (int c=0; c<2; c++)
      check_ref(a,b,c);

Synthesis and sign-off notes

Elaborate clean — no OOM from unconstrained generate
Constraints cover all clocks and I/O delays
Cross-check RTL parameters vs integration top
Attach sim log + seed to code review

Lab exercise (45–60 min)

Extended theory

Combinational cones set the raw MHz ceiling of a block. Before pipelining, quantify depth: each wide mux or carry chain adds delay that shows up as setup slack erosion at the next register boundary.

For "Wired-AND / wired-OR behavior", the invariant you defend in review is: behavior matches spec under all legal input sequences, reset flows, and backpressure patterns—not just the happy path shown in introductory diagrams.

Write the invariant as a comment above the module or as an SVA property when possible. Future you (and formal tools) will treat it as the contract.

Waveform reading guide

diagram

WAVEFORM NARRATIVE — Wired-AND / wired-OR behavior

cycle 0: reset asserted, outputs safe/idle
cycle 1-2: reset held, clocks running
cycle 3: reset released, first legal inputs
cycle 4+: check output latency (N cycles)
mark FIRST mismatch cycle — not last

Second worked example

Alternate pattern emphasizing debug, coverage, or integration:

verilog

// Pipeline-style comb for timing (register inputs)
always_ff @(posedge clk) a_r <= a;
always_ff @(posedge clk) b_r <= b;
assign y = a_r & b_r;  // shorter path from flop

Comparison: naive vs production

diagram

NAIVE APPROACH              PRODUCTION APPROACH
quick hack, one sim vector    self-checking TB + corners
ignore lint warnings          zero new waivers
implicit widths               explicit casts/parameters
undocumented latency          latency in module header comment

Additional interview questions

Explain Wired-AND / wired-OR behavior to a verification engineer — what would they assert?
What breaks first at high frequency or low voltage?
What is your rollback plan if synthesis QoR is unacceptable?
How would you debug this block with only a 32-bit GPIO trace?

Follow-up interview model answer

diagram

Q: What is the #1 mistake with Wired-AND / wired-OR behavior?
A:
  MECHANISM: [core rule in one line]
  MOTIVATION: why teams care in tape-out
  PITFALL: what juniors do wrong
  EXAMPLE: one Verilog line or one waveform event

Hands-on lab part 2

Fork the worked example; add one assertion or SVA cover.
Inject a bug deliberately; confirm TB or assertion catches it.
Write 5-bullet PR description for your change.
Peer review: can a teammate enable the block without asking you?

Sign-off evidence checklist

Directed sim log attached (PASS, seed noted)
Lint report clean for touched files
If sequential: reset + clocking section in README
If bus-facing: protocol cheat sheet in module doc
If timing-critical: note expected critical path endpoint

Practice this lesson

Navigate

Wired-AND / wired-OR behavior