i
Five files, five readers
| View | File (for memristor_hfo2_al) | Who reads it | In this PDK |
| Verilog | user_models/verilog/memristor_hfo2_al.v | Digital simulators (Icarus Verilog) and synthesis (Yosys): "this block exists, with these pins" | Pins only, no behaviour |
| Liberty | libraries/openmemristorpdk_pr/memristor_hfo2_al.lib | Synthesis and timing tools (Yosys, OpenSTA): how fast and how power-hungry a block is | Pins only, no timing |
| LEF | libs.ref/openmemristorpdk_pr/lef/openmemristorpdk_pr.lef | Place-and-route (OpenROAD, LibreLane): the block's size and where its pins are | Complete (1 × 1 µm) |
| CDL | libraries/openmemristorpdk_pr/memristor_hfo2_al.cdl | LVS (Netgen): checks the layout matches the circuit | Complete |
| GDS | libraries/openmemristorpdk_pr/memristor_hfo2_al.gds | The factory: the actual shapes to build | Complete |
memristor_hfo2_al.vVerilog
module memristor_hfo2_al(BE, TE);
inout BE;
inout TE;
endmodule
memristor_hfo2_al.libLiberty
library (memristor_hfo2_al) {
cell (memristor_hfo2_al) {
pin (BE) {
direction : inout;
}
pin (TE) {
direction : inout;
}
}
}
Why so empty?A memristor has no clock and no logic function, so Liberty's usual "delay from input to output" doesn't describe it. Real memory chips solve this by wrapping the memristors in a memory macro (array + the circuits that write and read it), and only the macro gets real Verilog and Liberty views.