[dv/alert_handler] interrupt needs one clock cycle to be reset In the alert_handler design, there is a `timeout` counter that will count how many cycles the interrupt has been set. If the cycle is larger than the threshold, the corresponding escalation will be triggered. Upon interrupt is set, design will take one more clock cycle to stop the counter. But tb's scb here stop the counter immediately. If the interrupt is issued at the last clock cycle before timeout, design will continue to count one more clock cycle and trigger the escalation, while in tb I will exit immediately. This PR fixed it by adding a one clock cycle delay before setting the interrupt values. Signed-off-by: Cindy Chen <chencindy@google.com>
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).