Add the minimum required components needed for this Pi Pico 2 to function properly. Keep the design as simple and minimal as possible.
You may include a single humidity sensor as the primary peripheral, along with any essential supporting components such as power regulation, pull-up resistors, decoupling capacitors, or required connectors.
I’ll turn this Pico 2 shield template into a minimal working humidity-sensor shield: first I’ll inspect the existing Pico header part, then select a simple I2C humidity sensor and only the required support parts, wire power/I2C/decoupling, and run checks.
I found the Pico 2 shield exposes 3V3/GND and GPIO pins, so I’m using the Pico’s onboard 3.3 V rail—no extra regulator is needed. I selected an SHTC3 I2C humidity/temperature sensor; its datasheet requires only a 100 nF decoupling capacitor and SDA/SCL pull-ups.
Done — I added the minimal SHTC3 humidity/temperature sensor circuit for the Pico 2 shield: SHTC3 on I2C0 using GPIO0/GPIO1, 10 kΩ SDA/SCL pull-ups, and a 100 nF local decoupling capacitor on 3V3. Schematic ERC/manufacturing/passive checks are clean; full review still shows PCB airwires because layout/routing has not been done yet.
I also recorded the design rationale in Minimal Pico 2 Humidity Shield Notes. The next step is layout placement for the new sensor and passives, then routing.
Add the minimum required schematic components for a Raspberry Pi Pico 2 shield to support one humidity sensor peripheral.
Selected peripheral
Sensor: Sensirion SHTC3-TR-2.5KS humidity and temperature sensor
Interface: I2C Fast Mode Plus capable
I2C address: 0x70
Supply range: 1.62 V to 3.6 V
Typical/maximum measurement current from datasheet: 430 uA typical, 900 uA maximum in normal measurement mode
Power approach
The shield uses the Pico 2 3V3 pin as the sensor rail. No additional regulator is required because the SHTC3 operates from 1.62 V to 3.6 V and the sensor load is under 1 mA peak.
The schematic-level ERC and manufacturing checks are clean after wiring and adding passive MPN metadata. Full project review still reports PCB airwires because the new schematic nets have not been placed/routed on the PCB yet; this is expected until the user approves moving from schematic to layout.