3.4.4 · D5Sequential Circuits
Question bank — JK and T flip-flops
Every symbol used here is defined in the parent note. Quick anchor so line one makes sense:
Recall Symbol reminder
= the flip-flop's current stored bit. = the bit after the next clock edge. = "not " (the opposite bit). = XOR ("output 1 when the two inputs disagree"). = the two JK inputs; = the single toggle input; = set/reset of the older SR Flip-Flop.
True or false — justify
A JK flip-flop still has one forbidden input combination, just like SR.
False. SR breaks at , but JK routes to a defined action — toggle. Internally , so and can never both be 1, killing the hazard structurally.
A T flip-flop toggles its output on every clock edge.
False. It toggles only when . When it holds. The characteristic is , not .
Setting makes a JK flip-flop output 0.
False. is the hold command: , so it keeps whatever it already had (could be 1). To force 0 you need the reset row .
and describe the same flip-flop.
True. XOR is the sum-of-products "the two inputs disagree", so by definition. See XOR Gate.
A T flip-flop can be built from a JK flip-flop but not the other way around.
True in the simple sense. Tying gives T. Going backward, a lone T input can't recreate the four independent JK commands (it collapses set and reset into one toggle line), so you lose set/reset control.
Excitation tables and characteristic tables contain the same information in different layouts.
Mostly true, but the direction differs. Characteristic: inputs → output. Excitation: desired transition → required inputs. The excitation table also introduces don't-cares (X) that the characteristic table never shows.
The don't-care for the JK transition means is broken or floating.
False. It means 's value is irrelevant here: when , (which only acts to reset an already-1 output) has no effect. Either or produces , so you're free to pick whichever simplifies the logic.
A level-triggered (transparent) JK with held high behaves identically to an edge-triggered one.
False. A transparent JK toggles repeatedly while the clock is high (the "race" problem). Edge-triggered / master–slave designs toggle exactly once per edge — see Edge-Triggering and Master-Slave.
The D Flip-Flop and the JK flip-flop both eliminate the forbidden state, so they are interchangeable.
False in purpose. Both avoid a forbidden state, but D just copies its input () with no hold/toggle, while JK gives independent hold/set/reset/toggle. They solve the same problem differently.
Cascading T flip-flops (each fed the previous output) divides the clock frequency by 2 at each stage.
True. Each stage with toggles once per input edge, so its output cycles at half its input's rate — giving ÷2, ÷4, ÷8… This is exactly a ripple counter.
Spot the error
" sets the output to 1 because both inputs are high."
Error: high-high is toggle, not set. , so the result depends on the current state — it could go to 0.
"To hold the output, use so both agree to keep it."
Error: toggles. Hold is . The mnemonic is "J sets, K kills, both flip."
"For the JK transition we need ."
Error: the excitation row is . We only require "don't reset" (); is a don't-care because setting is pointless when already at 1.
" tells you the toggle input from a desired next state."
Error: the correct excitation is — you need exactly when the state must change, which depends on both current and next state, not alone.
"Since T means Toggle, a T flip-flop with holds the inverted value."
Error: holds the value as-is (), no inversion. Inversion happens only for .
"SR's characteristic equation is ."
Error: it's (with the constraint ). We keep only when is not asserted, hence , not .
"In JK we substitute and to feed back the state."
Error: it's the other way: (set only when currently 0) and (reset only when currently 1). Swapping them would break the toggle behaviour.
Why questions
Why does feeding back into the inputs eliminate the forbidden state?
Because and depend on complementary signals and — one is always 0 — so internal and can never be 1 simultaneously. The illegal input becomes physically unreachable.
Why does XOR appear in the T flip-flop equation and not, say, AND or OR?
Because "toggle when , hold when " is precisely "output differs from exactly when " — the disagreement rule, which is the definition of XOR.
Why are the don't-cares in the JK excitation table valuable for design?
Each X is a free choice a K-map can set to whatever simplifies the Boolean expression, producing cheaper, smaller logic than a fully-specified table would allow.
Why does a T flip-flop, not a D flip-flop, naturally build a binary counter?
A counter bit must flip each time its stage should advance; T's toggle-on-command does this directly by wiring , whereas D would need external feedback () to imitate the same toggle.
Why does the JK characteristic equation assume exactly one update per clock edge?
Because the equation gives one per current . A transparent JK held with would keep re-toggling, contradicting the single-valued equation — hence real designs enforce one update per edge.
Why is called "useful" rather than "illegal", unlike ?
Because it produces a fully defined, repeatable output () that we deliberately use for counting and dividing frequency — a feature, not a fault.
Edge cases
What does a JK flip-flop do if is applied but the clock never ticks?
Nothing — a clocked/edge-triggered flip-flop only updates on the active clock edge. With no edge, stays put regardless of the inputs.
A T flip-flop starts at an unknown and gets for one edge. What is ?
The opposite of whatever it started as. Toggle inverts the current bit, so an unknown start gives an unknown-but-inverted result — you still don't know the absolute value without knowing the start.
For the JK transition , both and have constraints — true?
False. The excitation is : we must not set (), but is a don't-care since resetting an already-0 output changes nothing.
If you build a T flip-flop from JK but accidentally tie only and leave , what happens?
It becomes a set-only / hold device, never a toggler: sets to 1 and stays, since can never reset. You lose the toggle entirely.
What is for a JK flip-flop with when is already 0?
Still 0. This is the reset row; resetting an already-0 output is a no-op, so .
In a ripple counter of T flip-flops, why doesn't every stage update at the same instant?
Each stage's clock is driven by the previous stage's output transition, so toggles ripple through with small delays — the source of the "ripple" name and of timing skew in ripple counters.
Connections
- Parent: JK and T flip-flops
- SR Flip-Flop — the forbidden-state ancestor
- D Flip-Flop — the other no-forbidden-state design
- Edge-Triggering and Master-Slave — why held toggling doesn't race
- Ripple Counters — cascaded T flip-flops
- Excitation Tables and Sequential Design — the design-direction tables
- Karnaugh Maps — where don't-cares pay off
- XOR Gate — the heart of the T equation