AMBA based Subsystems: What does it take to verify them? - The AMBA System Level Environment
In my previous blog (AMBA based Subsystems: What does it take to verify them?), I had talked about some of the key verification challenges when it comes to verifying complex SOCs based on AMBA based subsystems. It was seen that it would indeed be useful to have an extensible AMBA based verification environment which can be tweaked minimally so that it can be reused for the new systems or derivatives.
To enable the SOC verification engineers to create highly configurable AMBA fabric, the system environment should provide place-holders for hooking the DUT with any of the quintessential AMBA VIP components such as AXI3/4/ACE, AHB or APB. With the use of AMBA System environment we can configure it to instantiate as many number of AXI/AHB/APB VIP with minimal additional code. Thus, such an environment would need to encapsulate the following amongst others..
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
- How do you Verify the AMBA System Level Environment?
- IP-SoC trip report (part II): system level mantra
- AMBA System Monitor, Scoreboarding and Beyond
- Synopsys AMBA CHI C2C System Verification Solutions
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?