[Simh] Making Ethernet DEC DELUA available to RSX11M+

Phil J FIsher phil.fisher at peejayeff.co.uk
Sun May 31 11:37:28 EDT 2020


All
Following Mark P's feedback and comments, this is in many respects a
re-submission of a previous poorly put together post.

My goal in all this is to make an Ethernet adapter on PDP11 under SimH
available to RSX11M+ V4.6 so that I can enable networking within that
environment.  I have not been able to do this so far despite following what
I believed to be correct approaches.

The following setup comes from running SIMH on a Win10 box directly using a
pre-built binary.

SIMH>
sim> show version
PDP-11 simulator V4.0-0 Current
    Simulator Framework Capabilities:
        32b data
        32b addresses
        Threaded Ethernet Packet transports:PCAP:NAT:UDP
        Idle/Throttling support is available
        Virtual Hard Disk (VHD) support
        RAW disk and CD/DVD ROM support
        Asynchronous I/O support (Lock free asynchronous event queue)
        Asynchronous Clock support
        FrontPanel API Version 12
    Host Platform:
        Compiler: Microsoft Visual C++ 15.00.30729.01
        Simulator Compiled as C arch: x86 (Release Build) on Mar 10 2020 at
00:42:02
        Build Tool: simh-Visual-Studio-Project
        Memory Access: Little Endian
        Memory Pointer Size: 32 bits
        Large File (>2GB) support
        SDL Video support: SDL Version 2.0.10, PNG Version 1.6.37, zlib:
1.2.11
        PCRE RegEx (Version 8.43 2019-02-23) support for EXPECT commands
        OS clock resolution: 1ms
        PDTime taken by msleep(1): 1ms
        Ethernet packet info: Unsupported - Npcap version 0.9991, based on
libpcap version 1.9.1
        Time taken by msleep(1): 1ms
        OS: Microsoft Windows [Version 10.0.18363.836]
        Architecture: x86 on AMD64, Processors: 4
        Processor Id: Intel64 Family 6 Model 142 Stepping 9, GenuineIntel,
Level: 6, Revision: 8e09
        git commit id: c30c88c2
        git commit time: 2020-03-10T00:18:19-07:00

CONFIG>
PDP-11 simulator configuration

CPU     11/70, FPP, RH70, autoconfiguration disabled, idle enabled
SYSTEM
RHA     address=17776700-17776753, vector=254, BR5
RHB     disabled
RHC     disabled
CLK     60Hz, address=17777546-17777547, vector=100, BR6
PCLK    disabled
PTR     address=17777550-17777553, vector=70, BR4
PTP     address=17777554-17777557, vector=74, BR4
TTI     address=17777560-17777563, vector=60, BR4
TTO     address=17777564-17777567, vector=64, BR4
TDC     disabled
CR      disabled
LPT     address=17777514-17777517, vector=200, BR4
DLI     disabled
DLO     disabled
DCI     disabled
DCO     disabled
DZ      address=17760100-17760107*, vector=300-304*, BR5, lines=8
VH      disabled
RC      disabled
RF      disabled
RK      address=17777400-17777417, vector=220, BR5, 8 units
RL      RL11, address=17774400-17774411, vector=160, BR5, 4 units
HK      disabled
RX      disabled
RY      disabled
RP      Massbus adapter 0 (RHA), 8 units
RS      disabled
RQ      disabled
RQB     disabled
RQC     disabled
RQD     disabled
TC      disabled
TM      disabled
TS      disabled
TQ      TU81 (180MB), address=17774500-17774503, no vector, BR5, 4 units
TU      disabled
TA      disabled
VT      disabled
XQ      disabled
XQB     disabled
XU      disabled
XUB     disabled
KG      disabled
DMC     disabled
DUP     disabled
DPV     disabled
KDP     disabled
KE      disabled
ROM     4 units
CH      disabled
NG      disabled
DAZ     disabled

