https://open-source-silicon.dev logo
Channels
aa
abcc
activity
adiabatonauts
analog-design
announce
announcements
b2aws
b2aws-tutorial
bag
basebands
beagleboard
bluetooth
board-respin
cadence-genus
cadence-innovus
cadence-spectre
cadence-virtuoso
caravan
caravel
caravel-board
chilechipmakers
chip-yard
chipignite
chipignite2206q_stanford_bringup
chisel
coalition-for-digital-environmental-sustainability
community_denmark_dtu
containers
courses
design-review
design-services
dffram
digital-design
digital-electronics-learners
discord-mods
dynamic-power-estimation
efabless
electric
events
fasoc
fault
foss-asic-tools
fossee-iitb-esim
fossee-iitb-google-sky130
fpga
funding
fuserisc
general
generative-ai-silicon-challenge
genius-vlsi
gf180
gf180mcu
hardware-beginners
help-
ieee-sscs-cac-23
ieee-sscs-dc-21q3
ieee-sscs-dc-22
ieee-sscs-dc-23
ihp-sg13g2
images
infiniband
j-core
japan-region
junk
klayout
latam_vlsi
layouteditor
lvs
lvs-analysis
magic
magical
maker-projects
maker-zone
microwatt
mpw-2-silicon
mpw-one-clean-short
mpw-one-silicon
neuro-mem
nydesign
open_pdks
open-pdk
openadiabaticlogic
openfpga
openhighqualityresonators
openlane
openlane_cloudrunner
openlane-development
openocd
openpositarithmetic
openpower
openram
openroad
opentitan
osu
pa-test-chip
paracells
pd-openlane-and-sky130
picosoc
pll
popy_neel
power
private-shuttle
rad-lab-silicon
radio
rdircd
reram
researchers
rf-mmw-design
rios
riscv
sdram
serdes
shuttle
shuttle-precheck
shuttle-status
silicon-photonics
silicon-validation
silicon-validation-private
sky130
sky130-ci
sky130-pv-workshop
sky65
sky90
skywater
sram
stdcelllib
strive
swerv
system-verilog-learners
tapeout-job
tapeout-pakistan
team-awesome
timing-closure
toysram
travis-ci
uvm-learners
vendor-synopsys
venn
verification-be
verification-fe
verilog-learners
vh2v
vhdl
vhdl-learners
vliw
vlsi_verilog_using_opensource_eda
vlsi_verilog_using_opensoure_eda
vlsi-learners-group
vlsi101
waveform-viewers
xls
xschem
xyce
zettascale
Powered by
Title
t

Tim Edwards

09/12/2020, 3:45 PM
@User: We will have space for 40 projects; that's what fits in a standard reticle, more or less, so that number remains unless SkyWater tells us otherwise. The only strict criterion is that the project must pass DRC to the satisfaction of the foundry. However, I cannot necessarily say what satisfies the foundry. A number of DRC rules are tied to specific, fixed layout cells (some of which we don't even have), which tends to inihibit experimentation at the device level, which runs counter to the purpose of the whole project. So I expect to be generating lots of waiver reports, or perhaps we can work out some kind of agreement with SkyWater. The bottom line is that if you are experimenting with digital circuits but otherwise expect the underlying circuits to work, then you should make sure you are DRC clean. If you are playing around with devices, then you should make sure that your project is able to survive any experiment that does not work and can still provide valuable feedback (i.e., the community should be aware of what doesn't work as well as what does work). Beyond the DRC "requirement", there is the unknown factor of how many valid submissions we will end up with for the first run. If we are overloaded with submissions, then we will probably apply some ranking to the projects (where certain things like tests of open-source IP that could become critical components of the harness for the next shuttle run would be given priority). But as yet, not knowing whether we will get ten submissions or a hundred, there is no particular point in discussing project rankings.
👍 2
✔️ 1