mirror of
https://git.k-space.ee/arti/vt1200.git
synced 2026-11-01 12:14:56 +02:00
arti
eabc3051be
A new folder so the demo can be reproduced instead of re-derived: the delivery
and the clip packing were living in throwaway scripts under /tmp, and the only
written route to a real clip was an ffmpeg recipe that packs MSB first -- the
order that mirrors every eight pixels on a display.
harness/badapple/rdebug_load.py image -> terminal RAM over the firmware's
own remote-debug service (TCP 771), then
jump to the entry from vidstream.env
harness/badapple/clip_from_video.py video -> LSB-first 1-bpp frames for
make_tiles.py --clip
harness/badapple/demo.sh ICMP gate, load, send; one command
harness/badapple/README.md setup, run in MAME, run on real hardware,
what success looks like, failure modes
The loader records the two protocol facts that cost time to find: a 512-byte
poke chunk (1024 is mis-parsed as a following opcode: "Invalid command
0xA5A5A5A5"), and that nothing can be probed after the jump, so the image is
read back BEFORE jumping and the run is observed from the machine afterwards.
Tests cover what a wrong assumption would silently corrupt -- chunk arithmetic,
the linkage the entry point is read from, and pixel 0 landing on bit 0 -- and
the tool was exercised end to end against MAME: demo.sh loaded the payload and
the terminal reported DICT_BYTES=32768, DICT_BAD=0, RX_OK=28, TILES_DROP=0
while the sender saw frames_rx=129, drops=0.
153 tests pass (7 new).
11 lines
542 B
Python
11 lines
542 B
Python
"""The Bad Apple demo: build a clip cache, deliver the payload, play it.
|
|
|
|
``harness/badapple/README.md`` is the setup and run guide. The three pieces:
|
|
|
|
* ``clip_from_video.py`` a video file -> raw 1-bpp frames in the terminal's
|
|
bit order, the input ``make_tiles.py --clip`` wants;
|
|
* ``rdebug_load.py`` the payload image into a running terminal over the
|
|
firmware's own remote-debug service (TCP 771);
|
|
* ``demo.sh`` one command: wait for the OS, load, send the frames.
|
|
"""
|