gf180-buck (2AMLogic) errors
3 failures reported against gf180-buck (2AMLogic), sorted by how they fail and ranked by impact.
#179 by errors trackedSimulation & verification
Recurring gf180-buck (2AMLogic) errors, by impact
- 11,260 Via1 cuts in the committed GDS sit entirely outside Metal1 and connect the Metal2 straps to nothing, and no rule in the curated DRC deck reports them. The row generator only asserts a row isn't wider than the strap field, so a narrower row passes silently. Orphan vias in a committed layout, invisible to the DRC deck.Simulation & verification · Silent failure · 1 report66
- 2A companion issue clears 20 Via2 enclosure findings that a README had recorded with no issue ever opened. The findings existed only as prose in a README, with no tracked issue behind them, so they were invisible to the workflow that clears findings.Simulation & verification · Missing capability · 1 report66
- 3gf180-buck's README still says 1 of 11 T1 items and 'Current position: spec ratified', while manifests/gf180-buck.signoff.json has t1_met_count 4. Schematics, netlists, a power-stage GDS and six benches are on main, and six averaged-model records exist that the README says don't. The README fix has to go through a T1 re-attestation, so two README issues got bundled to avoid re-attesting the same pinned file twice.Simulation & verification · Silent failure · 1 report66
How it fails
Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.