Debug of AMBA AXI Outstanding Transactions
Verifying today’s complex designs is time consuming, as simulations run for long time and millions of transaction are executed. Traditional approach of debug is to dump all the information of millions of packets in a log file, however it would always be challenging to filter out specific transactions from the huge log file. For example, in case of AXI Protocol, a fixed number of outstanding transactions are allowed during simulation, it would always be difficult to find out such outstanding transaction in the huge log file of a single run of simulation or during interactive simulation. It is one of the biggest pain point of debugging.
To read the full article, click here
Related Semiconductor IP
- Flexible Pixel Processor Video IP
- Bluetooth Low Energy 6.0 Digital IP
- Verification IP for Ultra Ethernet (UEC)
- MIPI SWI3S Manager Core IP
- Ultra-low power high dynamic range image sensor
Related Blogs
- How to Use the AXI VIP Debug Port
- AMBA AXI Exclusive Access De-mystified
- Jumping the Barrier of Verifying AMBA ACE Barrier Transactions
- New AMBA 5 ACE/AXI Specification: Rationale for Atomic Transactions
Latest Blogs
- Accelerating RTL Design with Agentic AI: A Multi-Agent LLM-Driven Approach
- UEC-CBFC: Credit-Based Flow Control for Next-Gen Ethernet in AI and HPC
- RISC-V for Infrastructure: For Now, It’s All About the Developer
- Unlock Your AI Potential: A Deep Dive into BrainChip’s Akida™ Cloud
- Breaking the Silence: What Is SoundWire‑I3S and Why It Matters