RF_HandleEdgeInterrupt()'s software ping-pong toggle can leave P3IM0
parked in either edge direction while awake; Enter_Low_Power_Sleep()
never reset it, so sleep entry could randomly land on a direction that
misses the wake edge. Per the datasheet truth table (WO-04 2.9), only
edge modes support power-down wake, not level modes, so this forces a
known rising-edge state (matching RF_Init()'s own boot default) instead
of switching to level-triggered as originally requested. wo-05 updated
to record the deviation and rationale.
Confirms clock_app is the boot-default app (main.c:280) and should be
renamed home_app; time editing becomes its own set_clock_app instead
of time_set_app. Drops all remaining menu_level wording, and
cross-references items 1/2 to the renamed APP_ID_HOME/home_app.
Replace the ad-hoc menu_level state machine plan with a uniform
App-per-screen model (home_app/menu_app/time_set_app/pair_app/
ipc_bind_app), each child App exiting to its own parent via long-press
CONFIRM. Folds the sensor-type selection screen into pair_app as a new
initial state, and updates item 5's cyclic-navigation notes to match.
Lists boot-flicker backlight timing, menu idle auto-close, submenu
long-press-confirm exit, default language, cyclic menu navigation, and
P3.6 sleep-wake trigger reliability, each with a brief implementation
approach based on current code.
Multiple real transmissions (Data=08/04/02/01) decoded correctly and
stably with the ping-pong single-edge trigger fix, no interrupt storm
or crash observed. Closes out the phase-2 RF decode root-cause saga.
Root cause found via datasheet: PxIM0/PxIM1 has no dual-edge mode, only
falling/rising/low-level/high-level. (IM1=1,IM0=1) was actually
high-level interrupt, refiring continuously for the whole high-pulse
duration (confirmed by scope: no real HF noise, and edge_count=0 when
P3.6 grounded). Fix: start in rising-edge mode, software-toggle to the
opposite edge on every trigger (ping-pong) to emulate true dual-edge
triggering, feeding exact edge direction into the incremental decode
state machine (no glitch filter needed). Also switch P3.6 idle bias
from pull-up to pull-down, since floating-high under the old high-level
mode caused the interrupt-storm boot issue; removed the now-conflicting
pull-up restore in Wakeup_Restore().
Diagnostic experiment: restore the commit d8df5d4 polling decode
algorithm/thresholds unchanged, while P3.6 ISR now only increments an
edge counter (no decode state machine). Successful decodes print the
edge-count delta over the decode window to compare against the
EV1527 theoretical 50-edges-per-frame, to validate/refute the
edge-interrupt glitch-noise hypothesis.
