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
- LPDDR6/5X/5 PHY V2 - Intel 18A-P
- ML-KEM Key Encapsulation & ML-DSA Digital Signature Engine
- MIPI SoundWire I3S Peripheral IP
- ML-DSA Digital Signature Engine
- P1619 / 802.1ae (MACSec) GCM/XTS/CBC-AES 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
- Accurate System Level Power Estimation through Fast Gate-Level Power Characterization
Latest Articles
- FPGA-Accelerated RISC-V ISA Extensions for Efficient Neural Network Inference on Edge Devices
- MultiVic: A Time-Predictable RISC-V Multi-Core Processor Optimized for Neural Network Inference
- AnaFlow: Agentic LLM-based Workflow for Reasoning-Driven Explainable and Sample-Efficient Analog Circuit Sizing
- FeNN-DMA: A RISC-V SoC for SNN acceleration
- Multimodal Chip Physical Design Engineer Assistant