arti/vt1200
1
0 Fork 1
mirror of https://git.k-space.ee/arti/vt1200.git synced 2026-10-31 12:05:05 +02:00
Code Wiki Activity

NETWORK_REPORT: osboot works on the unit -- 40 s, Terminal Manager back

Browse Source 
osboot at 17:11:21, rdebug back at 17:12:01 (40 s), ping OK, and the VRAM
screenshot shows the Terminal Manager with a live display, the right MAC/IP/
LAT name and the clean-boot banner.

Same machine, same payload as the two failed reset-vector attempts: reboot
0/2 (POST, never returns), osboot 1/1 (OS cold start, 40 s).  The display
returns before the network -- the operator could see the screen at 32 s while
port 771 was still closed.

Recorded as 1 of 1, not as reliable: section 72.3 already lists three
conclusions drawn from single observations, so a second run is needed before
this is the standard hand-back.
This commit is contained in:
arti committed 2026-10-30 17:12:41 +02:00
1 parent baffb8292e
commit f74bd7ae05
1 file changed
+31 -2
Download Patch File Download Diff File Expand all files Collapse all files
harness/mame/NETWORK_REPORT.md
+31 -2
View File
@@ -4827,6 +4827,35 @@ t=11.828960 W RDP val=0004 pc=3FDDCAE0 <- OS driver (io5800_5900_init)
and the OS keeps servicing the chip afterwards (`pc=3F9D*`, 134 accesses in the
window). So the cold start restores the LANCE and the OS continues.
### 73.2 Real unit
### 73.2 Real unit: works, 40 s (1 of 1)
Result recorded in 73.3 once the unit run completes.
`osboot` issued at **17:11:21** while the payload owned the LANCE:
```
osboot: control -> bit 0x3f5788c0, status 0
rdebug back after 40s at 17:12:01
pings
```
A VRAM screenshot (`dwt/screenshot.py --real`) at that point shows the Terminal
Manager fully operating — `08-00-2B-16-4B-5A`, `100.103.100.103`,
`LAT_08002B164B5A`, 4 MB free, the clean-boot `Ethernet Port Error - 24` banner
and the boot messages (`Attempting to set font path. / Using local fonts.`) in
the Messages pane.
Compare with `reboot` (section 72.3), same machine, same payload:
| command | entry | display | port 771 | ping |
|---|---|---|---|---|
| `reboot` | `0x3F200040` (POST) | never returns | never (0/2) | no |
| `osboot` | `0x3F5788C0` (OS cold start) | back, TM live | **40 s** | yes |
Also observed: the display comes back **before** the network. At 32 s the
operator could see the screen while `:771` was still closed; the interface comes
up later in the OS boot.
**This is 1 of 1.** It is the vendor's own entry, it does exactly what a payload
breaks (STOP the LANCE, re-program the board window), and it worked first time —
but this section has already recorded three conclusions drawn from single
observations, so the status is "one confirmed success", not "reliable". A second
run is needed before it is treated as the standard hand-back.