Pico W Part Audit


There are currently 14 distinct Section values, but only Terminal Orders 1–10, and the exact sections Power and Ground no longer both represent all related pins because Section was copied from Pin Group.
Please confirm this interpretation:
  • All power-related sections (Power Input, 3V3, Analog Reference) → Terminal Order 1, Top
  • All ground-related sections (Ground, Analog Ground, Debug Ground, Test Ground) → Terminal Order 10, Bottom
  • Remaining sections → orders 2–9, distributed between Left and Right
  • Pins within the same section will share the section-level Terminal Order and Orientation
Proceed with this mapping?
Make the functional group more general.
I’ll consolidate the pins into 10 broader functional groups, assign group order 1–10, keep Power on Top and Ground on Bottom, and alternate the remaining groups between Left and Right.
ok
Applied and verified the generalized 10-group structure:
  1. Power — Top
  2. Control — Left
  3. GPIO Low — Right
  4. GPIO High — Left
  5. Analog — Right
  6. USB Data — Left
  7. USB Shield — Right
  8. Debug — Left
  9. Wireless / Test — Right
  10. Ground — Bottom

SC0918 Part Audit
Date: 2026-07-23
Part identity and metadata

Table


FieldCurrent / observed valueDatasheet / official source check
MPNSC0918Official Raspberry Pi Pico W ordering code is SC0918 (datasheet OCR also renders it as SCO918 in one table; context confirms SC0918).
ManufacturerRaspberry PiMatches official Raspberry Pi Pico W documentation.
ProductRaspberry Pi Pico WMatches SC0918.
Part typeLibrary entry reports blank/part project context shows Evaluation Board in indexed metadataShould be Raspberry Pi Pico W microcontroller board / module / evaluation board.
Description2.1 Manufacturer Recommendations 3.6mm Raspberry PiToo terse/unclear; should describe Raspberry Pi Pico W RP2040 wireless microcontroller board.
Terminal count53Matches: 40 main header pins + 4 USB shell pads A-D + 3 SWD/debug pads E/F/G + 6 test points TP1-TP6.
Datasheet URLSet during this auditOfficial URL used: https://pip-assets.raspberrypi.com/categories/686-raspberry-pi-pico-w/documents/RP-008312-DS-2-pico-w-datasheet.pdf
Supporting official pinoutNot a propertyhttps://pip-assets.raspberrypi.com/categories/686-raspberry-pi-pico-w/documents/RP-008315-DS-1-PicoW-A4-Pinout.pdf
Key datasheet specs
  • Board/module: Raspberry Pi Pico W, RP2040-based microcontroller board with 2.4 GHz wireless.
  • PCB body: 51 mm x 21 mm x 1 mm; micro-USB connector overhangs top edge.
  • Main interface: 40 pins on 2.54 mm / 0.1 in pitch, dual castellated/through-hole style, 1 mm holes on the module.
  • Exposed GPIO: 26 GPIO; GP0-GP22 digital, GP26-GP28 digital/ADC inputs.
  • Logic/GPIO voltage: fixed 3.3 V.
  • VBUS: nominal 5 V, 5 V +/-10%.
  • VSYS: 1.8 V to 5.5 V system input.
  • 3V3 output: generated by on-board SMPS; recommended external load under 300 mA.
  • Operating temperature: -20 C to +70 C including self-heating.
  • Mounting holes on module: 4 x 2.1 mm +/-0.05 mm drilled mounting holes.
  • Antenna keepout/cutout: 14 mm x 9 mm; place antenna at board edge and avoid nearby/underlying material or metal enclosure.
Schematic symbol cross-check
Pin mapping
The 40 main terminals match the official Pico W physical pin order:

Table


