1 |
22 |
wfjm |
# $Id: w11a_os_guide.txt 547 2013-12-29 13:10:07Z mueller $
|
2 |
4 |
wfjm |
|
3 |
5 |
wfjm |
Guide to run operating system images on w11a systems
|
4 |
|
|
|
5 |
|
|
Table of content:
|
6 |
|
|
|
7 |
21 |
wfjm |
1. I/O emulation setup
|
8 |
|
|
2. FPGA Board setup
|
9 |
|
|
3. Rlink and Backend Server setup
|
10 |
|
|
4. simh simulator setup
|
11 |
|
|
5. oskits
|
12 |
|
|
a. Unix systems
|
13 |
|
|
b. DEC operating systems
|
14 |
5 |
wfjm |
|
15 |
4 |
wfjm |
1. I/O emulation setup ----------------------------------------------------
|
16 |
|
|
|
17 |
|
|
All UNIBUS peripherals which exchange data (currently DL11, LP11, PC11, RK11)
|
18 |
20 |
wfjm |
are currently emulated via a backend process. The communication between
|
19 |
|
|
FPGA board and backend server can be via
|
20 |
4 |
wfjm |
|
21 |
21 |
wfjm |
- Direct USB connection using a Cypress FX2 USB controller
|
22 |
|
|
- is supported on the nexys2 and nexys3 FPGA boards
|
23 |
|
|
- much faster than serial port connections (see below)
|
24 |
|
|
- also allows to configure the FPGA over the same USB connection
|
25 |
|
|
|
26 |
20 |
wfjm |
- Serial port
|
27 |
|
|
- via direct (/dev/ttySx) or via a USB-RS232 adapter. A direct connection
|
28 |
|
|
is limited to 115k Baud on most PCs, while a connection via a USB-RS232
|
29 |
|
|
adapter was tested up to 460k Baud. A USB-RS232 adapter is thus highly
|
30 |
|
|
recommended
|
31 |
|
|
- via integrated USB-RS232 adapter, like on nexys3 board. This is much
|
32 |
|
|
faster, allows bitrates up to 2 M Baud.
|
33 |
|
|
|
34 |
21 |
wfjm |
Notes: - A USB-RS232 cable with a FTDI FT232R chip, like the cable offered
|
35 |
|
|
by FTDI as US232R-100 works fine.
|
36 |
|
|
- A USB-RS232 cable with a Prolific Technology PL2303 chip simply
|
37 |
20 |
wfjm |
never gave reliable connections for higher Baud rates.
|
38 |
|
|
- The rest assumes that a USB-RS232 cable with FTDI chip is used
|
39 |
|
|
- A 460k Baud connection gives in practice a disk throughput of
|
40 |
|
|
about 20 kB/s. This allows to test the system but is a bit slow
|
41 |
|
|
to real usage. In an OS with good disk caching like 2.11BSD the
|
42 |
|
|
impact of such a 'slow disk' is actually smaller than the bare
|
43 |
|
|
numbers suggest.
|
44 |
21 |
wfjm |
- On older linux kernels (prior 2.6.32) it is essential to set the
|
45 |
|
|
latency timer for the FTDI USB-RS232 cable to 1 ms (from the
|
46 |
|
|
power up default of 16 ms), e.g. with
|
47 |
|
|
sudo $RETROBASE/tools/bin/set_ftdi_lat USB0 1
|
48 |
|
|
For linux kernel 2.6.32 or newer the default is 1 ms already.
|
49 |
4 |
wfjm |
|
50 |
|
|
2. FPGA Board setup -------------------------------------------------------
|
51 |
|
|
|
52 |
21 |
wfjm |
- Using Cypress FX2 USB controller for configuration and rlink communication
|
53 |
|
|
- for nexys2
|
54 |
|
|
- connect USB cable to mini-USB connector (between RS232 and PS/2 port)
|
55 |
|
|
- for nexys3
|
56 |
|
|
- connect USB cable to micro-USB connector labeled 'USB PROG'
|
57 |
|
|
|
58 |
|
|
- Using serial port for rlink communication
|
59 |
20 |
wfjm |
- for s3board and nexys2
|
60 |
21 |
wfjm |
- connect the USB-RS232 cable to the RS232 port
|
61 |
20 |
wfjm |
- for nexys3
|
62 |
21 |
wfjm |
- connect USB cable to the micro-USB connector 'UART'
|
63 |
|
|
(next to the 5 buttons)
|
64 |
|
|
- connect a JTAG programmer (e.g. Xilinx USB Cable II) to JTAG pins
|
65 |
4 |
wfjm |
|
66 |
21 |
wfjm |
- Configure the FPGA
|
67 |
|
|
- if Cypress FX2 port is connected load design with
|
68 |
|
|
make .jconfig
|
69 |
|
|
- otherwise use impact with
|
70 |
|
|
make .iconfig
|
71 |
15 |
wfjm |
|
72 |
21 |
wfjm |
3. Rlink and Backend Server setup -----------------------------------------
|
73 |
4 |
wfjm |
|
74 |
21 |
wfjm |
All examples below use the same basic setup
|
75 |
4 |
wfjm |
|
76 |
21 |
wfjm |
- setup vt100 emulator windows
|
77 |
4 |
wfjm |
|
78 |
21 |
wfjm |
cd $RETROBASE/tools/oskit/
|
79 |
4 |
wfjm |
telnet_starter -d DL0 &
|
80 |
21 |
wfjm |
telnet_starter -d DL1 &
|
81 |
20 |
wfjm |
|
82 |
21 |
wfjm |
- setup rlink connection using ti_rri backend server via the ti_w11
|
83 |
|
|
quick start wrapper script. Ensure that all 8 switches on the board
|
84 |
|
|
are in the indicated positions (SWI=...). The concrete boot script
|
85 |
|
|
name is given in the following sections
|
86 |
4 |
wfjm |
|
87 |
21 |
wfjm |
[for n2,n3 over fx2:]
|
88 |
|
|
SWI = 00000100
|
89 |
|
|
ti_w11 -u @_boot.tcl
|
90 |
20 |
wfjm |
|
91 |
|
|
[for s3,n2 over serial:]
|
92 |
|
|
SWI = 00000010
|
93 |
21 |
wfjm |
ti_w11 -tu0,460k,break,xon @_boot.tcl
|
94 |
20 |
wfjm |
[for n3 over serial:]
|
95 |
|
|
SWI = 00000010
|
96 |
21 |
wfjm |
ti_w11 -tu0,2M,break,xon @_boot.tcl
|
97 |
|
|
|
98 |
|
|
4. simh simulator setup ---------------------------------------------------
|
99 |
20 |
wfjm |
|
100 |
21 |
wfjm |
Sometimes it is good to compare the w11a behaviour with the PDP-11 software
|
101 |
|
|
emulator from the simh project (see http://simh.trailing-edge.com/).
|
102 |
20 |
wfjm |
|
103 |
21 |
wfjm |
Under $RETROBASE/tools/simh two setup files are provided with configure
|
104 |
|
|
simh to reflect the w11a setup as close as possible:
|
105 |
|
|
- setup_w11a_min.scmd
|
106 |
|
|
Very close the current w11a state when it runs on an S3BOARD
|
107 |
|
|
- processor: 11/70, no FPP, 1 Mbyte
|
108 |
|
|
- periphery: 2 DL11, LP11, RK11, PC11
|
109 |
|
|
- setup_w11a_max.scmd
|
110 |
|
|
Planned configuration for the w11a, in addition
|
111 |
|
|
- processor: 4 Mbyte memory (as on Nexys2, Nexys3,...)
|
112 |
|
|
- periphery: DZ11, RL11/RL02, RK70/RP06, TM11/TU10
|
113 |
4 |
wfjm |
|
114 |
21 |
wfjm |
Startup scripts are provided with each oskit. They call the w11a_max
|
115 |
|
|
configuration, so will show in the emulator what w11a can do when
|
116 |
|
|
finished.
|
117 |
4 |
wfjm |
|
118 |
21 |
wfjm |
All examples below use the same basic setup
|
119 |
4 |
wfjm |
|
120 |
21 |
wfjm |
- setup vt100 emulator window for 2nd DL11
|
121 |
4 |
wfjm |
|
122 |
21 |
wfjm |
cd $RETROBASE/tools/oskit/
|
123 |
22 |
wfjm |
telnet_starter -s -d DL1 &
|
124 |
4 |
wfjm |
|
125 |
21 |
wfjm |
{Note: the -s ensures that the port numbers used by simh are taken!}
|
126 |
4 |
wfjm |
|
127 |
21 |
wfjm |
- start the simulator
|
128 |
4 |
wfjm |
|
129 |
21 |
wfjm |
pdp11 _boot.scmd
|
130 |
20 |
wfjm |
|
131 |
21 |
wfjm |
5. oskits -----------------------------------------------------------------
|
132 |
4 |
wfjm |
|
133 |
21 |
wfjm |
Ready to be used 'oskits' are provided under
|
134 |
|
|
$RETROBASE/tools/oskit/
|
135 |
20 |
wfjm |
|
136 |
21 |
wfjm |
The tarballs with the disk images are provided from a web server
|
137 |
|
|
and have to be installed separately.
|
138 |
20 |
wfjm |
|
139 |
21 |
wfjm |
5a. Unix systems -----------------------------------------------------
|
140 |
20 |
wfjm |
|
141 |
21 |
wfjm |
Legal and license issues:
|
142 |
20 |
wfjm |
|
143 |
21 |
wfjm |
Ancient UNIX systems for the PDP-11 can now be freely used under the
|
144 |
|
|
'Caldera license'. 2.11BSD was released 1992 under the 4 clause BSD
|
145 |
|
|
license. Taken together
|
146 |
4 |
wfjm |
|
147 |
21 |
wfjm |
- Unix V1 to V7
|
148 |
|
|
- all BSD Unix versions for PDP-11
|
149 |
4 |
wfjm |
|
150 |
21 |
wfjm |
can be freely distributed and used for non-commercial purposes.
|
151 |
4 |
wfjm |
|
152 |
21 |
wfjm |
Two oskits are currently provided:
|
153 |
4 |
wfjm |
|
154 |
21 |
wfjm |
- unix-v5_rk: Unix V5 System on RK05
|
155 |
|
|
- 211bsd_rk: 2.11BSD system on RK05
|
156 |
|
|
|
157 |
|
|
For further details consult the README_set.txt file in the
|
158 |
|
|
oskit directory.
|
159 |
4 |
wfjm |
|
160 |
21 |
wfjm |
5b. DEC operating systems --------------------------------------------
|
161 |
|
|
|
162 |
|
|
Legal and license issues:
|
163 |
4 |
wfjm |
|
164 |
21 |
wfjm |
Unfortunately there is no general hobbyist license for DEC operating
|
165 |
|
|
systems for PDP-11 computers. The 'Mentec license' commonly understood
|
166 |
|
|
to cover the some older versions of DEC operating systems, for example
|
167 |
|
|
- RT-11 V5.3 or prior
|
168 |
|
|
- RSX-11M V4.3 or prior
|
169 |
|
|
- RSX-11M PLUS V3.0 or prior
|
170 |
|
|
on software simulators, most notably on the 'simh' suite.
|
171 |
|
|
|
172 |
|
|
HOWEVER: THIS LICENSE DOES NOT COVER THE USAGE OF THESE HISTORIC DEC
|
173 |
|
|
OPERATING SYSTEMS ON ANY 'REAL HARDWARE' IMPLEMENTATION OF A
|
174 |
|
|
PDP-11. SO USAGE ON THE W11 IS *NOT* COVERED BY THE
|
175 |
|
|
'Mentec-license'.
|
176 |
|
|
|
177 |
|
|
Some oskits are provided with systems sysgen'ed to run on a configuration
|
178 |
|
|
like the w11a.
|
179 |
|
|
|
180 |
|
|
- Feel free to explore them with the simh simulator.
|
181 |
|
|
The boot scripts for simh are included ( .simh )
|
182 |
|
|
|
183 |
|
|
- In case you happen to have a valid license feel free to try them
|
184 |
|
|
out the W11A and let the author know whether is works as it should.
|
185 |
|
|
For convenience the boot scripts are also included ( .tcl ).
|
186 |
|
|
|
187 |
|
|
Three oskits are currently provided
|
188 |
|
|
|
189 |
|
|
- rsx11m-31_rk: RSX-11M V3.1 on RK05
|
190 |
|
|
- rsx11m-40_rk: RSX-11M V4.0 on RK05
|
191 |
|
|
- rt11-40_rk: RT-11 V4.0 on RK05
|
192 |
|
|
|
193 |
|
|
For further details consult the README_set.txt file in the
|
194 |
|
|
oskit directory.
|