Legacy RTL brought into system-level flow
John Wilson, EE Times
(06/26/2006 9:00 AM EDT)
As system-on-chip complexity grows, designers are turning to electronic system-level (ESL) methodologies to create next-generation designs.
Designers might hesitate to use ESL because of legacy RTL intellectual-property libraries that represent thousands of man-years of invested time. But legacy RTL IP can be the basis for new designs that leverage ESL methodologies.
Designers who have tried ESL design recognize that some parts of a design are more conducive to ESL while others are more efficiently implemented using established IP libraries. Typically, ESL is used to create new, differentiated system components; RTL IP is best for the obligatory nondifferentiated parts of the design.
Where do these two methodologies come together? Actually, they are different aspects of a holistic electronic-system design methodology.
ESL does not replace RTL design. Instead, the ESL design flow extends RTL flows into higher levels of abstraction, much as RTL design extends gate-level design.
Platform-based design lets designers automatically integrate ESL modules with existing RTL IP. Platform-based design is made more effective when it uses Spirit XML data books from the Spirit Consortium to describe the IP. These data books include configuration and validation information to help determine the processes that must be executed to integrate the block into a system-on-chip design.
(06/26/2006 9:00 AM EDT)
As system-on-chip complexity grows, designers are turning to electronic system-level (ESL) methodologies to create next-generation designs.
Designers might hesitate to use ESL because of legacy RTL intellectual-property libraries that represent thousands of man-years of invested time. But legacy RTL IP can be the basis for new designs that leverage ESL methodologies.
Designers who have tried ESL design recognize that some parts of a design are more conducive to ESL while others are more efficiently implemented using established IP libraries. Typically, ESL is used to create new, differentiated system components; RTL IP is best for the obligatory nondifferentiated parts of the design.
Where do these two methodologies come together? Actually, they are different aspects of a holistic electronic-system design methodology.
ESL does not replace RTL design. Instead, the ESL design flow extends RTL flows into higher levels of abstraction, much as RTL design extends gate-level design.
Platform-based design lets designers automatically integrate ESL modules with existing RTL IP. Platform-based design is made more effective when it uses Spirit XML data books from the Spirit Consortium to describe the IP. These data books include configuration and validation information to help determine the processes that must be executed to integrate the block into a system-on-chip design.
To read the full article, click here
Related Semiconductor IP
- Dual Port, Voltage Scaling Register File Compiler on GF22FDX+
- Single Port, Voltage Scaling, High Speed SRAM Memory Compiler on GF22FDX+
- I3C Full Controller / Target
- I3C HCI Host Controller
- USB-C Power Delivery IP Core
Related Articles
- Gbit interface forces analog IP into digital flow
- Transactional level as the new design and verification abstraction above RTL
- From Behavioral to RTL Design Flow in SystemC
- How to raise the RTL abstraction level and design conciseness with SystemVerilog - Part 1
Latest Articles
- An Agentic Python Framework for LLM-Driven UVM Testbench Synthesis with Closed-Loop Compiler Feedback
- Reconfiguring System-Level Protection Through Bounded Delegation in RISC-V MCUs
- SkipLane: Write-Once, Conflict-Free Accumulation for Zero-Skipping CNN Engines on FPGAs
- Priority-Aware Deficit Round Robin for AXI4 Bandwidth Fairness in ASAP-7nm Process
- Atik: A Shared-Mesh Transformer Accelerator for RISC-V