Closed bvhoof closed 3 years ago
Hi, we will take a look at this. It should not be using that netlist for LVS but just for simulation.
Hi,
I solved it myself by creating a new hierarchical pex extractor script in calibre. Now, it does a hierarchical pex extract. This way, the module names stay the same as in the generated spice netlist. Additionally, simulation runs faster. Then, I modified all the code so that if calibre pex is used, it runs as if it was a hierarchical non-pexed design.
See pull request 110 for all calibre related fixes. I hope you can merge this.
Regression test works, although I had to re-write test 30 to pass trough the technology flag correctly.
Best regards, Bob.
Merged in your changes.
Hi,
Recently, you added labels on the top level (for pex and timing). However, for calibre LVS, there is a spice netlist without propagated ports and the gds (and extracted spice) do have all these propagated ports.
Is there some kind of switch to propagate the ports in spice, similar to the layout, so that LVS is clean?
Best, Bob
some code below: run script:
python3 $OPENRAM_HOME/openram.py myconfig --debug
config file:generated spice netlist sram subckt definition:
spice netlist from calibre: