Validating channel routing mode (two metals) on SNX.
* New: In Hurricane::Entity, add an id counter limit and a memory size
limit. The two limits are checked only when a new Entity object is
created. This should help avoiding massive memory links.
* New: In CRL Core, add a "crlcore.groundName" and a "crlcore.powerName"
parameter to specify the name of the ground/power signals to be
created if they are missing in a Cell. For Alliance libraries it
would be "vss" & "vdd" (default values), but for real technologies,
it is often "gnd!" & "vdd!".
The Blif parser is modificated to make use of it.
* Bug: In AnabaticEngine::unify(), set the resulting unified segment in
the center of the GCells common side. Gcells under a segment are
found by using the edge that cover the segment axis. When we have
a "bend" GCell stack and the axis is wrong, they could be ommited.
This was causing deleted segments to be not removed from some
Edges, then core dump.
* Change: In Anabatic::AutoSegment::create(), smarter choosing of the
reference contact, select the fixed or terminal one instead of
always the source one.
* New: In Anabatic::Edge::isEnding(), new function to check if a
segment going through an Edge is starting/ending in either source
or target GCell of the edge (active only when running in channel
mode).
* New: In Anabatic::Edge::add(), a segment takes part in the occupancy
only if it is not ending in either source or target (channel mode
only). The occupancy due to terminal is pre-computed in Katana.
* New: In Anabatic::Edge::ripup(), in channel mode, never ripup a
segment which is ending in either source or target (we *have* to
access this edge to connect to the terminal).
* Bug: In Anabatic::GCell::hcut() and vcut(), force the update of
the Edge which is on the side that will get splitted by the cut.
It's capacity will be reduced to it must be updated.
* Change: In Anabatic::GCell::updateGContacts() add a flag to conditionnally
update horizontals or verticals only. We may require only a partial
update when resizing the GCell in only one direction.
This, again, related to the fact that we compute the GCells under
a segment thanks to it's axis position, so we need to be very careful
when modificating axis.
* Change: In Katana::Block::resizeChannels(), only update GContact vertical
position. Do not disturb X positions of segments.
* Bug: In Katana::GlobalRoute::DigitalDistance, in channel mode, some
Edges can have a zero capacity, but still be reachable if the net has
a terminal in either source or target. Look for this case and return
a distance of zero instead of "unreachable". This was causing the
global routing not to complete in channel mode.
For computing the edge distance, makes the vertical edges much more
long (10 times) than the horizontal ones as the vertical capacity is
very limited. Hard coded for now, should make it a parameter in the
future.
* Change: In KatanaEngine::annotateGlobalGraph(), decrease the capacity
of edges with reserveCapacity for each terminal inside a GCell.
Both north and south edges are decreased as we a terminal will
block both north and south edges.
As a counterpart, the Edge capacity is not decreased when the
global router connect to a terminal.
* Change: In Katana::RoutingEvent::revalidate(), when in repair stage,
do not expand the slack for horizontal segments in channel mode.
So they may not overlap the standard cell row.
* Bug: In Stratus documentation, do not use the french option in babel,
the documentation is in english!
* New: In Documentation, added Hurricane/Python tutorial, part for drawing
layout.
2018-03-16 10:20:04 -05:00
|
|
|
.. -*- Mode: rst -*-
|
|
|
|
.. include:: ../etc/definitions.rst
|
|
|
|
.. include:: ./definitions.rst
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2. Setting up the Environment
|
|
|
|
=============================
|
|
|
|
|
|
|
|
2.1 Setting up the Pathes
|
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
|
|
|
|
To simplify the tedious task of configuring your environment, a helper is provided.
|
|
|
|
It will setup or modify the :cb:`PATH`, :cb:`LD_LIBRARY_PATH` (or :cb:`DYLD_LIBRARY_PATH`
|
|
|
|
under |Darwin|), :cb:`PYTHONPATH` and :cb:`CORIOLIS_TOP` variables.
|
|
|
|
It should automatically adapt to your kind of shell (``Bourne`` like
|
|
|
|
or ``C-Shell`` like). ::
|
|
|
|
|
|
|
|
<CORIOLIS_INSTALL>/etc/coriolis2/coriolisEnv.py
|
|
|
|
|
|
|
|
Use it like this (don't forget the ``eval`` **and** the backquotes):
|
|
|
|
|
|
|
|
.. code-block:: console
|
|
|
|
|
|
|
|
dummy@lepka:~> eval `<CORIOLIS_INSTALL>/etc/coriolis2/coriolisEnv.py`
|
|
|
|
|
|
|
|
.. note:: **Do not call that script in your environement initialisation.**
|
2019-03-04 07:35:16 -06:00
|
|
|
When used under |RHEL6| or clones, it needs to be run in the |devtoolset|
|
Validating channel routing mode (two metals) on SNX.
* New: In Hurricane::Entity, add an id counter limit and a memory size
limit. The two limits are checked only when a new Entity object is
created. This should help avoiding massive memory links.
* New: In CRL Core, add a "crlcore.groundName" and a "crlcore.powerName"
parameter to specify the name of the ground/power signals to be
created if they are missing in a Cell. For Alliance libraries it
would be "vss" & "vdd" (default values), but for real technologies,
it is often "gnd!" & "vdd!".
The Blif parser is modificated to make use of it.
* Bug: In AnabaticEngine::unify(), set the resulting unified segment in
the center of the GCells common side. Gcells under a segment are
found by using the edge that cover the segment axis. When we have
a "bend" GCell stack and the axis is wrong, they could be ommited.
This was causing deleted segments to be not removed from some
Edges, then core dump.
* Change: In Anabatic::AutoSegment::create(), smarter choosing of the
reference contact, select the fixed or terminal one instead of
always the source one.
* New: In Anabatic::Edge::isEnding(), new function to check if a
segment going through an Edge is starting/ending in either source
or target GCell of the edge (active only when running in channel
mode).
* New: In Anabatic::Edge::add(), a segment takes part in the occupancy
only if it is not ending in either source or target (channel mode
only). The occupancy due to terminal is pre-computed in Katana.
* New: In Anabatic::Edge::ripup(), in channel mode, never ripup a
segment which is ending in either source or target (we *have* to
access this edge to connect to the terminal).
* Bug: In Anabatic::GCell::hcut() and vcut(), force the update of
the Edge which is on the side that will get splitted by the cut.
It's capacity will be reduced to it must be updated.
* Change: In Anabatic::GCell::updateGContacts() add a flag to conditionnally
update horizontals or verticals only. We may require only a partial
update when resizing the GCell in only one direction.
This, again, related to the fact that we compute the GCells under
a segment thanks to it's axis position, so we need to be very careful
when modificating axis.
* Change: In Katana::Block::resizeChannels(), only update GContact vertical
position. Do not disturb X positions of segments.
* Bug: In Katana::GlobalRoute::DigitalDistance, in channel mode, some
Edges can have a zero capacity, but still be reachable if the net has
a terminal in either source or target. Look for this case and return
a distance of zero instead of "unreachable". This was causing the
global routing not to complete in channel mode.
For computing the edge distance, makes the vertical edges much more
long (10 times) than the horizontal ones as the vertical capacity is
very limited. Hard coded for now, should make it a parameter in the
future.
* Change: In KatanaEngine::annotateGlobalGraph(), decrease the capacity
of edges with reserveCapacity for each terminal inside a GCell.
Both north and south edges are decreased as we a terminal will
block both north and south edges.
As a counterpart, the Edge capacity is not decreased when the
global router connect to a terminal.
* Change: In Katana::RoutingEvent::revalidate(), when in repair stage,
do not expand the slack for horizontal segments in channel mode.
So they may not overlap the standard cell row.
* Bug: In Stratus documentation, do not use the french option in babel,
the documentation is in english!
* New: In Documentation, added Hurricane/Python tutorial, part for drawing
layout.
2018-03-16 10:20:04 -05:00
|
|
|
environement. The script then launch a new shell, which may cause an
|
|
|
|
infinite loop if it's called again in, say :cb:`~/.bashrc`.
|
|
|
|
|
|
|
|
Instead you may want to create an alias: ::
|
|
|
|
|
|
|
|
alias c2r='eval "`<CORIOLIS_INSTALL>/etc/coriolis2/coriolisEnv.py`"'
|
|
|
|
|
|
|
|
|
|
|
|
2.2 User's Configurations File
|
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
|
|
|
|
You may create, in the directory you are lanching |Coriolis| tools, a special
|
|
|
|
sub-directory ``.coriolis2/`` that can contains two configuration files:
|
|
|
|
|
|
|
|
* ``techno.py`` tells which technology to use.
|
|
|
|
* ``settings.py`` can overrides almost any default configuration setting.
|
|
|
|
|
|
|
|
Those two files are *optional*, if they do not exists the default settings
|
|
|
|
will be used and the technology is ``symbolic/cmos`` (i.e. purely symbolic).
|
|
|
|
|
|
|
|
.. note:: Those two files will by processed by the |Python| interpreter,
|
|
|
|
so they can contain any code in addition to the mandatory
|
|
|
|
variables.
|
|
|
|
|
|
|
|
2.2.1 The :cb:`techno.py` File
|
|
|
|
------------------------------
|
|
|
|
|
|
|
|
Must provide one variable named :cb:`technology` which value the path towards
|
|
|
|
the technology file. The available technologies are installed under
|
|
|
|
``<CORIOLIS_INSTALL>/etc/coriolis2``. For example, to use the 45nm FreeDPK
|
|
|
|
which is in: ::
|
|
|
|
|
|
|
|
<CORIOLIS_INSTALL>/etc/coriolis2/45/freepdk_45/
|
|
|
|
|
|
|
|
The ``techno.py`` file must contain:
|
|
|
|
|
|
|
|
.. code-block:: Python
|
|
|
|
|
|
|
|
technology = '45/freepdk_45'
|
|
|
|
|
|
|
|
|
|
|
|
2.2.2 The :cb:`settings.py` File
|
|
|
|
--------------------------------
|
|
|
|
|
|
|
|
The entries of the ``parametersTable`` and their definitions are detailed
|
|
|
|
in `CGT - The Graphical Interface <../UsersGuide/ViewerTools.html>`_.
|
|
|
|
|
|
|
|
Example of file:
|
|
|
|
|
|
|
|
.. code-block:: Python
|
|
|
|
|
|
|
|
defaultStyle = 'Alliance.Classic [black]'
|
|
|
|
|
|
|
|
parametersTable = \
|
|
|
|
( ('misc.catchCore' , TypeBool , False )
|
|
|
|
, ('misc.info' , TypeBool , False )
|
|
|
|
, ('misc.paranoid' , TypeBool , False )
|
|
|
|
, ('misc.bug' , TypeBool , False )
|
|
|
|
, ('misc.logMode' , TypeBool , False )
|
|
|
|
, ('misc.verboseLevel1' , TypeBool , False )
|
|
|
|
, ('misc.verboseLevel2' , TypeBool , True )
|
|
|
|
)
|