Standing offer: If you’re building consumer hardware and want advice on anything (business strategy, building a team, finding suppliers, go to market, design/architecture decisions, fundraising, etc), send me a DM and I am happy to have a call with you.
A better example with these instructions from the start. This looks pretty close to what I would have placed and routed by hand (though it is a simple board).
- When placing a PCB, place it the way an experienced layout engineer would by hand:
- For sub-systems sensitive to placements, like ESD protection, crystals, and passives for switching regulators, follow the layout in the relevant datasheet where possible.
- Put each decoupling capacitor directly at the supply pin it serves, with its pad facing the pin and about 1 mm away. Treat a reference design's looser spacing as a maximum, not a target.
- Put every other passive at the pin it serves, oriented so the connection is a short straight trace.
- Group related parts and align them: shared centre lines, even pitch, rows like capacitor – IC – capacitor, test pads on a grid.
- Keep one legible reference label per part, with no overlapping text.
- Review a rendered image of the placement before presenting it, not just DRC, and fix anything that looks scattered or misaligned.
In my CLAUDE.md:
- When routing a PCB, do it the way an experienced layout engineer would by hand:
- No bends sharper than 135°. No square or acute junctions: branch at 45°, and preferably at a pad or via.
- Tracks leave pads and vias from the centre, in a straight run until clear of the copper. No hooks or doubling back.
- Tracks that run the same way within about 0.5 mm of each other are routed side by side at the clearance rule. Plan buses and nets with a common destination as bundles before routing them.
- Leave no gaps that are too narrow to use: either at minimum spacing or wide enough for another track plus clearance. Avoid slivers and pour islands.
- Stagger vias so bundled tracks can stay together up to their ends.
- Start with power pours, then sensitive buses like high speed differential pairs and the micro routing around crystals and switching regulators, then more general bundles of low speed signals.
Before anyone jumps on it, this was a first pass with no input from me other than asking it to route it within JLC's default 6 layer design rules. At first glance, it looks like it should function, though I haven't done a review of it yet.
I (well, Opus) just mocked up a quick design of a mostly drop-in replacement for a Raspberry Pi Zero 2 W. It loses the HDMI interface, but otherwise likely handles a lot of the use cases that RPi Zero is used (and overkill) for.
With DDR and LPDDR shortages and pricing breaking the single board computer category, it's interesting to see that PSRAM-only microcontrollers are getting closer to closing the gap. e.g. ESP32-S31 has a real MMU and can run Linux!