English
Viewpoint: Capture OCP systems in IP-XACT 1.4
By Stéphane Guntz, Magillem Design Services
edadesignline.com (June 22, 2009)
The Open Core Protocol's unique flexibility, configurability and scalability characteristics enable integrators to build complex systems for high-performance domains A complete standardization process describing how OCP cores and systems can be captured in IP-XACT is the end goal.
The IP-XACT specifications, delivered by The Spirit Consortium is enabling and standardizing effective IP reuse. Members of the consortium are EDA providers (Mentor Graphics, Synopsys, Cadence), IP providers (ARM) and system integrators (TI, NXP, ST).
The IP-XACT specs are defining human-readable documentation for language-independent, interoperable IP module descriptions and tool interfaces using an XML databook format.
The IP-XACT description can document, for example, an IP interface, its registers and bit fields, pointers to the VHDL or SystemC files which define its RTL or TLM implementation, or its software views.
As an example, a third-party UART IP, packaged in an IP-XACT XML format, may be associated with an IP-XACT compliant configuration script by its provider.
The system integrator who receives this UART can automatically import it into his IP-XACT compliant platform assembly tool and integrate it into his existing sub-system (which is also being captured in IP-XACT).
edadesignline.com (June 22, 2009)
The Open Core Protocol's unique flexibility, configurability and scalability characteristics enable integrators to build complex systems for high-performance domains A complete standardization process describing how OCP cores and systems can be captured in IP-XACT is the end goal.
The IP-XACT specifications, delivered by The Spirit Consortium is enabling and standardizing effective IP reuse. Members of the consortium are EDA providers (Mentor Graphics, Synopsys, Cadence), IP providers (ARM) and system integrators (TI, NXP, ST).
The IP-XACT specs are defining human-readable documentation for language-independent, interoperable IP module descriptions and tool interfaces using an XML databook format.
The IP-XACT description can document, for example, an IP interface, its registers and bit fields, pointers to the VHDL or SystemC files which define its RTL or TLM implementation, or its software views.
As an example, a third-party UART IP, packaged in an IP-XACT XML format, may be associated with an IP-XACT compliant configuration script by its provider.
The system integrator who receives this UART can automatically import it into his IP-XACT compliant platform assembly tool and integrate it into his existing sub-system (which is also being captured in IP-XACT).
|
E-mail This Article | 
|
|
Printer-Friendly Page |
|
||||||
Related Articles
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)