Professional Documents
Culture Documents
Abstract
The use of right configurations are essential for the efficient performance of any routing
tool. In this project a comparative study was done on the results obtained from various
configurations of the tool and different routing scripts were used to obtain best possible
results. The two versions of the tool used were Talus 1.0.80 and Talus 1.0.82.The
experiments were carried out on OMAP3430 and Kaleido databases.
Introduction
The Talus platform consists of the Automated Chip Creation product, which is most
useful for larger, hierarchical designs, and Talus Design and Talus Vortex products,
which are most useful for block and flat designs. To create a chip design we have to
follow certain process. The process in order is shown in the figure on the next page.
Routing Basics
In the Magma design flow, you complete routing at the fix wire stage, after completing
physical optimization (fix cell) and clock routing (fix clock), as shown in the Figure.
In the fix wire stage, the Magma design tools complete the physical implementation of a
design. Up to this point, the tools have done some routing of both power and clock nets,
but they do the majority of the routing of a design at this time. The fix wire script routes
all signal nets, and finishes clock net routing and any power routing not previously
completed.
Stub Routing
Stub routing is the first step in signal routing. During stub routing, very short nets are
identified and routed on the metal1 layer only. The purpose of stub routing is to take
advantage of the otherwise unused metal1 resources and to avoid inaccuracy during the
global routing of short nets.
Global Routing
Global routing focuses on resolving congestion and timing issues. Global routing creates
net segments and defines the initial bucket-level routing topologies. The topologies
include a layer assignment for each segment of each net. Each net segment is a total
contiguous length of interconnect on a given layer.
Track routing is a fast process, compared to detailed routing, and quickly produces initial
routing that will later be used during detailed routing. Track routing does not generate
vias or create connections
To exact pin locations and does not address all layout rules.
Like global routing, track routing works on the bucket level . It orders
and spaces the net segments and assigns them to legal track positions. Proper ordering
and spacing greatly reduces crosstalk coupling and noise. Track routing does not adjust
the topologies set during global routing; therefore, the congestion predicted by global
routing is not altered.
Track Routing
Track routing complements detailed routing in terms of the types of regions routed. By
routing long channels across entire single-bucket rows or columns, track routing
processes much larger areas at a time than detailed routing. A more global view of the
layout allows the track router to generate long, straight routes for long nets and produces
accurate jogging around large routing obstacles, such as
power mesh elements.Track routing results are the starting point for final routing by the
detailed router.
Detailed Routing
The Magma design system’s detailed router is a powerful area router that works on
arbitrary regions (of reasonable sizes). Detailed routing respects any nondefault routing
rules you define, allowing you to control routing results. In addition, detailed routing has
engineering change order (ECO) and incremental capability, which supports quick
repairs. The detailed router observes DRC and LVS rules, such as island and multiport
rules.
• Analyzes the net-segment topologies
• Converts the segments to actual wires and vias that connect all pins
of all nets.
• Begins the process of correcting technology rule violations
Experiments
Aim: To find the change in various parameters between normal fix wire and when
crosstalk delay option is enabled in the fix wire.
600000
481223 nets changed their length in the range of 0 to 10
392557 nets did not undergo any change in wire length
500000 All figures are in microns
100-250
400000 10 to 50
50 to 100
300000 250 -500
500 - 750
200000 750 -1000
0 -10
100000
0
Number of cells versus displacement in microns
(remaining cells displacement is 0)
12000
10000 0-5
5 to 15
8000 15-30
30-50
6000 50-75
75-150
4000 150-250
250-400
2000 >400
18
16
14 via1
12 via2
via3
10
via4
8
via5
6
via6
4 via7
2
0
Aim: To find the change in the number of vias after changing the overhang dimensions
according to the fab requirements.
Fab requirements :
0.3
via1
0.25 via2
0.2 via3
via4
0.15
via5
0.1 via6
0.05 via7
• SPCE 34747 6
• SHRT 64216 0
• ISPC 1626 0
• offg 306509 1752
• ispc 164926 8980
• spce 387876 32913
• nspc 8478 0
• shrt 458021 -7725
• ntch 33370 1357
• Open 64 6
• ilnd 494055 152070
• dgnl 939 18
• Hole 530 -10
• mprt 543 -1
• pwro 79683 0
• viav 9338 0
• shed 49647 -275
Aim: To obtain changes in various routing parameters with different versions of TALUS
and different fix wire scripts.
COMPARISON OF VARIOUS PARAMETERS DURING ROUTING IN
DIFFERENT VERSIONS OF TALUS (OMAP3430)
No. of CPUs 1 1 1 1
Overflow>100% 0% 0% 0% 0%
G
L Overflow>85% 83% 83.1% 83.3% 83.3%
O
B Std. Cell Region 0% 0% 0% 0%
A Overflow>100%
L
Std. Cell Region 39.1% 39.2% 40.5% 40.5%
R Overflow>85%
O
U Set Up WNS/TNS/FEP -7631 -7649 -7629 -7629
T -3481331 -3510595 -3563669 -3563669
I 1070 1073 1079 1079
N
G Hold WNS/TNS/FEP -4691 -4848 -4762 -4762
-318391 -323497 -314234 -314234
808 841 730 730
DRC count
Spce 219 223 339 353
shrt 3963 3846 4312 4486
No. of CPUs 4 4 4 4
Overflow>100% 0% 0% 0% 0%
G
L Overflow>85% 35% 35% 35.2% 35%
O
B Std. Cell Region 0% 0% 0% 0%
A Overflow>100%
L
Std. Cell Region 26.3% 26.5% 26.6% 26.4%
R Overflow>85%
O
U Set Up WNS/TNS/FEP -70 -78 -6 -11
T -260 -377 -6 -25
I 6 9 1 4
N
G Hold WNS/TNS/FEP -68186 -68187 -68184 -68184
-1632341 -1641320 -1674599 -1726031
32499 32580 33229 34065
T
R Short 0 0 0 0
A
C Spacing 0 0 1273 649
K (15679u) (7587u)
Talus 1.0.82
Run Time 63 60 C 66 59
TR W 28
RR Antenna 12 11 11 13
The right configurations and the right script gave considerably better results. Talus
version 1.0.82 did not show much benefit though. Enabling sub grid routing reduced the
DRC count. Configuring enhanced access points also improved results. Allowed via
overhang rotation increased via count considerably and did not make much changes in
the DRC count. Changing the dimensions of the overhang according to the Fabrication
requirements increased the via count marginally but considerably increased the DRC
count.