Vector values contained in device information blocks are the true bus relative vector values. CPU specific biased vector values are produced by the respective vector fetching logic and vector values are limited to 9 bits with <1:0> = 0 as specified in both the Unibus and Qbus documents.
This capability will allow a GDB RSB stub to be created to support dynamic debugging of code running in a simulator.
This capability will also allow a complete front panel emulation system to operate a simulator.
This capability is engaged in a simulator by:
sim> set remote telnet=remoteconsoleport#
sim> set console telnet=consoleport#
sim> set remote master
Master mode will provide a TCP session which accepts SCP commands that allow full control of the simulator.
The goals here being to simplify calling code while getting consistent output delivered everywhere it may be useful.
Modified most places which explicitly used sim_log or merely called printf to now avoid doing that and merely call sim_printf().
This is the results of external KDP development activities. The KDP side done by Timothe Litt and DMC and DUP by Mark Pizzolato
Additionally, other PDP10 updates from Timothe Litt
PDP11/pdp11_io_lib.c: In function 'show_iospace':
PDP11/pdp11_io_lib.c:363: warning: too few arguments for format
PDP10/pdp10_lp20.c: In function 'lp20_set_vfu_type':
PDP10/pdp10_lp20.c:1038: warning: implicit declaration of function
'toupper'
PDP10/pdp10_lp20.c:1121: warning: implicit declaration of function
'isspace'
Show IOSPACE doesn't always get the number of devices right due to device creativity.
o The distinction between UNIT and DEVICE has blurred
o MUX devices merge several physical devices into one device/unit
o Dynamic device sizing has made things more volatile.
This edit solves the problem for SHOW IOSPACE by adding an (optional) word to the DIBs.
The word contains the amount of IO space consumed by each instance of the physical device that's being emulated.
E.G., if it's a DZ11, the device is the DZ11 module, or 8 lines, even though the MUX device may support 32.
This enables SHOW IOSPACE to determine the number of physical devices being emulated, which is what folks need when configuring software. The word may have other uses - in a generic dynamic device sizing routine - which is why the amount of IOSPACE per device was chosen rather than the 'number of physical devices.'
The edit should not make any existing device regress. If the new word (ulnt) is zero (not initialized), SHOW IOSPACE will default to the number of units in the device, or if there's no device (CPUs), 1 as before. If it is present, the number of devices is the calculated as total allocation/allocation-per-device.
The edit updates all the devices that seem to require this treatment, and all the processors that define the UNIBUS/QBUS DIBs.
EA calc of interrupt instructions is an extension by SimH, and performed incorrectly. Indirect references are resolved in current context, not exec mode.
Since the Console Execute emulation takes advantage of this extension, correct it to calculate the EA in EXEC mode.
Add Optical VFU support
Correct some inconsistencies with the hardware.
Add documentation and help.
Flush output file after 10 seconds of idleness to allow external watchers/processors to access entire job without forcing a simulator halt or detach/attach.
Make CR return to column 0, not column 1.
Make DAVFU contents accessible via SHOW.
Initialize RAM structures on power-up reset, but not reboot.
Implement keep-alive and os-requested reload functions of FE.
Preserve HW config flags during (re-) boot.
Allow IPL30 device to interrupt.
Add 18-bit DMA functions.
Implement DMA to/from I/O space.
Optimize DMA memory mapping - once per page, not once per byte.
Teach SHOW IO to report vectors and BR levels as well as CSR addresses.
Add DUP and KDP to Autoconfigure table.
Make the boot ROMs a bit easier to maintain.
Add assertion that the two variants of each are the same size.
Add offsets to the comments so it's easier to see where jumps are going.
The boot rom for tape didn't handle a tapes coming on-line, didn't take
the RH/TM/addresses from the FE. The launcher also didn't handle
autoboot.
Now it does, with the restriction that ITS will only talk to UBA1.
The KS10's 8080 interfaces to the OS thru a small communications region.
The documentation is rather lacking, and the 8080 microcode is difficult
to follow. Many years ago (while still at DEC), I worked it out, and
put definitions into TOPS-10. They're now here, too.
Also, properly initialize the KLINIK communication words and the
keep-alive word.
The KS front end microcode actually reads the wrong alternate HOM block.
Teach the bootstrap to try the wrong one (in case someone counts on
this), but also the correct block.
Implement boot -A to emulate an autoboot - the boot that happens on
power-on or when the boot switch is pressed. No questions, just boots.
The pdp10_rp emulator had several problems:
1) disks are not recognized properly when they come on-line. Same issue
as tapes, but not the same code paths.
2) The bootstrap code did not wait for disks to become ready.
3) The bootstrap code did not take the RH CSR address from the front end
(device). Hence, would not boot if the device address was changed.
4) The bootstrap looked for the second HOM block at block 10 of the
disk. Unfortunately, it read block 8. 10 is decimal; you need all 10
(decimal) fingers.
Fixes:
1) Implement spin-up delay. A device that is attached/re-attached comes
on-line a second later. Replace tests for 'attached' with tests for
up-to-speed.
2) Wait for the drive to become ready after issuing a controller clear.
When it's ready, write the attention summary register to prevent the
un-tended on-line interrupt for looking like an error.
3) Read the RHBASE from main memory instead of storing it there. Teach
the bootstrap command to put it in memory from the dib, as it did with
the unit.
4) Read the correct block.
FILSER now gets on-line and off-line interrupts.
