riscv
/
coriolis
mirror of https://gitlab.lip6.fr/vlsi-eda/coriolis.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
coriolis/crlcore/etc/symbolic/cmos/technology.conf

63 lines
2.1 KiB
Plaintext
Raw Normal View History

Add a common/ to share the trunk of symbolic technologies configurations. In CRL Core configuration files, "display.conf", "patterns.conf" and "technology.conf" share most of their code. So that common part is put into "common/" and sourced from the final configuration file. Update the documentation according the the new initialization scheme.
2014-05-21 17:13:17 -05:00
# -*- Mode:Python; explicit-buffer-name: "technology.conf<cmos>" -*-
* All Tools: - A complete sweep of cleanup to suppress allmost all compiler warnings. * ./crlcore: - New: Extented Python support for all objects needed to configure Coriolis. - New: Configuration files and load helpers completly written in Python. An XML emulation mode is still avalaible. - New: UsersGuide, as a replacement for README, written in ReST. - New: Start of Doxygen documentation (mostly for documenting the initialisation objects & methods).
2012-11-16 06:49:47 -06:00
Correct handling of lambdas & microns in configuration files. * Bug: In CRL/etc/NODE/VENDOR/Technology.conf, the database must be configured as early has possible so the functions ensuring length conversions can work correctly (l(v), u(v)). So we can no longer rely on a table to be read after the execution of the file. We perform a direct call to the helpers.Technology.initTechno() function. And it must be made first thing. In all tables taking dimensions, we must use one of the converter function helpers.l(v), helpers.u(v) or helpers.n(v) so the the value v get converted in lambda, microns or nanometer (resp.). Make the modifications in all technology.conf and kite.conf files. * Change: In CRL/coriolisInit.py, remove the technoConfig variable that has been replaced by a direct call to helpers.Technology.initTechno(). * Change: In CRL/helpers.Alliance.loadRoutingGaugesTable(), no longer try to convert coordinates, they must already be in DbU. * Change: In CRL/helpers.__init__.py, remove lambdaMode() and micronsMode() they could not be made to work as expected. Create l(), u(), n() as replacement.
2018-07-16 04:32:40 -05:00
from Hurricane import DbU
from helpers import sysConfDir
from helpers import l, u, n
from helpers.Technology import initTechno
* All Tools: - A complete sweep of cleanup to suppress allmost all compiler warnings. * ./crlcore: - New: Extented Python support for all objects needed to configure Coriolis. - New: Configuration files and load helpers completly written in Python. An XML emulation mode is still avalaible. - New: UsersGuide, as a replacement for README, written in ReST. - New: Start of Doxygen documentation (mostly for documenting the initialisation objects & methods).
2012-11-16 06:49:47 -06:00
Add a common/ to share the trunk of symbolic technologies configurations. In CRL Core configuration files, "display.conf", "patterns.conf" and "technology.conf" share most of their code. So that common part is put into "common/" and sourced from the final configuration file. Update the documentation according the the new initialization scheme.
2014-05-21 17:13:17 -05:00
# The informations here are extracted from the Alliance ".rds" file,
# and must be coherent with it.
* All Tools: - A complete sweep of cleanup to suppress allmost all compiler warnings. * ./crlcore: - New: Extented Python support for all objects needed to configure Coriolis. - New: Configuration files and load helpers completly written in Python. An XML emulation mode is still avalaible. - New: UsersGuide, as a replacement for README, written in ReST. - New: Start of Doxygen documentation (mostly for documenting the initialisation objects & methods).
2012-11-16 06:49:47 -06:00
#
Add a common/ to share the trunk of symbolic technologies configurations. In CRL Core configuration files, "display.conf", "patterns.conf" and "technology.conf" share most of their code. So that common part is put into "common/" and sourced from the final configuration file. Update the documentation according the the new initialization scheme.
2014-05-21 17:13:17 -05:00
# Provides standard settings for:
# - <viewerConfig>
# - <realLayersTable>
Cleaner support for real technologies (Hurricane, CRL Core configuration). * Change: In Hurricane::Technology, in all the layer connexity methods (getLayers(), getMetalAbove(), getCutAbove(), getViaBetween(), ...) the "useWorking" parameter is replaced by a more accurate "useSymbolic". BEHAVIOR CHANGE: formerly, if a symbolic layer was requested, and none was found, NULL was returned. Now, if the symbolic layer is not found, we try to return the associated real one (same layer mask, but not flagged as symbolic, and usually with a lowercase name). All thoses changes have been propagated to Python bindings. * Change: In Hurricane::BasicLayer and derived classes, rename the "isWorking" attribute into "isSymbolic" (to match the technology renaming). * Change: In Hurricane::Cell::flattenNets(), ignore power, ground and blockage nets for the flatten. * Change: In CRL Core, in coriolisInit.py and Technology.py helpers, rename the tables describing the technology as follow: - symbolicLayersTable --> compositeLayersTable - workingLayersTable --> symbolicLayersTable - symbolicRulesTable --> layersExtensionsTable This is to give the table names a more clearer semantic after merging real technologies configurations (testbench AMS c35b4). In particular, we need to define a composite layer for the real VIAs, and not only the symbolic ones. And with correct enclosures expressed in real dimensions (microns).
2017-12-27 06:13:29 -06:00
# - <compositeLayersTable>
Add a common/ to share the trunk of symbolic technologies configurations. In CRL Core configuration files, "display.conf", "patterns.conf" and "technology.conf" share most of their code. So that common part is put into "common/" and sourced from the final configuration file. Update the documentation according the the new initialization scheme.
2014-05-21 17:13:17 -05:00
# - <symbolicLayersTable>
* All Tools: - A complete sweep of cleanup to suppress allmost all compiler warnings. * ./crlcore: - New: Extented Python support for all objects needed to configure Coriolis. - New: Configuration files and load helpers completly written in Python. An XML emulation mode is still avalaible. - New: UsersGuide, as a replacement for README, written in ReST. - New: Start of Doxygen documentation (mostly for documenting the initialisation objects & methods).
2012-11-16 06:49:47 -06:00
Correct H/K parameters for global routing. New cmos45 symbolic. * Change: In CRL/etc/cmos/kite.conf, setup correct H/K parameters for the Katana global router. Value copied from Knik. They give a faster solution. * New: In CRL/etc/cmos45/, new symbolic settings adapted to FreePDK 45nm. Courtesy of N. Shimizu. To be used with NSXLIB. * New In CRL::System, add "coriolis_top" to the set of pathes available to the user.
2019-02-26 13:00:28 -06:00
initTechno( { 'name' : 'cmos45'
Correct handling of lambdas & microns in configuration files. * Bug: In CRL/etc/NODE/VENDOR/Technology.conf, the database must be configured as early has possible so the functions ensuring length conversions can work correctly (l(v), u(v)). So we can no longer rely on a table to be read after the execution of the file. We perform a direct call to the helpers.Technology.initTechno() function. And it must be made first thing. In all tables taking dimensions, we must use one of the converter function helpers.l(v), helpers.u(v) or helpers.n(v) so the the value v get converted in lambda, microns or nanometer (resp.). Make the modifications in all technology.conf and kite.conf files. * Change: In CRL/coriolisInit.py, remove the technoConfig variable that has been replaced by a direct call to helpers.Technology.initTechno(). * Change: In CRL/helpers.Alliance.loadRoutingGaugesTable(), no longer try to convert coordinates, they must already be in DbU. * Change: In CRL/helpers.__init__.py, remove lambdaMode() and micronsMode() they could not be made to work as expected. Create l(), u(), n() as replacement.
2018-07-16 04:32:40 -05:00
, 'precision' : 2
, 'gridValue' : 0.005
, 'gridUnit' : DbU.UnitPowerMicro
, 'gridsPerLambda' : 24
, 'symbolicGridStep' : 1.0
, 'polygonStep' : 24.0
} )
* All Tools: - A complete sweep of cleanup to suppress allmost all compiler warnings. * ./crlcore: - New: Extented Python support for all objects needed to configure Coriolis. - New: Configuration files and load helpers completly written in Python. An XML emulation mode is still avalaible. - New: UsersGuide, as a replacement for README, written in ReST. - New: Start of Doxygen documentation (mostly for documenting the initialisation objects & methods).
2012-11-16 06:49:47 -06:00
Correct handling of lambdas & microns in configuration files. * Bug: In CRL/etc/NODE/VENDOR/Technology.conf, the database must be configured as early has possible so the functions ensuring length conversions can work correctly (l(v), u(v)). So we can no longer rely on a table to be read after the execution of the file. We perform a direct call to the helpers.Technology.initTechno() function. And it must be made first thing. In all tables taking dimensions, we must use one of the converter function helpers.l(v), helpers.u(v) or helpers.n(v) so the the value v get converted in lambda, microns or nanometer (resp.). Make the modifications in all technology.conf and kite.conf files. * Change: In CRL/coriolisInit.py, remove the technoConfig variable that has been replaced by a direct call to helpers.Technology.initTechno(). * Change: In CRL/helpers.Alliance.loadRoutingGaugesTable(), no longer try to convert coordinates, they must already be in DbU. * Change: In CRL/helpers.__init__.py, remove lambdaMode() and micronsMode() they could not be made to work as expected. Create l(), u(), n() as replacement.
2018-07-16 04:32:40 -05:00
execfile( sysConfDir+'/common/technology.conf' )
Reorganisation of technology configuration files. * Change: In CRL Core, in coriolis2/etc the file an directory structure describing the technonolies is modified. Before, one technology was split in two: the symbolic part that may be shared across multiple real technology and the real technology itself. To configure this we needed in ".coriolis2/techno.py" two variables: * symbolicTechnology. * realTechnology. After, we duplicate the symbolic technology in each real ones, so to configure we only have to refer to one technology with the variable: * technology. Pure sympolic technologies are still availables, associated with a dummy real one. We provides: * 180/scn6m_deep_09 for MOSIS 180nm * 45/freepdk_45 for FreePDK 45nm (work in progress). * symbolic/cmos for classical Alliance symbolic. * Change: In CRL Core python/helpers, SymbolicTechnology.py and RealTechnology.py are now grouped under Technology.py.
2017-11-17 04:10:32 -06:00
Cleaner support for real technologies (Hurricane, CRL Core configuration). * Change: In Hurricane::Technology, in all the layer connexity methods (getLayers(), getMetalAbove(), getCutAbove(), getViaBetween(), ...) the "useWorking" parameter is replaced by a more accurate "useSymbolic". BEHAVIOR CHANGE: formerly, if a symbolic layer was requested, and none was found, NULL was returned. Now, if the symbolic layer is not found, we try to return the associated real one (same layer mask, but not flagged as symbolic, and usually with a lowercase name). All thoses changes have been propagated to Python bindings. * Change: In Hurricane::BasicLayer and derived classes, rename the "isWorking" attribute into "isSymbolic" (to match the technology renaming). * Change: In Hurricane::Cell::flattenNets(), ignore power, ground and blockage nets for the flatten. * Change: In CRL Core, in coriolisInit.py and Technology.py helpers, rename the tables describing the technology as follow: - symbolicLayersTable --> compositeLayersTable - workingLayersTable --> symbolicLayersTable - symbolicRulesTable --> layersExtensionsTable This is to give the table names a more clearer semantic after merging real technologies configurations (testbench AMS c35b4). In particular, we need to define a composite layer for the real VIAs, and not only the symbolic ones. And with correct enclosures expressed in real dimensions (microns).
2017-12-27 06:13:29 -06:00
# Format of <layersExtensionsTable>:
* All Tools: - A complete sweep of cleanup to suppress allmost all compiler warnings. * ./crlcore: - New: Extented Python support for all objects needed to configure Coriolis. - New: Configuration files and load helpers completly written in Python. An XML emulation mode is still avalaible. - New: UsersGuide, as a replacement for README, written in ReST. - New: Start of Doxygen documentation (mostly for documenting the initialisation objects & methods).
2012-11-16 06:49:47 -06:00
# Each entry is a pair of (string, value).
Cleaner support for real technologies (Hurricane, CRL Core configuration). * Change: In Hurricane::Technology, in all the layer connexity methods (getLayers(), getMetalAbove(), getCutAbove(), getViaBetween(), ...) the "useWorking" parameter is replaced by a more accurate "useSymbolic". BEHAVIOR CHANGE: formerly, if a symbolic layer was requested, and none was found, NULL was returned. Now, if the symbolic layer is not found, we try to return the associated real one (same layer mask, but not flagged as symbolic, and usually with a lowercase name). All thoses changes have been propagated to Python bindings. * Change: In Hurricane::BasicLayer and derived classes, rename the "isWorking" attribute into "isSymbolic" (to match the technology renaming). * Change: In Hurricane::Cell::flattenNets(), ignore power, ground and blockage nets for the flatten. * Change: In CRL Core, in coriolisInit.py and Technology.py helpers, rename the tables describing the technology as follow: - symbolicLayersTable --> compositeLayersTable - workingLayersTable --> symbolicLayersTable - symbolicRulesTable --> layersExtensionsTable This is to give the table names a more clearer semantic after merging real technologies configurations (testbench AMS c35b4). In particular, we need to define a composite layer for the real VIAs, and not only the symbolic ones. And with correct enclosures expressed in real dimensions (microns).
2017-12-27 06:13:29 -06:00
# * string: a synthetic way to designate the real or symbolic layer on
# which it applies, an optional sub layer (BasicLayer) in case
# where there is more than one, and the dimension name.
Correct handling of lambdas & microns in configuration files. * Bug: In CRL/etc/NODE/VENDOR/Technology.conf, the database must be configured as early has possible so the functions ensuring length conversions can work correctly (l(v), u(v)). So we can no longer rely on a table to be read after the execution of the file. We perform a direct call to the helpers.Technology.initTechno() function. And it must be made first thing. In all tables taking dimensions, we must use one of the converter function helpers.l(v), helpers.u(v) or helpers.n(v) so the the value v get converted in lambda, microns or nanometer (resp.). Make the modifications in all technology.conf and kite.conf files. * Change: In CRL/coriolisInit.py, remove the technoConfig variable that has been replaced by a direct call to helpers.Technology.initTechno(). * Change: In CRL/helpers.Alliance.loadRoutingGaugesTable(), no longer try to convert coordinates, they must already be in DbU. * Change: In CRL/helpers.__init__.py, remove lambdaMode() and micronsMode() they could not be made to work as expected. Create l(), u(), n() as replacement.
2018-07-16 04:32:40 -05:00
# * value : the rule (dimension) value.
# Values/dimensions must be given using one of the following conversion
# function:
# * l(value) : value expressed in lambda (symbolic).
# * u(value) : value is expressed in microns.
# * n(value) : value is expressed in nanometers.
layersExtensionsTable = symbolicLayersExtensionsTable
Reorganisation of technology configuration files. * Change: In CRL Core, in coriolis2/etc the file an directory structure describing the technonolies is modified. Before, one technology was split in two: the symbolic part that may be shared across multiple real technology and the real technology itself. To configure this we needed in ".coriolis2/techno.py" two variables: * symbolicTechnology. * realTechnology. After, we duplicate the symbolic technology in each real ones, so to configure we only have to refer to one technology with the variable: * technology. Pure sympolic technologies are still availables, associated with a dummy real one. We provides: * 180/scn6m_deep_09 for MOSIS 180nm * 45/freepdk_45 for FreePDK 45nm (work in progress). * symbolic/cmos for classical Alliance symbolic. * Change: In CRL Core python/helpers, SymbolicTechnology.py and RealTechnology.py are now grouped under Technology.py.
2017-11-17 04:10:32 -06:00
gdsLayersTable = \
Added GDSII driver. Bug in Blif parser. * New: In CRL, implement a true GDSII driver. The driver is directly under CRL and do not use an intermediate structure in vlsisapd. The ASCII GDSII is removed. Huge polygons are not supported yet. Have to be split up in sub-polygons of less than 4000 vertexes. Symbolic layout can be exported to give a rough idea of the layout but RDS expension is not applied. Symbolic composite layers are expansed into their basic layers so the design *looks* normal. * Deprecated: In CRL, remove all traces of the old XML configuration parsers. No one needs them now, including Chams. * Bug: In CRL::BlifParser, before blindly loading the model of a subckt from disk with AllianceFramework, checks if it is in the Catalog first. Load with AllianceFramework only cells that are in the Catalog. This prevent a file of the same name than a model to be loaded shadowing the later defintion of the model in the Blif file. All this is due to the fact that Blif could be non-ordered for the models... * Change: In Hurricane::BasicLayer, the "extract number" is replaced by a GdsLayer and GdsDatatype to generate accurate GDS files. Even if datatype is 0 most of the time. Update all the "technology.conf" files in CRL to provide those two numbers.
2018-05-15 03:03:13 -05:00
( ("nWell" , "NWELL" , 3, 0)
, ("nImplant", "NPLUS" , 26, 0)
, ("pImplant", "PPLUS" , 25, 0)
, ("active" , "ACTIVE" , 6, 0)
, ("poly" , "POLY" , 17, 0)
, ("cut0" , "CONTACT", 30, 0)
, ("metal1" , "METAL1" , 31, 0)
, ("cut1" , "VIA1" , 51, 0)
, ("metal2" , "METAL2" , 32, 0)
, ("cut2" , "VIA2" , 52, 0)
, ("metal3" , "METAL3" , 33, 0)
, ("cut3" , "VIA3" , 53, 0)
, ("metal4" , "METAL4" , 34, 0)
, ("cut4" , "VIA4" , 54, 0)
, ("metal5" , "METAL5" , 35, 0)
, ("cut5" , "VIA5" , 55, 0)
, ("metal6" , "METAL6" , 36, 0)
Reorganisation of technology configuration files. * Change: In CRL Core, in coriolis2/etc the file an directory structure describing the technonolies is modified. Before, one technology was split in two: the symbolic part that may be shared across multiple real technology and the real technology itself. To configure this we needed in ".coriolis2/techno.py" two variables: * symbolicTechnology. * realTechnology. After, we duplicate the symbolic technology in each real ones, so to configure we only have to refer to one technology with the variable: * technology. Pure sympolic technologies are still availables, associated with a dummy real one. We provides: * 180/scn6m_deep_09 for MOSIS 180nm * 45/freepdk_45 for FreePDK 45nm (work in progress). * symbolic/cmos for classical Alliance symbolic. * Change: In CRL Core python/helpers, SymbolicTechnology.py and RealTechnology.py are now grouped under Technology.py.
2017-11-17 04:10:32 -06:00
)