diff --git a/dwt/evidence/real-unit-romtest-result.png b/dwt/evidence/real-unit-romtest-result.png
new file mode 100644
index 0000000..dd3d4f6
Binary files /dev/null and b/dwt/evidence/real-unit-romtest-result.png differ
diff --git a/dwt/notes/REAL_UNIT.md b/dwt/notes/REAL_UNIT.md
index 101ff86..bf180c3 100644
--- a/dwt/notes/REAL_UNIT.md
+++ b/dwt/notes/REAL_UNIT.md
@@ -229,3 +229,25 @@ During the boot it was unusable (timeouts / AssertionError). So the level-1
 result is consumed before rdebug exists; the mailbox is a dialog/debug
 structure, not the boot handoff. The only durable record is the **screen**:
 the boot alert, and the Diagnostics dialog's on-screen results.
+
+### Menu-driven Ethernet Address ROM test: PASS
+
+After a clean power cycle, selecting **Ethernet Address ROM Test** in the
+Diagnostics dialog completed, the dialog closed, and the Terminal Manager's
+bottom notification reads:
+
+```
+All Diagnostics Passed
+```
+
+Evidence: `dwt/evidence/real-unit-romtest-result.png`.
+
+This is the ROM checksum test (service-guide error **23** would be the
+failure), and it **passes** on the real unit, consistent with MAME. The
+boot-level `Ethernet Port Error - 24` is the separate AUI/transceiver
+termination test, not the ROM.
+
+The first attempt hung the Terminal Manager; this one completed. The hang is
+not deterministic. The mailbox watcher's reconnect storm during boot is one
+possible co-factor (it spawns a debug process per accepted connection), but the
+diagnostic reset is the other; a single success does not settle which.