mirror of
https://git.k-space.ee/arti/vt1200.git
synced 2026-10-31 12:05:05 +02:00
arti
504d63a705
The operator confirms attempt 1's recovery at 88 s was a manual power cycle, not the payload. That makes the record 0 confirmed successes out of 2, and the first reading of attempt 1 -- "black and hung, needs a power cycle" -- was right after all. Three corrections are now recorded in section 72.3, because they are one mistake made three times: "hung" from a single sample, then "works" from the same sample after it recovered, then "works" again when that recovery was attributed to the payload. The recovery had an external cause, which one observation cannot tell apart from the payload working. The Ghidra finding stands: the firmware has no software reboot, so there is no supported entry to jump to. Untested hypothesis for the hang remains that the reset path leaves the LANCE busy-mastering; CSR0_STOP before the jump would be the single-variable test. vtcmd.py reboot requires --force and now says plainly that it has never worked and that a power cycle should be expected.