| commit | a5e687fcf5f44e15cc4aea026504f6448edc7ae5 | [log] [tgz] |
|---|---|---|
| author | Rupert Swarbrick <rswarbrick@lowrisc.org> | Mon Mar 01 11:51:41 2021 +0000 |
| committer | Rupert Swarbrick <rswarbrick@gmail.com> | Thu Mar 11 16:26:49 2021 +0000 |
| tree | 22a26b14d58f2357acf9999f98db4aec588b298f | |
| parent | 6c83129f0129d4c5c3334b6b0813788ffacc61a7 [diff] |
[topgen] Allow named bus interfaces to connect to crossbar
The big change here is in topgen, where we teach it to cope with
wiring up named devices. To do so, incorporate each module's
bus_interfaces field into its instances and then use that field to
figure out how connections should work.
To refer to named interfaces in the crossbar file, use the syntax
"<instance>.<iface_name>" for the name of the entry in the node list
and for entries in the connections lists.
To test this, I edited OTBN's bus_interfaces list to look like this:
bus_interfaces: [
{ protocol: "tlul", direction: "device", name: "cabbage" }
],
and renamed the corresponding ports in otbn.sv accordingly:
input tlul_pkg::tl_h2d_t cabbage_tl_i,
output tlul_pkg::tl_d2h_t cabbage_tl_o,
The only other change needed is to the wiring in xbar_main.hjson (as
you'd expect, since the target has changed). Here we edit the list of
connections to replace "otbn" with "otbn.cabbage". Once everything is
re-generated, we get a load of signals with names involving
"otbn__cabbage" (replacing "." with "__") and everything seems to be
wired up correctly.
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).