Google Git
Sign in
foss-eda-tools / third_party / shuttle / sky130 / mpw-008 / slot-034 / d48021badab89c6aa03d2bd218140a0c13b37bae
commitd48021badab89c6aa03d2bd218140a0c13b37bae[log] [tgz]
authorm-usama-z <107983847+m-usama-z@users.noreply.github.com>Sat Nov 26 14:39:44 2022 +0500
committerGitHub <noreply@github.com>Sat Nov 26 14:39:44 2022 +0500
treeb5ade259d5e85ec65e09eaf35c7b634c73163356
parentad442a33dbef429cb3030cf024725e9b259c1879 [diff]
Update README.md
1 file changed
tree: b5ade259d5e85ec65e09eaf35c7b634c73163356
  1. .github/
  2. def/
  3. dependencies/
  4. deps/
  5. docs/
  6. gds/
  7. lef/
  8. lib/
  9. mag/
  10. maglef/
  11. openlane/
  12. sdc/
  13. sdf/
  14. signoff/
  15. spef/
  16. spi/
  17. venv/
  18. verilog/
  19. caravel
  20. mgmt_core_wrapper
  21. .gitignore
  22. a.out
  23. LICENSE
  24. Makefile
  25. README.md
  26. README.md.old
README.md

UETRV_ESoC_v2

UETRV_ECORE_v2 is a RISC-V based SoC derived from UETRV_ESoC with a few bug-fixes and increased memory sizes; it has been passed through the Cadence VLSI flow for submission to Google and Efabless' Open-MPW-8 shuttle using Skywater's 130 nm PDK. The verilog rtl used in this repo is generated from Scala source, available here. Further details about the peripheral memory map, bootloader, example programs, testbenches etc. are also provided in that repo.

The following are the differences between UETRV_ESoC_v2 and UETRV_ESoC:

  • Fixed width of address bus in the instruction bus. Previously, the address bus was 2 bits narrower than required for the instruction memory size specified in the config.scala file.
  • Fixed selection of the motor control module to be accessed using the address given to data bus. Previously, although three motor control modules were instantiated, only the first motor module was accessible.
  • Fixed data memory to be word-addressable. Previously, data memory was byte-addressable which did not map properly to the Skywater PDK's SRAMs.
  • Added 2 inputs and 2 outputs to the motor control module, to aid in controlling stepper motors for a plotter's operation. The 2 inputs have been used to read the state of homing switches, and the 2 outputs have been used to provide the direction inputs to the stepper motor driver, but this usage of the IOs been done using firmware, thus they can be easily used for other purposes by modifying the firmware written in C language.