Physical Hierarchy Configuration Engine for Logical Design Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current computer-aided design systems face challenges in efficiently mapping logical designs to physical designs across different technology-specific libraries, requiring time-consuming modifications and lacking visualization of physical design elaboration, especially when dealing with multiple technology-specific physical libraries and requiring write access to logical design databases.
Innovation Solution
A method involving a separate physical configuration view and a physical hierarchy configuration editor to store and edit mapping annotations in a library attributes mapping file (LAM file), allowing users to define and edit mappings without modifying the logical design, and providing a visual representation of physical design attributes within the physical layout editor.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If mapping attributes are embedded within the logical design library, then the mapping information is stored with the logical design, but modifying mappings requires write access to the logical design database and time-consuming transistor-by-transistor changes
Solution Approach 1:
The patent separates mapping attributes from the logical design library into a distinct physical design mapping file. This segmentation allows mapping information to be stored independently, enabling modifications without requiring write access to the logical design database. Users can edit mapping attributes in the separate file, eliminating time-consuming transistor-by-transistor changes while preserving the association between logical and physical designs.
2Adaptability or versatility
If a single logical design library is mapped to multiple technology-specific physical libraries, then versatility is improved, but storing different properties for each physical library on the same cells becomes difficult
Solution Approach 1:
The patent implements a universal mapping file format that can store multiple technology-specific physical library mappings for a single logical design library. The mapping attributes are structured to support different technology nodes and physical libraries simultaneously, allowing one logical design to be mapped to multiple physical implementations without increasing configuration complexity. This universal approach enables versatile multi-technology support while maintaining manageable mapping configurations.
3Loss of information
If physical design mapping attributes are added to the logical design, then the logical design can be elaborated physically, but the logical design tools cannot read these attributes and visualization is not possible until physical layout creation
Solution Approach 1:
The patent introduces a separate physical design mapping file as an intermediary between the logical design library and the physical layout editor. This intermediary file stores physical design mapping attributes that can be read by both logical design tools and physical layout tools. By placing mapping information in this intermediate format, the system enables visualization of physical design attributes during the logical design phase, allowing users to see and verify mapping configurations before physical layout creation without losing physical elaboration information.
Data Source
AI summary
In one embodiment a new method to address configuring a logical design and libraries of design elements with additional information is proposed that may be used to create a physical design from that logical design. Logical designs may be generic, while physical design libraries are normally targeted towards specific technology. Consequently, there can be a mapping from the cells in a logical library to cells which correspond to their implementation in a physical library. In one embodiment, annotations required to map from logical design to physical design may be stored in a separate design view. In one embodiment the user can modify the physical mapping attributes of cells, instances, and occurrences in the logical design and save the modifications back to the physical configuration view.