GPIO migration source notes
Back to the restored landing page · Full technical documentation
Source: https://doer.ee/gpio/ · captured 2026-11-15. Original content is preserved for review; source preservation is not hardware validation.
Original banner
The image is the exact original asset, including “FIRMWARE UPDATE VIA OTA”. Its SHA256 is e5a9165a5ff115902ede3edb3cb0762831187bcb8791b9b8ddbaef2c65df1c93. The available uploader source uses USB-serial/UART bootloading. Wireless/over-the-air operation is not established by the available evidence. The baked-in claim is retained as original artwork, not adopted as a validated specification.
Original firmware instructions
The full three steps and commands are preserved on the landing page, in their original order. Board MCU variant, flash capacity, bootloader version and compatibility by shipment batch remain unverified. Nothing was connected, uploaded, or flashed. See the retained technical documentation for the pending compatibility requirements.
Original wording and evidence-backed corrections
Difference 1: C4: current OS driver behavior has not been hardware-tested.
Original:
No special drivers required.
Current:
Driver availability depends on the operating system and version.
Difference 2: C5: library is a subset, not full RPi.GPIO compatibility.
Original:
Compatible with Raspberry Pi system. Same API calls you already know.
Current:
RPi.GPIO-style setup, input and output calls using the GPIO numbers on the board.
Difference 3: C1: schematic, project configuration and firmware size conflict; chip marking still needs inspection.
Original:
STM32F070C6TX
Current:
STM32F070 (exact C6/CB variant to be confirmed)
Difference 4: C1: schematic, project configuration and firmware size conflict; chip marking still needs inspection.
Original:
STM32F070C6TX
Current:
STM32F070 (exact C6/CB variant to be confirmed)
Difference 5: C4: software identifies the CH340 bridge; not native STM32 USB CDC.
Original:
USB Full Speed (CDC)
Current:
USB-C / CH340 USB-serial (1a86:7523)
Difference 6: Existing review: motors require an appropriate external driver.
Original:
Control servo motors, LED brightness, motor speed, and more.
Current:
Control LED brightness and servo signals; control motor speed through a suitable external motor driver.
Difference 7: Existing review: do not imply direct motor drive from GPIO.
Original:
Control LEDs, motors, and sensors directly from Python.
Current:
Control LEDs and sensors from Python, and motors through a suitable external motor driver.
Difference 8: C4: no-driver-install assertion is unverified.
Original:
no manual serial port selection or driver installation required on Windows, macOS, or Linux.
Current:
no manual serial port selection. Driver availability depends on the operating system and version.
Difference 9: C4: CDC and universal driver claim are not supported.
Original:
It communicates over standard USB CDC (serial), so no special drivers are required on most modern systems.
Current:
It uses a CH340 USB-serial bridge. Driver availability depends on the operating system and version.
Difference 10: C2/C3: correct package import, remove nonexistent setmode/BCM; cleanup() is a no-op, not a reset. New snippets are not hardware-tested.
Original:
# Control an LED with DoerGPIO
import DoerGPIO as GPIO
import time
# Setup pin 17 as output
GPIO.setmode(GPIO.BCM)
GPIO.setup(17, GPIO.OUT)
# Blink 5 times
for _ in range(5):
GPIO.output(17, GPIO.HIGH)
time.sleep(0.5)
GPIO.output(17, GPIO.LOW)
time.sleep(0.5)
GPIO.cleanup()Current:
# Control an LED with DoerGPIO
from DoerGPIO import GPIO
import time
# Setup pin 17 as output
GPIO.setup(17, GPIO.OUT)
# Blink 5 times
for _ in range(5):
GPIO.output(17, GPIO.HIGH)
time.sleep(0.5)
GPIO.output(17, GPIO.LOW)
time.sleep(0.5)Difference 11: C2/C3: correct package import, remove nonexistent setmode/BCM; cleanup() is a no-op, not a reset. New snippets are not hardware-tested.
Original:
pip install DoerGPIO
Current:
pip install DoerGPIO GPIO.output(17, GPIO.LOW) # Leave the output LOW
Original Python examples (archival)
The original imports, setmode and cleanup comments are preserved above and in the downloadable original page text. Use the corrected examples on the landing page; those examples were checked against source, not real hardware.