3 Reasons Why Verification Engineers should use Python instead of Perl
December 8, 2015
After many years of writing design verification automation scripts in Perl, we at Arrow Devices made a conscious decision to shift to Python, lock, stock and barrel. Scripting in Perl has multiple problems and so we started looking for an alternative. We looked at multiple options but finally zeroed in on Python. Here is why:
Related Semiconductor IP
- 1.8V/3.3V I/O library with ODIO and 5V HPD in TSMC 16nm
- 1.8V/3.3V I/O Library with ODIO and 5V HPD in TSMC 12nm
- 1.8V to 5V GPIO, 1.8V to 5V Analog in TSMC 180nm BCD
- 1.8V/3.3V GPIO Library with HDMI, Aanlog & LVDS Cells in TSMC 22nm
- Specialed 20V Analog I/O in TSMC 55nm
Related Blogs
- Top 3 Reasons Why Design IP Is Business Friendly
- Why Codasip Cares About Processor Verification - and Why you Should too
- What you should ask for instead of just PPA
- FiRa 3.0 Use Cases: Expanding the Future of UWB Technology
Latest Blogs
- Cadence Unveils the Industry’s First eUSB2V2 IP Solutions
- Half of the Compute Shipped to Top Hyperscalers in 2025 will be Arm-based
- Industry's First Verification IP for Display Port Automotive Extensions (DP AE)
- IMG DXT GPU: A Game-Changer for Gaming Smartphones
- Rivos and Canonical partner to deliver scalable RISC-V solutions in Data Centers and enable an enterprise-grade Ubuntu experience across Rivos platforms