The objective is to enable multiple users to share the same Caravel chip. This would allow several small MPW projects to be implemented into a single chip, increasing the number of designs per each MPW run.

To minimize the effort, we leverage the existing Caravel chip design through a custom user’s project wrapper design. This unique design partitions the user’s project area between multiple projects. After fabrication, only one design can be active at any time. Design selection is performed through two dedicated I/O pads.

The number of projects per chip depends on the configuration. We planned 3 configurations:

• 4 (2x2) designs, each 1.3x1.6 $mm^2$ (~ 200K Sky130 HD cells)
• 9 (3x3) designs, each 0.85x1.0 $mm^2$ (~ 80K Sky130 HD cells)
• 20 (4x5) designs, each 0.6x0.6 $mm^2$ (~ 40K Sky130 HD cells)

For chipIgnite runs, it would reduce the fabrication cost for designs that don’t utilize the whole user’s area. Each design can still access most of Caravel user's I/Os as well as the Wishbone bus.

Each project gets the following:

• Area of 1300 um x 1600 um (for 4 projects/chip configuration)
• 36 IO ports.
• 32 logic analyzer probes only.
• Wishbone port connection to the management SoC wishbone bus.
• 1 digital power domain only.

• Analog IOs are not supported.
• Metal5 cannot be used in the user's project.
• The User's project has a fixed PDN configuration.

• The Clock is enabled only for the selected project. The active project selection is achieved through Caravel I/Os 36 and 37.
• Each project is assigned one power supply (either vccd1 or vccd2) based on it location in the chip. The left side projects are powered by vccd2 and the right side projects are powered using vccd1. The power supply domain not used for the active project can be disabled on the development board. There is no on-chip power switching to power down non-active projects.

In order to harden such chip,

1. The 4 multiple projects should be hardened with a fixed floorplan, PDN, and boundary constraints.
2. Then, the top-level should be hardened. Or it can be regenerated using the new multiple user projects.

To rebuild everything using the current designs. Run the following:

export OPENLANE_ROOT=<openlane_dir>
export OPENLANE_TAG=<openlane commit_id>
epxort PDK_ROOT=<pdk dir>
export PDK=sky130A
cd openlane
make user_project_1
make user_project_3
make user_project_5
make user_project_7
make user_project_wrapper

In order to regenerate the wrapper with new designs, you can the following as in this commit

1. Change the multiple project names in the mag/user_project_wrapper.mag

2. Make sure that the new projects mag files are under mag/

3. Regenarate the user project wrapper GDS using this script