Preface
This course is for anyone who wants to design analog integrated circuits and has a laptop. You need no licences, no non-disclosure agreements and no prior IC design experience: only curiosity and some circuit theory.
Contents
Who this course is for
The course is written for final-year undergraduates in electrical and electronic engineering, graduate students starting in integrated circuits, and engineers from board-level or digital design who want to understand what happens inside an analog chip. It assumes you are comfortable with:
- circuit analysis: Kirchhoff’s laws, Thévenin and Norton equivalents, phasors and transfer functions;
- basic electronics: diodes, the idea of a transistor as an amplifier, and the operational amplifier as a building block;
- a little Python, enough to run a script and change a number in it.
Semiconductor physics is helpful but not required. Chapter 4 builds the MOSFET up from the picture a circuit designer needs.
How to read it
The course has seven parts. Read them in order the first time: each part uses the vocabulary of the one before it.
| Part | Chapters | You will be able to |
|---|---|---|
| I · Getting started | 1–3 | Install the tools, run a simulation in either PDK and explain what a PDK contains. |
| II · The transistor | 4–6 | Predict how a MOSFET behaves in any region and size one with gm/ID. |
| III · Building blocks | 7–10 | Analyse and design single-stage amplifiers, mirrors, references and the 5T OTA. |
| IV · Amplifier design | 11–14 | Design, compensate and verify a two-stage OTA, and budget its noise and offset. |
| V · Schematic to silicon | 15–17 | Lay out a block, verify it with DRC, LVS and extraction, and prepare a tape-out. |
| VI · Mixed-signal circuits | 18–22 | Design switched-capacitor and sample-and-hold circuits, comparators, data converters and phase-locked loops from the blocks of Parts III to V. |
| VII · The art of analog layout | 23–30 | Draw resistors, capacitors, matched arrays, bipolar and power devices that work and last, protect them against ESD, and assemble a die. |
If you already know analog design and want to learn the open-source flow, read Chapters 2, 3 and 6, then go straight to Part V and the labs. If you are teaching, each chapter maps to one or two lectures and each lab to one lab session; the course plan turns this into a set-up week and fourteen weeks, with Part VI as an optional five-week module.
The boxes
Every chapter uses the same set of boxes, so you can skim a chapter by its boxes alone.
- Each chapter opens with a box like this one, listing what you will be able to do at the end.
Key equation · The result to remember
The equations worth memorizing, for example the saturation current of the square-law model, \(I_D = \tfrac{1}{2}\mu_n C_{ox}\tfrac{W}{L}(V_{GS}-V_{TH})^2\).
Worked example · Numbers from both PDKs
A calculation with real numbers, usually done once for SG13G2 and once for SKY130.
What this means for your design
What the theory implies for the circuit in front of you.
Common pitfall
A mistake that is easy to make and expensive to find.
Try it · Lab number
A pointer to the lab or script that reproduces the result.
SG13G2 vs SKY130
Where the two processes differ in a way that matters for the topic at hand.
- Each chapter closes with the few points to remember.
The two PDKs, and how to choose
Every circuit is designed in both IHP SG13G2 and SkyWater SKY130. Where a netlist or script differs between them, it appears in tabs:
* SG13G2: 1.2 V core NMOS, W and L with units
.lib cornerMOSlv.lib mos_tt
XM1 d g s 0 sg13_lv_nmos W=2u L=0.5u ng=1 m=1
* SKY130: 1.8 V core NMOS, W and L in micrometres (the library sets .option scale=1u)
.lib "$PDK_ROOT/sky130A/libs.tech/ngspice/sky130.lib.spice" tt
XM1 d g s 0 sky130_fd_pr__nfet_01v8 W=2 L=0.5 nf=1
Pick a tab once and every tab group on every page follows. If you have to choose one PDK for your own work, choose the one your tape-out route uses (Chapter 17). Otherwise SG13G2 is the default PDK of the IIC-OSIC-TOOLS container and of the IHP open shuttles, and SKY130 has the longer history of community designs.
Reproducing every figure
All plots in the course are produced by Python scripts in tools/ that write netlists, run ngspice with each PDK’s own models and plot the results. They come with the lab files in one archive, which Lab 0 shows how to download and unpack inside the container:
tools/aicd/ shared helpers: PDK definitions, ngspice runner, lookup tables, plot style
tools/gmid/ the device characterization sweeps behind the gm/ID tables
tools/data/ the gm/ID lookup tables for both PDKs (NumPy .npz)
tools/figs/ one script per chapter, writing assets/figs/*.svg
tools/schem/ circuit diagrams (CircuiTikZ), compiled to SVG
Inside the IIC-OSIC-TOOLS container the scripts find the PDKs by themselves. Run, for example, python3 tools/figs/ch06_gmid.py. The labs walk through the same simulations by hand in Xschem.
Notation
Large-signal (total) quantities use upper-case symbols with upper-case subscripts, such as \(V_{GS}\) and \(I_D\). Small-signal quantities use lower case, such as \(v_{gs}\) and \(i_d\). A bias value written alone, such as \(V_{GS}\), means the DC operating point. Transconductance is \(g_m\), output conductance is \(g_{ds} = 1/r_o\), and the supply is \(V_{DD}\). Sizes are written as W/L in micrometres, so 2/0.5 means W = 2 µm and L = 0.5 µm.
Acknowledgements and sources
The scope and order of topics draw on several excellent courses, all cited on the References page: Prof. Sam Palermo’s ECEN 474 at Texas A&M [1], Prof. Harald Pretl’s analog circuit design course at JKU Linz [2], the IHP Analog Academy [3], Prof. Boris Murmann’s open gm/ID material [46, 56], and Kwantae Kim’s guides to the open-source tools [4, 5]. The textbooks of Razavi [51], Chan Carusone, Johns and Martin [52] and Gray, Hurst, Lewis and Meyer [53] are the standard references for the theory. The page design follows the Open-SERDES tutorial [10].
The course would not be possible without the people who build and maintain the open PDKs [14, 19] and tools [35, 36, 38, 39, 40, 41].
Contributing
This is a living draft. If you find an error, have a better explanation or want to add a lab, please tell us through SkillSurf or email skillsurfedu@gmail.com. The writing and figure conventions that every chapter follows are kept with the course files.