Flexible Routing Tracks for Electronic Design Implementation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional electronic design routing methods struggle with flexible routing tracks, especially at half-pitches of 14 nm or below, where region-based and non-uniform track patterns are required, and existing approaches fail to accommodate on-track and off-track requirements across different layers effectively.
Innovation Solution
The method involves using spacetiles as search probes to find viable routing solutions, allowing for transition across regions with different rules, including soft and hard rules, on the same or different layers, and creating spacetile layers associated with specific rules to comply with on-track requirements while minimizing costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional routing methods are used, then routing simplicity is maintained, but adaptability to region-based and non-uniform track patterns is insufficient
Solution Approach 1:
The routing space is divided into multiple regions, each with its own track pattern characteristics (uniform or non-uniform, different pitches). The router selectively applies different routing strategies to different regions based on their specific track patterns, enabling adaptability without requiring a completely complex unified approach.
Solution Approach 2:
The routing method dynamically adjusts its behavior based on the track pattern type in each region. The router can switch between constrained routing (for uniform track patterns) and unconstrained routing (for non-uniform track patterns), optimizing performance for each region while maintaining overall system manageability.
2Adaptability or versatility
If flexible routing tracks are implemented, then adaptability to different design rules is improved, but routing complexity increases
Solution Approach 1:
Track patterns and their associated design rules (on-track, off-track requirements) are defined and stored in a database before the routing process begins. This preliminary setup allows the router to efficiently query and apply appropriate rules during routing without increasing real-time complexity, as the decision logic is pre-configured.
Solution Approach 2:
A track pattern database acts as an intermediary between the routing engine and design rules. The database stores multiple track pattern definitions with their associated rules, allowing the router to select and apply appropriate patterns without directly managing complex rule sets, thereby simplifying the routing process while maintaining flexibility.
3Manufacturing precision
If region-based track patterns are used, then manufacturing precision is improved, but ease of manufacture decreases
Solution Approach 1:
The system manages multiple track pattern definitions with different parameters (pitch, uniformity, orientation) in a database. By parameterizing track patterns rather than hardcoding them, the system achieves high manufacturing precision for 14 nm processes while maintaining ease of manufacture through database-driven configuration and automated router selection.
Data Source
AI summary
One aspect interconnects two regions subject to different rules and using transition rule(s) in a transition region or cost mechanism(s), where these rules may include soft rule(s), hard rule(s), or combinations thereof. These two regions may reside on the same routing layer or on different routing layers. This aspect allows physical design tools to transition across gridded, gridless, tracked, or trackless regions subject to different rules on the same or different layers. Another aspect interconnects an object subject to the first rule(s) and the second rule(s), while the object satisfies or violates the first rule(s). These aspects use spacetile(s) on a spacetile layer as search probe(s) to find viable implementation solutions, although the spacetile(s) and hence the search probe may violate one or more rules. A spacetile layer may be identified or created for each rule and may be associated with relevant features subject to relevant rule(s).


