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:
To read the full article, click here
Related Semiconductor IP
- SoC Security Platform / Hardware Root of Trust
- SPI to AHB-Lite Bridge
- Octal SPI Master/Slave Controller
- I2C and SPI Master/Slave Controller
- AHB/AXI4-Lite to AXI4-Stream Bridge
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