Cooking Up Better Performance for Arm-Based SoCs
With increasing complexity, ascertaining performance in Arm-based SoCs design has become challenging, as it involves system-wide protocols connecting multiple IP in collaboration to deliver the expected performance. Verification teams must do the performance verification at the system level to ensure data integrity and avoid any bandwidth throttling or cache coherency issues at a later stage. However, it is difficult for developers to evaluate this combination's performance running the anticipated mix of workloads. Integrating more functionality and multicores suits the customer's expectations and market demands, but it introduces tremendous challenges for SoC verification teams.
To read the full article, click here
Related Semiconductor IP
- nQrux® Root of Trust IP
- AXI to UCIe Bridge IP
- UCIe 2.x Controller IP
- SWI3S (SoundWire I3S Interface) Peripheral Controller Core IP
- OpenTitan-based RISC-V Secure Element
Related Blogs
- Integration and Verification of PCIe Gen4 Root Complex IP into an Arm-Based Server SoC Application
- Defacto SoC Compiler performance on AWS Graviton3
- Raspberry Pi Pico 2: Arm-based Development Board Delivers Higher, More Secure Performance for Commercial Applications
- Where Is The ARM-Based Netbook?
Latest Blogs
- From Bug Hunting to Engineering Methodology: Lessons from AI-Driven Development
- Manufacturing Intelligence: Turning EDA Data into Trusted Action
- Execute-in-Place: Getting More from Embedded NVM
- Rethinking RTL flows with AI-driven hybrid formal verification
- Arm and NVIDIA: Building the trusted compute foundation for the agentic AI era