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
p

Peter Schmidt-Nielsen

06/18/2021, 10:04 PM
Hey folks, I have three questions about a macro I'm making with OpenLane (I am not using caravel_user_project, just OpenLane directly, then this macro will be incorporated into a design): 1. I'd like to be pretty sure that there aren't antenna check issues with my macro before Weston integrates it into what he's submitting. Synthesis failed when I tried to use
DIODE_INSERTION_STRATEGY = 1
(spray diodes), but synthesis works fine with
DIODE_INSERTION_STRATEGY = 3
(FastRoute's antenna avoidance). It failed saying
[WARNING DPL-0005] Overlap check failed (14269)
. My main question: If I can't use
DIODE_INSERTION_STRATEGY = 1
, is there some easy way I can just guarantee that every input pin has diodes? Or will they all already have diodes? 2. Secondly, I see these reported in
manufacturability_report.rpt
(again, synthesizing with
DIODE_INSERTION_STRATEGY = 3
):
Antenna Summary:
Source: /openLANE_flow/designs/snproc/runs/run7_rev2_mem512/reports/routing//41-antenna.rpt
Number of pins violated: 960
Number of nets violated: 651
How scared should I be of that? 3. Finally, I'd like to perform some sort of LVS check. I see a
results/lvs/
directory that contains some log files reassuring me that no mismatches were found. Are these checks performed on the final GDS all the way back to the first netlist? If not, do folks have advice on running an LVS, and which is the best netlist to LVS the GDS against?
(Done: Weston helped me with this.)