-
Notifications
You must be signed in to change notification settings - Fork 3
reading pinouts
Distinguish physical connector positions, GPIO names and alternate functions before wiring.
A physical position tells you where a contact is on a particular connector. A signal name tells you what it connects to. GPIO numbers, Arduino-style labels and connector positions can all differ. Do not assume a label such as D4 means the fourth physical pin.
- Match the model and revision. Check whether the drawing shows the top, bottom, connector mating face or cable side.
- Locate pin 1, USB, antenna and other landmarks. A view from the opposite side can reverse the apparent order.
- Locate power and ground before signals. Read supply ranges and logic levels from the manufacturer documentation.
- Check alternate functions, startup restrictions and pins already used by onboard hardware.
- Trace each wire against the reference and verify the disconnected circuit before applying power.
Physical pinout sources may cover only one connector. Pin-function tables explain signal names and purposes, but do not always locate contacts on the PCB. Package maps refer to the chip itself. Board labels, product photos and block diagrams are supporting references, not substitutes for physical board pinouts.
Some annotated manufacturer-model sheets use K callouts. K01 connects the illustration to its table; it is not an inferred GPIO number or header position. The sheet states the model and scope. Unmodeled contacts and other family members remain outside that sheet’s coverage.
First Edition / 2026 · Open the guide · Source collection
- HaleHound and Elechouse hardware references
- Datasheets, I/O boards and carrier revisions
- ARM, x86 and RISC-V computers
- Start at the workbench
- How to read a pinout reference
- GPIO, I²C, SPI and UART
- Identify displays and sensors
- Use the Power Desk carefully
- Find a power-module reference
- Search, themes and saved boards
- Coverage, sources and review status
- Help improve the maker reference