Hello, When trying to get the back annotation feature working. I have in place:

* Is this option needed, this option causes the ngspice error:
* "Warning from checkvalid: vector @m.xm1.msky130_fd_pr__pfet_01v8[ib] is not available or has zero length."
* .option savecurrents
.save all

When the

.option savecurrents

is specified, this causes no new RAW file to be created, but an error to occur, is this usage error or a bug ? When I attempt to "load waves" with code.sym "xschem raw_read $netlist_dir/testbench.raw tran" no error is shown, no indication an action was performed occurs and no update to visual seen. When I use the menu "Graphs -> Annotate Operating Point ... -> pick RAW file -> OK" the visual updates with question marks "? ?" the only data that is updated are the ammeter.sym and spice_probe.sym I added to the design. None of the transistors show values. I think I need to inject a wave graph into the schematic view, to provide an X axis time reference to show sample for, can''t see an obvious design/*.sym to insert for this, so hunting for a project with that configured. Also what is the best symbol to be using to inject test points for data collection (I and V for example), ideally with a quick toggle button list to disable/enable (without need to rework the schematic, to remove the injected symbol when you want to disable it). This would then modify the netlist creation and ngspice config accordingly to the disable/enable state of the individual test point. Also after some time in usage of xschem the application refuses to take any more mouse click input to select items in the main design area. Menu items work ok, a restart always fixes it. Is this is known matter maybe with Tk/X11, using Linux/Xwayland ? Thanks

Hi We are working on mixed signal design. We have a digital Macro and integrate it into user analog project wrapper along with our analog design in magic and manually do the routing , finally generate spice file and gds. How we can incorporate our digital design into xschem for the purpose of LVS in precheck?

Hi everybody, I would like to know how could I add a digital part to user_analog_project_wrapper? I mean, to obtain a similar result as when in caravel I do make user_proj_example and then make user_project_wrapper. I copied the openlane from caravel to caravan, I changed the pin_order.cfg so they could be similar to user_project_wrapper_empty (but I don’t know if this is correct) and I also tried to add from Magic, but it was not possible to open two different .gds files, this is, the user_project_wrapper_empty and the user_proj_example.gds. I also tried with Klayout and I also could not integrate both .gds. Could you please help me with an explanation about how this should be done? Thanks in advance!

@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.

StefanSchippers I was trying out one of your comparator design with xschem based on this . but im facing this problem, even though the utile stimuli code and stimule code is same as yours im getting error. I dont know what error I'm facing , im unable to debug it . Please help

Hi everyone! On the documentation webpage of sky130 PDK, In device details section, What do these parameters - VTXNL, VTXNN42 etc. mean? In the PDK, I can only find one transistor corresponding to each type while here, there are multiple parameters given. Also where can I find information about such parameters? I tried searching the documentation of sky130 but wasn't able to find any information on these codewords.

Hello everyone, when I run qflow on my verilog design it creates a folder named "layout" where you have .gds and .mag files which you can open in magic and view, however when I try to do this then I do not see the standard cell gates and on the console window it says that it is unable to read them, what could be the issue.

I realized that the sky130 pdk has a deep N well for isolating nfets. Has anyone done anything with this? I searched the channel but did not see any talk about it.

Have a question about parasitic extraction. My design flow goes like this: 1. Generate devices in Magic (since it is possible to import a spice circuit directly) 2. Import to klayout and perform layout 3. Import GDS to magic for LVS 4. Extract using netgen magic for parasitic extraction 5. Change port order in the extracted netlist by copying the subcircuit definition from my schematic 6. Simulate extracted layout Is there a way to set the port order in Klayout instead of in magic, or manually?

Hmmmm I'm trying to do LVS and at this point I'm not sure if I'm having a magic problem, a spice problem, a klayout problem, or some other problem. I'm running @Amro Tork’s https://github.com/mabrains/sky130_klayout_pdk/blob/main/scripts/run_standard_lvs.py script, on my gds file https://github.com/pepijndevos/sky130_lvds which shells out to @Tim Edwards’s magic and netgen. My gds is very incomplete, but I just want to get all the things working before I go all the way and have to ge back and fix a million things. So I made this dummy schematic of just the mosfets I drew

* schematic.cir
* .lib /usr/local/share/pdk/sky130A/libs.tech/ngspice/sky130.lib.spice tt
XM3 cm V- bufneg VDD_IO sky130_fd_pr__pfet_g5v0d10v5 l=0.5 w=10 m=10
XM2 cm V+ bufpos VDD_IO sky130_fd_pr__pfet_g5v0d10v5 l=0.5 w=10 m=10

And then I ran

python ../sky130_klayout_pdk/scripts/run_standard_lvs.py lvds.gds output.txt schematic.cir report.txt TOP

which generates some

.ext

files as well as write some spice to

output.txt

* NGSPICE file created from TOP.ext - technology: sky130A

.subckt sky130_fd_pr__pfet_g5v0d10v5_VU6JZ7 a_50_n1036# w_n144_n1098# a_n50_n1062#
+ a_n108_n1036#
X0 a_50_n1036# a_n50_n1062# a_n108_n1036# w_n144_n1098# sky130_fd_pr__pfet_g5v0d10v5 ad=2.9e+12p pd=2.058e+07u as=2.9e+12p ps=2.058e+07u w=1e+07u l=500000u
.ends

.subckt TOP
Xpfet_g5v0d10v5_7x05[0|0] m1_n102_n1172# w_n1336_n1674# m1_n66_1210# m1_n102_n1172#
+ sky130_fd_pr__pfet_g5v0d10v5_VU6JZ7
Xpfet_g5v0d10v5_7x05[1|0] m1_n102_1628# w_n1336_n1674# m1_n66_4010# m1_n102_1628#
[...]

But that's where the happiness ends. There was an error message from magic, but maybe it can be ignored?

Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 338): Cell "contact" was already defined in this file.
Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 338): Ignoring duplicate definition

But then comes the netgen part and here it completely goes of the rails. If I add a

.lib

statement it just gives an error, and if I don't, it seems to generate a dummy device and then complain that it doesn't have any properties:

Netgen 1.5.224 compiled on vr 24 jun 2022 10:27:18 CEST
Warning: netgen command 'format' use fully-qualified name '::netgen::format'
Warning: netgen command 'global' use fully-qualified name '::netgen::global'
Reading netlist file output.txt
Call to undefined subcircuit sky130_fd_pr__pfet_g5v0d10v5
Creating placeholder cell definition.
Reading netlist file schematic.cir
Call to undefined subcircuit sky130_fd_pr__pfet_g5v0d10v5
Creating placeholder cell definition.
Reading setup file /usr/local/share/pdk/sky130A//libs.tech/netgen/sky130A_setup.tcl
Model sky130_fd_pr__pfet_g5v0d10v5 pin 1 == 3
No property mult found for device sky130_fd_pr__pfet_g5v0d10v5
No property sa found for device sky130_fd_pr__pfet_g5v0d10v5
No property sb found for device sky130_fd_pr__pfet_g5v0d10v5
No property sd found for device sky130_fd_pr__pfet_g5v0d10v5
No property nf found for device sky130_fd_pr__pfet_g5v0d10v5
No property nrd found for device sky130_fd_pr__pfet_g5v0d10v5
No property nrs found for device sky130_fd_pr__pfet_g5v0d10v5
No property area found for device sky130_fd_pr__pfet_g5v0d10v5
No property perim found for device sky130_fd_pr__pfet_g5v0d10v5
No property topography found for device sky130_fd_pr__pfet_g5v0d10v5
[...]

And then the report is just

Equate elements:  no current cell.

Equate elements:  no current cell.
Verify:  no current cell to verify.