NETWORK>
sim> sh eth
ETH devices:
 eth0   \Device\NPF_{0CAAD8E0-0523-432A-89C3-29377479808C} (VirtualBox
Host-Only Network)
 eth1   \Device\NPF_{A2D25F8C-319D-4D10-A2D1-F612E89065DC} (Local Area
Connection* 10)
 eth2   \Device\NPF_{EAE8073C-4368-41F5-9B70-77671D8038DE} (WiFi)
 eth3   \Device\NPF_{2CEDB723-3207-46CB-A136-081880A0C53A} (VMware Network
Adapter VMnet1)
 eth4   \Device\NPF_{87E9C4CC-4570-4792-840C-D13C7E5806B0} (Local Area
Connection* 2)
 eth5   \Device\NPF_{3290B149-A507-49C1-86EE-EB9D894D48A1} (Local Area
Connection* 8)
 eth6   \Device\NPF_{A5A812CA-928E-4EA9-8738-2E125D177FF3} (Local Area
Connection* 3)
 eth7   \Device\NPF_{E4948FE0-C106-4D09-9310-EB0B72477D28} (VMware Network
Adapter VMnet8)
 eth8   \Device\NPF_{21E275FA-748D-414E-942D-E86C23FF7260} (Local Area
Connection* 9)
 eth9   \Device\NPF_{438585F9-46EB-4060-8674-0029AE4FAEE1} (Ethernet)
 eth10  nat:{optional-nat-parameters}                      (Integrated NAT
(SLiRP) support)
 eth11  udp:sourceport:remotehost:remoteport               (Integrated UDP
bridge support)

MANUAL CONFIG DELUA>
sim> set XU enable
sim> set XU autoconfigure
sim> set XU type=DELUA
sim> sh xu
XU      no vector, BR5, MAC=08:00:2B:03:FE:68, type=DELUA
        throttle=disabled
        not attached
sim>

Now I have deliberately not attached the XU device;  I just want to make
sure it is picked up by RSX11M+.  I believe it should do so even if it then
fails to do anything sensible.  I get identical results when attached to a
network (for details of attach, see later).

When booted (via RL0), RSX11M+ fires up as expected.  When I try to enable
the network via NETINS.CMD, I see that it is not able to "install" the UNA-0
network device.  

NTL -- Config File -- Device UNA-0 Offline
        CNT$DF  0,120,174510,5,,NX
NTINIT -- Failed To Load Line UNA-0

Inspecting the RSX11M+ config shows:

RSX>
>con dis attr
SYS
                PDP-11/70, EIS,UNIBUS_Map,D-Space,SWR,Cache,FPP,
                Clock=KW11-L, $TKPS=60., $TTPRM=000002, Cache_control=000001
LAA
                Csr=170460, Vector=000340, Pri=000005, Urm=000001
YLA
                Csr=177560, Vector=000060, Pri=000005, Urm=000001
DLA
                Csr=174400, Vector=000160, Pri=000005, Urm=000001
DUA
                Csr=172150, Vector=000154, Pri=000005, Urm=000001
LPA
                Csr=177514, Vector=000200, Pri=000004, Urm=000001
MUA
                Csr=174500, Vector=000260, Pri=000005, Urm=000001
YZA
                Csr=160100, Vector=000300, Pri=000005, Urm=000001
VF0:    ,Type=
VF1:    ,Type=
LA0:    LAA0:
CO0:
TT0:    YLA0:
TT1:    YZA0:
TT2:    YZA1:
TT3:    YZA2:
TT4:    YZA3:
TT5:    YZA4:
TT6:    YZA5:
TT7:    YZA6:
TT10:   YZA7:
VT0:
DL0:    DLA0:,Type=RL02
DL1:    DLA1:,Type=RL02
DL2:    DLA2:,Type=RL02
DL3:    DLA3:,Type=RL02
NL0:
DU0:    DUA0:
DU1:    DUA1:
DU2:    DUA2:
DU3:    DUA3:
LP0:    LPA0:
MU0:    MUA0:,Type=TU81
NN0:
NM0:
HT0:
HT1:
HT2:
HT3:
RT0:
RT1:
RT2:
RT3:

This seems to show that the device is not being seen by RSX11M+ at all since
there is no device information.

I also retried this having attached a network to the device XU0:

ETH-ATTACHED>
sim> attach xu0 eth2
Eth: opened OS device \Device\NPF_{EAE8073C-4368-41F5-9B70-77671D8038DE} -
WiFi
sim> sho xu0
XU0     attached to eth2

This gave exactly as far as I can tell the same results on booting RSX11M+
and running the NETINS command script.

If I am given guidance I can provide more information from SimH or from
RSX11M+.

I hope on this occasion I have provided the correct type of submission.


-- 
Phil J Fisher         phil.fisher at peejayeff.co.uk
Mobile:   +44 7984 781 929 (please leave message if busy or N/A)
Director, PeeJayEff Services Ltd
IT Consultancy and Technical Training in UNIXes/Linux
http://www.peejayeff.co.uk/

Email and any attachments sent are scanned by McAfee
Anti-Virus but integrity cannot be guaranteed.
_____________________________________________________




More information about the Simh mailing list