Some PDP-11 boot ROMs include a utility to display a memory map. This can be useful to confirm that the controller CSR address decoding has been configured correctly as desired. For example the KDJ11-D/S M7554 "MAP" command will display a memory map as shown in the example below.
The "17772150 - 17772152 DU" line indicates that the MSCP disk CSR was found at the standard address for the first MSCP controller and the "17774500 - 17774502 MU" line indicates that the TMSCP tape CSR was found at the standard address for the first TMSCP controller. In this example both the MSCP controller and the TMSCP controller were the same physical CMD CQD-200/TM controller.
9 8 7 6 5 4 3 2 1 Commands are Help, Boot, List, Map, Test and Wrap. Type a command then press the RETURN key: MAP KDJ11-D/S ROM V2.0 3584 K Bytes 00000000 - 05777776 1536 KB CSR = 17772100 06000000 - 15777776 2048 KB CSR = 17772102 Press the RETURN key to continue: 17772100 - 17772102 MCSR 17772150 - 17772152 DU 17772200 - 17772216 SIPDR0-7 17772220 - 17772236 SDPDR0-7 17772240 - 17772256 SIPAR0-7 17772260 - 17772276 SDPAR0-7 17772300 - 17772316 KIPDR0-7 17772320 - 17772336 KDPDR0-7 17772340 - 17772356 KIPAR0-7 17772360 - 17772376 KDPAR0-7 17772516 MMR3 17773000 - 17773776 CPU ROM 17774500 - 17774502 MU 17776500 - 17776506 SLU1 17777520 NR 17777546 LTC CSR, BEVENT = 1 17777560 - 17777566 SLU0 Press the RETURN key to continue: 17777572 - 17777576 MMR0,1,2 17777600 - 17777616 UIPDR0-7 17777620 - 17777636 UDPDR0-7 17777640 - 17777656 UIPAR0-7 17777660 - 17777676 UDPAR0-7 17777750 - 17777752 MREG,Hit/Miss 17777766 CPUER 17777772 PIRQ 17777776 PSW Commands are Help, Boot, List, Map, Test and Wrap. Type a command then press the RETURN key: The CMD CQD-200/TM contains an on-board utility which can be accessed through the ODT console. To access the on-board utility halt the processor and at the ODT prompt enter the magic number "123456" at the <CSR base address + 2>, then the magic number "100" again at the <CSR base address + 2>, then begin execution at 5000.
In the example below the on-board utility is entered and used to display the list of SCSI devices attached to confirm that the CQD-200/TM correctly sees a hard drive attached at SCSI ID 0 and an Exabyte 8200 8MM tape drive attached at SCSI ID 4.
@17772152/005400 123456 @/001000 100 @5000G SCSI UTILITY PROGRAM DISK TAPE 1 = 772150 A = 774500 2 = 760334 B = 760404 3 = 760354 C = 760444 4 = 760374 D = 760504 5 = 760340 E = 760544 6 = 760344 F = 760410 7 = 760350 G = 760450 8 = 760360 H = 760454 SELECT CSR ADDRESS 1 MAIN MENU: CSR = 772150 1 = BOOT DRIVE 2 = CONFIGURE LUN (Logical Unit Number) OFFSET 3 = FORMAT DRIVE 4 = QUALIFY DRIVE 5 = MANUAL REPLACE BAD SECTORS 6 = READ, WRITE, AND VERIFY TEST 7 = ADDITIONAL UTILITIES SELECT OPTION : 7 ADDITIONAL UTILITIES SN = 0 D = DISPLAY SCSI DEVICES ATTACHED S = SEND SCSI COMMAND TO THE DEVICE T = TEST SCSI DEVICE R = FORMAT RCT BLOCK SELECT OPTION ? D SCSI DEVICES DV0 SCSI ID 0 LUN 0 HP C3725S 5153 DV1 SCSI ID 1 LUN 0 OFFLINE DV2 SCSI ID 2 LUN 0 OFFLINE DV3 SCSI ID 3 LUN 0 OFFLINE DV4 SCSI ID 4 LUN 0 EXABYTE EXB-8200 2618 DV5 SCSI ID 5 LUN 0 OFFLINE DV6 SCSI ID 6 LUN 0 OFFLINE DV7 SCSI ID 7 HOST ADAPTER The on-board utility can also be used to boot from either a SCSI disk or tape. In the example below the tape CSR is selected and then the system is booted from the Exabyte 8200 at SCSI ID 4 as MU0. The boot tape in this example is a 2.11BSD installation tape. Note that the "45Boot" is a 2.11BSD bug which is corrected in patch #433 which will corrects the KDJ11-D/S identification to "53Boot". Note that there is are two other bugs affecting the use of 2.11BSD on a CMD CQD-200/TM. The first bug is that when booting from the installation tape the root filesystem restoration during "tms(0,3)" hangs. As far as I know the cause of that bug and its fix is unknown. The second bug is that if you manage to sucessfully install 2.11BSD on a hard drive attached to a CQD-200/TM using a different tape controller or via other means the MSCP rauboot bootblock does not work with the CQD-200/TM. That 2.11BSD bug is corrected in patch #441.
SCSI UTILITY PROGRAM DISK TAPE 1 = 772150 A = 774500 2 = 760334 B = 760404 3 = 760354 C = 760444 4 = 760374 D = 760504 5 = 760340 E = 760544 6 = 760344 F = 760410 7 = 760350 G = 760450 8 = 760360 H = 760454 SELECT CSR ADDRESS A MAIN MENU: CSR = 774500 1 = BOOT DRIVE 2 = CONFIGURE LUN (Logical Unit Number) OFFSET 3 = TAPE DIAGNOSTIC 4 = ADDITIONAL UTILITIES SELECT OPTION : 1 BOOT DRIVE NUMBER <0 TO 7>: 0 BOOT MU0 . ARE YOU SURE? Y WAIT... 45Boot from tms(0,0,0) at 0174500 : tms(0,1) Boot: bootdev=06001 bootcsr=0174500 disklabel Disk? ra(0,0) 'ra(0,0)' is unlabeled or the label is corrupt. Proceed? [y/n] y d(isplay) D(efault) m(odify) w(rite) q(uit)? D d(isplay) D(efault) m(odify) w(rite) q(uit)? d type: MSCP disk: RA82 label: DEFAULT flags: bytes/sector: 512 sectors/track: 139 tracks/cylinder: 9 sectors/cylinder: 1251 cylinders: 3352 rpm: 3600 drivedata: 0 0 0 0 0 1 partitions: # size offset fstype [fsize bsize] a: 4194057 0 2.11BSD 1024 1024 # (Cyl. 0 - 3352*) d(isplay) D(efault) m(odify) w(rite) q(uit)? The CMD CQD-200/TM appears to be compatible with RSTS/E V10.1. The example console output below shows a KDJ11-D/S booting from a RSTS/E V10.1 installation tape on an Exabyte 8200 tape drive and the beginning of the installation process to a disk drive with both the tape drive and disk drive attached to the same CQD-200/TM controller. 9 8 7 6 5 4 3 2 1 Commands are Help, Boot, List, Map, Test and Wrap. Type a command then press the RETURN key: BOOT MU0 MU0 Performing limited hardware scan. RSTS V10.1 (MU0) INIT V10.1-0L Today's date? 14-DEC-10 Current time? 23:45 Installing RSTS on a new system disk? <Yes> 14-Dec-10 11:45 PM Disk? DU0: Pack ID? RSTS10 Pack cluster size <64>? MFD cluster size <16>? SATT.SYS base <32765>? Pre-extend directories <NO>? PUB, PRI, or SYS <SYS>? [1,1] cluster size <16>? [1,2] cluster size <16>? [1,1] and [1,2] account base <32765>? Date last modified <YES>? New files first <NO>? Read-only <NO>? Patterns <3>? 0 Erase Disk <YES>? NO Proceed (Y or N)? Y 14-Dec-10 11:46 PM Copying required system files Performing limited hardware scan. RSTS V10.1 (DU0) INIT V10.1-0L 14-Dec-10 11:49 PM Starting SYSGEN.SIL . . . Rebooting . . . RSTS V10.1 (DU0) INIT V10.1-0L 14-Dec-10 11:49 PM Creating SWAP.SYS file with minimum size of 136 blocks Memory allocation table: 0K: 00000000 - 00503777 ( 81K) : EXEC 81K: 00504000 - 11777777 (1199K) : USER 1280K: 12000000 - 13777777 ( 256K) : XBUF 1536K: 14000000 - 15777777 ( 256K) : USER 1792K: 16000000 - 17757777 ( 252K) : NXM Memory available to RSTS/E is 1792K words. Creating CRASH.SYS file with minimum size of 1472 blocks 17 devices disabled RSTS/E V10.1-L Software Installation Procedure 14-Dec-10 11:49 PM Please mount the RSTS/E Installation media and enter the name and unit number of the device. Valid device types are: 'MM', 'MS', 'MT', 'MU', 'DM' or 'DL' Restoring required _SY0:[0,1] components |
CMD CQD-200 SCSI >