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
e

Emilio Baungarten

04/21/2023, 8:34 PM
Hello everyone, I want to know if this is correct, in my Core module I had multiple sub-modules, when I fill in the "FP_PDN_MACRO_HOOKS" I usually use the power pin connection" vccd1 vssd1 vccd1 vssd1". Usually that generates some LVS errors because some sub-modules are not connected to those pins, so I go to OpenROAD -GUI and just choose the power grid that passes over the module. e.g. the "6__7_" module is connected to vccd1, and vssd1. but as u can see in the picture the power pin cannot be connected to the module "7__6_" so I used power pins vdda1 and vssa1. My questions are: that is a correct connection? that could generate some error? How can I uses only vccd1 and vssd1?
m

Mitch Bailey

04/21/2023, 10:56 PM
1. You could make your macros taller so that they will always connect to at least 1 vccd1, vssd1. 2. You could manually place your macros so that they will connect to vccd1, vssd1. As vdda1 is usually 3.3V, you probably don’t want to use that.
e

Emilio Baungarten

04/21/2023, 11:48 PM
In these modules I can do it (change the size or place of the macro) but in other areas (like in the image) with more connections and sub-modules around I can't. is there another solution?
m

Mitch Bailey

04/22/2023, 1:22 AM
There are 8 repeating power straps. Ideally, your macros should be tall enough to intersect with all of them so you don’t need to worry about placement. You can set the macro size when synthesizing. vccd1 and vccd2 are both digital power supplies, nominally 1.8V, so you might be able to connect to either of those. Some designs short the digital power supplies: vccd1-vccd2 and vssd1-vssd2. I cannot comment on the merits or demerits of either of these suggestions.
1