<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Removal on bitwiz</title><link>https://bitwiz.io/tags/removal/</link><description>Recent content in Removal on bitwiz</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 03 Jan 2026 20:01:00 +0000</lastBuildDate><atom:link href="https://bitwiz.io/tags/removal/index.xml" rel="self" type="application/rss+xml"/><item><title>Resets: The Timing Event You Forgot</title><link>https://bitwiz.io/articles/resets-the-timing-event-you-forgot/</link><pubDate>Sat, 03 Jan 2026 20:01:00 +0000</pubDate><guid>https://bitwiz.io/articles/resets-the-timing-event-you-forgot/</guid><description>&lt;p&gt;&lt;em&gt;Timing Series: Part 6 of 6&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Previous: &lt;a href="https://bitwiz.io/articles/cdc-two-flip-flops-are-not-magic/"&gt;CDC: Two Flip-Flops Are Not Magic&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="the-flop-that-didnt-reset"&gt;The Flop That Didn&amp;rsquo;t Reset&lt;/h2&gt;
&lt;p&gt;You&amp;rsquo;re debugging a sporadic startup failure. The system initializes correctly nine times out of ten. On the tenth, one module starts in a corrupted state while everything else works fine. The state machine begins in an illegal state. The counter starts at 7 instead of 0. The FIFO pointers are misaligned.&lt;/p&gt;
&lt;p&gt;You add more reset logic. You connect the reset to more flip-flops. The problem gets worse.&lt;/p&gt;</description></item></channel></rss>