summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorPaul Vincent Bezzina <109743463+Vertrex-star@users.noreply.github.com>2026-10-16 19:31:40 +0100
committerGitHub <noreply@github.com>2026-10-16 19:31:40 +0100
commitecdc6ee93f28752781062a79ebb88778761bf17f (patch)
treec700838b2616f41050e65c0e84977fc6ab5df01e /README.md
parentf9ed6da5ff74eb887a0fd351369433f84397e173 (diff)
downloadPCB-Challenge-2026-ecdc6ee93f28752781062a79ebb88778761bf17f.zip
Update README.md
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 21dd9d1..610acdc 100644
--- a/README.md
+++ b/README.md
@@ -76,7 +76,7 @@ The keep out zone of the ESP32 antenna does not have to cover any PCB area, it c
- All submitted boards must pass KiCad's Design Rule Checker to a good degree (Inspect → Design Rules Checker). I understand that the DRC can be quite buggy especially with imported footprints, thus I will be a bit lenient.
- DRC **warnings** (e.g. minor silkscreen clipping) will not disqualify a board, but excessive or careless warnings may count against a board at the routing quality tie break stage.
-#### I am aware that there is an issue with the flip flop footprints and we will ignore any DRC errors associated with them. Just ensure you use a trace width of 0.17mm for them.
+#### I am aware that there is an issue with the flip flop footprints and we will ignore any DRC errors associated with them. Just ensure you use a trace width of 0.17mm or less for them.
### Note on High-Speed & Power Rules
The challenge schematic does include a high speed signal paths (a differential pair requiring a continuous reference plane). It does not however have a significant power delivery requirement (e.g. wide power traces, stitching vias). As such, no specific power plane rules are imposed in this iteration.