AMBA based Subsystems: What does it take to verify them?
Let’s look at a typical AMBA based subsystem in the SOCs that you find today:
From this picture, what is clear to me is a preponderance of multiple AMBA components of different flavors (AXI3/4, ACE, AHB, APB). So, even if we have all of the different VIPs to represent these .different flavors, it is not a slam dunk as far as completing the verification of the full subsystem. Stitching all these components together and bringing up such a verification environment itself is a big challenge. To deal with market pressures of shipping out new devices every 4-6 months, SoC companies are adding new design blocks incrementally to existing platforms. Given these time constraints, new verification environments cannot be developed again from scratch. If we dig deeper, we see the types of verification needed to bring in changes to the SoC:
Related Semiconductor IP
- AES GCM IP Core
- High Speed Ethernet Quad 10G to 100G PCS
- High Speed Ethernet Gen-2 Quad 100G PCS IP
- High Speed Ethernet 4/2/1-Lane 100G PCS
- High Speed Ethernet 2/4/8-Lane 200G/400G PCS
Related Blogs
- AMBA based Subsystems: What does it take to verify them? - The AMBA System Level Environment
- Industry's First Source Code Test Suite and Verification IP for Arm AMBA ACE5 and AXI5 Enables Early Adopter Success
- Cache Coherent Verification - New Features in AMBA CHI
- Synopsys Introduces the Industry's First Verification IP for Arm AMBA 5 CHI-F
Latest Blogs
- Why Choose Hard IP for Embedded FPGA in Aerospace and Defense Applications
- Migrating the CPU IP Development from MIPS to RISC-V Instruction Set Architecture
- Quintauris: Accelerating RISC-V Innovation for next-gen Hardware
- Say Goodbye to Limits and Hello to Freedom of Scalability in the MIPS P8700
- Why is Hard IP a Better Solution for Embedded FPGA (eFPGA) Technology?