Differences

This shows you the differences between two versions of the page.

--- language:langs:sizing [2020/05/03 12:47] – rajit
+++ language:langs:sizing [2022/05/13 12:53] (current) – rajit
@@ Line 2: / Line 2: @@
 The sizing sub-language is used to simplify gate sizing specifications. The [[prs|prs]] sub-language already provides a mechanism to specify sizing, but this can become very verbose. For example, consider an inverter
-<code>
+<code act>
 prs {
   in => out-
@@ Line 9: / Line 9: @@
 Now, if we want the pull-up network to have width 20 units and  the pull-down to have width 10 units, this gets turned into:
-<code>
+<code act>
 prs {
   in<10> -> out-
@@ Line 20: / Line 20: @@
 Often all one is interested in is sizing the gates so that they have some unit drive strength, where the unit selected is technology/project specific.  The sizing body is the way this can be specified. Suppose the ''net'' section of the configuration file specifies that the unit drive strength is 10 lambda, and that the p-to-n ratio is 2. In this case, one can write the following instead:
-<code>
+<code act>
 prs {
   in => out-
@@ Line 32: / Line 32: @@
 This has the same effect as:
-<code>
+<code act>
 prs {
   in <10> -> out-
@@ Line 40: / Line 40: @@
 The p-to-n ratio is automatically used to size the pull-up network differently from the pull-down network.
-<code>
+<code act>
 prs {
   a & b => c-
@@ Line 51: / Line 51: @@
 The example above results in the following sizing:
-<code>
+<code act>
 prs {
   a<20> & b<20> -> c-
@@ Line 66: / Line 66: @@
 An example of the general form of the sizing directive is:
-<code>
+<code act>
  sizing {
    out {-5,lvt,2 ; +4,lvt,2 }
@@ Line 72: / Line 72: @@
 </code>
 This says that the pull-down network should be sized with 5 times  the drive strength, and all gates should use two fingers and ''lvt'' flavor transistors. The pull-up network should be sized with 4 times the unit drive strength, use ''lvt'' transistors, and two fingers. The order of the two drive strengths can be interchanged; i.e. this is the same as writing
-<code>
+<code act>
 sizing {
   out {+4,lvt,2 ; -5,lvt,2 }
@@ Line 80: / Line 80: @@
 If a circuit wants to use a different unit width, that can also be specified as follows:
-<code>
+<code act>
 sizing {
-  unit_n 20;
+  unit_n <- 20;
   out {-1};
 }
@@ Line 92: / Line 92: @@
 The benefits of a sizing body are best illustrated when combined with the implementation relation. Consider the following example:
-<code>
+<code act>
 defproc inv (bool? i; bool! o)
 {
@@ Line 114: / Line 114: @@
 This is an example of defining two standard inverters, that correspond to the same logical production rules but having different sizing.
+===== P/N ratios =====
+The default sizing equalizes drive strengths for the pull-up and pull-down network. For gates used in cyclic control logic in asynchronous design, the optimal drive strengths are different. To use the optimal ratio, you can add:
+<code act>
+prs {
+  in[1] & in[0] #> out-
+}
+sizing {
+  p_n_mode <- 1; /* this modifies the sizing */
+  out {-1}
+}
+</code>
+The ratio will be computed using parameters in the netlist section of the ACT [[config:netlist|configuration]] file.
+===== Low leak addition on channel length =====
+In some technologies, the minimum length devices have extremely high leakage. To avoid using these, you can specify an adjustment that will be added to the length to avoid this case. This adjustment is only applied to minimum length devices.
+For adding a specified additional length to the minimum length of your transistors, activate ''leak_adjust''.
+<code act>
+prs {
+  in => out-
+}
+sizing {
+   leak_adjust <- 1;
+   out{-1}
+}
+</code>
+To configure how much is added add this line to the configuration
+<code>
+# add to length for leakage management [used if l=min length]
+real leakage_adjust 15e-9
+</code>
+The length unit here is absolute (i.e. not scaled), so the amount specified above is 15nm.