Pin rangeResult
1-20GP0, GP1, GND, GP2, GP3, GP4, GP5, GND, GP6, GP7, GP8, GP9, GND, GP10, GP11, GP12, GP13, GND, GP14, GP15 — matches official pinout.
21-40GP16, GP17, GND, GP18, GP19, GP20, GP21, GND, GP22, RUN, GP26, GP27, AGND, GP28, ADC_VREF, 3V3, 3V3_EN, GND, VSYS, VBUS — matches official pinout, except the symbol names pin 36 3V3_OUT rather than official 3V3 / 3V3(OUT).
A-DUSB shell pads — present.
E/F/GSWCLK, GND, SWDIO debug pads — present and match official debug header functions.
TP1-TP6TP1_GND, TP2_USB_DM, TP3_USB_DP, TP4_WL_GPIO1/SMPS_PS, TP5_WL_GPIO0/LED, TP6_BOOTSEL — present and match datasheet test point functions.
Symbol/pin-description findings
  • No explicit Pin Description properties were found on the terminals; the terminal designators encode the primary names/functions, but alternate functions and warnings are not captured as descriptions.
  • 3V3_OUT should ideally be renamed or described as 3V3 / 3V3(OUT) to match Raspberry Pi naming.
  • Pin 36 3V3_OUT is currently typed Power In; datasheet describes this as the generated 3.3 V supply output for external circuitry, so Power Out/power-source semantics would be more accurate.
  • ADC_VREF is marked Power In; it is normally a filtered ADC reference/supply node and can be externally driven for a better reference. This is acceptable only if documented; otherwise an analog-reference/passive style would be clearer.
  • USB shield pads A-D are marked Power In; a passive/shield/ground/mechanical type would better reflect function.
  • TP4 is typed Not Connected, which aligns with the datasheet warning “do not use”, but the reason should be captured in Pin Description.
  • TP5 is typed Output, which is directionally reasonable, but the datasheet warning should be captured: it is not recommended and only swings from 0 V to the LED forward voltage.
  • GP26-GP28 should include ADC0/ADC1/ADC2 aliases in descriptions; GP0-GP22 could include UART/I2C/SPI/PWM alternate-function notes if this part is intended to be richly documented.
Footprint cross-check
Matches
  • Footprint asset present: MODULE_SC0918.kicad_mod.
  • 3D model asset present: SC0918.step.
  • Symbol/thumbnail asset present: SC0918 SC0918 Symbol.svg.
  • Pad count is 53, matching all expected electrical/contact pads.
  • Silkscreen/outline geometry includes a Pico-sized body outline around 21 mm x 51 mm and an antenna keepout/cutout drawing around 14 mm x 9 mm.
  • Main pin naming/order appears to match the official Pico W pinout.
Footprint mismatches / risks
  • Critical footprint scale issue: pad coordinates and sizes reported by the layout tree are ~1000x too small compared with the silkscreen/body geometry. Example: main pad positions report around x = +/-0.00969, y = +/-0.02413, size around 0.0016, where a usable footprint should be around +/-9.69 mm, +/-24.13 mm, and ~1.6 mm-class pads. This makes the actual copper pads effectively microscopic/clustered near the origin even though the silkscreen outline is full scale.
  • No explicit mounting-hole nodes were found, despite the datasheet identifying four 2.1 mm +/-0.05 mm mounting holes on the Pico W. If this footprint is meant to model full mechanical mating, those should be added or intentionally documented as omitted.
  • The antenna keepout appears as drawn outline/silkscreen geometry, not as an enforced copper/component keepout rule. For board reuse, it should be an actual keepout/cutout constraint.
  • The datasheet recommends paste stencil zones 163% larger than the SMT footprint. Paste apertures were not visible in the inspected layout data, so paste compliance could not be verified.
  • The current footprint appears to model an SMT carrier footprint, not a through-hole DIP footprint. That is acceptable only if the intended use is reflow mounting the Pico W as a module; the part description should say so.
Actions performed
  • Found the official Raspberry Pi Product Information Portal datasheet for SC0918 / Raspberry Pi Pico W.
  • Set the datasheet URL to the official Raspberry Pi PDF so datasheet queries now resolve for this part project.
  • Filed an internal Flux part-quality report for the critical footprint pad scale mismatch and missing/unenforced mechanical features.
  1. Fix the footprint pad scale: convert pad coordinates/sizes to real millimetres while preserving the correct 21 mm x 51 mm outline.
  2. Add/verify real copper/component keepout for the 14 mm x 9 mm antenna area.
  3. Add or explicitly document the four 2.1 mm mounting holes.
  4. Add Pin Description properties for each terminal, especially ADC aliases, power pin behavior, TP4/TP5 warnings, and SWD notes.
  5. Adjust pin types for 3V3_OUT, USB shell pads, and possibly ADC_VREF.
  6. Improve metadata: set a clearer description and part type such as Raspberry Pi Pico W RP2040 wireless microcontroller board / SMT module.
  • Part identity and metadata

  • Key datasheet specs

  • Schematic symbol cross-check

  • Pin mapping

  • Symbol/pin-description findings

  • Footprint cross-check

  • Matches

  • Footprint mismatches / risks

  • Actions performed

  • Recommended fixes