From 081e16d7d9ee4c5b48d37b97be150a5588ec403d Mon Sep 17 00:00:00 2001 From: stefan schippers Date: Tue, 20 Dec 2022 12:32:15 +0100 Subject: [PATCH] doc updates (schematic symbol attribute) --- doc/xschem_man/symbol_property_syntax.html | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/doc/xschem_man/symbol_property_syntax.html b/doc/xschem_man/symbol_property_syntax.html index 732752b3..88716fdb 100644 --- a/doc/xschem_man/symbol_property_syntax.html +++ b/doc/xschem_man/symbol_property_syntax.html @@ -485,7 +485,22 @@ verilog_format="xnor #(@risedel , @falldel ) @name ( @@Z , @@A , @@B );"
  • schematic

    • This attribute specifies an alternate schematic file to open when descending into the subcircuit: + 

     schematic=inv_2.sch
    +

    + It is possible to call a TCL procedure to decide the schematic to descend into: +

    + 
     schematic="tcleval([hierarchy_config @symname])"
    +

    + The above schematic attribute will be evaluated by a hierarchy_config + TCL procedure (which must be defined) and the @symname attribute will be expanded to the name of the + symbol before passing the argument to the TCL procedure. + This allows user defined schematic selection in the hierarchy to simulate the design at different + details/abstraction levels.
    + One suggested approach is to define for a given opamp_65nm.sym symbol several schematics like + opamp_65nm.sch, opamp_65nm_pex.sch, opamp_65nm_aged.sch, + opamp_65nm_empty.sch, ... and define some user accessible method in hierarchy_config procedure + to select one of these 'switch' schematics.

    PREDEFINED SYMBOL VALUES