Pad Frame Test Logics: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
A collection of simple functionality tests for verifying the proper behavior of a pad frame when porting [[LibrePDK]] to a new technology node. | A collection of simple functionality tests for verifying the proper behavior of a pad frame when porting [[LibrePDK]] to a new technology node. | ||
The base repository with branches for individual generated layouts for test tapeouts, with their GDS files in GIT LFS, can be found here https://gitlab.libresilicon.com/designs/highwaytestchip/-/tree/master?ref_type=heads | |||
Below the functions are being documented. | Below the functions are being documented. | ||
Revision as of 18:39, 10 November 2026
A collection of simple functionality tests for verifying the proper behavior of a pad frame when porting LibrePDK to a new technology node.
The base repository with branches for individual generated layouts for test tapeouts, with their GDS files in GIT LFS, can be found here https://gitlab.libresilicon.com/designs/highwaytestchip/-/tree/master?ref_type=heads
Below the functions are being documented.
8 bit ring counter
I/O pad drive mode test
clock net loop back
The clock net loop-back is simply one of the pads, being permanently configured as an input, passing on the clock signal to all the other test circuits on the die, as well as directly passing it to a pad directly configured as output with active driver.
This test configuration allows us to measure clock skew and maximum clock propagation between input and output pads cells.