jcarr
/
coriolis
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
coriolis/crlcore/etc/symbolic/cmos/kite.conf

65 lines
2.9 KiB
Plaintext
Raw Normal View History

More configuration sharing. * Change: In CRL Core, .../etc/, put all that's shared under .../common/, all layouts and some settings not technologically dependant.
2014-05-27 08:40:42 -05:00
# -*- Mode:Python; explicit-buffer-name: "kite.conf<cmos>" -*-
import helpers
# Contains the layout (shared by all technologies).
execfile( helpers.sysConfDir+'/common/kite.conf' )
* 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
parametersTable = \
In CRL, update real conf. files. Smarter management of pin in LEF parser. * Change: In CRL Core, etc/, update the configuration files of real technologies. Mostly for FreePDK 45. This work is also done for AMS c35b4 (350nm) but in a private (SoC) git repository. Added a new parameter 'lefImport.minTerminalwidth' for the minimum size (width) of a metal1 terminal in standard cells. Corrected bug of the minimum trace level which must be initialized to a great value and *not* zero; * Change: In CRL Core, BlifParser, detect when there is no tie low or tie high defined, issue an error (connexion left open) but continue. * New: In CRL::RoutingLayerGauge, new overlad of getTrackPosition() with the parameter set of getTrackIndex(). Used to know if a terminal is on-grid or not. * New: In CRL::LefImport, smarter management of metal1 pins. Adds a _pinPostProcess() function to select the external components among the various shapes. If the gauge is VH, all the pin rectangles are translateds into vertical segments (even if the metal1 gauge says the tracks are horizontals). The _pinPostProcess() function adds as external components of a net, only the segments of a sufficent width as given in 'lefImport.minTerminalWidth' and that are on-grid.
2018-01-06 09:18:33 -06:00
( ('lefImport.minTerminalWidth' ,TypeDouble ,0.0 )
, ("katabatic.globalLengthThreshold",TypeInt ,1450 ) # Katabatic parameters.
More configuration sharing. * Change: In CRL Core, .../etc/, put all that's shared under .../common/, all layouts and some settings not technologically dependant.
2014-05-27 08:40:42 -05:00
, ("katabatic.saturateRatio" ,TypePercentage,80 )
, ("katabatic.saturateRp" ,TypeInt ,8 )
Express "xEdgeCapacity" ratio as "xTracksReservedLocal" a number of tracks. * Change: In Kite, Katabatic & Knik, express the number of tracks truly available to the global router by the number of tracks reserved to the local routage inside a GCell. Replace the ratio parameter "hEdgeCapacity" by an integer parameter "hTracksReservedLocal" (duplicate for verticals). It is more explicit to give directly the number of tracks that are to be used locally, and potentially saves us from rouding problems when calculating the number of availables tracks. Note: we cannot do that for the layer saturateRatio as it uses the density ratio that take account local wires, leading to fractional results. * Change: In Katabatic, in <GCellGrid>, rename checkEdgeSaturation() into checkEdgeOverflow(), more explicit. * Change: In Knik, in <Graph>, display the computed capacities of the lower left node edges (should be the same througout all the grid). * Change: In Unicorn, in <cgt.py>, uses the new parameters names for edge density.
2014-06-10 09:58:52 -05:00
, ('katabatic.topRoutingLayer' ,TypeString , 'METAL5')
Added Routing Gauge for 2-Metal technologies only. * New: In CRL Core, etc/cmos/kite.conf new routing gauge "sxlib-2M" for two metals only technologies. * New: In CRL Core, python/helpers/kite.py, new parameter to set the routing gauge to be used: "kite.routingGauge" (default: "sxlib"). * Change: In CRL/AllianceFramework.cpp, forgot to put the Cell gauges and RoutingGauges in the object Records (Inspector). * New: In pyCRL/PyAllianceFramework.cpp, export the setRoutingGauge() function.
2017-08-18 11:16:43 -05:00
, ('anabatic.routingGauge' ,TypeString , 'sxlib' )
* 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
# Kite parameters.
Express "xEdgeCapacity" ratio as "xTracksReservedLocal" a number of tracks. * Change: In Kite, Katabatic & Knik, express the number of tracks truly available to the global router by the number of tracks reserved to the local routage inside a GCell. Replace the ratio parameter "hEdgeCapacity" by an integer parameter "hTracksReservedLocal" (duplicate for verticals). It is more explicit to give directly the number of tracks that are to be used locally, and potentially saves us from rouding problems when calculating the number of availables tracks. Note: we cannot do that for the layer saturateRatio as it uses the density ratio that take account local wires, leading to fractional results. * Change: In Katabatic, in <GCellGrid>, rename checkEdgeSaturation() into checkEdgeOverflow(), more explicit. * Change: In Knik, in <Graph>, display the computed capacities of the lower left node edges (should be the same througout all the grid). * Change: In Unicorn, in <cgt.py>, uses the new parameters names for edge density.
2014-06-10 09:58:52 -05:00
, ("kite.hTracksReservedLocal" ,TypeInt ,3 , { 'min':0, 'max':20 } )
, ("kite.vTracksReservedLocal" ,TypeInt ,3 , { 'min':0, 'max':20 } )
, ("kite.eventsLimit" ,TypeInt ,4000002 )
, ("kite.ripupCost" ,TypeInt ,3 , { 'min':0 } )
, ("kite.strapRipupLimit" ,TypeInt ,16 , { 'min':1 } )
, ("kite.localRipupLimit" ,TypeInt ,9 , { 'min':1 } )
, ("kite.globalRipupLimit" ,TypeInt ,5 , { 'min':1 } )
, ("kite.longGlobalRipupLimit" ,TypeInt ,5 , { 'min':1 } )
Anabatic transient commit 2. * Change: In Hurricane, in CellWidget, enable the drawing of ExtensionGos according to the the threshold paramaters (as layers do). * Change: In CRL Core, provide DrawingStyle for Anabatic::GCell & Anabatic::Edge. Use the exact name of the ExtensionGo. In kite.conf, add settings for the size of an edge as the optimal size may change between analog & digital designs. * New: In Anabatic: - Support for fast position query using a matrix. - Computation of the Edge capacity, based on the routing gauge parameters. - Graphic display of the edges capacity. Added configuration parameters to size the bounding box of an Edge. * Bug: In Anabatic: - GCell::_moveEdges was both too complex (some cases never arise the way we divide GCells) and bugged.
2016-05-26 06:56:16 -05:00
# Anabatic parameters are temporarily hosted here.
, ("anabatic.edgeLength" ,TypeInt ,24 )
, ("anabatic.edgeWidth" ,TypeInt ,4 )
Anabatic transient commit 8. More Dijkstra bugs correcteds. * Bug: In Anabatic: - In _propagate(), on reaching a target, forgot to remove it from the queue before pushing it back with the new distance. It also simplificate the core algorithm as target as treated normal nodes. * New: In Anabatic: - Update cdebug to use the fastest macro version. - More readable drawings of GCells and Edges. - Added timer support. - The distance is now computed in DbU::Unit (aka long) and not in normalized float. - The distance function is now a callback (std::function<>) that can be changed (a default is provided at initialization). - New concept of branch in the agglomerated connex component. Each trace back part create a "branch" (tagged with a "branchId"). When a node is reached with the same distance, but from two different branches, choose the the branch that was lastly created. This create a slightly different tree which grows outward from the newest branches. - Makes the horizontal edges *slightly* longer than the vertical ones to skew the tree to use vertical edges, as it is usually less congested than the horiontal one (due to metal1 cell terminals). It is also my understanding that it is useful to reduce the number of vias, whithout introducing a via cost. * New: In Bootstrap: - Script sprof.py to perform sprof & demangle libraries execution profile. * ToDo: In Anabatic: - Corner optimization. Sometimes when two corners are possible, the wrong one is choosen. That is, one of it's edge cannot be used for further grow of the tree.
2016-06-17 06:09:34 -05:00
, ("anabatic.edgeCostH" ,TypeDouble ,9.0 )
, ("anabatic.edgeCostK" ,TypeDouble ,-10.0 )
Enable the display of GCells as a density map (and not boundaries). * Bug: In Anabatic::RawGCellsUnder, *again*, the north and east borders of the whole area *are* includeds (shut up disgraceful warning). * New: In Anabatic::GCell, add a display mode to select between boundary display (for analogic) and density display (for numeric). * Bug: In KatanaEngine::runGlobalRouter(), do not check if an Edge cannot be desatured when the vector or overloaded Edges is empty. (one less disgraceful warning) * New: In GraphicKatanaEngine::drawGCell(), support for drawing the GCells in density mode. Use the fire scale and the MaxDensity mode. Setup the GCell drawing mode in GraphicKatanaEngine::initGCell(). * Change: In GraphicKatanaEngine::drawEdge(), adjust the various thresholds for showing the Edge and its label. * New: In CRL Core, adds "anabatic.gcell.displayMode" to the set of Anabatic parameters. Adjust the showing threshold for GCells in "display.conf" so when the zoom level is low, we still can see the density map.
2016-09-10 11:49:48 -05:00
, ("anabatic.gcell.displayMode" ,TypeEnumerate ,1
, { 'values':( ("Boundary" , 1)
, ("Density" , 2) ) }
)
* 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
)
New coriolis launcher. Configuration files cleanup. * Change: In CRL Core, simplify the loading sequence. The technology, both symbolic and real is now loaded directly from coriolisInit.py and not through the Alliance loader. This was a leftover from the time configuration was in XML. Remove others traces of XML loading. Remove SYMB_TECHNO_NAME, REAL_TECHNO_NAME & DISPLAY from the Alliance environement, as they was no longer used. Note that technology *still* need to be loader *after* Alliance framework has been initialized. Gauge information is moved from <alliance.conf> to <kite.conf>. * Bug: In Coloquinte, in optimization_subproblems.cxx static variables must not be inlined. Generate a problem when linking in debug mode (seems the symbol gets optimised out). * Bug: In Katabatic, in Grid::getGCell(), when the coordinate is *outside* the area, do not try to find a GCell, directly return NULL. * New: In Unicorn, create a generic command launcher named "coriolis" which automatically take cares of all environement setup, then run a command by default, it's <cgt>, but it can be anything. For example: <zsh>.
2015-04-13 11:54:09 -05:00
# Format of routingGaugesTable (dictionary):
# A list of entry of the form:
New "obstacleDw" for Kite. * New: In CRL Core, in RoutingLayerGauge, adds a new parameter "obstacleDw". It represents the distance to add from the *edge* of a blockage segment to the next *axis* of a routing track. This was previously computed as the pitch minus the mimimum half wire width. This works if the pitch is *equal* to the wire width plus the minimal distance (edge to edge). But if the wire width is less, than it leads to too great a distance around obstacles, making them bigger than they are. And potentially blocking everything. To summarize: before: obstacleDw = pitch - wireWidth/2 (deduced) after: obstacleDw = explicitly setup, usually: pitch - max(wireWidth)/2 Modify the Alliance configuration helper and the various kite.conf file accordingly. * New: In Kite, in BuildPowerRails, make use of "obstacleDw" to compute the footprint of a blockage.
2016-04-13 11:18:43 -05:00
# ( METAL_NAME, (Direction, Type, depth, density, offset, pitch, wire_width, via_width, obs_dw) )
New coriolis launcher. Configuration files cleanup. * Change: In CRL Core, simplify the loading sequence. The technology, both symbolic and real is now loaded directly from coriolisInit.py and not through the Alliance loader. This was a leftover from the time configuration was in XML. Remove others traces of XML loading. Remove SYMB_TECHNO_NAME, REAL_TECHNO_NAME & DISPLAY from the Alliance environement, as they was no longer used. Note that technology *still* need to be loader *after* Alliance framework has been initialized. Gauge information is moved from <alliance.conf> to <kite.conf>. * Bug: In Coloquinte, in optimization_subproblems.cxx static variables must not be inlined. Generate a problem when linking in debug mode (seems the symbol gets optimised out). * Bug: In Katabatic, in Grid::getGCell(), when the coordinate is *outside* the area, do not try to find a GCell, directly return NULL. * New: In Unicorn, create a generic command launcher named "coriolis" which automatically take cares of all environement setup, then run a command by default, it's <cgt>, but it can be anything. For example: <zsh>.
2015-04-13 11:54:09 -05:00
routingGaugesTable = {}
routingGaugesTable['sxlib'] = \
New "obstacleDw" for Kite. * New: In CRL Core, in RoutingLayerGauge, adds a new parameter "obstacleDw". It represents the distance to add from the *edge* of a blockage segment to the next *axis* of a routing track. This was previously computed as the pitch minus the mimimum half wire width. This works if the pitch is *equal* to the wire width plus the minimal distance (edge to edge). But if the wire width is less, than it leads to too great a distance around obstacles, making them bigger than they are. And potentially blocking everything. To summarize: before: obstacleDw = pitch - wireWidth/2 (deduced) after: obstacleDw = explicitly setup, usually: pitch - max(wireWidth)/2 Modify the Alliance configuration helper and the various kite.conf file accordingly. * New: In Kite, in BuildPowerRails, make use of "obstacleDw" to compute the footprint of a blockage.
2016-04-13 11:18:43 -05:00
( ( 'METAL1', ( Gauge.Vertical , Gauge.PinOnly, 0, 0.0, 0, 5, 2, 1, 4 ) )
, ( 'METAL2', ( Gauge.Horizontal, Gauge.Default, 1, 7.0, 0, 5, 2, 1, 4 ) )
, ( 'METAL3', ( Gauge.Vertical , Gauge.Default, 2, 0.0, 0, 5, 2, 1, 4 ) )
, ( 'METAL4', ( Gauge.Horizontal, Gauge.Default, 3, 0.0, 0, 5, 2, 1, 4 ) )
, ( 'METAL5', ( Gauge.Vertical , Gauge.Default, 4, 0.0, 0, 5, 2, 1, 4 ) )
#, ( 'METAL6', ( Gauge.Horizontal, Gauge.Default, 5, 0.0, 0, 5, 2, 1, 4 ) )
#, ( 'METAL7', ( Gauge.Vertical , Gauge.Default, 6, 0.0, 0, 5, 2, 1, 4 ) )
New coriolis launcher. Configuration files cleanup. * Change: In CRL Core, simplify the loading sequence. The technology, both symbolic and real is now loaded directly from coriolisInit.py and not through the Alliance loader. This was a leftover from the time configuration was in XML. Remove others traces of XML loading. Remove SYMB_TECHNO_NAME, REAL_TECHNO_NAME & DISPLAY from the Alliance environement, as they was no longer used. Note that technology *still* need to be loader *after* Alliance framework has been initialized. Gauge information is moved from <alliance.conf> to <kite.conf>. * Bug: In Coloquinte, in optimization_subproblems.cxx static variables must not be inlined. Generate a problem when linking in debug mode (seems the symbol gets optimised out). * Bug: In Katabatic, in Grid::getGCell(), when the coordinate is *outside* the area, do not try to find a GCell, directly return NULL. * New: In Unicorn, create a generic command launcher named "coriolis" which automatically take cares of all environement setup, then run a command by default, it's <cgt>, but it can be anything. For example: <zsh>.
2015-04-13 11:54:09 -05:00
)
Added Routing Gauge for 2-Metal technologies only. * New: In CRL Core, etc/cmos/kite.conf new routing gauge "sxlib-2M" for two metals only technologies. * New: In CRL Core, python/helpers/kite.py, new parameter to set the routing gauge to be used: "kite.routingGauge" (default: "sxlib"). * Change: In CRL/AllianceFramework.cpp, forgot to put the Cell gauges and RoutingGauges in the object Records (Inspector). * New: In pyCRL/PyAllianceFramework.cpp, export the setRoutingGauge() function.
2017-08-18 11:16:43 -05:00
routingGaugesTable['sxlib-2M'] = \
( ( 'METAL1', ( Gauge.Horizontal, Gauge.Default, 0, 0.0, 0, 5, 2, 1, 4 ) )
, ( 'METAL2', ( Gauge.Vertical , Gauge.Default, 1, 0.0, 0, 5, 2, 1, 4 ) )
)
New coriolis launcher. Configuration files cleanup. * Change: In CRL Core, simplify the loading sequence. The technology, both symbolic and real is now loaded directly from coriolisInit.py and not through the Alliance loader. This was a leftover from the time configuration was in XML. Remove others traces of XML loading. Remove SYMB_TECHNO_NAME, REAL_TECHNO_NAME & DISPLAY from the Alliance environement, as they was no longer used. Note that technology *still* need to be loader *after* Alliance framework has been initialized. Gauge information is moved from <alliance.conf> to <kite.conf>. * Bug: In Coloquinte, in optimization_subproblems.cxx static variables must not be inlined. Generate a problem when linking in debug mode (seems the symbol gets optimised out). * Bug: In Katabatic, in Grid::getGCell(), when the coordinate is *outside* the area, do not try to find a GCell, directly return NULL. * New: In Unicorn, create a generic command launcher named "coriolis" which automatically take cares of all environement setup, then run a command by default, it's <cgt>, but it can be anything. For example: <zsh>.
2015-04-13 11:54:09 -05:00
# Format of cellGaugesTable (dictionary):
# A list of entry of the form:
# ( METAL_PIN, xy_common_pitch, slice_height, slice_step )
cellGaugesTable = {}
cellGaugesTable['sxlib'] = ('metal2', 5.0, 50.0, 5.0)