GPIO pin numbering (BCM vs BOARD) in Raspberry Pi - Performance Comparison
When working with Raspberry Pi GPIO pins, choosing a pin numbering system affects how your program runs. We want to understand how the program's steps grow as we handle more pins.
How does the number of pins you use affect the program's work?
Analyze the time complexity of the following code snippet.
import RPi.GPIO as GPIO
GPIO.setmode(GPIO.BCM) # Use BCM numbering
pins = [17, 18, 27, 22]
for pin in pins:
GPIO.setup(pin, GPIO.OUT)
GPIO.output(pin, GPIO.HIGH)
This code sets up a list of GPIO pins using BCM numbering and turns each pin on.
Identify the loops, recursion, array traversals that repeat.
- Primary operation: Looping through each pin in the list to set it up and turn it on.
- How many times: Once for each pin in the list (4 times in this example).
Each pin requires the program to do the setup and output steps once. So, if you add more pins, the work grows directly with the number of pins.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | About 10 setup and output steps |
| 100 | About 100 setup and output steps |
| 1000 | About 1000 setup and output steps |
Pattern observation: The work grows evenly as you add more pins, doubling pins doubles the work.
Time Complexity: O(n)
This means the program's work grows in a straight line with the number of pins you use.
[X] Wrong: "Using BCM or BOARD numbering changes how fast the program runs."
[OK] Correct: Both numbering systems just label pins differently; the program still does the same steps for each pin, so speed depends on how many pins you handle, not the numbering style.
Understanding how your program scales with the number of GPIO pins helps you write clear and efficient code. This skill shows you can think about how your code behaves as it grows, which is important in many projects.
"What if we added nested loops to control pins in groups? How would the time complexity change?"
Practice
Solution
Step 1: Understand GPIO numbering modes
GPIO pins can be numbered by their physical location (BOARD) or by the Broadcom chip numbering (BCM).Step 2: Identify physical pin numbering
BOARD mode refers to the physical pin numbers on the Raspberry Pi header.Final Answer:
BOARD numbering mode -> Option AQuick Check:
Physical pins = BOARD [OK]
- Confusing BCM with physical pin numbers
- Thinking BCM is the physical numbering
- Assuming WIRING or PIN modes exist
Solution
Step 1: Recall the correct function to set GPIO mode
The function to set numbering mode is GPIO.setmode().Step 2: Use the correct constant for BCM mode
GPIO.BCM is the constant for BCM numbering mode.Final Answer:
GPIO.setmode(GPIO.BCM) -> Option DQuick Check:
Use setmode with BCM constant [OK]
- Using GPIO.mode instead of GPIO.setmode
- Using BOARD instead of BCM constant
- Calling GPIO.setupmode which doesn't exist
import RPi.GPIO as GPIO GPIO.setmode(GPIO.BOARD) GPIO.setup(7, GPIO.OUT) GPIO.output(7, GPIO.HIGH)
Which physical pin is set HIGH?
Solution
Step 1: Identify the numbering mode used
The code uses GPIO.setmode(GPIO.BOARD), so pin numbers refer to physical header pins.Step 2: Check which pin is set HIGH
GPIO.setup(7, GPIO.OUT) and GPIO.output(7, GPIO.HIGH) set physical pin 7 HIGH.Final Answer:
Pin 7 on the physical header -> Option CQuick Check:
BOARD mode pin 7 = physical pin 7 [OK]
- Confusing BOARD pin 7 with BCM GPIO 7
- Assuming pin 7 means BCM numbering
- Mixing physical pin numbers with BCM numbers
import RPi.GPIO as GPIO GPIO.setmode(GPIO.BCM) GPIO.setup(10, GPIO.OUT) GPIO.output(10, GPIO.HIGH)
Assuming the LED is wired to physical pin 10 on the header.
Solution
Step 1: Understand numbering mismatch
GPIO.setmode(GPIO.BCM) means pin numbers refer to Broadcom chip pins, not physical pins.Step 2: Check wiring vs numbering
Physical pin 10 corresponds to BCM GPIO 15. The code uses BCM pin 10 (physical pin 19), so it does not control the wired physical pin 10.Final Answer:
Pin 10 in BCM does not match physical pin 10 wiring -> Option AQuick Check:
BCM 10 controls physical 19 ≠ pin 10 [OK]
- Assuming physical pin numbers work with BCM mode
- Using string instead of int for pin number
- Thinking GPIO.setup can't use BCM numbering
Solution
Step 1: Identify physical pin 12's BCM number
Physical pin 12 corresponds to BCM GPIO 18 on Raspberry Pi.Step 2: Use BCM numbering mode and correct pin
Set mode to GPIO.BCM and use pin 18 in setup and output.Final Answer:
GPIO.setmode(GPIO.BCM) GPIO.setup(18, GPIO.OUT) GPIO.output(18, GPIO.HIGH) -> Option BQuick Check:
Physical pin 12 = BCM 18, use BCM mode [OK]
- Using physical pin number with BCM mode
- Using BCM pin number with BOARD mode
- Mixing pin numbers without conversion
Ready to prove it?
Pass the test and this pattern moves unknown
