Google Git
Sign in
foss-eda-tools / third_party / shuttle / sky130 / mpw-001 / slot-014 / 47ff6e79e4607be5402a5640442e8bd828f4a52e
commit47ff6e79e4607be5402a5640442e8bd828f4a52e[log] [tgz]
authorTim Edwards <tim@opencircuitdesign.com>Mon Oct 12 22:05:18 2020 -0400
committerTim Edwards <tim@opencircuitdesign.com>Mon Oct 12 22:05:18 2020 -0400
tree96dea37f5673c8e442119bd5fe9ec8416cd5d51c
parent16ae3821a8b8481b42830c0ec3183d6d8a64c1c2 [diff]
Testbench simulations are now all working correctly with the pre-release
version of sky130_fd_io.
21 files changed
tree: 96dea37f5673c8e442119bd5fe9ec8416cd5d51c
  1. doc/
  2. verilog/
  3. README.md
README.md

CIIC Harness (Phase 1)

A template SoC for Google SKY130 free shuttles. It is still WIP. The current SoC architecture is given below.

Managment SoC

The managment SoC runs firmware taht can be used to:

  • Configure Mega Project I/O pads
  • Observe and control Mega Project signals (through on-chip logic analyzer probes)
  • Control the Mega Project power supply

The memory map of the management SoC is given below

Mega Project Area

This is the user space. It has limitted silicon area (???) as well as a fixed number of I/O pads (???). The repoo contains a sample mega project that contains a binary 32-bit up counter.

The firmware running on the Management Area SoC, configures the I/O pads used by the counter and uses the logic probes to observe/control the counter. Three firmware examples are provided:

  1. Configure the Mega Project I/O pads as o/p. Observe the counter value in the testbench: IO_Ports Test.
  2. Configure the Mega Project I/O pads as o/p. Use the Chip LA to load the counter and observe the o/p till it reaches 500: LA_Test1.
  3. Configure the Mega Project I/O pads as o/p. Use the Chip LA to control the clock source and reset signals and observe the counter value for five clock cylcles: LA_Test2.