sg13g2-bandgap (2AMLogic) errors
3 failures reported against sg13g2-bandgap (2AMLogic), sorted by how they fail and ranked by impact.
#214 by errors trackedMechanicalSimulation & verificationElectronics & PCB
Recurring sg13g2-bandgap (2AMLogic) errors, by impact
- 1The previous tracker hit GitHub's 2,500-comment limit, mostly from sweep lease comments. The new audit grades 5 of 11 items met; item 11's ERC half cites the SG13CMOS5L port's report, not an ERC of the SG13G2 block, and that report still shows 10 missing-tie findings although the issue for them was closed.Mechanical · Wrong verdict · 1 report74
- 2A layout PR regenerated the bandgap's GDS and PEX netlists. CI then failed because the audited characterization report pins those netlists by sha256, and two no longer match, which invalidates three PEX sims (PSRR, output impedance, startup trip point). The fix is a new dated report, fresh sims through the batch fleet, and a re-minted signoff manifest. Do not relax the dependency check. One layout change, and the evidence behind signoff has to be rebuilt. This is the change-impact problem, handled well, and it is still a lot of work.Simulation & verification · Missing capability · 1 report66
- 3PR #435 resized the NMOS mirror to w=40u l=4u in the schematic and netlists, but the layout generator still hardcodes 10u by 1u and the committed GDS, LVS reference and PEX netlist all describe the old devices. The PEX generator self-test now fails with 'no schematic XM matches gate', and every downstream result that used the as-built amp has to be rerun.Electronics & PCB · Wrong design output · 1 report66
How it fails
Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.