Differences

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

--- intro_example:start [2025/05/17 11:58] – [Simple circuit examples] rajit
+++ intro_example:start [2025/05/22 10:01] (current) – [Organizing your design] rajit
@@ Line 5: / Line 5: @@
 ACT supports the description of circuits are multiple levels of abstraction in a unified framework. Details of the language can be found in the [[language:start|detailed language description]]. The examples provided below are a gentler introduction to various language features, and may be easier to follow than the language description itself.
-===== Simple circuit examples =====
+===== Circuit examples =====
 ACT can describe circuits are multiple levels of abstraction. At the highest level of abstraction, circuits
@@ Line 19: / Line 19: @@
   * Dependent [[template_deps|templates]]
   * Using [[standard_sim|standard testing environments]]
+  * More on [[connection_info|connections]] and how they work
   * [[loops|Loops]] and selections
   *Other ways to write the [[intro_example:chp_fifo2|buffer example]]
+  * [[assertions|Assertions]] in parameterized definitions
+  * [[name_mangling|Expanded names]] in ACT
+  * Using [[.pure_struct|pure structures]]
+  * Defining [[.operators|operators]]
-Sometimes parameterized components are only valid for certain parameter ranges. ACT includes
-assertions that are checked at expansion time that can be used to validate the assumptions made.
-   * [[assertions|Assertions]] in parameterized definitions
-===== Pure structures =====
-[[language:types2:data#pure_structures|Pure structures]] are user-defined data types that can be used to group related values (like ''struct'' in C/C++).
-   * Using [[.pure_struct|pure structures]]
-   * Defining [[.operators|operators]]
 ===== Organizing your design =====
@@ Line 39: / Line 33: @@
   * Creating [[namespace|libraries and namespaces]]
+  * Organizing your [[files|files]]
   * Tracking [[dependencies|dependencies]] between ACT files
@@ Line 44: / Line 39: @@
 ===== Low-level circuit design and SPICE simulation =====
-So far we have learned how to describe a circuit in ACT, simulate using prsim and irsim. Now, we will move on to the next stage i.e. designing CMOS circuits from ACT description. The process of designing circuit often starts with creating a spice netlist to simulate transistor-level circuit behavior. In order to generate a spice netlist, ACT requires some technology-dependent information and information to understand designer’s intent. We use configuration files to provide such information. For more information on configuration files, see [[config:start|ACT configuration files]]
+So far we have learned how to describe a circuit in ACT, simulate using actsim, prsim and irsim. Now, we will move on to the next stage i.e. designing CMOS circuits from ACT description. The process of designing circuit often starts with creating a spice netlist to simulate transistor-level circuit behavior. In order to generate a spice netlist, ACT requires some technology-dependent information and information to understand designer’s intent. We use configuration files to provide such information. For more information on configuration files, see [[config:start|ACT configuration files]]
 The configuration files are saved in ''$ACT_HOME/conf/<technology>/'' directory. The default technology is called ''generic'', and the default configuration options are in ''global.conf''. It is possible to save technology specific configuration for each tool in a separate configuration file. For example, ''prs2net.conf'' for configuration related to netlist generator and ''layout.conf'' for layout parameters.
@@ Line 50: / Line 45: @@
    * Specifying transistor [[sizing|sizes]] for CMOS implementation
    * Generating spice [[netlist|netlist]] and simulation with [[https://xyce.sandia.gov/about_xyce/index.html|Xyce]]
+   * [[name_mangling|Name mangling]] in ACT
 ===== External tools =====