I have made a few monoblocks before but this is my first time designing a double sided board.
With the nice nano off the board and connected via USB the firmware registers itself as a keyboard as it should. But once I socket it on the pcb it keeps restarting it seems.
I have checked all tracks and I can’t see any obvious errors. Using a multimeter I made sure that no tracks are shorted or broken.
KiCad also doesn’t show any missing connections.
Maybe you can have a quick look and see if I missed something obvious?
Sorry, I’m not volunteering to inspect your images, but insufficient supply voltage can be a cause of MCU resets. And that would not be a KiCad question.
If I connect the MCU via USB it works and registers as a keyboard. Once I socket it on the PCB it starts resetting repeatedly. So I’m guessing it must be the routing - but I’m not really sure.
This thread is not about how to use Kicad. It seems to be about a keyboard autorouter. Maybe that is why the tracks are stupidly thin for a PCB that will have to take physical abuse. It is impossible to diagnose the problem mentioned by the OP with just the PCB layout.
Smell like a BoR (Brown out Reset) issue. As mentioned, BoR issues are usually a result of a poor power distribution scheme. (too much parasitic RCL and/or poor bypass / decoupling)
