Handshakes and pulses

You will learn

How a handshake moves a pulse between worlds, and what an edge-driven report and a toggle synchronizer share.

A pulse is the hardest thing to move: one clock wide here is not one clock wide there. The handshake turns it into a level: the sending side raises a request, the receiving side samples it, raises an acknowledge, and the request drops -- four edges, and the pulse became a conversation. The widget is a report that works the same way: 25 live checks, printing only rows that are NEW red or CLEARED since the last look -- the far side sees the change, not the level, exactly what a toggle synchronizer arranges in hardware. The spec frame opens clock_domain.t27, whose handshake strategy is this conversation as one enum value.

Open the interactive lesson →