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)

sky130-lvds-tx (2AMLogic)Simulation & verificationSilent failureMedium confidence

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

  1. 12AMLogic/sky130-lvds-tx PR #121: fix(signoff): regenerate the serializer netlist under the pinned yosys; re-close item 1 digital as r2 (stacked on #112)github.com

More recurring errors in sky130-lvds-tx (2AMLogic)

See all 3 sky130-lvds-tx (2AMLogic) errors

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.