mirror of
https://github.com/wfjm/w11.git
synced 2026-02-14 20:16:24 +00:00
- ibdr_dl11_buf: new DL11 interface with fifo buffering
- ibdr_dl11: drop rbuf.rrdy, set rbuf.[rx]size0 instead
- ibdr_maxisys: add ibdr_dl11_buf
- librw11/RtraceTools: new, some helper methods for buffer tracing
- librw11/Rw11CntlDL11: add dl11_buf readout
- librwxxtpp/RtclRw11CntlDL11: add getters& setters for dl11_buf readout
- ibd_dl11/util.tcl: setup defs for dl11_buf; add rdump proc
- rw11/util.tcl: setup_tt: add dl{rxqlim,txrlim}; dlrrlim->dlrxrlim
- oskit/*/*_boot.tcl: setup dlrxrlim
- tbench/dl11: tbench for dl11(_buf)
Notes on oskit: RT-11 V4.0 system on RK05 volumes
General remarks
See notes in w11a_os_guide.md on
- I/O emulation setup
- FPGA Board setup
- Rlink and Backend Server setup
- Legal terms
Also read README_license.txt which is included in the oskit !!
Installation
A disk set is available from http://www.retro11.de/data/oc_w11/oskits/rt11-40_rkset.tgz
Download, unpack and copy the disk images (*.dsk), e.g.
cd $RETROBASE/tools/oskit/rt11-40_rk
wget http://www.retro11.de/data/oc_w11/oskits/rt11-40_rkset.tgz
tar -xzf rt11-40_rkset.tgz
Usage
-
Start disk image in simulator
pdp11 rt11-40_rk_boot.scmdor ONLY IF YOU HAVE A VALID LICENSE on w11a
ti_w11 <opt> @rt11-40_rk_boot.tclwhere
<opt>is the proper option set for the board. -
Hit
<ENTER>in the xterm window to connect to simh or backend server. The boot dialog in the consolextermwindow will look like (required input is in{..}, with{<CR>}denoting a carriage return:RT-11SJ V04.00C .D 56=5015 .TYPE V4USER.TXT Welcome to RT-11 Version 4. RT-11 V04 provides new hardware support and some major enhancements over Version 3B. Please use the HELP command; it describes the new options in many of the utilities. If you are using a terminal that requires fill characters, modify location 56 with a Deposit command before proceeding with system installation. LA36 DECwriter II and VT52 DECscope terminals do NOT require such modification. .D 56=0 .Now you are at the RT-11 prompt and can exercise the system.
There is no
haltorshutdowncommand, just terminate the simulator or backend server session.