A 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.
Silent failure reported against sky130-lvds-tx (2AMLogic)
What engineers report
A silent failure reported against sky130-lvds-tx (2AMLogic): reports success, or uses stale data, while the result is wrong or missing.
Recorded mode: validation / failure
Analyst note
From the Grok pain-radar digests, Nov 14-15 2026 (Nov 14 8:41 PM ET through Nov 15 1:41 AM ET digests plus the Haitch edition). Verified live 2026-11-15: issue/PR read; title and state confirmed.
What it costs a team
Modeled annual cost
$30,000
For a team of 5
Prototype delay
3 days
Modeled schedule slip per occurrence
Time lost
240 min
Per engineer per month, about 1 incidents
How the cost is modeled
240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000
A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.
Engineering tools that address it
No engineering tool profile lists this error yet. Browse tools that connect to sky130-lvds-tx (2AMLogic).
Evidence
More recurring errors in sky130-lvds-tx (2AMLogic)
- The 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 · impact 74
- sky130-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 · impact 66
Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.