You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The non-QEMU boot-passphrase keypad path directly configures and scans GPIO using placeholder row/column pins and a generic MT67xx register layout. The source itself says the AGM M7 assignments are unverified, but boot can execute those MMIO writes before any hardware qualification. #753 owns later service-loop reachability, not the board pin/register contract.
Evidence
crates/thumos/src/board/m7.rs sets row pins 40-43 and columns 44-46 as placeholders copied from the unlinked haphe surface.
GPIO_BASE and direction/data/pull bank offsets are generic-family assumptions pending MT6739 grounding.
crates/thumos/src/keypad.rs writes those direction/output/pull registers and polls inputs in the non-QEMU boot path.
Host tests inject matrix state and therefore cannot validate pins, mux mode, bank stride, pull semantics, polarity, electrical settle timing, or conflicts.
Why this matters
Wrong GPIO/pinmux writes can alter unrelated board functions or make the boot credential gate unusable. This is source-adjudication/software work before an M7 session, not a fact that a physical smoke test should discover by executing placeholder writes.
Finding
The non-QEMU boot-passphrase keypad path directly configures and scans GPIO using placeholder row/column pins and a generic MT67xx register layout. The source itself says the AGM M7 assignments are unverified, but boot can execute those MMIO writes before any hardware qualification. #753 owns later service-loop reachability, not the board pin/register contract.
Evidence
crates/thumos/src/board/m7.rssets row pins 40-43 and columns 44-46 as placeholders copied from the unlinked haphe surface.GPIO_BASEand direction/data/pull bank offsets are generic-family assumptions pending MT6739 grounding.crates/thumos/src/keypad.rswrites those direction/output/pull registers and polls inputs in the non-QEMU boot path.Why this matters
Wrong GPIO/pinmux writes can alter unrelated board functions or make the boot credential gate unusable. This is source-adjudication/software work before an M7 session, not a fact that a physical smoke test should discover by executing placeholder writes.
Done when