I'm trying to get my head around VAXELN and system time.
Before I cry "Wolf" and accuse any innocent program(mer) of instruction
obstruction, I want to know how things are supposed to work here (i.e.
as on a real rtVAX with VAXELN)
I have built a VAXELN system image and can download this into the simh
rtVAX. Whatever simh setting I use, the VAXELN system clock always
starts at 0, starting time after boot on 17-NOV-1858. I can set the time
manually, but it is not preserved across boot. Should it be?
simh ini file:
echo rtVAX-1000
set CPU diag=MIN 16M idle=ELN conhalt autoboot
set WTC time=STD
set DZ disable
set LPT disable
set RL disable
set TS disable
set TQ disable
att -e NVR /opt/ka620.nvr
set RQ0 rd54
att -e RQ0 /vdisk/VAXELN.vdisk
set XQ type=DEQNA mac=08:00:2B:13:01:92
att XQ TAP:tap0
set DEBUG /opt/ka620.debug
set WTC DEBUG
boot
contents of ka620.debug after booting and shutdown (well, no shutdown on
ELN, so ctrl/E)
/opt/rtvax1000.ini-20> set DEBUG /opt/ka620.debug
Debug output to "/opt/ka620.debug"
Debug output to "/opt/ka620.debug" at Sat Dec 15 11:57:42 2018
rtVAX1000 (KA620) simulator V4.0-0 Current git commit id: c2b45a26
/opt/rtvax1000.ini-23> boot
Loading boot code from internal ka620.bin
DBG(146257)> WTC REG: wtc_rd(pa=0x200B801A [CSRD], data=0x80) VALID1
Simulation stopped, PC: 800066EA (TSTL 80000900)
sim> quit
Goodbye
NVR: writing buffer to file
Eth: closed tap0
contents of ka620.nvr:
pi@raspi2-old ~ $ hexdump /opt/ka620.nvr
0000000 0000 0000 0000 0000 0000 0000 0000 0220
0000010 0000 fe00 00ff 0000 0000 0000 0000 fe00
0000020 00ff fe00 00ff 4548 5041 0000 0000 0000
0000030 0000 0000 0000 0000 0000 0000 0000 0000
0000040
_______________________________________________
Simh mailing list
[email protected]
http://mailman.trailing-edge.com/mailman/listinfo/simh
