mirror of
https://github.com/RetroPortingToolKit/psxrecomp
synced 2026-10-27 10:38:46 -04:00
Matthew Stanley
8a694af69c
Per global rule: use ring buffers, never time/attach. Add static always-on wtrace coverage at boot for the addresses that determine card-chain progress, so we can answer "when was X written?" by querying the ring instead of racing live samples. Newly always-watched (range 5..9, total ranges 7→10, MAX 8→16): - 0x7514..18: chain counter (shared by detection + read chains) - 0x7528..30: per-slot chain handler ptr (=0x5688 read, =0x5B64 detect) - 0x755A: chain abort flag (D1/state-1 set, outer coord checks) - 0x7520: read-chain success flag (state-3 sets, cascade reads) - 0x74A4: chain status flag This let us deterministically prove (without racing samples) that: - read chain DOES get installed at 0x7528 briefly on press X (seq 12754) - counter DOES advance 0→11 successfully during read-chain runs - but resets at counter=11 via func_00005000's BFC14B90 abort path - reset triggers because state-1 set 0x755A=1 and chain never reaches state-13 to clear it Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>