vwemirror/riojoy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Move RIO hardware + firmware archive to the TeslaRel410 repo

Browse Source 
The physical RIO board docs (photos, schematics, GAL decode) and the
board firmware (dumps, disassembly, make_patch.py, RIO 4.3 + FastRIO
images, analysis, testlogs) describe hardware shared across all Tesla
cockpits with a lifecycle independent of this Windows app — a
native-game-only cabinet runs the firmware and never touches RIOjoy.
They now live in TeslaRel410/restoration/{rio-hardware,rio-firmware}
with full history preserved (git subtree).

Kept here: docs/PROTOCOL.md (this app's interface contract) and the
RioSerialMonitor bench harness (--mash/--e0test, C# on RioJoy.Core).
README + code comments now point at the TeslaRel410 archive.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Cyd
2026-07-19 20:50:46 -05:00
co-authored by Claude Fable 5
parent adfcee4bac
commit 30c1a85445
64 changed files with 10 additions and 133660 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tools/RioSerialMonitor/E0Test.cs
+1 -1
View File
@@ -4,7 +4,7 @@ using RioJoy.Core.Serial;
namespace RioSerialMonitor;
/// <summary>
/// E0-threshold firmware verification (rio-firmware `--e0thresh` images).
/// E0-threshold firmware verification (TeslaRel410 restoration/rio-firmware `--e0thresh` images).
///
/// Two phases against a DTR-reset board (counters zeroed, display F0000000):
/// - Phase A (gate hold): analog requests answered NAK-then-ACK — NAKing
tools/RioSerialMonitor/MashTest.cs
+2 -2
View File
@@ -7,8 +7,8 @@ namespace RioSerialMonitor;
/// <summary>
/// Instrumented firmware mash test (the RIO_TAP protocol, mechanized) for
/// validating the RIOv4.2 reply-latch wedge patch — see
/// rio-firmware/RIOv4_2-ANALYSIS.md "Validation plan".
/// validating the RIOv4.2 reply-latch wedge patch — see the firmware
/// analysis in the TeslaRel410 repo (restoration/rio-firmware/RIOv4_2-ANALYSIS.md).
///
/// Runs the live link with the app's own &gt;5s reset-recovery DISABLED (so a
/// board wedge stays observable instead of being revived by our watchdog),
tools/RioSerialMonitor/Program.cs
+2 -2
View File
@@ -12,10 +12,10 @@ using RioJoy.Core.Serial;
// Firmware wedge-patch validation (RIO_TAP mash test, see MashTest.cs):
// dotnet run --project tools/RioSerialMonitor -- --mash [port] [seconds]
// [--label baseline|patched] [--no-lamps] [--wedge seconds] [--baud rate]
// --baud: 31250 for the retuned firmware variant (rio-firmware --baud31250).
// --baud: 31250 for the retuned FastRIO firmware (TeslaRel410 restoration/rio-firmware, make_patch.py --baud31250).
// Exit: 0 = ran, 2 = could not open the port (mash: 1 = wedge detected).
// E0-threshold firmware verification (rio-firmware --e0thresh images, see E0Test.cs):
// E0-threshold firmware verification (TeslaRel410 restoration/rio-firmware --e0thresh images, see E0Test.cs):
// dotnet run --project tools/RioSerialMonitor -- --e0test [port] [--baud rate] [--events n]
if (args.Contains("--e0test"))
return await RioSerialMonitor.E0Test.RunAsync(args);