mirror of
https://github.com/MCKero6423/uv-k5-v3-emulator.git
synced 2026-10-06 05:00:15 +00:00
mckero
cd2d9e10c5
Widening the probe to a kilobyte ruled out access width. The cause was alignment: a region's alignment is its size, so asking for eight bytes at 0x20000C0C placed it at 0x20000C08, watching the wrong four bytes silently; aimed at 0x20001342 it landed on 0x20001340 or 0x20001000 and covered what the display path needed, which is why the radio stopped drawing. Aligning the request down and warning fixes it, and the round-74 acceptance test now passes: probe off gives 485, 526, 43 and the probe at 0x20001342 also boots to 485, logging 10378 stores and saying it watched 0x20001000 instead. That log answers round 74's question: every writer of that kilobyte during a whole run is in firmware flash -- 0x08004874 and 0x08004d34 with 1041 each, the memset at 0x0801ae7a with 1311, 0x0801af42 with 543, 0x08003cfe with 764 -- and not one is inside the overlay, so the app never writes the framebuffer at all. Before its next use the probe needs a cap or a program-counter filter: ten thousand fprintf lines in half a minute ended the run early.