Cloud native EDA tools & pre-optimized hardware platforms
My name is Keith Redmond and welcome to my blog series, ¡°Verification Viewpoints." In this series, I will be posting about a number of processes and flows that have helped make our verification team at Synopsys more productive.
As we know, there are a couple of major reasons why teams look to increase productivity:
Thus, our goal should always be to have the verification team focused as much as possible on problems that cannot be solved by machines, tools, or automation.
I¡¯ve spent my entire career doing either ASIC verification or software. Most of my experience been working as a technical lead on ASIC verification, but my time in software provided me with valuable hands-on experience with processes, techniques, and design patterns pioneered in the software industry that are very applicable to verification.
As a verification lead, I¡¯ve seen the positive impact automation and efficiency improvements can make, and conversely how frustrating it is when a fragile testbench causes endless time spent on debug and maintenance. My goal with this blog is to highlight pitfalls you may encounter during the verification process and inspire you with solutions to overcome those pitfalls. The solutions I will discuss in this series are certainly not the only way to do things, they are meant to serve as examples that have worked for us.
If you¡¯re reading this blog series I¡¯m going to be assuming a few things about what your team does.
Please keep in mind that if some (or all) of the assumptions above don¡¯t align with your current activities/role, my hope is that you may still be able to glean some wisdom from these posts, but understand they will be written from the perspective of a digital verification team.
Here is an outline of the topics that I intend to cover in this blog series:
I hope you enjoy reading this blog series!
Lastly, I encourage you to visit our website for more detailed information on Synopsys¡¯ industry-leading verification and IP solutions.