Multi-core analysis made easy with the Nexus 5001 debug spec
By Dr. Neal Stollon, HDL Dynamics
(03/05/08, 12:05:00 AM EST), Embedded.com
In System on Chip (SoC) architectures, the ability to effectively analyze problems and optimize operations using real time in-system instrumentation is recognized as one of the most effective methods for completing product development.
Perhaps nowhere is this need more prevalent than for multi-core architectures, since this is an areas where traditional processor simulation and system analysis methodologies tend to break down when faced with issues such as concurrent programming and multiple processor flows, asynchronous operations, core-to-core integration issues, etc.
Real (either prototype or production) hardware provides the best source of information for this type of analysis, but often suffers from visibility into functionality of the system, such as processor instruction flow and data movement on embedded buses, which are not typically made available at the pin IO. Increasing the visibility of these embedded operations typically requires an instrumentation subsystem.
Debug solutions vary greatly with different IP vendors, which can make integrating debug and instrumentation systems for heterogeneous multi-core architectures difficult. In this is dynamic area, the most mature standardized solutions addressing system instrumentation and debug are those based on IEEE 5001, also widely referred to as Nexus.
(03/05/08, 12:05:00 AM EST), Embedded.com
In System on Chip (SoC) architectures, the ability to effectively analyze problems and optimize operations using real time in-system instrumentation is recognized as one of the most effective methods for completing product development.
Perhaps nowhere is this need more prevalent than for multi-core architectures, since this is an areas where traditional processor simulation and system analysis methodologies tend to break down when faced with issues such as concurrent programming and multiple processor flows, asynchronous operations, core-to-core integration issues, etc.
Real (either prototype or production) hardware provides the best source of information for this type of analysis, but often suffers from visibility into functionality of the system, such as processor instruction flow and data movement on embedded buses, which are not typically made available at the pin IO. Increasing the visibility of these embedded operations typically requires an instrumentation subsystem.
Debug solutions vary greatly with different IP vendors, which can make integrating debug and instrumentation systems for heterogeneous multi-core architectures difficult. In this is dynamic area, the most mature standardized solutions addressing system instrumentation and debug are those based on IEEE 5001, also widely referred to as Nexus.
To read the full article, click here
Related Semiconductor IP
- Ultra-Low-Power LPDDR3/LPDDR2/DDR3L Combo Subsystem
- Parameterizable compact BCH codec
- 1G BASE-T Ethernet Verification IP
- Network-on-Chip (NoC)
- Microsecond Channel (MSC/MSC-Plus) Controller
Related Articles
- Reusable debug infrastructure in multi core SoC : Embedded WiFi case study
- Communication centric test and debug infrastructure for multi core SoC
- Throttle IP Core Power Dissipation: Use RTL Power Analysis Early and Often
- A SystemVerilog DPI Framework for Reusable Transaction Level Testing, Debug and Analysis of SoC Designs
Latest Articles
- Leveraging FPGAs for Homomorphic Matrix-Vector Multiplication in Oblivious Message Retrieval
- Extending and Accelerating Inner Product Masking with Fault Detection via Instruction Set Extension
- ioPUF+: A PUF Based on I/O Pull-Up/Down Resistors for Secret Key Generation in IoT Nodes
- In-Situ Encryption of Single-Transistor Nonvolatile Memories without Density Loss
- David vs. Goliath: Can Small Models Win Big with Agentic AI in Hardware Design?