Does your VIP need a GUI?
Remember the days of internet text browsers? There were no pictures, video clips or even colorful fonts to catch the users’ eye. Users had to read through lines and lines of plain text just to find a section of their interest. Unimaginable isn't it? Internet wouldn't quite have been the same without the advent of GUI based browsers.
In some respects, we can draw parallels between the Internet and design/verification worlds. DV engineers have, so far, been debugging VIP issues with the help of log files. The log files are analogous to text browsers, as DV engineers have to sift through thousands of lines of unformatted and unstructured text to find relevant information that can help identify the root cause of a failure. Wouldn't it be so much better if there were GUI based tools that could display interface and transaction level information in a protocol defined format? Just as the full power of the Internet would not have been unleashed if not for GUI browsers, the true potential of Verification IPs will perhaps never be realized without GUI protocol analyzers.
Related Semiconductor IP
- Network-on-Chip (NoC)
- 12-bit, 400 MSPS SAR ADC - TSMC 12nm FFC
- DVB-S2 Demodulator
- UCIe PHY (Die-to-Die) IP
- UCIe-S 64GT/s PHY IP
Related Blogs
- How fast a GPU do you need for your user interface?
- ARM Cortex-A15 - does this processor IP core need a new category ... Superstar IP?
- Will your multicore SoC hit the memory wall? Will the memory wall hit your SoC? Does it matter?
- Does an externally bought IP need re-verification?
Latest Blogs
- Enabling End-to-End EDA Flow on Arm-Based Compute for Infrastructure Flexibility
- Real PPA improvements from analog IC migration
- Design specification: The cornerstone of an ASIC collaboration
- The importance of ADCs in low-power electrocardiography ASICs
- VESA Adaptive-Sync V2 Operation in DisplayPort VIP