| commit | 31dcc4fc65a1e0671e56107f1d8993f9dafa4de6 | [log] [tgz] |
|---|---|---|
| author | Rupert Swarbrick <rswarbrick@lowrisc.org> | Thu May 07 09:43:39 2020 +0100 |
| committer | sriyerg <46467186+sriyerg@users.noreply.github.com> | Tue Aug 04 08:39:05 2020 -0700 |
| tree | 0bb72154afe32b8d6e20abdf9541c153bdfacce8 | |
| parent | fb7cc68e04334af359834dca2a9990d6d9284ffc [diff] |
[dvsim] Tidy up config file loading in FlowCfg.py This changes how command line overrides work, but I think the previous behaviour probably wasn't intentional. Before this patch, a command line override would only take effect when reading a second config file that set a given key where both config files set it with a 'non-default' value. This behaviour was added by commit 680f7e2 and I think the point was just to allow the user to set the tool (VCS or xcelium) on the command line. After this patch, a command line override takes effect as soon as we see the corresponding key in any configuration file. However, we can't allow any old command line argument. For example, there is a --waves command line argument which clashes with a config file key. (Presumably, the existing code would get confused if we had multiple config files setting the waves key inconsistently, but no-one does this). To avoid this confusion, we now list the keys that can be overridden on the command line in _CMDLINE_FIELDS. 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).