Hello. I tried to put macros into my project. I have finished placing the macros and setting up the config.json. I proceed to run openlane for synthesis and tapeout. I get a Running Global Routing error code. Specifically, the error: [ERROR GRT-0119] Routing congestion too high. Check the congestion heatmap in the GUI and load /home/edabk/efabless/caravel_user_project/openlane/neuron_core_dffram/runs/23_11_28_11_46/tmp/routing/groute-congestion.rpt in the DRC viewer.

Hello, I'm having error with the following line: ".include ~/skywater-pdk-libs-sky130_fd_pr/cells/nfet_01v8/sky130_fd_pr__nfet_01v8__tt.corner.spice". It returns error of: "Error in line include "sky130_fd_pr__esd_nfet_05v0_nvt.pm3" Not enough parameters"

Hi, i saw some post on gm/Id method, an IEEE paper for the same https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=535416&tag=1 However, to plot graphs, 1. gm/Id Vs Vgs --> for gate Voltage 2. gm/Id Vs Vdsat --> i.e. VDD (also called as gate overdrive voltage) 3. gm/Id Vs gm/gds --> intresic gain 4. gm/Id Vs Vth ---> threshold voltage 5. gm/Id Vs Id/W ---> Current Density i'm searching for ngspice commands to be used with sky130, from some time. But, with few forms not able to find help. So, can anyone having example for such. It would be great help.

@Tim Edwards We are looking into implementing some inductors in Skywater 130 and I am not sure where we could get some references. Are there any primitives? can I find them in open_pdks or generate them using Magic? @Chirag Agarwal FYI

I'm trying to extract spice from a GDS file (Tiny Tapeout ROM) and simulate it in NG Spice to dump the ROM contents. This is how I'm extracting the spice: https://github.com/TinyTapeout/tt06-rom-spice-sim/blob/master/extract_spice.sh

What is the exact meaning of "Result: The top level cell failed pin matching." for netgen? I have two netlists with matching components and number of nodes and it is giving that error. I seem to remember a more explicit error if the connectivity in the netlist is different.

@Stefan Schippers I am trying to do a basic parametric sweep (snapshot attached). In the waveform graph, how to differentiate between the traces? i.e., how to show the parameter associated with every VOUT trace? Also for the cursors, how to jump from one VOUT trace to another? Is this explained in xschem manual? I couldn't find this.

@Stefan Schippers: After a round of testing and bug fixing, I resolved a number of issues with the continuous sky130 models. It's clear that they work for the most part, but I missed (or my scripts missed) a handful of spectre-to-ngspice conversions. I would like to transition completely from the discrete-binned models to the continuous ones, which requires (1) changing the "ngspice" directory in the PDK path for models to "combined" ("combined" meaning a combination of the new continuous models and the original models that weren't in the set of continuous models provided by SkyWater), (2) running all the device tests to make sure nothing else is broken, (3) fixing anything that is broken, and (4) pushing the updated xschem library. If you or somebody else can run the tests and give me feedback on any errors, I can patch the repositories when/if needed.

Hi everyone, I'm stuck on routing congestion for our final user_project_wrapper build. I really can't understand the way in which the router is behaving. The ports its having trouble with appear to be just those along the bottom edge of the macro. I've brought these right out to the edge, and they are few and far between (only about 60 ports spanning a 1200um edge) but its still having trouble with congestion. It seems to be sending all the wires up a narrow corridor to the left of the macro, and then across and down, why? There's loads of empty space below it!

Hmm... in various points throughout my build I've gotten the following warnings at the end: • There are max slew violations in the design at the typical corner • There are max capacitance violations in the design at the typical corner • There are max fanout violations in the design at the typical corner What would be a good way to address each of these issues? More specifically, what knobs should I be adjusting in the configuration file for each warning?