PinDown-ML - Automatic Debugger of Regression Failures

Debug is the most resource intensive aspect of semiconductor development, typically requiring more than a third of total development time. Verifyter’s unique regression debug automation technology, based on Machine Learning (ML), typically shaves 75% off regression debug time. Used by many electronic systems and semiconductor companies today, Pindown easily fits into your simulation or emulation environment, accelerating the entire verification cycle while reducing manual debug intervention.

This video series highlights how Pindown leverages ML for bug prediction to identify failing code segments, simplifying bug triage, and ensuring successful regression runs. After an introduction, the series takes a deep dive into the technology and its application, before showing how the tool maybe be easily leveraged in many regression flows. The tool will be demonstrated in real system situations.

Overview
How does Automatic Debug work? How does Bug Prediction using Machine Learning work? (video 2:15)

Deep Dive
How to debug dependencies between code and tests (video 2:17)
Scaling: handle many tests, many commits (video 2:28)
Avoiding IT issues (video 2:28)
Handling Constrained Random Testing (video 3:14)

Adding Automatic Debug to your Test Flow
Debugging RTL simulations, software, tests on emulators, continuous integration (video 3:14)
Reduce the test run-time (video 3:17)
PinDown licensensing - test phase is free (video 0:47)

Demo
Demo of PinDown-ML (video 9:31)

Getting Started (NEW!)
Step 1. Install and Run Demo (video 6:29)
-> Install (at 0:10)
-> Demo - Kick Off (at 0:32)
-> PinDown Basics (at 0:46)
    -> File Structure (at 1:35)
    -> Regression/Run Debug Scripts (at 2:44)
    -> PinDown Logs (at 3:32)
-> Demo - Analyze Results (at 4:40)

Step 2. Create Your Own Project (video 5:49)
-> Revision control system (at 0:53)
-> Regression script (at 1:34)
-> Extract results (at 1:54)
-> Run debug script (at 3:30)

Step 3. Fixing Setup Issues (video 6:51)
-> Script not found (at 0:25)
-> Script not running (at 0:57)
-> No test results (at 1:31)
-> Missing build pass/fail (at 2:44)
-> Missing test names (at 3:16)
-> No debug results (at 3:38)
-> Missing test pass/fail (at 5:38)

(see all 3 steps in one go)

Partners
Optimizing Verification with Altair Accelerator(TM) + PinDown-ML

Quiz
Test your Automatic Debug knowledge