mirror of
https://github.com/MCKero6423/uv-k5-v3-emulator.git
synced 2026-10-08 13:47:24 +00:00
mckero
33e2d7f38e
Raise the panel probe cap (40000 transfers is reached about forty seconds after boot) and rebuild qemu-system-arm, then run the toggling app on a hand-copy: after F, 7, DOWN, MENU the probe grew from 22568 to 139404 lines, 114028 of them pixel data, with the longest run of byte 00 at 108273 transfers -- about 105 full-screen writes in a row, histogram 111061 zeros against a longest 0xFF run of 68. A hundred consecutive full-screen fills is a loop, not a launcher repainting once: the app runs and blits, which retires the conclusion carried since round 32 that an app's calls do nothing. What hid it was the cap -- the instrument went blind forty seconds after boot and the blindness was read as an app that never acted; the third time this file records capping a diagnostic before knowing the shape of the data, and the first where the cap was inside the model. Next: the 0xFF phase never appears. An app that fills 0xFF only, with no zeros at all, separates 'it never gets there' from 'the firmware repaints over it' in one run.