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
n

Nelson Rodriguez

02/21/2023, 3:50 PM
Hello everyone, I was studying the layout of some cells from sky130 pdk and I would like to know why all of them have some nwell portions outside the yellow box? I play with the layout (fig 2), and see that without them (red boxes) there is no DRC violation. Same thing with the blue box, where in this case there is no nwell, I filled it and no DRC error. Thanks in advance.
t

Tim Edwards

02/21/2023, 4:36 PM
The abutment box shows where cells should touch in an array---it is what is used by digital place and route tools to place the cells into a standard cell layout. The actual layers in the cell may extend beyond the abutment box to satisfy various width, overlap, and spacing rules.
n

Nelson Rodriguez

02/21/2023, 5:36 PM
All right, thanks Tim. Regarding the top part where there is no nwell (yellow box), I guess filling or not with n-well was optional and the design team adopted not to fill that part. what do you think/know?
t

Tim Edwards

02/21/2023, 7:50 PM
Your "yellow box" here is not really the abutment box; attached is a screenshot showing the abutment box (inner white box) and extent of geometry (outer white box). The abutment box runs through the centerlines of the power and ground rails, so when cells are abutted, the rails overlap. So do the nwells.
n

Nelson Rodriguez

02/21/2023, 7:59 PM
Clear, thanks Tim
l

Luis Henrique Rodovalho

02/21/2023, 8:56 PM
What is this yellow box? Is it a boundary box? How do I use it?
Currently I'm designing inverter-based amplifiers, but I need extended nwells to pass DRC. It is not area efficient, so I must overlap subcells
image.png,image.png
n

Nelson Rodriguez

02/22/2023, 1:11 AM
@Luis Henrique Rodovalho I draw that yellow box with my screenshot tool. I don't know if I understood very well what you want to do, but If you need to extend the nwells, could you use filler cells?
@Tim Edwards One question, Fig 1 is my inverter focused only on verifying all DRCs, so the n-well is as large as required to satisfy the 0.18 um with respect to diffusions. You mentioned that the actual layers may extend beyond the abutment box to satisfy the overlap. My question is, how big should I draw the n-well so that when doing p&r I am sure that the tool will create continuity in the n-wells? Is Fig. 1 ok or should I fill in the empty space as in Fig. 3? I have measured in sky130 hd std cells the n-well outside the abutment box [Fig 2], are those extent dimensions mandatory?
t

Tim Edwards

02/23/2023, 4:44 PM
In principle, as long as it reaches to the abutment box edge, it will be okay; there is no particular reason to require the nwell to satisfy the minimum rule within the cell (in Magic, where the DRC engine is interactive, the DRC error will show up as long as you are viewing the cell by itself, but will not show up in the top level view of a placed and routed design).
The idea may be that designers (especially mixed-signal designers) may use a handful of digital cells outside of a P&R environment, so having the cell clean by itself is useful. By contrast, I/O cells are often not DRC clean by themselves, because they would never be used outside of the context of a full padframe.