mirror of
https://git.k-space.ee/arti/vt1200.git
synced 2026-10-31 12:05:05 +02:00
arti
f1dc5e7f6e
Attempt 1 (16:58:45) came back: port 771 reopened at 88 s, the unit pinged, and a VRAM screenshot showed the Terminal Manager. Attempt 2 (17:04:15, after a power cycle) never came back -- no ping, no rdebug at 130 s, monitor asleep, operator reports it stuck. The previous commit recorded attempt 1 as "it works, no power cycle needed". That was a single sample and attempt 2 falsified it. Section 72.3 now records both runs as a table, the 1-of-2 rate, and the two corrections made on the way (first "hung", then "works"). Untested hypothesis: the reset path does not reset the LANCE, and the payload hands over with bus-master DMA enabled; an in-flight transfer or pending interrupt may leave the board-window handshake at 0xC00000B0/0xC0000100 waiting forever. The single-variable test would be CSR0_STOP before the jump. vtcmd.py reboot requires --force again and states the measured rate.