Skip to content

docs: correct the haptic motor pin — display GPIO 35, not 46 - #25

Open
JimStenstrom wants to merge 1 commit into
freewili:masterfrom
JimStenstrom:fix/hardware-pinout-haptic-motor
Open

JimStenstrom wants to merge 1 commit into
freewili:masterfrom
JimStenstrom:fix/hardware-pinout-haptic-motor

Conversation

@JimStenstrom

Copy link
Copy Markdown

Summary

One-line fix to the haptic row in docs/hardware/pinmap.md: the motor is on the display CPU's GPIO 35, not GPIO 46 as FwDisplayVibe.md states.

Why

Bench-verified on a production FreeWili 2 (stock firmware v07) through the built-in debug probe: neither CPU ever configures GPIO 46 — both sit at power-on reset even while stock touch feedback is buzzing the motor, and driving that pin directly does nothing — while driving display GPIO 35 actuates the motor in exact sync. Stock firmware drives it with PWM at 180 Hz / 50 % duty (slice 9 ch B; sysclk measured at 240 MHz). Happy to share the full register-level notes if useful.

Testing

Docs-only, one-line table fix. tests/test_no_private_refs.py passes; git diff --check clean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant