updating docs to include correct build path [skip ci]

This commit is contained in:
nayiri-k
2023-03-10 15:09:56 -08:00
parent 81e11ee8e0
commit 89a23faa00
3 changed files with 9 additions and 9 deletions

View File

@@ -126,9 +126,9 @@ To run DRC & LVS, and view the results in Calibre:
.. code-block:: shell .. code-block:: shell
make drc CONFIG=TinyRocketConfig make drc CONFIG=TinyRocketConfig
./build/drc-rundir/generated-scripts/view-drc ./build/chipyard.TestHarness.TinyRocketConfig-ChipTop/drc-rundir/generated-scripts/view-drc
make lvs CONFIG=TinyRocketConfig make lvs CONFIG=TinyRocketConfig
./build/lvs-rundir/generated-scripts/view-lvs ./build/chipyard.TestHarness.TinyRocketConfig-ChipTop/lvs-rundir/generated-scripts/view-lvs
Some DRC errors are expected from this PDK, as explained in the `ASAP7 plugin readme <https://github.com/ucb-bar/hammer/blob/master/hammer/technology/asap7>`__. Some DRC errors are expected from this PDK, as explained in the `ASAP7 plugin readme <https://github.com/ucb-bar/hammer/blob/master/hammer/technology/asap7>`__.
Furthermore, the dummy SRAMs that are provided in this tutorial and PDK do not have any geometry inside, so will certainly cause DRC errors. Furthermore, the dummy SRAMs that are provided in this tutorial and PDK do not have any geometry inside, so will certainly cause DRC errors.

View File

@@ -161,9 +161,9 @@ To run DRC & LVS, and view the results in Calibre:
.. code-block:: shell .. code-block:: shell
make drc tutorial=sky130-commercial make drc tutorial=sky130-commercial
./build/drc-rundir/generated-scripts/view_drc ./build/chipyard.TestHarness.TinyRocketConfig-ChipTop/drc-rundir/generated-scripts/view_drc
make lvs tutorial=sky130-commercial make lvs tutorial=sky130-commercial
./build/lvs-rundir/generated-scripts/view_lvs ./build/chipyard.TestHarness.TinyRocketConfig-ChipTop/lvs-rundir/generated-scripts/view_lvs
Some DRC errors are expected from this PDK, especially with regards to the SRAMs, as explained in the Some DRC errors are expected from this PDK, especially with regards to the SRAMs, as explained in the
`Sky130 Hammer plugin README <https://github.com/ucb-bar/hammer/blob/master/hammer/technology/sky130>`__. `Sky130 Hammer plugin README <https://github.com/ucb-bar/hammer/blob/master/hammer/technology/sky130>`__.

View File

@@ -184,7 +184,7 @@ Hammer generates a convenient script to launch these sessions
.. code-block:: shell .. code-block:: shell
cd ./build/par-rundir cd ./build/chipyard.TestHarness.TinyRocketConfig-ChipTop/par-rundir
./generated-scripts/open_chip ./generated-scripts/open_chip
Note that the conda OpenROAD package was compiled with the GUI disabled, so in order to view the layout, Note that the conda OpenROAD package was compiled with the GUI disabled, so in order to view the layout,
@@ -199,7 +199,7 @@ These databases can be restored using the same ``open_chip`` script for debuggin
.. code-block:: shell .. code-block:: shell
cd build/par-rundir cd build/chipyard.TestHarness.TinyRocketConfig-ChipTop/par-rundir
./generated_scripts/open_chip -h ./generated_scripts/open_chip -h
" "
Usage: ./generated-scripts/open_chip [-t] [openroad_db_name] Usage: ./generated-scripts/open_chip [-t] [openroad_db_name]
@@ -215,7 +215,7 @@ These databases can be restored using the same ``open_chip`` script for debuggin
# load post-clock tree database with timing inforamtion # load post-clock tree database with timing inforamtion
./generated_scripts/open_chip -t post_clock_tree ./generated_scripts/open_chip -t post_clock_tree
.. Timing reports are found in ``build/par-rundir/timingReports``. They are gzipped text files. Various reports, including timing reports, are found in ``build/par-rundir/reports``.
See the `OpenROAD tool plugin <https://github.com/ucb-bar/hammer/blob/master/hammer/par/openroad>`__ for the full list of OpenROAD tool steps and their implementations. See the `OpenROAD tool plugin <https://github.com/ucb-bar/hammer/blob/master/hammer/par/openroad>`__ for the full list of OpenROAD tool steps and their implementations.
@@ -232,9 +232,9 @@ To run DRC & LVS in Magic & Netgen, respectively:
.. code-block:: shell .. code-block:: shell
make drc tutorial=sky130-openroad make drc tutorial=sky130-openroad
./build/drc-rundir/generated-scripts/view_drc ./build/chipyard.TestHarness.TinyRocketConfig-ChipTop/drc-rundir/generated-scripts/view_drc
make lvs tutorial=sky130-openroad make lvs tutorial=sky130-openroad
./build/lvs-rundir/generated-scripts/view_lvs ./build/chipyard.TestHarness.TinyRocketConfig-ChipTop/lvs-rundir/generated-scripts/view_lvs
Note that in ``sky130-openroad.yml`` we have set the following YAML keys: Note that in ``sky130-openroad.yml`` we have set the following YAML keys: