From 26e08a39f7d3c791c3fd3dea8288d9e17506c6f0 Mon Sep 17 00:00:00 2001 From: Cyd Date: Sun, 19 Jul 2026 20:48:22 -0500 Subject: [PATCH] Fix cross-links in imported RIO docs after the move Sibling links (hardware<->firmware) now resolve within restoration/; links to RIOjoy's PROTOCOL.md and Win32RIO/ (which stayed in the RIOjoy repo) point to gitea web URLs. --- restoration/rio-firmware/RIOv4_2-ANALYSIS.md | 2 +- restoration/rio-hardware/README.md | 10 +++++----- restoration/rio-hardware/display-board-1408.md | 6 +++--- restoration/rio-hardware/gal/README.md | 2 +- 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/restoration/rio-firmware/RIOv4_2-ANALYSIS.md b/restoration/rio-firmware/RIOv4_2-ANALYSIS.md index 4bc0404e..4c6ccb81 100644 --- a/restoration/rio-firmware/RIOv4_2-ANALYSIS.md +++ b/restoration/rio-firmware/RIOv4_2-ANALYSIS.md @@ -410,7 +410,7 @@ retired, preserved unmodified. Complete map of what the board does — and pointedly does not do — when things go wrong. Complements the wedge analysis above; display-side -detail in [`docs/hardware/display-board-1408.md`](../docs/hardware/display-board-1408.md). +detail in [`rio-hardware/display-board-1408.md`](../rio-hardware/display-board-1408.md). ### Host-facing (protocol) diff --git a/restoration/rio-hardware/README.md b/restoration/rio-hardware/README.md index 858b1843..5f0ff7e3 100644 --- a/restoration/rio-hardware/README.md +++ b/restoration/rio-hardware/README.md @@ -38,7 +38,7 @@ as a 20L8, fitted as a GAL20V8A-15LP** — decodes A[8:15] into `ROM_SEL*` header (`J4`–`J8`) carrying CHA/CHB from a HEDS-5700. The DB9 COM port goes through a MAX231/MAX232-class level shifter; the schematic's `IN_RESET*` from the serial side is the hardware behind the **DTR reset pulse** described in -[PROTOCOL.md](../PROTOCOL.md) §1. The "display interface" block (ALS541 +[PROTOCOL.md](https://gitea.mysticmachines.com/VWE/RIOJoy/src/branch/main/docs/PROTOCOL.md) §1. The "display interface" block (ALS541 buffers, HEADER14) exports latched data lines `HD[00:04]` + digit address `AS0-2` to the display board — this is a memory-mapped port, *not* the pod bus. A 22V10 site (U31) is drawn mostly N/C and is **unpopulated** on the @@ -79,7 +79,7 @@ Every pod board carries a 74HCT164 whose parallel outputs go to an pattern down the cable, the jumper picks which bit this board answers to, and 74LS00 gates qualify `RD_SB`/`WR_SB` with that selection. This hardware addressing is what the 0x00–0x6F logical input map in -[PROTOCOL.md](../PROTOCOL.md) ultimately resolves to. +[PROTOCOL.md](https://gitea.mysticmachines.com/VWE/RIOJoy/src/branch/main/docs/PROTOCOL.md) ultimately resolves to. ## Peripheral boards @@ -161,10 +161,10 @@ amplifier board 2026-07-19). ## Cross-references -- [`../PROTOCOL.md`](../PROTOCOL.md) — the 9600 8N1 wire protocol this +- [`docs/PROTOCOL.md` (RIOjoy)](https://gitea.mysticmachines.com/VWE/RIOJoy/src/branch/main/docs/PROTOCOL.md) — the 9600 8N1 wire protocol this hardware speaks; its DTR reset pulse and 0x00–0x6F input map both have their physical explanation above. -- [`../../rio-firmware/`](../../rio-firmware/) — v4.2 EPROM dump (from the +- [`../rio-firmware/`](../rio-firmware/) — v4.2 EPROM dump (from the AM27C512 at U10) and 68HC11 disassembly/patches. -- [`../Win32RIO/`](../Win32RIO/) — FASA's original Windows driver for the +- [`docs/Win32RIO/` (RIOjoy)](https://gitea.mysticmachines.com/VWE/RIOJoy/src/branch/main/docs/Win32RIO/) — FASA's original Windows driver for the same hardware. diff --git a/restoration/rio-hardware/display-board-1408.md b/restoration/rio-hardware/display-board-1408.md index db44d776..7d2b6e04 100644 --- a/restoration/rio-hardware/display-board-1408.md +++ b/restoration/rio-hardware/display-board-1408.md @@ -66,7 +66,7 @@ re-init (`$C64B`), then left alone. **Test mode** — entered by typing the keypad sequence **A, 9, E** on a cockpit keypad (`$C1CB` tracks the sequence at `$20F8`); entry sets flag `$2421`, shows `F1000000`, and notifies the PC (`TestModeChange`, cmd -`0x8C` — see [PROTOCOL.md](../PROTOCOL.md)). Within test mode the next +`0x8C` — see [PROTOCOL.md](https://gitea.mysticmachines.com/VWE/RIOJoy/src/branch/main/docs/PROTOCOL.md)). Within test mode the next keypad digit selects a sub-test; **F** ends a sub-test (back to `F1000000`), **D** exits test mode (back to `F0000000`). @@ -125,7 +125,7 @@ also the RIO's **error annunciator**: has been dropping or retrying. Note there is **no threshold in stock firmware** — the first event paints `E0000001` permanently; the **RIO 4.3** firmware (`make_patch.py --e0thresh`, see - [RIOv4_2-ANALYSIS.md](../../rio-firmware/RIOv4_2-ANALYSIS.md)) keeps + [RIOv4_2-ANALYSIS.md](../rio-firmware/RIOv4_2-ANALYSIS.md)) keeps the display quiet until a counter reaches 5, and repaints honestly after every check self-test. - **`dEAd` crash screen** (`$DAB8`, loop at `$DAB2`) — the TX-ISR ring @@ -142,7 +142,7 @@ also the RIO's **error annunciator**: - [README.md](README.md) — board family, photos, schematic page map - [gal/README.md](gal/README.md) — `DSP_SEL*` decode (`$A000-$A00F`, write-only) recovered from the GAL fuse map -- [`rio-firmware/RIOv4_2.disasm.asm`](../../rio-firmware/RIOv4_2.disasm.asm) +- [`rio-firmware/RIOv4_2.disasm.asm`](../rio-firmware/RIOv4_2.disasm.asm) — display routines `$CB20/$CB36/$CB49` (buffer render), `$CB7C` (`F0`), `$CBA7` (`F1`), `$CBD2`/`$CBFD` (lamp-test banners), `$CC28` (zeros), test dispatcher `$C241`, entry-sequence tracker `$C1CB` diff --git a/restoration/rio-hardware/gal/README.md b/restoration/rio-hardware/gal/README.md index 17f6e57e..e032392d 100644 --- a/restoration/rio-hardware/gal/README.md +++ b/restoration/rio-hardware/gal/README.md @@ -44,7 +44,7 @@ full machine output comes from `galdecode.py`, below.) `OE*` (`E & R/W`) is the shared read-side output enable for EPROM/SRAM/counters; the write-only decodes double as write strobes. -**Firmware cross-check** — [`RIOv4_2.disasm.asm`](../../../rio-firmware/RIOv4_2.disasm.asm) +**Firmware cross-check** — [`RIOv4_2.disasm.asm`](../../rio-firmware/RIOv4_2.disasm.asm) touches precisely these windows and nothing else in `$A0xx`: digit writes to `$A000-$A007`, pod-bus latch writes to `$A010`, and encoder reads at `$A021/$A023/$A025/$A027/$A029` + `$A028/$A030-$A038` (five chips × two count