[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>
1 file changed
tree: 44b7866d732487b66d9440a9e51c2524f531155e
  1. .github/
  2. ci/
  3. doc/
  4. hw/
  5. rules/
  6. site/
  7. sw/
  8. test/
  9. util/
  10. .bazelignore
  11. .bazelrc
  12. .bazelversion
  13. .clang-format
  14. .dockerignore
  15. .flake8
  16. .gitignore
  17. .style.yapf
  18. .svlint.toml
  19. .svls.toml
  20. _index.md
  21. apt-requirements.txt
  22. azure-pipelines.yml
  23. BUILD
  24. check_tool_requirements.core
  25. CLA
  26. COMMITTERS
  27. CONTRIBUTING.md
  28. LICENSE
  29. meson.build
  30. meson_init.sh
  31. meson_options.txt
  32. python-requirements.txt
  33. README.md
  34. tool_requirements.py
  35. toolchain.txt
  36. topgen-reg-only.core
  37. topgen.core
  38. WORKSPACE
  39. yum-requirements.txt
README.md

OpenTitan

OpenTitan logo

About the project

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.

About this repository

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.

Documentation

The project contains comprehensive documentation of all IPs and tools. You can access it online at docs.opentitan.org.

How to contribute

Have a look at CONTRIBUTING and our documentation on project organization and processes for guidelines on how to contribute code to this repository.

Licensing

Unless otherwise noted, everything in this repository is covered by the Apache License, Version 2.0 (see LICENSE for full text).