Verification
Every interface on a chip needs something on the other side of it in simulation: a model that drives traffic, a monitor that watches it, checkers that catch protocol errors and coverage that shows what was exercised. That bundle is verification IP, and a team can get it in three ways. It can buy it from a vendor, build it in house, or borrow it from an open-source project or a partner. The choice is usually made on licence price alone, which i…
by
Murugavel Ganesan
November 19, 2026
Verification
Part 4 let a producer push several entries in one cycle. The mirror image is just as common. A wide consumer, such as a decoder that handles up to four instructions a cycle, a packer that fills a wide output word from narrow entries, or a scheduler that issues several requests at once, wants to take more than one entry from the head of a queue per cycle, and how many it takes depends on what it finds there. This is Part 5 of the FIFO Series: t…
by
The Semiconductor Hub
November 19, 2026
SystemVerilog
Parts 1 to 3 moved one entry per cycle on each side. That is enough for many blocks, but not for a wide front end that decodes four instructions a cycle, a network interface that splits a wide bus into several narrow flits, or a gather engine that collects several results at once. All of them need to put more than one entry into a FIFO in the same cycle, and they need those entries to come out in the order the lanes define. This is Part 4 of t…
by
The Semiconductor Hub
November 19, 2026
Verification
Almost no chip today is designed from scratch. A modern SoC is assembled from processor cores, interconnect, memory controllers, PHYs, security blocks and analog functions, many of them bought from vendors or reused from earlier projects. Each block arrives verified on its own. The trouble starts when they are wired together, and that step, IP integration, is where a large share of schedule slips and silicon bugs now come from. This special re…
by
Murugavel Ganesan
November 19, 2026
Tutorials
Most engineers learn to read a timing or synthesis report by being handed one and told to fix the worst path. Nobody explains that a senior engineer usually does not start with the worst path at all. The first few minutes go to a different question: can this report be trusted? A clean report from the wrong run, the wrong corner or the wrong constraints is worse than a failing one, because it ends the conversation early. This is Part 1 of Readi…
by
The Semiconductor Hub
November 19, 2026