Initial version of donated sources by Avertec, 3.4p5.
[tas-yagle.git] / distrib / docxml2 / text / doc / hitas_reference / ctkFormat.xml
1 <?xml version="1.0" encoding="ISO-8859-1" ?>
2 <section niv='2'><title>CTK - Crosstalk Report Information</title>
3
4 <p>The <f>.ctk</f> file is an ASCII text file made up of three distinct sections. This file contains the following information:</p>
5 <list>
6 <item>Delay changes due to crosstalk</item>
7 <item>Detailed aggression reports for all analyzed nets</item>
8 <item>Peak noise voltage for all analyzed nets</item>
9 </list>
10
11
12
13
14
15
16 <section niv='3'><title>Delay Changes due to Crosstalk</title>
17
18 <p>This section reports all delay and slopes which have changed due to crosstalk. Thresholds for slope and delay changes can be set to avoid excessive reporting information. These thresholds are set using the <f>ctkDeltaDelayMin</f> and <f>ctkDeltaSlopeMin</f> configuration variables.</p>
19 <p>The syntax of this section is as follows:</p>
20 <code>
21 <cl>BeginDelay</cl>
22 <cl> UP|DW &lt;start&gt; UP|DW &lt;end&gt;</cl>
23 <cl> delay|slope min|max &lt;nominal&gt; -&gt; &lt;aggressed&gt;</cl>
24 <cl> | |</cl>
25 <cl> | |</cl>
26 <cl> delay|slope min|max &lt;nominal&gt; -&gt; &lt;aggressed&gt;</cl>
27 <cl> |</cl>
28 <cl> |</cl>
29 <cl> UP|DW &lt;start&gt; UP|DW &lt;end&gt;</cl>
30 <cl> delay|slope min|max &lt;nominal&gt; -&gt; &lt;aggressed&gt;</cl>
31 <cl> | |</cl>
32 <cl> | |</cl>
33 <cl> delay|slope min|max &lt;nominal&gt; -&gt; &lt;aggressed&gt;</cl>
34 <cl>EndDelay</cl>
35 </code>
36 <p>Fields &lt;start&gt; and &lt;end&gt; represent timing signal names. If the timing signal name is different from the net name, then the net name is given in brackets. Fields &lt;nominal&gt; and &lt;aggressed&gt; represent delay values in picoseconds without and with crosstalk respectively.</p>
37
38 </section>
39
40 <section niv='3'><title>Detailed Aggression Report</title>
41
42 <p>This section gives detailed aggressor information for nets whose total coupling capacitance exceeds a certain threshold. The coupling capacitance due to each aggressor is given, as well as information as to whether the aggressor can modify minimum or maximum delays. Only nets for which the relative coupling capacitance is greater than the <f>ctkrcapamin</f> configuration variable are reported.</p>
43 <p>The syntax of this section is as follows:</p>
44 <code>
45 <cl>BeginCrosstalk</cl>
46 <cl> Node: DW|UP &lt;signal&gt; </cl>
47 <cl> Ground capacitance: &lt;value&gt;</cl>
48 <cl> Aggressor:</cl>
49 <cl> [*] &lt;signal&gt; [B] [W] [R] [F] cc=&lt;value&gt;</cl>
50 <cl> | |</cl>
51 <cl> | |</cl>
52 <cl> [*] &lt;signal&gt; [B] [W] [R] [F] cc=&lt;value&gt;</cl>
53 <cl> ---------</cl>
54 <cl> &lt;total&gt; (&lt;relative&gt;)</cl>
55 <cl> |</cl>
56 <cl> |</cl>
57 <cl> Node: DW|UP &lt;signal&gt; </cl>
58 <cl> Ground capacitance: &lt;value&gt;</cl>
59 <cl> Aggressor:</cl>
60 <cl> [*] &lt;signal&gt; [B] [W] [R] [F] cc=&lt;value&gt;</cl>
61 <cl> | |</cl>
62 <cl> | |</cl>
63 <cl> [*] &lt;signal&gt; [B] [W] [R] [F] cc=&lt;value&gt;</cl>
64 <cl> ---------</cl>
65 <cl> &lt;total&gt; (&lt;relative&gt;)</cl>
66 <cl> </cl><cl>EndCrosstalk</cl>
67 </code>
68 <p>If a star (*) is present before an aggressor name, it mean that there is no corresponding timing signal. As no switching information is provided for this aggressor, the crosstalk engine assumes that this aggressor is always an active aggressor.</p>
69 <p>If the character 'B' or 'W' or both are present on a line, this means that the aggressor can modify minimum propagation delays (B = Best Case) or maximum propagation delays (W = Worst Case). If the character 'R' or 'F' or both are present on a line, this means that the aggressor has made a contribution to calculate the real rise (R) peak noise voltage value or the real fall (F) peak noise voltage value. These characters can appear in lower case ('b','w','r','f') when crosstalk mutex are used. This means the influence of the net is ignored because of the crosstalk mutex.
70 The total value of the coupling capacitance and it relative contribution to the total net capacitance is also given.</p>
71
72 </section>
73
74 <section niv='3'><title>Peak Noise Report</title>
75
76 <p>This section gives the results of a calculation of upper and lower peak voltages on a net as a result of its aggressors. This list is sorted according to the peak noise voltage value. Only nets for which the peak noise voltage is above the threshold given by the <f>ctknoisemin</f> configuration variable are reported.</p>
77 <p>The syntax of this section is as follows:</p>
78 <code>
79 <cl>BeginNoise</cl>
80 <cl> DW|UP &lt;signal&gt; &lt;mod ovr&gt; &lt;max ovr&gt; &lt;real ovr&gt; \\</cl>
81 <cl> &lt;mod und&gt; &lt;max und&gt; &lt;real und&gt;</cl>
82 <cl> |</cl>
83 <cl> DW|UP &lt;signal&gt; &lt;mod ovr&gt; &lt;max ovr&gt; &lt;real ovr&gt; \\</cl>
84 <cl> &lt;mod und&gt; &lt;max und&gt; &lt;real und&gt;</cl>
85 <cl>EndNoise</cl>
86 </code>
87 <p>For each state (UP or DOWN) of a signal, the crosstalk engine gives the peak noise voltage (&lt;max ovr&gt; and &lt;max und&gt;) calculated with all aggressors considered active, and the "real" noise voltage (&lt;real ovr&gt; and &lt;real und&gt;) calculated considering possible switching configurations of aggressors. &lt;mod ovr&gt; and
88 &lt;mod und&gt; are the electrical model used to evaluate peak noise voltage.</p>
89 <p>Currently, the noise voltage on the net is evaluated by replacing the net driver by a single equivalent constant-valued resistor. This value is either determined from the transistor netlist (model SCR) or, if this is not possible, defined by the <f>ctknoisedefaultresi</f> configuration variable (model CC). Both overshoot and undershoot values are calculated for each signal state.</p>
90
91 </section>
92 </section>
93