Please login to view the entire Verification Horizons article.
Please register or login to view.
You are about to go into a planning meeting for a new project when you get a call from one of your company’s Customer Advocate Managers: a product that you worked on just started shipping in volume, and there are a growing number of field reports that the system randomly freezes-up after a few weeks in operation. While a soft reset “works,” it will run anywhere from 5 to 10 days before it has to be rebooted again.
The highly variable MTBF suggests the problem is not a clock-domain crossing (CDC) issue (after all, crashes from CDC issues would have never made it out of the pre-production lab). The unfortunate conclusion is that the design’s logic itself has a problem. Somehow the code reviews, linting, and constrained-random simulations
...
