English
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.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
Related Articles
- Multicore programming made easy?
- Leveraging OCP for Cache Coherent Traffic Within an Embedded Multi-core Cluster
- Debugging a Shared Memory Problem in a multi-core design with virtual hardware
- Virtual Prototyping Environment for Multi-core SoC Hardware and Software Development
- Demystifying multithreading and multi-core
New Articles
- Quantum Readiness Considerations for Suppliers and Manufacturers
- A Rad Hard ASIC Design Approach: Triple Modular Redundancy (TMR)
- Early Interactive Short Isolation for Faster SoC Verification
- The Ideal Crypto Coprocessor with Root of Trust to Support Customer Complete Full Chip Evaluation: PUFcc gained SESIP and PSA Certified™ Level 3 RoT Component Certification
- Advanced Packaging and Chiplets Can Be for Everyone
Most Popular
- System Verilog Assertions Simplified
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- UPF Constraint coding for SoC - A Case Study
- Dynamic Memory Allocation and Fragmentation in C and C++
- Enhancing VLSI Design Efficiency: Tackling Congestion and Shorts with Practical Approaches and PnR Tool (ICC2)