eos (mtmoreira) errors

4 recurring problems engineers report in eos (mtmoreira), ranked by impact.

#125 by errors trackedVerification

Recurring eos (mtmoreira) errors, by impact

  1. 1DRC and antenna checks pass but LVS is NOT CLEAN: KLayout cannot read the pinned platform CDL, and with a patched copy its comparison reports a mismatch but writes no report database in batch mode.Verification · Agent failure · 1 report74
  2. 2OpenRCX versus Magic parasitic extraction on the same sky130 block agreed only under one accounting scope, all-records ratio 1.206 FAIL, wire-only 0.791 FAIL, SPEF-scope 0.996 PASS, and the setup WNS delta of 0.208 ns failed the 0.10 ns tolerance, with the whole gap traced to how the SPEF was built rather than extraction.Verification · Agent failure · 1 report74
  3. 3A sky130 SRAM-bearing reference run through OpenROAD flow scripts found the macro placer with no solution so placement was manual, Magic drops a port-less macro instance from extraction so the black-box LVS had to be done on the extracted netlist, and platform config overrides the design-level CDL variable.Verification · Agent failure · 1 report66
  4. 4In a Tiny Tapeout pilot chip, 167 max-slew violations blamed on the reset net were actually loads of 15 fanout buffer groups sized from placement estimates, with one residual remaining because TritonCTS enforces no per-buffer fanout count.Verification · Agent failure · 1 report66

How it fails

  1. Agent failure4

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.