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).
To read the full article, click here
Related Semiconductor IP
- HBM4 PHY IP
- Ultra-Low-Power LPDDR3/LPDDR2/DDR3L Combo Subsystem
- MIPI D-PHY and FPD-Link (LVDS) Combinational Transmitter for TSMC 22nm ULP
- HBM4 Controller IP
- IPSEC AES-256-GCM (Standalone IPsec)
Related Articles
- Scalable Verification Environment Using OCP Compliant Cores and eRM Compliant eVCs
- A Methodology for Verifying OCP Interfaces
- On-chip instrumentation aids OCP debugging
- OCP Interface for SoC - Verifying the Implementation of Embedded Processors
Latest Articles
- ElfCore: A 28nm Neural Processor Enabling Dynamic Structured Sparse Training and Online Self-Supervised Learning with Activity-Dependent Weight Update
- A 14ns-Latency 9Gb/s 0.44mm² 62pJ/b Short-Blocklength LDPC Decoder ASIC in 22FDX
- Pipeline Stage Resolved Timing Characterization of FPGA and ASIC Implementations of a RISC V Processor
- Lyra: A Hardware-Accelerated RISC-V Verification Framework with Generative Model-Based Processor Fuzzing
- Leveraging FPGAs for Homomorphic Matrix-Vector Multiplication in Oblivious Message Retrieval