You've already forked ivan-torvalds-GuitarPedal
forked from AllSpiceMirrors/torvalds-GuitarPedal
f133642f74
Using zones in design blocks doesn't seem to work very well in practice, at least in the version I have (10.0.4). I'm not entirely sure what is going on, but what seems to happen is that when a design block is imported into a PCB design (with the "update pcb from schematic" workflow), kicad will import it as a group, but then try to merge matching zones with the outside. And really confuse the grouping as a result, and also end up mixing up the zones occasionally so that the zone names are just completely wrong and misleading. Sometimes it gets so bad that you end up with zones that you can see on the PCB, but not actually access from the UI. No way to delete the stale zombie left-overs. At one point I ended up rescuing one PCB by editing the kicad_pcb file by hand and removing a group that seemed to only exist as a grouping of zombie zones that no longer existed in reality. NOTE! The above is purely a symptom description from what I've seen, not any kind of deeper understanding of what kicad actually does. There might be something entirely else going on, and I'm just confused. Whatever the real issue is, zones _work_, but they seem to have a propensity for causing problems, and I've never seen it with normal elements. The TAC5242 design never caused me any problems - it doesn't use any zones (except for the base ground plane that isn't part of the design block export). Anyway, I can just route the power rails under the RP2354 manually using actual traces. It's not like it's even all that complicated: the zones were there just to tie the room together. Let's see if this gets rid of some of the oddities of using pre-routed design blocks. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>