G9.15.2 The Line Nobody Pulled Up

EasyDebugIcarus · browser samples / server checksReview the topic

Name the cause of four faults on shared lines and open inputs, from a numbered list of causes.

Hardware context: A slow sensor input with a Schmitt-trigger receiver, and an open-drain interrupt line shared by several devices. Find why a shared line floats, fights or never rises.

A board review found four suspicious lines. Each report below comes from a switch-level simulation or a SPICE run.

This is a Debug problem. For each report, write the number of its cause from the cause bank. Some causes fit no report.

The check reads each output and reports the first one that is wrong.

Signals in the Timeline

SignalWidthRole
item8input of each check
Full specification
NumberCause
0No fault: the line behaves as designed.
1An open-drain line with no pull-up.
2An unused input left open.
3Two push-pull outputs driving one line.
4The pull-up resistor connected to ground instead of the supply.
5The pull-up resistor too large for the required rise time.
ReportWhat the run showedCause
W (worked)Two open-drain drivers and a pull-up share a line. For the driver inputs 00, 01, 10, 11 the line reads 1, 0, 0, 0.0
X (worked)An open-drain line of 50 pF has a 10 kΩ pull-up. It must rise from 10 % to 90 % within 500 ns. A SPICE run shows 1099 ns.5
Y (worked)An interrupt line with a pull-up reads 0 while one of four open-drain devices pulls it low, and 1 when none does.0
AAn open-drain reset line reads z in simulation whenever no device pulls it low.?
BA status line reads x in simulation whenever the two boards connected to it disagree. Each board has a normal CMOS output on the line.?
CA two-input NAND gate has its first input at 1. Its second input pin is not connected to anything. Its output reads x.?
DAn open-drain line with a 4.7 kΩ resistor reads 0 all the time, even when every device has let go.?

In switch-level simulation a line that nothing drives reads z. A line with a strong 1 and a strong 0 reads x.

Examples

Example 1

Worked Report W
Input
report W
Output
example_w = 0

That is the wired-AND truth table: the line is 1 only when both drivers let go. No fault: 0.

Example 2

Worked Report X
Input
report X
Output
example_x = 5

The line works but rises too slowly: 2.2 × 10 kΩ × 50 pF is about 1.1 µs. A smaller pull-up is needed. Cause 5.

Example 3

Worked Report Y
Input
report Y
Output
example_y = 0

One device pulling low wins over the pull-up, as designed. No fault: 0.

Constraints and Contract

  • Keep the module name answer and the names of its outputs.
  • Every output is one number from 0 to 5.

Hints

Hint 1

z means nothing drives the node. x means two drivers disagree, or a gate has an input that is z.

Hint 2

A gate output of x can come from one of its inputs. Look at what drives each input.

Hint 3

A line that never rises although every driver let go is being held low by something that is always there.

What the grader checks: The check reads seven outputs and compares each with the cause numbers set in JavaScript. Three are worked reports. The programs of lesson G9.15 print the switch-level behaviour of reports A to C and W. The rise time of report X is from its SPICE run.

7 checks on Icarus · browser samples / server checks. Run the examples first, then check the full regression. Full checks use the server judge. Downloads contain public samples only. A passing result establishes the tested cases, not a proof for all possible inputs.

See all 2 steps and the final capstone

Report a problem with this page

Your code SystemVerilogSaved locally
Ln 1, Col 1Tab indents · Ctrl/⌘ + Enter runs samples
Not run yet

Worked Report W

Input
report W
Expected output
example_w = 0

That is the wired-AND truth table: the line is 1 only when both drivers let go. No fault: 0.

Run samples executes all 3 public checks. Check all tests runs 7 checks on the server.

Icarus · browser samples / server checks