From 1945ca8e341c5c5992dde95013fe972056d017ef Mon Sep 17 00:00:00 2001 From: nayiri-k Date: Mon, 14 Feb 2022 17:18:35 -0800 Subject: [PATCH] fixed name of entry script to example-vlsi-sky130 --- docs/VLSI/Sky130-Tutorial.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/VLSI/Sky130-Tutorial.rst b/docs/VLSI/Sky130-Tutorial.rst index c07a19ac..4c9ca4e1 100644 --- a/docs/VLSI/Sky130-Tutorial.rst +++ b/docs/VLSI/Sky130-Tutorial.rst @@ -22,7 +22,7 @@ This example gives a suggested file structure and build system. The ``vlsi/`` fo * A template file for tool environment configuration. Fill in the install and license server paths for your environment. -* example-vlsi +* example-vlsi-sky130 * Entry point to Hammer. Contains example placeholders for hooks. @@ -83,8 +83,8 @@ For the curious, ``make buildfile`` generates a set of Make targets in ``build/h Running the VLSI Flow --------------------- -example-vlsi -^^^^^^^^^^^^ +example-vlsi-sky130 +^^^^^^^^^^^^^^^^^^^ This is the entry script with placeholders for hooks. In the ``ExampleDriver`` class, a list of hooks is passed in the ``get_extra_par_hooks``. Hooks are additional snippets of python and TCL (via ``x.append()``) to extend the Hammer APIs. Hooks can be inserted using the ``make_pre/post/replacement_hook`` methods as shown in this example. Refer to the Hammer documentation on hooks for a detailed description of how these are injected into the VLSI flow. @@ -130,7 +130,7 @@ To run DRC & LVS, and view the results in Calibre: Some DRC errors are expected from this PDK, especially with regards to the SRAMs, as explained in the `Sky130 Hammer plugin README `__. -For this reason, the ``example-vlsi`` script black-boxes the SRAMs for DRC/LVS analysis. +For this reason, the ``example-vlsi-sky130`` script black-boxes the SRAMs for DRC/LVS analysis. Simulation ^^^^^^^^^^