SShortSingh.
Back to feed

Engineer Catches Hidden RTL Bug in AXI Spec Two Weeks Before Chip Tapeout

0
·1 views

A hardware verification engineer discovered a critical latent bug in an AXI interconnect project just two weeks before tapeout, despite the design having passed over 500,000 simulation cycles and achieving more than 98% code coverage. The issue surfaced when a senior architect questioned what would happen if the AWLEN parameter wrapped around 256 during an INCR burst — a scenario the protocol spec left as undefined behavior. Because the testbench had been configured to skip undefined sequences, a state machine hang in the RTL had gone undetected throughout the verification process. The incident highlighted that verification must go beyond confirming the RTL matches the spec, and should also validate that the spec itself is complete and correct. The engineer concluded that the most critical skill in chip verification is not tool expertise, but knowing which edge-case questions the specification authors may have overlooked.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

Dowe: New Full-Stack Language Targets Server, Web, Desktop, and Mobile Platforms

A developer has introduced Dowe, a new full-stack programming language designed to work across server, web, desktop, Android, and iOS environments. The project was shared on Hacker News as a community showcase submission. Dowe aims to unify development across multiple platforms under a single language. The project's official website is available at dowe.dev, where further details can be found. At the time of posting, the submission had received minimal community engagement with only a few points and no comments.

0
ProgrammingDEV Community ·

Understanding JavaScript Closures: Scope, Execution Context, and Nested Functions

Closure is a default behavior of every JavaScript function, making it a fundamental concept for developers working with the language. To understand closures, one must first grasp lexical scope, which means JavaScript looks up variables where a function was defined, not where it is called. Every time a function is invoked, the JavaScript engine creates a new, independent execution context that is pushed onto the call stack and holds local variable bindings along with a reference to the outer lexical environment. Normally, when a function finishes executing, its context is removed and local variables are discarded, but nested functions can change this behavior. It is in the context of nested functions — where an inner function retains access to the outer function's scope even after the outer function has returned — that closures become observable and practically useful.

0
ProgrammingHacker News ·

Netflix fires employee who shared personal details during company retreat exercise

A Netflix employee was terminated after disclosing personal information during a trust-building exercise at a company retreat. The dismissal has since led to a lawsuit against the streaming giant. Legal experts suggest the reputational and legal consequences for Netflix may extend well beyond the initial case. The incident raises broader questions about the boundaries of mandatory vulnerability exercises in corporate settings.

0
ProgrammingDEV Community ·

Analog Keyboards Offer Precision Gains but Come With Serious Engineering Trade-offs

Modern analog keyboards using optical and Hall Effect switches have replaced traditional binary on/off inputs with continuous position tracking, enabling features like sub-millimeter rapid trigger resets favored by competitive gamers. Each keypress is processed through an analog-to-digital converter and onboard microcontroller, demanding far more powerful hardware than the simple 8-bit chips found in conventional keyboards. Continuous sensor data also introduces challenges such as LED degradation, dust interference, and thermal drift, all requiring sophisticated real-time auto-calibration algorithms to maintain accuracy. Because operating systems are built around binary keyboard input, analog keyboards must emulate gamepad controllers to deliver variable input to software, adding driver latency and compatibility issues. Beyond the purchase price, ongoing reliance on resource-heavy configuration software like Razer Synapse further raises the total cost of ownership for these devices.

Engineer Catches Hidden RTL Bug in AXI Spec Two Weeks Before Chip Tapeout · ShortSingh