You can also do some co-simulation with Xyce. I've used the python bindings in the past to couple to CocoTB. Worked reasonably well although you have to do the plumbing between the tow tools yourself

Thanks for sharing this! I've never heard of Xyce or CocoTB before. What sort of project did you use it for?

It was a only proof of concept but I did a full chip mixed signal simulation with a design we had and it worked well in the end. Unfortunately I can't share the actual code as it was done at work.

Thanks, that’s super interesting. What did you use to do the graphical schematic capture? (I’m assuming Xyce is headless?) And no worries, I’m sure many of us have signed more NDAs than we care to admit haha.

For that we had the netlist generated from Virtuoso and focused on the code to put the two parts together. But for skywater projects I'm using xschem for schematic capture. It's pretty good and has all the essential features for analog IC schematic capture. We also just started a channel for that: #xschem

Oh perfect, I’ll join that.

Xyce is produced in our lab! Good to see it mentioned 🙂

@Mike Frank you work at sandia? I'm curious what other tools you use for schematic/layout etc. The normal commercial offerings or is there some more interesting tools out there?

Mostly commercial stuff; a lot of different things, including most of the usual... We use tools from Cadence, Synopsys, and many smaller tool vendors... Xyce is one of relatively few major public tools that is produced in-house.

Xyce doesn’t support the .option size= command that seems to be relied on with the skywater spice models. I am going to switch to ngspice now.