wu-arch/chipyard
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Mention custom ChipTop in documentation'

Browse Source
This commit is contained in:
Jerry Zhao
2023-03-20 11:20:31 -07:00
parent 477456bc0b
commit 2831111134
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/Advanced-Concepts/Top-Testharness.rst
View File

@@ -18,6 +18,13 @@ The ``IOBinders`` are responsible for instantiating the IO cells for ``ChipTop``
The ``HarnessBinders`` are responsible for instantiating test harness collateral that connects to the ``ChipTop`` ports. The ``HarnessBinders`` are responsible for instantiating test harness collateral that connects to the ``ChipTop`` ports.
Most types of devices and testing collateral can be instantiated using custom ``IOBinders`` and ``HarnessBinders``. Most types of devices and testing collateral can be instantiated using custom ``IOBinders`` and ``HarnessBinders``.
Custom ChipTops
^^^^^^^^^^^^^^^^^^^^^^^^^
The default standard ``ChipTop`` provides a mimimal, barebones template for ``IOBinders`` to generate IOCells around ``DigitalTop`` traits.
For tapeouts, integrating Analog IP, or other non-standard use cases, Chipyard supports specifying a custom ``ChipTop`` using the ``BuildTop`` key.
An example of a custom ChipTop which uses non-standard IOCells is provided in `generators/chipyard/src/main/scala/example/CustomChipTop.scala <https://github.com/ucb-bar/chipyard/blob/main/generators/chipyard/src/main/scala/example/CustomChipTop.scala>`__
System/DigitalTop System/DigitalTop
------------------------- -------------------------