1. Purpose of the gate
Test chip sign-off is where the company decides that its first database is correct enough to commit. Once the database is released and wafers start, errors cannot be fixed until the next shuttle, and the cost of that delay is measured in runway as much as in money. The review judges the database: that it implements the frozen test chip specification, that verification has closed against its plan, that it meets the foundry's rules and that the waivers it carries are understood and accepted.
The gate criteria are a test chip verification report signed off against its plan; timing, power, physical verification and the foundry's checks clean or waived; the test chip RTL run on the prototype platform, with the results recorded; and every waiver reviewed and recorded with its reason.
A test chip is signed off at a reduced scope agreed in writing, and the review checks that the scope protected what matters: the blocks that carry the key claims and the paths that let the chip be brought up at all. The review is usually held in steps, with a readiness review on a near-final database and a final review once the last checks are run, early enough before the cut-off to fix what the provider's pre-checks find. The release itself is the Test chip tape-out gate that follows.
10 more sections for registered members.