| commit | 200d8b4fc66b86edc2baffe12941620ab84e6357 | [log] [tgz] |
|---|---|---|
| author | Rupert Swarbrick <rswarbrick@lowrisc.org> | Mon Mar 08 12:32:11 2021 +0000 |
| committer | Rupert Swarbrick <rswarbrick@gmail.com> | Thu Mar 11 16:26:49 2021 +0000 |
| tree | 4b2a5a595138c1b9f2f1f7698bdc2d1d41ad01fe | |
| parent | a5e687fcf5f44e15cc4aea026504f6448edc7ae5 [diff] |
[topgen] Allow multiple device interfaces to connect to the crossbar This looks like quite a big change, but lots of the changes are auto-generated. The main change to the data model is that an IpBlock can now contain multiple RegBlock objects (one for each device interface). While we're at it, we also remove the "Block" base class that nothing ever used: we're Python, not Java: time to embrace sum types :-D The other noticeable change is in how the xbar parsing logic works. If you want multiple device interfaces for a block, you should create a node for each in e.g. xbar_main.hjson. These should be named "<inst_name>.<if_name>" for a named interface. Obviously, these nodes also need adding to the connections list at the bottom. There's a problem of aliasing, where the first register in each interface will have address zero in <block>_ral_pkg.sv. For now, we're "solving" this by adding the index of the device interface to the address, shifted up by 28 bits. I'm not sure how best to do this at the chip level, but it can probably be addressed in a follow-up. The structure of most output files are unchanged. The only difference is stuff that needs creating per device interface (such as the reg_top modules and the FPV CSR files). Signed-off-by: Rupert Swarbrick <rswarbrick@lowrisc.org>
OpenTitan is an open source silicon Root of Trust (RoT) project. OpenTitan will make the silicon RoT design and implementation more transparent, trustworthy, and secure for enterprises, platform providers, and chip manufacturers. OpenTitan is administered by lowRISC CIC as a collaborative project to produce high quality, open IP for instantiation as a full-featured product. See the OpenTitan site and OpenTitan docs for more information about the project.
This repository contains hardware, software and utilities written as part of the OpenTitan project. It is structured as monolithic repository, or “monorepo”, where all components live in one repository. It exists to enable collaboration across partners participating in the OpenTitan project.
The project contains comprehensive documentation of all IPs and tools. You can access it online at docs.opentitan.org.
Have a look at CONTRIBUTING for guidelines on how to contribute code to this repository.
Unless otherwise noted, everything in this repository is covered by the Apache License, Version 2.0 (see LICENSE for full text).