diff --git a/README.md b/README.md index a37e721d..383e3663 100644 --- a/README.md +++ b/README.md @@ -18,8 +18,8 @@ For more information look into: - [installation notes](doc/INSTALL.md) - [short description of the directory layout](https://wfjm.github.io/home/w11/impl/dirlayout.html) - [guide to run test benches](doc/w11a_tb_guide.md) -- [guide to boot operation systems](doc/w11a_os_guide.md) -- [known issues generel](doc/README_known_issues.md) +- [guide to boot operating systems](doc/w11a_os_guide.md) +- [known issues general](doc/README_known_issues.md) - [known issues w11a CPU](doc/w11a_known_issues.md) ### Note on freecores/w11 diff --git a/doc/CHANGELOG-w11a_V0.60-w11a_V0.70.md b/doc/CHANGELOG-w11a_V0.60-w11a_V0.70.md index 261449bb..153a2ae5 100644 --- a/doc/CHANGELOG-w11a_V0.60-w11a_V0.70.md +++ b/doc/CHANGELOG-w11a_V0.60-w11a_V0.70.md @@ -1,21 +1,22 @@ # Changelog: w11a_V0.60 -> w11a_V0.70 ### Release highlights -- Bugfix for DIV instruction - (in [w11a_V0.61](#user-content-w11a-V0.61), +- bugfix for DIV instruction + (in [w11a_V0.61](#user-content-w11a_V0.61), see [ECO-026-div.md](ECO-026-div.md)) - revised rbus protocol V4 - (in [w11a_V0.62](#user-content-w11a-V0.63), see README_Rlink_V4.txt) + (in [w11a_V0.62](#user-content-w11a_V0.62), + see [README_Rlink_V4.md](README_Rlink_V4.md)) - add basic Vivado support - (in [w11a_V0.64](#user-content-w11a-V0.64)) + (in [w11a_V0.64](#user-content-w11a_V0.64)) - add Nexys4 and Basys3 port of w11a - (in [w11a_V0.64](#user-content-w11a-V0.64)) + (in [w11a_V0.64](#user-content-w11a_V0.64)) - add RL11/RL02 disk support - (in [w11a_V0.64](#user-content-w11a-V0.64)) + (in [w11a_V0.64](#user-content-w11a_V0.64)) - add RH70+RP/RM disk support - (in [w11a_V0.65](#user-content-w11a-V0.65)) + (in [w11a_V0.65](#user-content-w11a_V0.65)) - add TM11/TY10 tape support - (in [w11a_V0.66](#user-content-w11a-V0.66)) + (in [w11a_V0.66](#user-content-w11a_V0.66)) - reference system now ISE 14.7, Vivado 2014.4; Ubuntu 14.04 64 bit, ghdl 0.31 ### Table of contents @@ -26,7 +27,7 @@ - Release [w11a_V0.63](#user-content-w11a_V0.63) - Release [w11a_V0.62](#user-content-w11a_V0.62) - Release [w11a_V0.61](#user-content-w11a_V0.61) -- [CHANGELOG for w11a_V.50 to w11a_V0.60.md](CHANGELOG-w11a_V.50-w11a_V0.60.md) +- [CHANGELOG for w11a_V.50 to w11a_V0.60](CHANGELOG-w11a_V0.50-w11a_V0.60.md) --- @@ -289,7 +290,7 @@ --- -## 2015-03-01: w11a_V0.64 - svn rev 29(oc) 655(wfjm) +## 2015-03-01: w11a_V0.64 - svn rev 29(oc) 655(wfjm) ### Preface - The w11 project started on a Spartan-3 based Digilent S3board, and soon @@ -494,7 +495,7 @@ --- -## 2014-12-20: w11a_V0.62 - svn rev 27(oc) 614(wfjm) +## 2014-12-20: w11a_V0.62 - svn rev 27(oc) 614(wfjm) ### Summary - migrate to rlink protocol version 4 @@ -584,7 +585,7 @@ Notes: ### Summary - The `div` instruction gave wrong results in some corner cases when either divisor or quotient were the largest negative integer (100000 or -32768). - This is corrected now, for details see [ECO-026-div.md](ECO-026-div.md) + This is corrected now, for details see [ECO-026-div.md](ECO-026-div.md). - some minor updates and fixes to support scripts - `xtwi` usage and `XTWI_PATH` setup explained in INSTALL.txt diff --git a/doc/CHANGELOG-w11a_V0.70-w11a_V0.74.md b/doc/CHANGELOG-w11a_V0.70-w11a_V0.74.md index af922a99..6c881f38 100644 --- a/doc/CHANGELOG-w11a_V0.70-w11a_V0.74.md +++ b/doc/CHANGELOG-w11a_V0.70-w11a_V0.74.md @@ -1,12 +1,30 @@ # Changelog: w11a_V0.70 -> w11a_V0.74 +### Release highlights +- bugfix for mmu trap handling + (done in [w11a_V0.71](#user-content-w11a_V0.71), + reported in [w11a_V0.72](#user-content-w11a_V0.72), + see [ECO-027-trap_mmu.md](ECO-027-trap_mmu.md)) +- add debug and monitoring units + (in [w11a_V0.71](#user-content-w11a_V0.71)) +- add Arty port of w11a + (in [w11a_V0.72](#user-content-w11a_V0.72)) +- full Vivado support + (in [w11a_V0.73](#user-content-w11a_V0.73)) +- configurable size cache + (in [w11a_V0.73](#user-content-w11a_V0.73)) +- cram controller using 'page mode' + (in [w11a_V0.74](#user-content-w11a_V0.74)) +- add new test bench driver `tbrun` + (in [w11a_V0.74](#user-content-w11a_V0.74)) + ### Table of contents - Release [w11a_V0.74](#user-content-w11a_V0.74) - Release [w11a_V0.73](#user-content-w11a_V0.73) - Release [w11a_V0.72](#user-content-w11a_V0.72) - Release [w11a_V0.71](#user-content-w11a_V0.71) -- [CHANGELOG for w11a_V.60 to w11a_V0.70.md](CHANGELOG-w11a_V.60-w11a_V0.70.md) -- [CHANGELOG for w11a_V.50 to w11a_V0.60.md](CHANGELOG-w11a_V.50-w11a_V0.60.md) +- [CHANGELOG for w11a_V.60 to w11a_V0.70](CHANGELOG-w11a_V0.60-w11a_V0.70.md) +- [CHANGELOG for w11a_V.50 to w11a_V0.60](CHANGELOG-w11a_V0.50-w11a_V0.60.md) --- @@ -34,11 +52,11 @@ a subset given by selection criteria, and executes them. It can handle the parallel execution of tests so multi-core systems can be very easily exploited. Running all tests is now a single shell command. -- a new tool 'tbfilt' simplifies the logic of self-checking test benches +- a new tool `tbfilt` simplifies the logic of self-checking test benches and can also be used as a tool to analyze the full log files produced by the test benches - several test benches have been added to this release, most notably the - memory tester sys_tst_sram_* which was originally developed to verify + memory tester `sys_tst_sram_*` which was originally developed to verify the s3board SRAM controller and later ported to verify the nexys* CRAM controller. - the system test benches with SRAM and CRAM now include the PCB trace @@ -224,7 +242,7 @@ arty tb, proper portsel setup, configurable timeout, and finally proper timeout setting. - resolved known issue V0.64-3: So far the arty, basys3 and nexys4 serial - port, based on a FTDI FT2232, was often operated at 10 MBaud. This rate + port, based on a `FTDI FT2232`, was often operated at 10 MBaud. This rate is in fact not supported by FTDI, the chip will use 8 instead of 10 MBaud. Due to auto-bauding, which simly adapts to the actual baud rate, this went undetected for some time. Now all designs use a serport block clocked with diff --git a/doc/CHANGELOG.md b/doc/CHANGELOG.md index 6b8c0e66..ebd59d32 100644 --- a/doc/CHANGELOG.md +++ b/doc/CHANGELOG.md @@ -3,9 +3,9 @@ ### Table of contents - Current [master](#user-content-master) -- [CHANGELOG for w11a_V.70 to w11a_V0.74.md](CHANGELOG-w11a_V.70-w11a_V0.74.md) -- [CHANGELOG for w11a_V.60 to w11a_V0.70.md](CHANGELOG-w11a_V.60-w11a_V0.70.md) -- [CHANGELOG for w11a_V.50 to w11a_V0.60.md](CHANGELOG-w11a_V.50-w11a_V0.60.md) +- [CHANGELOG for w11a_V.70 to w11a_V0.74](CHANGELOG-w11a_V0.70-w11a_V0.74.md) +- [CHANGELOG for w11a_V.60 to w11a_V0.70](CHANGELOG-w11a_V0.60-w11a_V0.70.md) +- [CHANGELOG for w11a_V.50 to w11a_V0.60](CHANGELOG-w11a_V0.50-w11a_V0.60.md) --- diff --git a/doc/ECO-026-div.md b/doc/ECO-026-div.md index 4f500733..32af6972 100644 --- a/doc/ECO-026-div.md +++ b/doc/ECO-026-div.md @@ -99,7 +99,7 @@ algorithms need special rules and checks for this. w11a --> regs updated under some rare conditions KB11-C --> regs updated under some rare conditions but in cases different from w11a - 11/44 --> regs updated under some conditions (see v7_longdivide_bug.txt) + 11/44 --> regs updated under some conditions J11 --> regs never updated simh --> regs never updated ``` diff --git a/doc/INSTALL_fx2_support.md b/doc/INSTALL_fx2_support.md index 62e1b3ce..0e9d3d89 100644 --- a/doc/INSTALL_fx2_support.md +++ b/doc/INSTALL_fx2_support.md @@ -6,7 +6,7 @@ project uses a custom firmware in the FX2, this writeup describes the installation of tools, environment setup and generation of the FX2 firmware. ### Table of content - + - [System requirements](#user-content-sysreq) - [Setup environment variables](#user-content-envvar) - [Setup USB access](#user-content-usb-access) @@ -43,7 +43,7 @@ these devices. A set of rules is provided under $RETROBASE/tools/fx2/sys -Follow the 'README.txt' file in this directory. +Follow the [README.md](../tools/fx2/sys/README.md) file in this directory. Notes: - the provided udev rules use the VID/PID for **internal lab use** as diff --git a/doc/README_known_issues.md b/doc/README_known_issues.md index f0b31b1a..0dba6c0d 100644 --- a/doc/README_known_issues.md +++ b/doc/README_known_issues.md @@ -1,4 +1,10 @@ -## Known issues +# Known issues + +The issues of the w11 CPU are listed in a separate document +[w11a_known_issues.md](w11a_known_issues.md). + +This file descibes general issues. + The case id indicates the release when the issue was first recognized. ### V0.73-3 {[issue #11](https://github.com/wfjm/w11/issues/11)} diff --git a/doc/w11a_known_issues.md b/doc/w11a_known_issues.md index d7ca2996..dffa70ff 100644 --- a/doc/w11a_known_issues.md +++ b/doc/w11a_known_issues.md @@ -1,5 +1,10 @@ # Summary of known issues for w11a CPU and systems +General issues are listed on a separate document +[README_known_issues.md](README_known_issues.md). + +This file descibes issues of the w11 CPU. + ###Table of content - [Known differences between w11a and KB11-C (11/70)](#user-content-diff) diff --git a/doc/w11a_os_guide.md b/doc/w11a_os_guide.md index 9cb711ba..13d7c689 100644 --- a/doc/w11a_os_guide.md +++ b/doc/w11a_os_guide.md @@ -236,13 +236,12 @@ Several oskits are provided: | oskit Name | OS | Disk/Tape| Comment | | :---- | :----| :------ | :------ | -| unix-v5_rk | Unix V5 System | RK05 | | -| 211bsd_rk | 2.11BSD system | RK05 | _very elementary subset_ | -| 211bsd_rl | 2.11BSD system | RL02 | _small subset_ | -| 211bsd_rp | 2.11BSD system | RP06 | _full system_ | +| [unix-v5_rk](../tools/oskit/unix-v5_rk) | Unix V5 System | RK05 | | +| [211bsd_rk](../tools/oskit/211bsd_rk) | 2.11BSD system | RK05 | _very elementary subset_ | +| [211bsd_rl](../tools/oskit/211bsd_rl) | 2.11BSD system | RL02 | _small subset_ | +| [211bsd_rp](../tools/oskit/211bsd_rp) | 2.11BSD system | RP06 | _full system_ | -For further details consult the `README_set.txt` file in the -oskit directory. +For further details consult the `README.md` file in the oskit directory. ### DEC operating systems @@ -278,12 +277,11 @@ Several oskits are provided: | oskit Name | OS | Disk/Tape| Comment | | :---- | :----| :------ | :------ | -| rsx11m-31_rk | RSX-11M V3.1 | RK05 | | -| rsx11m-40_rk | RSX-11M V4.0 | RK05 | | -| rsx11mp-30_rp | RSX-11M+ V3.0 | RP06 | | -| rt11-40_rk | RT-11 V4.0 | RK05 | | -| rt11-53_rl | RT-11 V5.3 | RL02 | | -| xxdp_rl | XXDP 22 and 25 | RL02 | | +| [rsx11m-31_rk](../tools/oskit/rsx11m-31_rk) | RSX-11M V3.1 | RK05 | | +| [rsx11m-40_rk](../tools/oskit/rsx11m-40_rk) | RSX-11M V4.0 | RK05 | | +| [rsx11mp-30_rp](../tools/oskit/rsx11mp-30_rp) | RSX-11M+ V3.0 | RP06 | | +| [rt11-40_rk](../tools/oskit/rt11-40_rk) | RT-11 V4.0 | RK05 | | +| [rt11-53_rl](../tools/oskit/rt11-53_rl) | RT-11 V5.3 | RL02 | | +| [xxdp_rl](../tools/oskit/xxdp_rl) | XXDP 22 and 25 | RL02 | | -For further details consult the `README_set.txt` file in the -oskit directory. +For further details consult the `README.md` file in the oskit directory. diff --git a/tools/fx2/src/README.md b/tools/fx2/src/README.md new file mode 100644 index 00000000..e52feb34 --- /dev/null +++ b/tools/fx2/src/README.md @@ -0,0 +1,86 @@ +The FX2 software is based on the Sourceforge project ixo-jtag + + http://sourceforge.net/projects/ixo-jtag/ + +The usb_jtag sub project was checked out on 2011-07-17 (Rev 204) from +Sourceforge and taken as basis for the further developement. +The original README.txt is preserved under +[README_iso_jtag.txt](README_iso_jtag.txt). +Only the `hw_nexys.c` branch was kept on the import. + +### Change log: + +#### 2014-11-16 (Rev 604) +- ported to sdcc 3.3 + - all prior development was done with sdcc 2.x, latest sdcc 2.9 was bundled + with Ubuntu 12.04 LTS. + - now switching to sdcc 3.3 as bundled with Ubuntu 14.04 LTS. + - mayor changes: + - assembler now named `sdas8051` (was `asx8051`) + - all special reserved keywords start now with a double underscore + + at --> __at + bit --> __bit + interrupt --> __interrupt + sbit --> __sbit + sfr --> __sfr + xdata --> __xdata + _asm --> __asm + _endasm --> __endasm + _naked --> __naked + + - in general sources stayed untouched in the sdcc 2.9 form, all keyword + mappings are done with the preprocessor and defs like `-Dat=__at` + - make usage now + - default is now sdcc 3.x, in this case simply use + + make clean && make + + - on systems with sdcc 2.x use + + make clean && make SDCC29=1 + + - detected and fixed BUG inherted from ixo-jtag and GNU Radio in `SYNCDELAY` + The macro `SYNCDELAY` (defined in lib/syncdelay.h) inserts 'nop' needed + to resolve some timing issues in the FX2. The old implementation was + + #define SYNCDELAY _asm nop; nop; nop; _endasm + #define NOP _asm nop; _endasm + + This inserts into the assembler output a single line + + nop; nop; nop; + + Since `';'` is the comment delimiter for the assember the 2nd and 3rd nop + are simply ignored. + + This wrong implementation was changed to + + #define SYNCDELAY NOP; NOP; NOP + + That created three lines in the assembler output + + nop; + nop; + nop; + + and generated the three desired nops in the binary. + + > This was definitively broken from the very beginning. + > The code ran alway. Reason is mosu likely that the `SYNCDELAY` + > macros were only used in the setup phase and never is a + > really time critical context. + +#### 2011-07-17 (Rev 395) +- Makefile: reorganized to support multiple target/fifo configs +- renames: + + dscr.a51 -> dscr_jtag.a51 + hw_nexys.c -> hw_nexys2.c + usbjtag.c -> main.c + +- dscr_jtag.a51 + - Use USB 2.0; New string values + - use 512 byte for all high speed endpoints +- dscr_jtag_2fifo.a51 + - dscr with EP4 as HOST->FPGA and EP6 as FPGA->HOST hardware fifo diff --git a/tools/fx2/src/README.txt b/tools/fx2/src/README.txt deleted file mode 100644 index b6731200..00000000 --- a/tools/fx2/src/README.txt +++ /dev/null @@ -1,79 +0,0 @@ -# $Id: README.txt 604 2014-11-16 22:33:09Z mueller $ -# - -The FX2 software is based on the Sourceforge project ixo-jtag - - http://sourceforge.net/projects/ixo-jtag/ - -The usb_jtag sub project was checked out on 2011-07-17 (Rev 204) from -Sourceforge and take as the basis for the further developement. -The original README.txt is preserved under README_iso_jtag.txt. -Only the hw_nexys.c branch is kept on the import. - -Change log: - -2014-11-16 (Rev 604) - - ported to sdcc 3.3 - - all prior development was done with sdcc 2.x, latest sdcc 2.9 was bundled - with Ubuntu 12.04 LTS. - - now switching to sdcc 3.3 as bundled with Ubuntu 14.04 LTS. - - mayor changes: - 1. assembler now named sdas8051 (was asx8051) - 2. all special reserved keywords start now with a double underscore - at --> __at - bit --> __bit - interrupt --> __interrupt - sbit --> __sbit - sfr --> __sfr - xdata --> __xdata - _asm --> __asm - _endasm --> __endasm - _naked --> __naked - - in general sources stayed untouched in the sdcc 2.9 form, all keyword - mappings are done with the preprocessor and defs like "-Dat=__at" - - - make usage now - - default is now sdcc 3.x, in this case simply use - - make clean && make - - - on systems with sdcc 2.x use - - make clean && make SDCC29=1 - - - detected and fixed BUG inherted from ixo-jtag and GNU Radio in SYNCDELAY - The macro SYNCDELAY (defined in lib/syncdelay.h) inserts 'nop' needed - to resolve some timing issues in the FX2. The old implementation was - - #define SYNCDELAY _asm nop; nop; nop; _endasm - #define NOP _asm nop; _endasm - - This inserts into the assembler output a single line - nop; nop; nop; - Since ';' is the comment delimiter for the assember the 2nd and 3rd nop - are simply ignored. - - This wrong implementation was changed to - #define SYNCDELAY NOP; NOP; NOP - That created three lines in the assembler output - nop; - nop; - nop; - and generated the three desired nops in the binary. - - !! This was definitively broken from the very beginning. !! - !! The code ran alway. Reason is mosu likely that the SYNCDELAY !! - !! macros were only used in the setup phase and never is a !! - !! really time critical context. !! - -2011-07-17 (Rev 395) - - Makefile: reorganized to support multiple target/fifo configs - - renames: - dscr.a51->dscr_jtag.a51 - hw_nexys.c->hw_nexys2.c - usbjtag.c->main.c - - dscr_jtag.a51 - - Use USB 2.0; New string values - - use 512 byte for all high speed endpoints - - dscr_jtag_2fifo.a51 - - dscr with EP4 as HOST->FPGA and EP6 as FPGA->HOST hardware fifo diff --git a/tools/fx2/sys/README.md b/tools/fx2/sys/README.md new file mode 100644 index 00000000..4f38c2b9 --- /dev/null +++ b/tools/fx2/sys/README.md @@ -0,0 +1,30 @@ +This directory contains udev rules which ensure that the Cypress FX2 on +- Digilent Nexys2 +- Digilent Nexys3 +- Digilent Atlys + +is read/write accessible for user land processes, either in +- original power on state _(thus Digilent VID/PID)_ +- after custom firmware is loaded _(thus VOTI VID/PID)_ + +> **The rules assume that eligible user accounts are in group `plugdev`. +> Check with the `groups` command whether your account is in group `plugdev`, +> in not, add this group to your accounts groups list.** + +To setup udev rules do +```bash + sudo cp -a 99-retro-usb-permissions.rules /etc/udev/rules.d/ + sudo chown root:root /etc/udev/rules.d/99-retro-usb-permissions.rules + dir /etc/udev/rules.d/ + + sudo udevadm control --reload-rules +``` + +to verify whether usb device was really put into group `plugdev` +```bash + lsusb + # --> look for bus/dev of interest + + find /dev/bus/usb -type c | sort| xargs ls -l + # --> check whether bus/dev of interest is in group plugdev +``` diff --git a/tools/fx2/sys/README.txt b/tools/fx2/sys/README.txt deleted file mode 100644 index db37b2ba..00000000 --- a/tools/fx2/sys/README.txt +++ /dev/null @@ -1,30 +0,0 @@ -# $Id: README.txt 604 2014-11-16 22:33:09Z mueller $ - -This directory contains udev rules which ensure that the Cypress FX2 on - - Digilent Nexys2 - - Digilent Nexys3 - - Digilent Atlys - -is read/write accessible for user land processes, either in - - original power on state (thus Digilent VID/PID) - - after custom firmware is loaded (thus VOTI VID/PID) - -!! The rules assume that eligible user accounts are in group plugdev. -!! Check with the 'groups' command whether your account is in group plugdev, -!! in not, add this group to your accounts groups list. - -To setup udev rules do - - sudo cp -a 99-retro-usb-permissions.rules /etc/udev/rules.d/ - sudo chown root:root /etc/udev/rules.d/99-retro-usb-permissions.rules - dir /etc/udev/rules.d/ - - sudo udevadm control --reload-rules - -to verify whether usb device was really put into group 'plugdev' - - lsusb - --> look for bus/dev of interest - - find /dev/bus/usb -type c | sort| xargs ls -l - --> check whether bus/dev of interest is in group plugdev diff --git a/tools/oskit/211bsd_rk/README_211bsd_rkset.txt b/tools/oskit/211bsd_rk/README.md similarity index 53% rename from tools/oskit/211bsd_rk/README_211bsd_rkset.txt rename to tools/oskit/211bsd_rk/README.md index 94dcb460..40abd32f 100644 --- a/tools/oskit/211bsd_rk/README_211bsd_rkset.txt +++ b/tools/oskit/211bsd_rk/README.md @@ -1,45 +1,37 @@ -# $Id: README_211bsd_rkset.txt 688 2015-06-05 13:15:10Z mueller $ +## Notes on oskit: 2.11BSD system on RK05 volumes -Notes on oskit: 2.11BSD system on RK05 volumes +### General remarks +See notes in [w11a_os_guide.md](../../../doc/w11a_os_guide.md) on + 1. I/O emulation setup + 2. FPGA Board setup + 3. Rlink and Backend Server setup + 4. Legal terms - Table of content: +### Installation +A disk set is available from +http://www.retro11.de/data/oc_w11/oskits/211bsd_rkset.tgz - 1. General remarks - 2. Installation - 3. Usage +Download, unpack and copy the disk images (*.dsk), e.g. +```bash + cd $RETROBASE/tools/oskit/211bsd_rk/ + wget http://www.retro11.de/data/oc_w11/oskits/211bsd_rkset.tgz + tar -xzf 211bsd_rkset.tgz +``` -1. General remarks --------------------------------------------------- +### Usage - See notes on - - 1. I/O emulation setup - 2. FPGA Board setup - 3. Rlink and Backend Server setup - 4. Legal terms - - in $RETROBASE/doc/w11a_os_guide.txt - -2. Installation ------------------------------------------------------ - - - A disk set is available from - http://www.retro11.de/data/oc_w11/oskits/211bsd_rkset.tgz - Download, unpack and copy the disk images (*.dsk), e.g. - - cd $RETROBASE/tools/oskit/211bsd_rk/ - wget http://www.retro11.de/data/oc_w11/oskits/211bsd_rkset.tgz - tar -xzf 211bsd_rkset.tgz - -3. Usage ------------------------------------------------------------- - - - Start backend server and boot system (see section 3 in w11a_os_guide.txt) +- Start backend server and boot system + (see section Rlink in [w11a_os_guide.md](../../../doc/w11a_os_guide.md)) + ``` boot script: 211bsd_rk_boot.tcl example: ti_w11 @211bsd_rk_boot.tcl where is the proper option set for the board. + ``` - - Hit in the xterm window to connnect to backend server. - The boot dialog in the console xterm window will look like - (required input is in {..}, with {} denoting a carriage return: - +- Hit `` in the `xterm` window to connnect to backend server. + The boot dialog in the console `xterm` window will look like + (required input is in `{..}`, with `{}` denoting a carriage return: + ``` 70Boot from rk(0,0,0) at 0177404 : {} : rk(0,0,0)unix @@ -62,10 +54,11 @@ Notes on oskit: 2.11BSD system on RK05 volumes xp 0 csr 176700 vector 254 attached cn 1 csr 176500 vector 300 attached erase, kill ^U, intr ^C + ``` - In first '#' prompt the system is in single-user mode. Just enter a ^D - to continue the system startup to multi-user mode: - + In first `'#'` prompt the system is in single-user mode. Just enter a `^D` + to continue the system startup to multi-user mode: + ``` #^D checking quotas: done. Assuming non-networking system ... @@ -82,18 +75,20 @@ Notes on oskit: 2.11BSD system on RK05 volumes 2.11 BSD UNIX (curly.2bsd.com) (console) login: + ``` - The login prompt is sometimes mangled with the 'Device not configured' - system messages, if its not visible just hit to get a fresh one. - + The login prompt is sometimes mangled with the 'Device not configured' + system messages, if its not visible just hit `` to get a fresh one. + ``` login: {root} erase, kill ^U, intr ^C + ``` - Now the system is in multi-user mode, daemons runnng. You can explore - the system, e.g. with a 'pstat -T' or a 'mount' command. The second - xterm can be activated too, it will connect to a second emulated DL11. - At the end is important to shutdown properly with a 'halt': - + Now the system is in multi-user mode, daemons runnng. You can explore + the system, e.g. with a `pstat -T` or a `mount` command. The second + `xterm` can be activated too, it will connect to a second emulated DL11. + At the end is important to shutdown properly with a `halt`: + ``` # {pstat -T} 7/186 files 39/208 inodes @@ -110,15 +105,20 @@ Notes on oskit: 2.11BSD system on RK05 volumes # {halt} syncing disks... done halting + ``` - While the system was running the server process display the + While the system was running the server process display the + ``` cpumon> - prompt. When the w11 has halted after 211bsd shutdown a message like + ``` + prompt. When the w11 has halted after 211bsd shutdown a message like + ``` CPU down attention Processor registers and status: PS: 030350 cm,pm=k,u s,p,t=0,7,0 NZVC=1000 rust: 01 HALTed R0: 177560 R1: 161322 R2: 053436 R3: 000010 R4: 003000 R5: 147510 SP: 147466 PC: 000014 - - will be visible. Now the server process can be stopped with ^D. + ``` + + will be visible. Now the server process can be stopped with `^D`. diff --git a/tools/oskit/211bsd_rl/README_211bsd_rlset.txt b/tools/oskit/211bsd_rl/README.md similarity index 57% rename from tools/oskit/211bsd_rl/README_211bsd_rlset.txt rename to tools/oskit/211bsd_rl/README.md index 6fc87795..ba12626e 100644 --- a/tools/oskit/211bsd_rl/README_211bsd_rlset.txt +++ b/tools/oskit/211bsd_rl/README.md @@ -1,45 +1,37 @@ -# $Id: README_211bsd_rlset.txt 688 2015-06-05 13:15:10Z mueller $ +## Notes on oskit: 2.11BSD system on RL02 volumes -Notes on oskit: 2.11BSD system on RL02 volumes +### General remarks +See notes in [w11a_os_guide.md](../../../doc/w11a_os_guide.md) on + 1. I/O emulation setup + 2. FPGA Board setup + 3. Rlink and Backend Server setup + 4. Legal terms - Table of content: - - 1. General remarks - 2. Installation - 3. Usage - -1. General remarks --------------------------------------------------- - - See notes on - - 1. I/O emulation setup - 2. FPGA Board setup - 3. Rlink and Backend Server setup - 4. Legal terms - - in $RETROBASE/doc/w11a_os_guide.txt - -2. Installation ------------------------------------------------------ - - - A disk set is available from - http://www.retro11.de/data/oc_w11/oskits/211bsd_rlset.tgz - Download, unpack and copy the disk images (*.dsk), e.g. +### Installation +A disk set is available from +http://www.retro11.de/data/oc_w11/oskits/211bsd_rlset.tgz +Download, unpack and copy the disk images (*.dsk), e.g. +```bash cd $RETROBASE/tools/oskit/211bsd_rl/ wget http://www.retro11.de/data/oc_w11/oskits/211bsd_rlset.tgz tar -xzf 211bsd_rlset.tgz +``` -3. Usage ------------------------------------------------------------- +### Usage - - Start backend server and boot system (see section 3 in w11a_os_guide.txt) +- Start backend server and boot system + (see section Rlink in [w11a_os_guide.md](../../../doc/w11a_os_guide.md)) + ``` boot script: 211bsd_rl_boot.tcl example: ti_w11 @211bsd_rl_boot.tcl - where is the proper option set for the board. - - - Hit in the xterm window to connnect to backend server. - The boot dialog in the console xterm window will look like - (required input is in {..}, with {} denoting a carriage return: + where is the proper option set for the board. + ``` +- Hit `` in the `xterm` window to connnect to backend server. + The boot dialog in the console `xterm` window will look like + (required input is in `{..}`, with `{}` denoting a carriage return: + ``` 70Boot from rl(0,0,0) at 0174400 : {} : rl(0,0,0)unix @@ -62,10 +54,11 @@ Notes on oskit: 2.11BSD system on RL02 volumes xp 0 csr 176700 vector 254 attached cn 1 csr 176500 vector 300 attached erase, kill ^U, intr ^C + ``` - In first '#' prompt the system is in single-user mode. Just enter a ^D - to continue the system startup to multi-user mode: - + In first `'#'` prompt the system is in single-user mode. Just enter a `^D` + to continue the system startup to multi-user mode: + ``` #^D Fast boot ... skipping disk checks @@ -86,18 +79,19 @@ Notes on oskit: 2.11BSD system on RL02 volumes 2.11 BSD UNIX (curly.2bsd.com) (console) login: - - The login prompt is sometimes mangled with the 'Device not configured' - system messages, if its not visible just hit to get a fresh one. - + ``` + The login prompt is sometimes mangled with the 'Device not configured' + system messages, if its not visible just hit `` to get a fresh one. + ``` login: {root} erase, kill ^U, intr ^C + ``` - Now the system is in multi-user mode, daemons runnng. You can explore - the system, e.g. with a 'pstat -T' or a 'mount' command. The second - xterm can be activated too, it will connect to a second emulated DL11. - At the end is important to shutdown properly with a 'halt': - + Now the system is in multi-user mode, daemons runnng. You can explore + the system, e.g. with a `pstat -T` or a `mount` command. The second + `xterm` can be activated too, it will connect to a second emulated DL11. + At the end is important to shutdown properly with a `halt`: + ``` # {pstat -T} 7/186 files 40/208 inodes @@ -112,15 +106,20 @@ Notes on oskit: 2.11BSD system on RL02 volumes # {halt} syncing disks... done halting + ``` - While the system was running the server process display the + While the system was running the server process display the + ``` cpumon> - prompt. When the w11 has halted after 211bsd shutdown a message like + ``` + prompt. When the w11 has halted after 211bsd shutdown a message like + ``` CPU down attention Processor registers and status: PS: 030350 cm,pm=k,u s,p,t=0,7,0 NZVC=1000 rust: 01 HALTed R0: 177560 R1: 161322 R2: 053770 R3: 000010 R4: 003400 R5: 147510 SP: 147466 PC: 000014 - - will be visible. Now the server process can be stopped with ^D. + ``` + + will be visible. Now the server process can be stopped with `^D`. diff --git a/tools/oskit/211bsd_rp/README_211bsd_rpset.txt b/tools/oskit/211bsd_rp/README.md similarity index 62% rename from tools/oskit/211bsd_rp/README_211bsd_rpset.txt rename to tools/oskit/211bsd_rp/README.md index 84cb2009..ce1e0918 100644 --- a/tools/oskit/211bsd_rp/README_211bsd_rpset.txt +++ b/tools/oskit/211bsd_rp/README.md @@ -1,45 +1,37 @@ -# $Id: README_211bsd_rpset.txt 688 2015-06-05 13:15:10Z mueller $ +## Notes on oskit: 2.11BSD system on a RP06 volume -Notes on oskit: 2.11BSD system on a RP06 volume +### General remarks +See notes in [w11a_os_guide.md](../../../doc/w11a_os_guide.md) on + 1. I/O emulation setup + 2. FPGA Board setup + 3. Rlink and Backend Server setup + 4. Legal terms - Table of content: - - 1. General remarks - 2. Installation - 3. Usage - -1. General remarks --------------------------------------------------- - - See notes on - - 1. I/O emulation setup - 2. FPGA Board setup - 3. Rlink and Backend Server setup - 4. Legal terms - - in $RETROBASE/doc/w11a_os_guide.txt - -2. Installation ------------------------------------------------------ - - - A disk set is available from - http://www.retro11.de/data/oc_w11/oskits/211bsd_rpset.tgz - Download, unpack and copy the disk images (*.dsk), e.g. +### Installation +A disk set is available from +http://www.retro11.de/data/oc_w11/oskits/211bsd_rpset.tgz +Download, unpack and copy the disk images (*.dsk), e.g. +```bash cd $RETROBASE/tools/oskit/211bsd_rp/ wget http://www.retro11.de/data/oc_w11/oskits/211bsd_rpset.tgz tar -xzf 211bsd_rpset.tgz +``` -3. Usage ------------------------------------------------------------- +### Usage - - Start backend server and boot system (see section 3 in w11a_os_guide.txt) +- Start backend server and boot system + (see section Rlink in [w11a_os_guide.md](../../../doc/w11a_os_guide.md)) + ``` boot script: 211bsd_rp_boot.tcl example: ti_w11 @211bsd_rp_boot.tcl where is the proper option set for the board. + ``` - - Hit in the xterm window to connnect to backend server. - The boot dialog in the console xterm window will look like - (required input is in {..}, with {} denoting a carriage return: - +- Hit `` in the `xterm` window to connnect to backend server. + The boot dialog in the console `xterm` window will look like + (required input is in `{..}`, with `{}` denoting a carriage return: + ``` 70Boot from xp(0,0,0) at 0176700 : {} : xp(0,0,0)unix @@ -64,10 +56,11 @@ Notes on oskit: 2.11BSD system on a RP06 volume xp 0 csr 176700 vector 254 attached cn 1 csr 176500 vector 300 attached erase, kill ^U, intr ^C + ``` - In first '#' prompt the system is in single-user mode. Just enter a ^D - to continue the system startup to multi-user mode: - + In first `'#'` prompt the system is in single-user mode. Just enter a `^D` + to continue the system startup to multi-user mode: + ``` #^D Fast boot ... skipping disk checks checking quotas: done. @@ -93,18 +86,20 @@ Notes on oskit: 2.11BSD system on a RP06 volume 2.11 BSD UNIX (curly.2bsd.com) (console) login: + ``` - The login prompt is sometimes mangled with the 'Device not configured' - system messages, if its not visible just hit to get a fresh one. - + The login prompt is sometimes mangled with the 'Device not configured' + system messages, if its not visible just hit `` to get a fresh one. + ``` login: {root} erase, kill ^U, intr ^C + ``` - Now the system is in multi-user mode, daemons runnng. You can explore - the system, e.g. with a 'pstat -T' or a 'mount' command. The second - xterm can be activated too, it will connect to a second emulated DL11. - At the end is important to shutdown properly with a 'halt': - + Now the system is in multi-user mode, daemons runnng. You can explore + the system, e.g. with a `pstat -T` or a `mount` command. The second + `xterm` can be activated too, it will connect to a second emulated DL11. + At the end is important to shutdown properly with a `halt`: + ``` # {pstat -T} 7/186 files 40/208 inodes @@ -119,10 +114,15 @@ Notes on oskit: 2.11BSD system on a RP06 volume # {halt} syncing disks... done halting + ``` - While the system was running the server process display the + While the system was running the server process display the + ``` cpumon> - prompt. When the w11 has halted after 211bsd shutdown a message like + ``` + + prompt. When the w11 has halted after 211bsd shutdown a message like + ``` CPU down attention Processor registers and status: @@ -130,5 +130,6 @@ Notes on oskit: 2.11BSD system on a RP06 volume PS: 030350 cm,pm=k,u s,p,t=0,7,0 NZVC=1000 rust: 01 HALTed R0: 177560 R1: 010330 R2: 056172 R3: 000010 R4: 005000 R5: 147510 SP: 147466 PC: 000014 - - will be visible. Now the server process can be stopped with ^D. + ``` + + will be visible. Now the server process can be stopped with `^D`. diff --git a/tools/oskit/211bsd_tm/README_211bsd_tmset.txt b/tools/oskit/211bsd_tm/README.md similarity index 70% rename from tools/oskit/211bsd_tm/README_211bsd_tmset.txt rename to tools/oskit/211bsd_tm/README.md index 0efc8c2c..7e078743 100644 --- a/tools/oskit/211bsd_tm/README_211bsd_tmset.txt +++ b/tools/oskit/211bsd_tm/README.md @@ -1,69 +1,61 @@ -# $Id: README_211bsd_tmset.txt 699 2015-07-05 21:37:26Z mueller $ +## Notes on oskit: 2.11BSD system on a TM11 tape distribution kit -Notes on oskit: 2.11BSD system on a TM11 tape distribution kit +### General remarks +See notes in [w11a_os_guide.md](../../../doc/w11a_os_guide.md) on + 1. I/O emulation setup + 2. FPGA Board setup + 3. Rlink and Backend Server setup + 4. Legal terms - Table of content: +### Installation - 1. General remarks - 2. Installation - 3. Usage - 4. Install 211bsd from tape on a RP06 disk - 5. Install 211bsd from tape on a RM05 disk - -1. General remarks --------------------------------------------------- - - See notes on - - 1. I/O emulation setup - 2. FPGA Board setup - 3. Rlink and Backend Server setup - 4. Legal terms - - in $RETROBASE/doc/w11a_os_guide.txt - -2. Installation ------------------------------------------------------ - - - A tape set is available from - http://www.retro11.de/data/oc_w11/oskits/211bsd_tmset.tgz - Download, unpack and copy the tape images (*.tap), e.g. +A tape set is available from +http://www.retro11.de/data/oc_w11/oskits/211bsd_tmset.tgz +Download, unpack and copy the tape images (*.tap), e.g. +```bash cd $RETROBASE/tools/oskit/211bsd_tm/ wget http://www.retro11.de/data/oc_w11/oskits/211bsd_tmset.tgz tar -xzf 211bsd_tmset.tgz +``` -3. Usage ------------------------------------------------------------- +### Usage - - This is a tape distribution kit and tailoed to be installed on massbus - disks of RP or RM type. The 211bsd system doesn't contain a ready to - used boot block for RP07 disks, while RM03 and RP05 disks are too small - for a full 211bsd system. Therefore RP06 and RM05 disks are the supported - disk types. - - So first step is to create a disk image, use one of +- This is a tape distribution kit and tailoed to be installed on massbus + disks of RP or RM type. The 211bsd system doesn't contain a ready to + used boot block for RP07 disks, while RM03 and RP05 disks are too small + for a full 211bsd system. Therefore RP06 and RM05 disks are the supported + disk types. +- So first step is to create a disk image, use one of + ``` create_disk --typ=rp06 --bad 211bsd_rp06.dsk create_disk --typ=rm05 --bad 211bsd_rm05.dsk + ``` - - Start backend server and boot system (see section 3 in w11a_os_guide.txt) +- Start backend server and boot system + (see section Rlink in [w11a_os_guide.md](../../../doc/w11a_os_guide.md)) + ``` boot script: 211bsd_tm_rp06_boot.tcl or 211bsd_tm_rm05_boot.tcl example: ti_w11 @211bsd_tm_rp06_boot.tcl where is the proper option set for the board. + ``` - - Hit in the xterm window to connnect to backend server. - The boot dialog in the console xterm window will look like - (required input is in {..}, with {} denoting a carriage return: - +- Hit `` in the `xterm` window to connnect to backend server. + The boot dialog in the console `xterm` window will look like + (required input is in `{..}`, with `{}` denoting a carriage return: + ``` 70Boot from tm(0,0,0) at 0172522 : + ``` - This prompt of the 'mtboot' monitor, from which the different steps of - the installation procedure can be started. - -4. Install 211bsd from tape on a RP06 disk --------------------------- - - The tape distribution contains 8 files + This prompt of the `mtboot` monitor, from which the different steps of + the installation procedure can be started. +### Install 211bsd from tape on a RP06 disk +The tape distribution contains 8 files +``` file #records length Contents 0 73 512 tape boot (twice) and boot handler 1 38 1024 standalone disklabel @@ -74,20 +66,21 @@ Notes on oskit: 2.11BSD system on a TM11 tape distribution kit 6 3516 10240 tar of adm bin crash ... 7 903 10240 tar of sys include 8 4168 10240 tar of remaining directories +``` - The installation will - - partition the disk with disklabel - - create the root file system with mkfs - - re-store the root file system with restor - - than boot 211bsd from disk into single user mode - - write the boot block - - create the /usr file system - - load the /usr file with tar from tape (three steps) +The installation will +- partition the disk with disklabel +- create the root file system with mkfs +- re-store the root file system with restor +- than boot 211bsd from disk into single user mode +- write the boot block +- create the `/usr` file system +- load the `/usr` file with tar from tape (three steps) -4.1 Install 211bsd, tape phase --------------------------------------- +#### Install 211bsd, tape phase - The following shows the full dialogue, the input is after a '##' separator - +The following shows the full dialogue, the input is after a `##` separator +``` 70Boot from tm(0,0,0) at 0172522 : ## tm(0,1) Boot: bootdev=0401 bootcsr=0172522 @@ -201,15 +194,16 @@ End of tape 70Boot from tm(0,0,3) at 0172522 : ## xp(0,0)unix +``` -4.2 Install 211bsd, disk phase --------------------------------------- - - The last command boots 211bsd form the just setup disk, which has now - a root file system, but not yet a hardward boot block. - '#' is now the shell prompt - '!!' indicates comments - indented lines show output +#### Install 211bsd, disk phase +The last command boots 211bsd form the just setup disk, which has now +a root file system, but not yet a hardward boot block. In the following +- `#` is now the shell prompt +- `!!` indicates comments +- indented lines show output +``` Boot: bootdev=05000 bootcsr=0176700 2.11 BSD UNIX #9: Wed Dec 10 06:24:37 PST 2008 @@ -268,9 +262,11 @@ End of tape Filesystem 1K-blocks Used Avail Capacity Mounted on root 10285 4503 5782 44% / /dev/xp0c 154094 87043 67051 56% /usr +``` -4.3 test boot created sysyem ----------------------------------------- +#### test boot created sysyem +``` # halt on ti_w11 prompt @@ -278,30 +274,31 @@ on ti_w11 prompt 70Boot from xp(0,0,0) at 0176700 : ## +``` -from now on like for README_211bsd_rpset.txt +from now on like in [README for 211bsd_rpset](../211bsd_rp/README.md). -5. Install 211bsd from tape on a RM05 disk --------------------------- +### Install 211bsd from tape on a RM05 disk - The procedure is very similar to an RP06 install, the only differences are - - disk partitioning (creating disklabel) - - setup of boot block - - initializing the 'c' file system +The procedure is very similar to an RP06 install, the only differences are +- disk partitioning (creating disklabel) +- setup of boot block +- initializing the `c` file system - In the following only these differences are briefly summarized: - - - use 211bsd_tm_rm05_boot.tcl (instead of 211bsd_tm_rp06_boot.tcl) - - - in disklabel use different sizes and offsets +In the following only these differences are briefly summarized: +- use `211bsd_tm_rm05_boot.tcl` (instead of `211bsd_tm_rp06_boot.tcl`) +- in `disklabel` use different sizes and offsets + ``` 'a' size [500384]: ## 34c 'b' offset [0]: ## 34c 'b' size [0]: ## 13c 'c' offset [0]: ## 47c 'c' size [0]: ## 775c - - - the final 'd' or display in disklabel show show + ``` +- the final `'d'` or display in disklabel should show + ``` type: SMD disk: SMD label: DEFAULT @@ -319,20 +316,25 @@ from now on like for README_211bsd_rpset.txt a: 20672 0 2.11BSD 1024 1024 # (Cyl. 0 - 33) b: 7904 20672 swap # (Cyl. 34 - 46) c: 471200 28576 2.11BSD 1024 1024 # (Cyl. 47 - 821) + ``` - - after first boot write the correct boot block +- after first boot write the correct boot block + ``` # dd if=/mdec/rm05uboot of=/dev/rxp0a count=1 + ``` - Note: the boot code has the disk geometry hard coded, so using the right - one is essential. RP06 uses hpuboot, while RM05 uses rm05uboot !! - - - to create file system on partition c use + Note: the boot code has the disk geometry hard coded, so using the right + one is essential. RP06 uses `hpuboot`, while RM05 uses `rm05uboot` !! +- to create file system on partition c use + ``` # /sbin/mkfs -m 2 -n 304 -i 4096 -s 235600 /dev/rxp0c + ``` - - the final system should give a 'df' output like - +- the final system should give a `df` output like + ``` Filesystem 1K-blocks Used Avail Capacity Mounted on root 10173 4503 5670 44% / /dev/xp0c 231917 87043 144874 38% /usr + ``` \ No newline at end of file diff --git a/tools/oskit/rsx11m-31_rk/README.md b/tools/oskit/rsx11m-31_rk/README.md new file mode 100644 index 00000000..248a69c3 --- /dev/null +++ b/tools/oskit/rsx11m-31_rk/README.md @@ -0,0 +1,99 @@ +## Notes on oskit: RSX-11M V3.1 system on RK05 volumes + +### General remarks + +See notes in [w11a_os_guide.md](../../../doc/w11a_os_guide.md) on + 1. I/O emulation setup + 2. FPGA Board setup + 3. Rlink and Backend Server setup + 4. 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/rsx11m-31_rkset.tgz + +Download, unpack and copy the disk images (*.dsk), e.g. +```bash + cd $RETROBASE/tools/oskit/rsx11m-31_rk + wget http://www.retro11.de/data/oc_w11/oskits/rsx11m-31_rkset.tgz + tar -xzf rsx11m-31_rkset.tgz +``` + +### Usage + +- Start disk imge in simulator + ``` + pdp11 rsx11m-31_rk_boot.scmd + ``` + + or **ONLY IF YOU HAVE A VALID LICENSE** on w11a + ``` + ti_w11 @rsx11m-31_rk_boot.tcl + ``` + + where `` is the proper option set for the board. + +- Hit `` in the `xterm` window to connect to simh or backend server. + The boot dialog in the console `xterm` window will look like + (required input is in `{..}`, with `{}` denoting a carriage return: + ``` + RSX-11M V3.1 BL22 65408K MAPPED + >RED DK0:=SY0: + >RED DK0:=LB0: + >MOU DK0:SYSTEM0 + >@[1,2]STARTUP + ``` + + That RSX shows `65408K` is a bug in V3.1. It should be `1920K` the + size of accessible memory in words. For configurations with 1 MByte + and below the correct value is displayed, above a wrong one. + + This os version was released in December 1977, so it's no suprise + that it is not y2k ready. So enter a date before prior to 2000. + ``` + >* PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY) [S]: {<.. see above ..>} + >TIM 17:18 12-may-83 + >; + >RUN ERRLOG + > + ;ERL -- ERROR LOG INITIALIZED + >MOU DK1:SYSTEM1 + >; + >INS DK1:[1,54]BIGMAC/PAR=GEN + >INS DK1:[1,54]BIGTKB/PAR=GEN + >INS DK1:[1,54]CDA + >INS DK1:[1,54]DSC/PAR=GEN + >INS DK1:[1,54]EDT/PAR=GEN + >INS DK1:[1,54]FLX + >INS DK1:[1,54]FOR + >INS DK1:[1,54]FTB + >INS DK1:[1,54]LBR + >INS DK1:[1,54]PSE + >INS DK1:[1,54]RNO + >INS DK1:[1,54]SRD + >INS DK1:[1,54]SYE + >; + >INS DK1:[1,54]TEC + >INS DK1:[1,54]TEC/TASK=...MAK + >INS DK1:[1,54]TEC/TASK=...MUN + >; + >INS DK1:[1,54]VTEC + >; + >; + >SET /UIC=[1,6] + >PSE = + >SET /UIC=[200,200] + >; + >ACS DK1:/BLKS=512. + >; + >@ + > + ``` + + Now you are at the MCR prompt and can exercise the system. + + At the end is important to shutdown properly with a `run $shutup`. + The simululaor (or the rlink backend) can be stopped when the + CPU has halted. diff --git a/tools/oskit/rsx11m-31_rk/README_rsx11m-31_rkset.txt b/tools/oskit/rsx11m-31_rk/README_rsx11m-31_rkset.txt deleted file mode 100644 index 96fd1728..00000000 --- a/tools/oskit/rsx11m-31_rk/README_rsx11m-31_rkset.txt +++ /dev/null @@ -1,94 +0,0 @@ -# $Id: README_rsx11m-31_rkset.txt 680 2015-05-14 13:29:46Z mueller $ - -Notes on oskit: RSX-11M V3.1 system on RK05 volumes - - Table of content: - - 1. General remarks - 2. Installation - 3. Usage - -1. General remarks --------------------------------------------------- - - See notes, especially on legal terms, in $RETROBASE/doc/w11a_os_guide.txt - - Also read README_license.txt which is included in the oskit !! - -2. Installation ------------------------------------------------------ - - - A disk set is available from - http://www.retro11.de/data/oc_w11/oskits/rsx11m-31_rkset.tgz - Download, unpack and copy the disk images (*.dsk), e.g. - - cd $RETROBASE/tools/oskit/rsx11m-31_rk - wget http://www.retro11.de/data/oc_w11/oskits/rsx11m-31_rkset.tgz - tar -xzf rsx11m-31_rkset.tgz - -3. Usage ------------------------------------------------------------- - - - Start them in simulator - pdp11 rsx11m-31_rk_boot.scmd - or ONLY IF YOU HAVE A VALID LICENSE on w11a - ti_w11 @rsx11m-31_rk_boot.tcl - where is the proper option set for the board. - - - Hit in the xterm window to connect to simh or backend server. - The boot dialog in the console xterm window will look like - (required input is in {..}, with {} denoting a carriage return: - - RSX-11M V3.1 BL22 65408K MAPPED - >RED DK0:=SY0: - >RED DK0:=LB0: - >MOU DK0:SYSTEM0 - >@[1,2]STARTUP - - That RSX shows '65408K' is a bug in V3.1. It should be 1920K' the - size of accessible memory in words. For configurations with 1 MByte - and below the correct value is displayed, above a wrong one. - - This os version was released in December 1977, so it's no suprise - that it is not y2k ready. So enter a date before prior to 2000. - - >* PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY) [S]: {<.. see above ..>} - >TIM 17:18 12-may-83 - >; - >RUN ERRLOG - > - ;ERL -- ERROR LOG INITIALIZED - >MOU DK1:SYSTEM1 - >; - >INS DK1:[1,54]BIGMAC/PAR=GEN - >INS DK1:[1,54]BIGTKB/PAR=GEN - >INS DK1:[1,54]CDA - >INS DK1:[1,54]DSC/PAR=GEN - >INS DK1:[1,54]EDT/PAR=GEN - >INS DK1:[1,54]FLX - >INS DK1:[1,54]FOR - >INS DK1:[1,54]FTB - >INS DK1:[1,54]LBR - >INS DK1:[1,54]PSE - >INS DK1:[1,54]RNO - >INS DK1:[1,54]SRD - >INS DK1:[1,54]SYE - >; - >INS DK1:[1,54]TEC - >INS DK1:[1,54]TEC/TASK=...MAK - >INS DK1:[1,54]TEC/TASK=...MUN - >; - >INS DK1:[1,54]VTEC - >; - >; - >SET /UIC=[1,6] - >PSE = - >SET /UIC=[200,200] - >; - >ACS DK1:/BLKS=512. - >; - >@ - > - - Now you are at the MCR prompt and can exercise the system. - - At the end is important to shutdown properly with a 'run $shutup'. - The simululaor (or the rlink backend) can be stopped when the - CPU has halted. diff --git a/tools/oskit/rsx11m-40_rk/README.md b/tools/oskit/rsx11m-40_rk/README.md new file mode 100644 index 00000000..d008a3f3 --- /dev/null +++ b/tools/oskit/rsx11m-40_rk/README.md @@ -0,0 +1,93 @@ +## Notes on oskit: RSX-11M V4.0 system on RK05 volumes + +See notes in [w11a_os_guide.md](../../../doc/w11a_os_guide.md) on + 1. I/O emulation setup + 2. FPGA Board setup + 3. Rlink and Backend Server setup + 4. 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/rsx11m-40_rkset.tgz + +Download, unpack and copy the disk images (*.dsk), e.g. +``` + cd $RETROBASE/tools/oskit/rsx11m-40_rk + wget http://www.retro11.de/data/oc_w11/oskits/rsx11m-40_rkset.tgz + tar -xzf rsx11m-40_rkset.tgz +``` + +### Usage + +- Start disk image in simulator + ``` + pdp11 rsx11m-40_rk_boot.scmd + ``` + + or **ONLY IF YOU HAVE A VALID LICENSE** on w11a + ``` + ti_w11 @rsx11m-40_rk_boot.tcl + ``` + + where `` is the proper option set for the board. + +- Hit `` in the `xterm` window to connect to simh or backend server. + The boot dialog in the console `xterm` window will look like + (required input is in `{..}`, with `{}` denoting a carriage return: + ``` + RSX-11M V4.0 BL32 1920.K MAPPED + >RED DK:=SY: + >RED DK:=LB: + >MOU DK:SYSM40RKV0 + >@DK:[1,2]STARTUP + ``` + + This os version was released in November 1981, so it's no suprise + that it is not y2k ready. So enter a date before prior to 2000. + ``` + >* PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY) [S]: {<.. see above ..>} + >TIM 18:17 12-may-83 + >* ENTER LINE WIDTH OF THIS TERMINAL [D D:132.]: {} + >SET /BUF=TI:132. + >ACS SY:/BLKS=512. + >CLI /INIT=DCL/TASK=...DCL + >; + >; mount 2nd system disk + >; + >mou dk1:SYSM40RKV1/pub + >; + >; installing tasks from 2nd system disk + >; + >INS DK1:$BRU + >INS DK1:$DMP + >INS DK1:$DSC + >INS DK1:$EDT + >INS DK1:$FLX + >INS DK1:$K11RSX/TASK=...KER + >INS DK1:$LBR + >INS DK1:$MAC + >INS DK1:$RMD + >INS DK1:$SLP + >INS DK1:$SRD + >INS DK1:$TEC + >INS DK1:$TEC/TASK=...MAK + >INS DK1:$TKB + >INS DK1:$VFY + >INS DK1:$VTEC + >@ + > + ``` + + Now you are at the MCR prompt and can exercise the system. + + You can also login on the 2nd DL11, possible accounts are + ``` + >hel 1,1 ; password root + >hel 200,201 ; password test + ``` + + At the end it is important to shutdown properly with a `run $shutup`. + The simululaor (or the rlink backend) can be stopped when the + CPU has halted. diff --git a/tools/oskit/rsx11m-40_rk/README_rsx11m-40_rkset.txt b/tools/oskit/rsx11m-40_rk/README_rsx11m-40_rkset.txt deleted file mode 100644 index c53bb948..00000000 --- a/tools/oskit/rsx11m-40_rk/README_rsx11m-40_rkset.txt +++ /dev/null @@ -1,88 +0,0 @@ -# $Id: README_rsx11m-40_rkset.txt 680 2015-05-14 13:29:46Z mueller $ - -Notes on oskit: RSX-11M V4.0 system on RK05 volumes - - Table of content: - - 1. General remarks - 2. Installation - 3. Usage - -1. General remarks --------------------------------------------------- - - See notes, especially on legal terms, in $RETROBASE/doc/w11a_os_guide.txt - - Also read README_license.txt which is included in the oskit !! - -2. Installation ------------------------------------------------------ - - - A disk set is available from - http://www.retro11.de/data/oc_w11/oskits/rsx11m-40_rkset.tgz - Download, unpack and copy the disk images (*.dsk), e.g. - - cd $RETROBASE/tools/oskit/rsx11m-40_rk - wget http://www.retro11.de/data/oc_w11/oskits/rsx11m-40_rkset.tgz - tar -xzf rsx11m-40_rkset.tgz - -3. Usage ------------------------------------------------------------- - - - Start them in simulator - pdp11 rsx11m-40_rk_boot.scmd - or ONLY IF YOU HAVE A VALID LICENSE on w11a - ti_w11 @rsx11m-40_rk_boot.tcl - where is the proper option set for the board. - - - Hit in the xterm window to connect to simh or backend server. - The boot dialog in the console xterm window will look like - (required input is in {..}, with {} denoting a carriage return: - - RSX-11M V4.0 BL32 1920.K MAPPED - >RED DK:=SY: - >RED DK:=LB: - >MOU DK:SYSM40RKV0 - >@DK:[1,2]STARTUP - - This os version was released in November 1981, so it's no suprise - that it is not y2k ready. So enter a date before prior to 2000. - - >* PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY) [S]: {<.. see above ..>} - >TIM 18:17 12-may-83 - >* ENTER LINE WIDTH OF THIS TERMINAL [D D:132.]: {} - >SET /BUF=TI:132. - >ACS SY:/BLKS=512. - >CLI /INIT=DCL/TASK=...DCL - >; - >; mount 2nd system disk - >; - >mou dk1:SYSM40RKV1/pub - >; - >; installing tasks from 2nd system disk - >; - >INS DK1:$BRU - >INS DK1:$DMP - >INS DK1:$DSC - >INS DK1:$EDT - >INS DK1:$FLX - >INS DK1:$K11RSX/TASK=...KER - >INS DK1:$LBR - >INS DK1:$MAC - >INS DK1:$RMD - >INS DK1:$SLP - >INS DK1:$SRD - >INS DK1:$TEC - >INS DK1:$TEC/TASK=...MAK - >INS DK1:$TKB - >INS DK1:$VFY - >INS DK1:$VTEC - >@ - > - - Now you are at the MCR prompt and can exercise the system. - - You can also login on the 2nd DL11, possible accounts are - >hel 1,1 ; password root - >hel 200,201 ; password test - - At the end it is important to shutdown properly with a 'run $shutup'. - The simululaor (or the rlink backend) can be stopped when the - CPU has halted. diff --git a/tools/oskit/rsx11mp-30_rp/README.md b/tools/oskit/rsx11mp-30_rp/README.md new file mode 100644 index 00000000..0e4f59f3 --- /dev/null +++ b/tools/oskit/rsx11mp-30_rp/README.md @@ -0,0 +1,84 @@ +## Notes on oskit: RSX-11Mplus V3.0 system on RP06 volumes + +### General remarks + +See notes in [w11a_os_guide.md](../../../doc/w11a_os_guide.md) on + 1. I/O emulation setup + 2. FPGA Board setup + 3. Rlink and Backend Server setup + 4. 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/rsx11mp-30_rpset.tgz + +Download, unpack and copy the disk images (*.dsk), e.g. +```bash + cd $RETROBASE/tools/oskit/rsx11mp-30_rp + wget http://www.retro11.de/data/oc_w11/oskits/rsx11mp-30_rpset.tgz + tar -xzf rsx11mp-30_rpset.tgz +``` + +### Usage + +- Start disk image in simulator + ``` + pdp11 rsx11mp-30_rp_boot.scmd + ``` + + or **ONLY IF YOU HAVE A VALID LICENSE** on w11a + ``` + ti_w11 @rsx11mp-30_rp_boot.tcl + ``` + + where `` is the proper option set for the board. + +- Hit `` in the `xterm` window to connect to simh or backend server. + The boot dialog in the console xterm window will look like + (required input is in `{..}`, with `{}` denoting a carriage return: + ``` + RSX-11M-PLUS V3.0 BL24 1920.KW System:"RSXMPL" + >RED DB:=SY: + >RED DB:=LB: + >RED DB:=SP: + >MOU DB:"RSX11MPBL24" + >@DB:[1,2]STARTUP + >; ... some comments ... + ``` + + This os version was released in July 1985, so it's no suprise + that it is not y2k ready. So enter a date before prior to 2000. + ``` + >* Please enter time and date (HH:MM DD-MMM-YY) [S]: {<.. see above ..>} + + >TIME 12:42 14-MAY-95 + >ACS SY:/BLKS=1024. + >CON ONLINE ALL + >ELI /LOG/LIM + >CLI /INIT=DCL/CTRLC + >INS LB:[1,1]RMSRESAB.TSK/RON=YES/PAR=GEN + >INS LB:[1,1]RMSLBL.TSK/RON=YES/PAR=GEN + >INS LB:[1,1]RMSLBM.TSK/RON=YES/PAR=GEN + >INS $QMGCLI + >INS $QMGCLI/TASK=...PRI + >INS $QMGCLI/TASK=...SUB + >QUE /START:QMG + >INS $QMGPRT/TASK=PRT.../SLV=NO + >QUE LP0:/CR/NM + >START/ACCOUNTING + >CON ESTAT LP0: + >QUE LP0:/SP/FL:2/LOWER/FO:0 + >QUE BAP0:/BATCH + >QUE LP0:/AS:PRINT + >QUE BAP0:/AS:BATCH + >@ + > + ``` + + Now you are at the MCR prompt and can exercise the system. + + At the end it is important to shutdown properly with a `run $shutup`. + The simululaor (or the rlink backend) can be stopped when the + CPU has halted. diff --git a/tools/oskit/rsx11mp-30_rp/README_rsx11mp-30_rpset.txt b/tools/oskit/rsx11mp-30_rp/README_rsx11mp-30_rpset.txt deleted file mode 100644 index 28391910..00000000 --- a/tools/oskit/rsx11mp-30_rp/README_rsx11mp-30_rpset.txt +++ /dev/null @@ -1,79 +0,0 @@ -# $Id: README_rsx11mp-30_rpset.txt 680 2015-05-14 13:29:46Z mueller $ - -Notes on oskit: RSX-11Mplus V3.0 system on RP06 volumes - - Table of content: - - 1. General remarks - 2. Installation - 3. Usage - -1. General remarks --------------------------------------------------- - - See notes, especially on legal terms, in $RETROBASE/doc/w11a_os_guide.txt - - Also read README_license.txt which is included in the oskit !! - -2. Installation ------------------------------------------------------ - - - A disk set is available from - http://www.retro11.de/data/oc_w11/oskits/rsx11mp-30_rpset.tgz - Download, unpack and copy the disk images (*.dsk), e.g. - - cd $RETROBASE/tools/oskit/rsx11mp-30_rp - wget http://www.retro11.de/data/oc_w11/oskits/rsx11mp-30_rpset.tgz - tar -xzf rsx11mp-30_rpset.tgz - -3. Usage ------------------------------------------------------------- - - - Start them in simulator - pdp11 rsx11mp-30_rp_boot.scmd - or ONLY IF YOU HAVE A VALID LICENSE on w11a - ti_w11 @rsx11mp-30_rp_boot.tcl - where is the proper option set for the board. - - - Hit in the xterm window to connect to simh or backend server. - The boot dialog in the console xterm window will look like - (required input is in {..}, with {} denoting a carriage return: - - RSX-11M-PLUS V3.0 BL24 1920.KW System:"RSXMPL" - >RED DB:=SY: - >RED DB:=LB: - >RED DB:=SP: - >MOU DB:"RSX11MPBL24" - >@DB:[1,2]STARTUP - >; ... some comments ... - - This os version was released in July 1985, so it's no suprise - that it is not y2k ready. So enter a date before prior to 2000. - - >* Please enter time and date (HH:MM DD-MMM-YY) [S]: {<.. see above ..>} - - >TIME 12:42 14-MAY-95 - >ACS SY:/BLKS=1024. - >CON ONLINE ALL - >ELI /LOG/LIM - >CLI /INIT=DCL/CTRLC - >INS LB:[1,1]RMSRESAB.TSK/RON=YES/PAR=GEN - >INS LB:[1,1]RMSLBL.TSK/RON=YES/PAR=GEN - >INS LB:[1,1]RMSLBM.TSK/RON=YES/PAR=GEN - >INS $QMGCLI - >INS $QMGCLI/TASK=...PRI - >INS $QMGCLI/TASK=...SUB - >QUE /START:QMG - >INS $QMGPRT/TASK=PRT.../SLV=NO - >QUE LP0:/CR/NM - >START/ACCOUNTING - >CON ESTAT LP0: - >QUE LP0:/SP/FL:2/LOWER/FO:0 - >QUE BAP0:/BATCH - >QUE LP0:/AS:PRINT - >QUE BAP0:/AS:BATCH - >@ - > - - Now you are at the MCR prompt and can exercise the system. - - At the end it is important to shutdown properly with a 'run $shutup'. - The simululaor (or the rlink backend) can be stopped when the - CPU has halted. diff --git a/tools/oskit/rt11-40_rk/README.md b/tools/oskit/rt11-40_rk/README.md new file mode 100644 index 00000000..b1c64db0 --- /dev/null +++ b/tools/oskit/rt11-40_rk/README.md @@ -0,0 +1,66 @@ +## Notes on oskit: RT-11 V4.0 system on RK05 volumes + +### General remarks + +See notes in [w11a_os_guide.md](../../../doc/w11a_os_guide.md) on + 1. I/O emulation setup + 2. FPGA Board setup + 3. Rlink and Backend Server setup + 4. 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. +```bash + 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.scmd + ``` + + or **ONLY IF YOU HAVE A VALID LICENSE** on w11a + ``` + ti_w11 @rt11-40_rk_boot.tcl + ``` + + where `` is the proper option set for the board. + +- Hit `` in the xterm window to connect to simh or backend server. + The boot dialog in the console `xterm` window will look like + (required input is in `{..}`, with `{}` 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 `halt` or `shutdown` command, just terminate the + simulator or backend server session. diff --git a/tools/oskit/rt11-40_rk/README_rt11-40_rkset.txt b/tools/oskit/rt11-40_rk/README_rt11-40_rkset.txt deleted file mode 100644 index 81d75f03..00000000 --- a/tools/oskit/rt11-40_rk/README_rt11-40_rkset.txt +++ /dev/null @@ -1,62 +0,0 @@ -# $Id: README_rt11-40_rkset.txt 680 2015-05-14 13:29:46Z mueller $ - -Notes on oskit: RT-11 V4.0 system on RK05 volumes - - Table of content: - - 1. General remarks - 2. Installation - 3. Usage - -1. General remarks --------------------------------------------------- - - See notes, especially on legal terms, in $RETROBASE/doc/w11a_os_guide.txt - - Also read README_license.txt which is included in the oskit !! - -2. Installation ------------------------------------------------------ - - - A disk set is available from - http://www.retro11.de/data/oc_w11/oskits/rsx11m-31_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 - -3. Usage ------------------------------------------------------------- - - - Start them in simulator - pdp11 rt11-40_rk_boot.scmd - or ONLY IF YOU HAVE A VALID LICENSE on w11a - ti_w11 @rt11-40_rk_boot.tcl - where is the proper option set for the board. - - - Hit in the xterm window to connect to simh or backend server. - The boot dialog in the console xterm window will look like - (required input is in {..}, with {} 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 'halt' or 'shutdown' command, just terminate the - simulator or backend server session. diff --git a/tools/oskit/rt11-53_rl/README_rt11-53_rlset.txt b/tools/oskit/rt11-53_rl/README.md similarity index 54% rename from tools/oskit/rt11-53_rl/README_rt11-53_rlset.txt rename to tools/oskit/rt11-53_rl/README.md index 278b4672..0badc77d 100644 --- a/tools/oskit/rt11-53_rl/README_rt11-53_rlset.txt +++ b/tools/oskit/rt11-53_rl/README.md @@ -1,40 +1,44 @@ -# $Id: README_rt11-53_rlset.txt 699 2015-07-05 21:37:26Z mueller $ +##Notes on oskit: RT-11 V5.3 system on a RL02 volume -Notes on oskit: RT-11 V5.3 system on a RL02 volume +### General remarks - Table of content: +See notes in [w11a_os_guide.md](../../../doc/w11a_os_guide.md) on + 1. I/O emulation setup + 2. FPGA Board setup + 3. Rlink and Backend Server setup + 4. Legal terms - 1. General remarks - 2. Installation - 3. Usage +**Also read README_license.txt which is included in the oskit !!** -1. General remarks --------------------------------------------------- - - See notes, especially on legal terms, in $RETROBASE/doc/w11a_os_guide.txt - - Also read README_license.txt which is included in the oskit !! - -2. Installation ------------------------------------------------------ - - - A disk set is available from - http://www.retro11.de/data/oc_w11/oskits/rt11-53_rlset.tgz - Download, unpack and copy the disk images (*.dsk), e.g. +### Installation +A disk set is available from +http://www.retro11.de/data/oc_w11/oskits/rt11-53_rlset.tgz +Download, unpack and copy the disk images (*.dsk), e.g. +```bash cd $RETROBASE/tools/oskit/rt11-53_rl wget http://www.retro11.de/data/oc_w11/oskits/rt11-53_rlset.tgz tar -xzf rt11-53_rlset.tgz +``` -3. Usage ------------------------------------------------------------- +### Usage - - Start them in simulator +- Start disk image in simulator + ``` pdp11 rt11-53_rl_boot.scmd - or ONLY IF YOU HAVE A VALID LICENSE on w11a - ti_w11 @rt11-53_rl_boot.tcl - where is the proper option set for the board. + ``` - - Hit in the xterm window to connect to simh or backend server. - The boot dialog in the console xterm window will look like - (required input is in {..}, with {} denoting a carriage return: + or **ONLY IF YOU HAVE A VALID LICENSE** on w11a + ``` + ti_w11 @rt11-53_rl_boot.tcl + ``` + + where `` is the proper option set for the board. + +- Hit `` in the `xterm` window to connect to simh or backend server. + The boot dialog in the console `xterm` window will look like + (required input is in `{..}`, with `{}` denoting a carriage return: + ``` RT-11FB V05.03 @@ -64,8 +68,9 @@ Notes on oskit: RT-11 V5.3 system on a RL02 volume Release Notes. V5NOTE.TXT can be TYPED or PRINTED. . + ``` - Now you are at the RT-11 prompt and can exercise the system. + Now you are at the RT-11 prompt and can exercise the system. - There is no 'halt' or 'shutdown' command, just terminate the - simulator or backend server session. + There is no `halt` or `shutdown` command, just terminate the + simulator or backend server session. diff --git a/tools/oskit/unix-v5_rk/README.md b/tools/oskit/unix-v5_rk/README.md new file mode 100644 index 00000000..1ec68033 --- /dev/null +++ b/tools/oskit/unix-v5_rk/README.md @@ -0,0 +1,63 @@ +## Notes on oskit: Unix V5 system on RK05 volumes + +### General remarks +See notes in [w11a_os_guide.md](../../../doc/w11a_os_guide.md) on + 1. I/O emulation setup + 2. FPGA Board setup + 3. Rlink and Backend Server setup + 4. Legal terms + +### Installation +A disk set is available from +http://www.retro11.de/data/oc_w11/oskits/unix_v5_rkset.tgz + +Download, unpack and copy the disk images (*.dsk), e.g. +```bash + + cd $RETROBASE/tools/oskit/unix-v5_rk + wget http://www.retro11.de/data/oc_w11/oskits/unix_v5_rkset.tgz + tar -xzf unix_v5_rkset.tgz +``` + +### Usage + +- Start backend server and boot system + (see section Rlink in [w11a_os_guide.md](../../../doc/w11a_os_guide.md)) + ``` + boot script: uv5_rk_boot.tcl + example: ti_w11 @uv5_rk_boot.tcl + where is the proper option set for the board. + ``` + +- Hit `` in the xterm window to connect to backend server. + The boot dialog in the console `xterm` window will look like + (required input is in `{..}`, with `{}` denoting a carriage return: + ``` + @{unix} + + login: {root} + ``` + + Now you are at the shell prompt and can exercise the system, e.g. + ``` + # {ls -al} + total 62 + drwxr-xr-x 9 bin 160 Jan 29 16:14 . + drwxr-xr-x 9 bin 160 Jan 29 16:14 .. + drwxr-xr-x 2 bin 944 Nov 26 18:13 bin + drwxr-xr-x 2 bin 80 Nov 26 18:13 dev + drwxr-xr-x 2 bin 240 Mar 21 12:07 etc + drwxr-xr-x 2 bin 224 Nov 26 18:13 lib + drwxr-xr-x 2 bin 32 Nov 26 18:13 mnt + drwxrwxrwx 2 bin 32 Nov 26 18:13 tmp + -rwxrwxrwx 1 bin 25802 Mar 21 12:07 unix + drwxr-xr-x 14 bin 224 Nov 26 18:13 usr + ``` + + There is no `halt` or `shutdown` command, just terminate the server + session with a + ``` + tirri_exit + ``` + + command. The disks aren't cached, so no need to sync either. diff --git a/tools/oskit/unix-v5_rk/README_unix_v5_rkset.txt b/tools/oskit/unix-v5_rk/README_unix_v5_rkset.txt deleted file mode 100644 index 025967cc..00000000 --- a/tools/oskit/unix-v5_rk/README_unix_v5_rkset.txt +++ /dev/null @@ -1,65 +0,0 @@ -# $Id: README_unix_v5_rkset.txt 680 2015-05-14 13:29:46Z mueller $ - -Notes on oskit: Unix V5 system on RK05 volumes - - Table of content: - - 1. General remarks - 2. Installation - 3. Usage - -1. General remarks --------------------------------------------------- - - See notes on - - 1. I/O emulation setup - 2. FPGA Board setup - 3. Rlink and Backend Server setup - 4. Legal terms - - in $RETROBASE/doc/w11a_os_guide.txt - -2. Installation ------------------------------------------------------ - - - A disk set is available from - http://www.retro11.de/data/oc_w11/oskits/unix_v5_rkset.tgz - Download, unpack and copy the disk images (*.dsk), e.g. - - cd $RETROBASE/tools/oskit/unix-v5_rk - wget http://www.retro11.de/data/oc_w11/oskits/unix_v5_rkset.tgz - tar -xzf unix_v5_rkset.tgz - -3. Usage ------------------------------------------------------------- - - - Start backend server and boot system (see section 3 in w11a_os_guide.txt) - boot script: uv5_rk_boot.tcl - example: ti_w11 @uv5_rk_boot.tcl - where is the proper option set for the board. - - - Hit in the xterm window to connect to backend server. - The boot dialog in the console xterm window will look like - (required input is in {..}, with {} denoting a carriage return: - - @{unix} - - login: {root} - - Now you are at the shell prompt and can exercise the system, e.g. - - # {ls -al} - total 62 - drwxr-xr-x 9 bin 160 Jan 29 16:14 . - drwxr-xr-x 9 bin 160 Jan 29 16:14 .. - drwxr-xr-x 2 bin 944 Nov 26 18:13 bin - drwxr-xr-x 2 bin 80 Nov 26 18:13 dev - drwxr-xr-x 2 bin 240 Mar 21 12:07 etc - drwxr-xr-x 2 bin 224 Nov 26 18:13 lib - drwxr-xr-x 2 bin 32 Nov 26 18:13 mnt - drwxrwxrwx 2 bin 32 Nov 26 18:13 tmp - -rwxrwxrwx 1 bin 25802 Mar 21 12:07 unix - drwxr-xr-x 14 bin 224 Nov 26 18:13 usr - - There is no 'halt' or 'shutdown' command, just terminate the server - session with a - tirri_exit - command. The disks aren't cached, so no need to sync either. diff --git a/tools/oskit/xxdp_rl/README_xxdp_rlset.txt b/tools/oskit/xxdp_rl/README.md similarity index 52% rename from tools/oskit/xxdp_rl/README_xxdp_rlset.txt rename to tools/oskit/xxdp_rl/README.md index cace384f..65918244 100644 --- a/tools/oskit/xxdp_rl/README_xxdp_rlset.txt +++ b/tools/oskit/xxdp_rl/README.md @@ -1,25 +1,25 @@ -# $Id: README_xxdp_rlset.txt 680 2015-05-14 13:29:46Z mueller $ +## Notes on oskit: XXDP V2.2 and V2.5 system on RL02 volumes -Notes on oskit: XXDP V2.2 and V2.5 system on RL02 volumes +### General remarks - Table of content: +See notes in [w11a_os_guide.md](../../../doc/w11a_os_guide.md) on + 1. I/O emulation setup + 2. FPGA Board setup + 3. Rlink and Backend Server setup + 4. Legal terms - 1. General remarks - 2. Installation - 3. Usage +**Also read [README_license.txt](README_license.txt) !!** -1. General remarks --------------------------------------------------- - - See notes, especially on legal terms, in README_license.txt !! - -2. Installation ------------------------------------------------------ - - - A disk images for XXDP V2.2 and V2.5 are available from bitsavers - http://bitsavers.trailing-edge.com/bits/DEC/pdp11/discimages/rl02 +### Installation +A disk images for XXDP V2.2 and V2.5 are available from bitsavers +http://bitsavers.trailing-edge.com/bits/DEC/pdp11/discimages/rl02 +``` xxdp22.rl02.gz xxdp25.rl02.gz - Download, unpack and copy the disk images (*.dsk), e.g. +``` +Download, unpack and copy the disk images (*.dsk), e.g. +```bash cd $RETROBASE/tools/oskit/xxdp_rl disk_path=http://bitsavers.trailing-edge.com/bits/DEC/pdp11/discimages @@ -28,22 +28,28 @@ Notes on oskit: XXDP V2.2 and V2.5 system on RL02 volumes gunzip -c xxdp22.rl02.gz > xxdp22.dsk gunzip -c xxdp25.rl02.gz > xxdp25.dsk +``` -3. Usage ------------------------------------------------------------- +### Usage - - Start them in simulator +- Start disk in simulator + ``` pdp11 xxdp22_rl_boot.scmd pdp11 xxdp25_rl_boot.scmd + ``` - or on w11a + or on w11a + ``` ti_w11 @xxdp22_rl_boot.tcl ti_w11 @xxdp25_rl_boot.tcl - where is the proper option set for the board. + ``` - - Hit in the xterm window to connect to simh or backend server. - The boot dialog in the console xterm window will look like - (required input is in {..}, with {} denoting a carriage return. + where `` is the proper option set for the board. +- Hit `` in the `xterm` window to connect to simh or backend server. + The boot dialog in the console `xterm` window will look like + (required input is in `{..}`, with `{}` denoting a carriage return. + ``` XXDP V2.2 boot dialog: CHMDLD0 XXDP+ DL MONITOR @@ -56,9 +62,10 @@ Notes on oskit: XXDP V2.2 and V2.5 system on RL02 volumes THIS IS XXDP+. TYPE "H" OR "H/L" FOR HELP. . + ``` - XXDP V2.5 boot dialog: - + XXDP V2.5 boot dialog: + ``` BOOTING UP XXDP-XM EXTENDED MONITOR XXDP-XM EXTENDED MONITOR - XXDP V2.5 @@ -80,6 +87,7 @@ Notes on oskit: XXDP V2.2 and V2.5 system on RL02 volumes --> will list the files . {R EKBAD0} --> will run the 'PDP 11/70 cpu diagnostic part 1' + ``` - There is no 'halt' or 'shutdown' command, just terminate the - simulator or backend server session. + There is no `halt` or `shutdown` command, just terminate the + simulator or backend server session. diff --git a/tools/oskit/xxdp_rl/README_license.txt b/tools/oskit/xxdp_rl/README_license.txt index 503e8fd1..d054f28d 100644 --- a/tools/oskit/xxdp_rl/README_license.txt +++ b/tools/oskit/xxdp_rl/README_license.txt @@ -6,4 +6,4 @@ the software was provided with the system or brought to the customer site by a Field Service representative. Bottom line is that there is certainly a copyright on the xxdp software, -but as it seems not a license. +but it seems that there is no license restricting the usage.