4e159a04ed
SEL32: Update makefile and SEL32.vsproj file to add IPU device. SEL32: Update README.md file. SEL32: Do a general code cleanup.
123 lines
6.8 KiB
Markdown
123 lines
6.8 KiB
Markdown
|
|
# SEL32 Concept/32 Simulator
|
|
|
|
This is a working simulator for the SEL Concept/32 computer. The current
|
|
version is for the SEL 32/27, 32/67, 32/77, 32/87, 32/97, V6, and V9
|
|
computers. All of the processors except for the 32/77 can run the Gould
|
|
diags. Operational support for the 32/77 computers may be added in the
|
|
future. Additional processors are now supported. The 32/6780, 32/8780,
|
|
32/9780, V6/IPU, and V9/IPU processors with an IPU able to run an
|
|
additional instruction stream. Threads are used so support is provided
|
|
by both Windows and Linux.
|
|
|
|
# SEL Concept/32
|
|
|
|
This simulator is capable of running UTX2.1A, UTX2.1B, MPX 1.5F, MPX 3.4,
|
|
MPX 3.5, MPX 3.6, and SEL diagnostics. Actually any software using the SEL
|
|
instruction set should work. It is capable of creating a disk image for the
|
|
O/S from a UTX or MPX SDT tape. The disk image can be booted, initialized,
|
|
and can run many of the UTX and MPX utilities and programs. Ethernet is
|
|
supported on UTX and will be added to MPX in the future. Eight terminals
|
|
can be used to access MPX or UTX via Telnet port 4747. The sumulator has
|
|
support for excess 64 floating point arithmetic and passes the 32/27 and
|
|
32/67 FP diags. UTX is the SEL version of System V Unix and BSD Unix
|
|
ported to the V6 and V9 processors. UTX utilizes the basemode instruction
|
|
set and a virtual memory system supported by the V6 & V9 CPUs. The IPU is
|
|
also supported by UTX and MPX-32. The system needs further testing to
|
|
solidify the SEL32 simulator code in all of the supported environmenets
|
|
and hardware configurations.
|
|
|
|
# SEL32 installation configuration files in the installs directory:
|
|
|
|
The installs directory contains the simh command files to install and run
|
|
multiple UTX, MPX1X, and MPX3X systems. The install tape images are in
|
|
the tapes directory and created disks are in the dsk directory. The dsk
|
|
and tapes directories are initially missing but will be created during
|
|
the installation. The required tape(s) are read from the repo at
|
|
https://github.com/AZBevier/SEL32-installs when the installation
|
|
simh command file is run. The tapes are tar gzipped files that are
|
|
extracted during the installation. Only the tape(s) required for the
|
|
specific UTX or MPX installation are downloaded. A bootable disk is
|
|
created in the dsk directory. This disk can then be booted and the
|
|
installed operating system executed by using a second simh command file.
|
|
See the README.md file in the install directory for a description of the
|
|
available configurations.
|
|
|
|
# SEL32 test configuration files in the tests directory:
|
|
|
|
The tests directory contains the SEL32 machine diagnostic command file and
|
|
bootable tape. They are used by the simh makefile to test the SEL32
|
|
simulator after it built. All of the instruction set and operating modes
|
|
are validated by the diagnostic. There is a pass/failure indication from
|
|
the diagnostic. The command file sel32_test.ini is used by the makefile.
|
|
The command file diag.ini can be run at any time by the user to rerun the
|
|
diagnostics. There is an example of the initial configuration file (ICL)
|
|
used by the diagnostic. The machine configuration is loaded by the diag
|
|
or the UTX or MPX operating system at boot time. See the MPX manuals at
|
|
bitsavers.org/pdf/sel/sel32_mpx for using MPX 1X or 3X.
|
|
|
|
#sel32_test.ini - diag.tap; type "../sel32_test.ini" or run from makefile.
|
|
Auto run by sel32 makefile to validate build or can be run at any time
|
|
to validate system functionality.
|
|
|
|
#diag.ini - diag.tap; type "../sel32 diag.ini" to run.
|
|
This is the SEL32 memory diagnostic that validates the SEL32 instruction
|
|
set and memory management sumulated hardware. Any errors are reported
|
|
to the terminal. Different cpu models can be configured to test various
|
|
cpu model features.
|
|
|
|
Available Level One Diagnostic boot tape in tests directory:
|
|
diag.ini - command file to start diags. Type "../sel32 diag.ini"
|
|
diag.tap - bootable level one diagnostic tape w/auto testing.
|
|
Set cpu type to 32/27, 32/67, 32/87, 32/97, V6 or V9. All
|
|
cpu models now run all diagnostics provided on the
|
|
diagnostic tape. Running DEXP stand alone causes input
|
|
to stop after a few characters are entered. More testing
|
|
is still required.
|
|
|
|
CV.CSL - Firmware control diag. Disabled in auto testing.
|
|
CV.CP1 - CPU diag part 1 runs OK.
|
|
CV.CP2 - CPU diag part 2 runs OK.
|
|
CV.CP3 - CPU diag part 3 runs OK.
|
|
CV.EAD - Effective address diag runs OK.
|
|
CV.BRD - Base register instruction diag runs OK
|
|
Not supported on 32/27.
|
|
CV.INT - Interrupt diag runs OK.
|
|
CV.TRP - Traps diag runs OK.
|
|
CV.CMD - Cache/Shadow diag. Disabled in auto testing.
|
|
CN.MMM - Non virtual memory diag runs OK.
|
|
VM.MMM - Virtual memory diag for V6 & V9 runs OK.
|
|
CV.IPT - IPU trap diag. Disabled in auto testing.
|
|
CV.CSD - WCS read/write trap diag. Disabled in auto testing.
|
|
CV.CON - Operators Console runs all tests for all CPUs.
|
|
CV.DXP - Diagnostic executive for level 2 diags. OK in batch.
|
|
67.FPT - Level two floating point diag runs under DXP OK.
|
|
CV.ITD - Level two interval timer diag runs under DXP OK.
|
|
|
|
Set GPR[0] = 0xffffffff before booting from tape to disable the
|
|
auto test and go to the Diagnostic Overlay Loader (DOL>) prompt.
|
|
Testing is extremely difficult without any source for the
|
|
diagnostics. Updates to follow as tests are corrected.
|
|
|
|
# SEL32 tap tools available in the taptools directory:
|
|
|
|
Available tap tools in taptools directory:
|
|
./taptools - set of tools to work with .tap formatted tapes. Also tools
|
|
to convert between MPX and UNIX file formats. See README
|
|
file in the taptools directory and source for descriptions.
|
|
|
|
Other MPX versions support:
|
|
I have recently received some old MPX 3.X save tapes. Using
|
|
these I have been able to hand build a MPX3.6 SDT tape that
|
|
can be used to install MPX3.6. Once installed, the system can
|
|
be used to build a new user SDT tape and install it elsewhere.
|
|
Both based and non-based O/S images can be created. More images
|
|
for installation will be made available in the future as I work
|
|
my way through the save tapes. I still do not have a master SDT
|
|
tape for any of the MPX 1.X or MPX 3.X systems. I have a
|
|
1600/6250 BPI tape drive that can read 9 track tapes and convert
|
|
them to .tap files. If you have a master SDT, I would be very
|
|
thankfull. Please keep looking.
|
|
|
|
James C. Bevier
|
|
01/03/2023
|