commit | 5b61c56258a29a56058e44a6edd50b6ed083054d | [log] [tgz] |
---|---|---|
author | Eunchan Kim <eunchan@opentitan.org> | Fri Oct 29 16:17:36 2021 +0000 |
committer | Eunchan Kim <eunchan@opentitan.org> | Tue Nov 02 15:17:56 2021 +0000 |
tree | 44b7866d732487b66d9440a9e51c2524f531155e | |
parent | 3cb62ec91052a7c493771266bf856532cb0e2d5a [diff] |
[spi_device] Upload Cmd/Addr FIFO status revision In previous design, the cmdfifo, addrfifo in the spid_upload module reports the not empty status. The status bits are connected to the UPLOAD_STATUS CSR for SW to read and check the status. The not empty status, however, assert one clock earlier than the actual `rvalid` signals. The reason is due to the SRAM read latency. The upload module adopts SRAM FIFO interface to maintain the cmd, addr FIFOs. When the logic in SCK domain pushes entries, the pointer is increased. This triggers the FIFO logic in the bus clock domain fetches data from SRAM. The pointer crosses the clock boundary. It takes usually two cycles (in the receiver side). Then, as the read and write pointer in the bus clock domain has a gap by 1, the FIFO not empty status is raised. At this time, the logic just sent the read request to the SRAM. The data is not yet read. The `rvalid` asserts when it receives data from the SRAM. So, if the consumer reads data at the same cycle when notempty status is raised, it reads incorrect data. This is not a feasible scenario in the real usage as the core takes time to read the data from the FIFO CSR. Signed-off-by: Eunchan Kim <eunchan@opentitan.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 and our documentation on project organization and processes 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).