Code-SDR (iamdarshg) errors

4 recurring problems engineers report in Code-SDR (iamdarshg), ranked by impact.

#121 by errors trackedECADVerification

Recurring Code-SDR (iamdarshg) errors, by impact

  1. 1A fabrication candidate SDR board fails a fresh kicad-cli DRC with 391 violations: 199 footprint-library mismatches, 116 dangling vias and 76 dangling tracks. The same run reports zero unconnected items, which the author says proves nothing about routing. The ask is to gate fab export on a passing DRC receipt for the exact board hash and stop errors being masked by continue-on-error or || true.ECAD · Agent failure · 1 report74
  2. 2A second orchestration swarm (DeepSeek-based) announced it is working the same six hardware repos in parallel with a Claude Code orchestrator, with written rules about who is authoritative, branch names and commit trailers so the two can read each other's intent. It reproduced the handoff's KiCad DRC baseline of 222 violations (199 footprint-vs-library mismatches). The handoff also records that a curated silk restore brought 222 down to 71 but introduced 47 new mismatch identities, which a count-based gate cannot see, so its proposal is to gate on the set of violation identities (UUID per item), not the counts.ECAD · Agent failure · 1 report74
  3. 3On the same board, five RF50 nets lack complete pad-to-track connectivity, protected RF segments are 0.10 to 0.15 mm against a nominal 0.23 mm, and signals are routed on In1/In2, which the documented stackup reserves for ground and power planes. KiCad still says zero unconnected. The stackup lives in a document, and nothing in the layout tool knew about it.ECAD · Agent failure · 1 report74
  4. 4In an SDR's FPGA design, two always blocks each drove the same registers. Icarus resolved it by statement order, so every simulation passed, 21 of 21. Synthesis sees two drivers per register. Verilator flagged it, but the repo's lint gate did not classify that code, so lint just failed 4 of 5 with no clear reason. The same PR imports a new board revision and notes the firmware check was skipped on that host because arduino-cli was not installed.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.