Reset-domain failures look confusing because the symptom appears far from the cause: a duplicate word in a consumer three blocks from the mis-sequenced reset, or an X that shows up hundreds of cycles after a glitchy release. This topic organises debugging symptom-first: match what you see, confirm with the smallest test, then fix the structure.
Lesson | After it you can... |
|---|---|
Map four classic symptoms to their likely reset causes. | |
Tell a glitchy release from a clean one on a waveform. | |
Find and prevent domains reset at different times leaving inconsistent state. | |
Work any reset failure through one compact table. |
Suggested order: symptoms first, then the two mechanism lessons, then the checklist as a desk reference. The waveform lesson reuses the release waveform from the deassertion topic rather than making a second copy.
Reset timing: release landing at a random point in the cycle violates recovery/removal on some boots only. Start with the reset release path, not the data path.