sky130-lvds-tx (2AMLogic) errors
3 failures reported against sky130-lvds-tx (2AMLogic), sorted by how they fail and ranked by impact.
#216 by errors trackedSimulation & verification
Recurring sky130-lvds-tx (2AMLogic) errors, by impact
- 1The cited DRC report hashes to the placement-only GDS. PR #48 then added routing, the GDS hash changed, and DRC was never re-run. The 486-violation count, the claim that every violation sits in the stock pad frame, and the README line 'placement-only and unrouted' all describe a stream that no longer exists; the new met1 to met3 routing has no DRC result at all.Simulation & verification · Silent failure · 1 report74
- 2A sky130 LVDS transmitter's committed gate-level netlist came from a host Yosys build, so it could never be reproduced under the pinned toolchain. Regenerated under the pinned Yosys, the routed GDS still does not reproduce. Signoff evidence that nobody could rebuild.Simulation & verification · Silent failure · 1 report66
- 3sky130-lvds-tx's pad cell instantiates its ESD diode with area 400x the model default, so at 1.25 V it shunts 107.4 mA against 268.6 uA at default. The earlier driver bench had to leave the real pad out of the deck and 'argue DC equivalence' instead. Everything measured 'at the pad' is blocked or quietly wrong.Simulation & verification · Wrong design output · 1 report66
How it fails
Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.