I used KiCad to design a board around a XIAO RP2040, with an LDR input and an LED output. The aim was to move from a circuit diagram to a layout that could be milled, assembled and programmed. The fabrication and board test continue in Electronics Production.
Our group uses test equipment to connect circuit behaviour with measurable signals. A multimeter gives steady voltage or continuity information, while an oscilloscope shows voltage changing over time. We record the instrument settings and the probe ground reference so that the observations can be interpreted.
Our oscilloscope and function-generator work is on our group assignment page. The logic-analyzer capture and its channel interpretation still need to be included in the shared work.
I created a KiCad project and installed the Fab library through the Plugin and Content Manager. The library provides symbols and footprints suited to the parts available in the lab. In the Schematic Editor, I placed the XIAO RP2040, LDR, resistors, LED and connectors, then wired the nets and used labels to keep connections readable.
The archived component notes list a 10 Ω resistor and a 220 Ω LED resistor. The LDR input depends on its resistor network, so the fitted value needs to be checked against the actual board before using the schematic for another build. I have retained the recorded value rather than substituting an assumed one.
I assigned footprints and checked that the physical pad arrangement corresponded to the symbol connections. I updated the PCB from the schematic, placed the components and routed the board with a 0.8 mm track width. I added an Edge.Cuts outline and used the 3D viewer to inspect component placement.
The layout has to satisfy both electrical connections and the milling process. A wide trace alone does not guarantee that neighbouring copper can be separated by the cutter. Clearance, pad spacing, outline continuity and connector access all need checking on the exact revision that will be fabricated. A 3D view helps with placement but does not establish a passed electrical or design-rule check.
The archived project bundle contains a matching project, schematic and PCB layout. The separately linked schematic and project-settings file are also retained. A .kicad_pro file holds project settings; the actual routed layout is a .kicad_pcb file.
Before another milling run, I need to match the archived layout to the assembled-board photographs, confirm the fitted component values and run the relevant electrical and fabrication checks. This keeps the schematic, layout and physical result tied to the same revision.
The schematic defines connectivity, but the PCB adds physical constraints: component orientation, tool access, clearances and room for soldering. Moving between these views helped me see why a board needs more than a plausible-looking arrangement of tracks.
I exported readable schematic and copper-layout views from the archived KiCad pair. These are views of those source files, not a claim that they match every connection on the photographed board.
The exported netlist shows the LDR node on module D0/A0 and the LED branch on D1 through R2, recorded as 220 Ω. It also shows the LED anode connected to module ground pad 15. That does not implement the intended active-high LED circuit. R3 is still recorded as 10 Ω. I need to compare the LED orientation and the fitted divider resistor with the actual board before using this archive for another fabrication.
KiCad's checks report unresolved power/unused-pin issues and board clearances. In this source, the reported minimum hole and copper-to-edge clearance is 0.175 mm, below the configured 0.25 mm and 0.50 mm limits respectively. I have kept the original geometry and rules rather than changing the limits to make the warnings disappear. Missing Fab library links are a separate environment issue. Zero unrouted connections does not resolve those design problems.