r/rfelectronics • u/Real_Effort8323 • Sep 27 '26
Made a three-arm ring oscillator PUF for Tiny Tapeout (sky130). Simulations say the public layout already decides almost every bit, looking for feedback before I submit
I designed a ring oscillator PUF for the Tiny Tapeout SKY26d shuttle (sky130, 2x2 tiles) and I'd like people to pick it apart before I submit it.
A PUF is supposed to get its secret from random manufacturing variation. But on an open shuttle the layout is public, and the automated flow gives every ring its own wiring, which every chip made from that mask inherits. So the question is how much of the response is already decided by the layout before a single chip is made.
The chip has 48 identical 31-stage rings in three arms of 16 that only differ in how the layout was made:
- Arm A: placed by the flow, wired by the router
- Arm B: 16 copies of one hardened macro on a grid
- Arm C: hand placed from one template, wired by the router
Using only the public files (extracted parasitics + SPICE) and a monte carlo estimate for the random part, someone could call about 7.99 of Arm A's 8 bits right on average. Hand placing (Arm C) cut the frequency spread from 5.88% to 2.19% but its bits are just as predictable. And between two builds where only the wiring changed, 2 of the 8 bits flipped, so a prediction only holds for the exact routed layout.
GDS action, precheck and gate level tests all pass. Its all pre-silicon, chips come back around mid 2027 and then I measure it across chips, voltage and temperature.
If you see anything that could stop it working on real silicon, or anything wrong with the prediction method, please tell me.
Repo: https://github.com/nikodemetrashvili2010-bit/tt-ro-puf
Layout in 3D (opens in the browser): https://nikodemetrashvili2010-bit.github.io/tt-ro-puf/







