Google
 

Trailing-Edge - PDP-10 Archives - BB-L289B-RK - chk11.mem
There is 1 other file named chk11.mem in the archive. Click here to see a list.


+---------------+
! d i g i t a l !   I N T E R O F F I C E  M E M O R A N D U M
+---------------+

                                       Date: 19-February-82
                                       From: TSG/NCSS
                                       Loc:  MR1-2/H22
                                       Ext:  HOTLINE  5911


Subj:   CHK11

A new and useful feature  has  been  added  to  RSX20F.   At  system
startup you may optionally run CHK11.  CHK11 is a module which makes
some preliminary hardware checks on the  PDP11  Console  Front  End.
The  CHK11  which has been added to RSX20F is a variant of the CHK11
which runs on all other TOPS communication front ends and  works  in
much the same way.  When booting the system from the switch register
CHK11 will run if the switches in the register are set up  properly.
If switch 0 is on and switches 1 and 2 are off CHK11 will run before
KLI begins to initalize the system.  Switches 3 through  15  may  be
set  as desired to control other boot options.  CHK11 is designed to
look for and report certain UNIBUS devices.  When it  runs  it  will
attempt  to address and test the devices that are normally connected
to the RSX20F Console Front End.  CHK11 will print  a  list  of  the
devices  it  finds  and  if any of the hardware tests fail will also
print some error information describing the device and  error  found
on the CTY.

CHK11 is contained in the SAVE utility and is overwritten  when  KLI
is  run.   It cannot be run again unless the system is rebooted from
the switches.  If the system were booted from  the  switch  register
with  bit 0 set and bits 1 and 2 cleared the output on the CTY might
look like the following  example  depending  on  what  devices  were
connected to the UNIBUS.



Initializing RSX-20F
   160000 bytes of memory
     MF11-UP
     KW11-L
   1 DL11-C CTY
   1 DL11-E KLINIK
   2 DL11-E's
   1 CD11
   1 RX11
   1 RH11
   1 DTE20


%  DTE20 #0(Adr = 174400)

       DTE20 is not restricted
                                                              Page 2
Subj:	CHK11


   4 DH11's
   4 DH11-BB's
   1 LP20

RSX-20F VB14-45 13:40 12-Nov-81

        .
        .
        .

and the normal typeout which RSX-20F has always printed would
continue here ie. the KLI typeout etc.





Any error reports will be preceded by a % warning.   The  device  in
error,  its  address  and  a  brief  description of the problem will
follow.  If a device cannot be accessed by the software nothing will
be  printed  on  the CTY about it.  This means that the absence of a
device in the CTY printout is also an  error.   If  the  device  was
reported  previously  and  is  still  connected  physically  but not
currently seen by the software it is  probably  not  functioning  at
all.

The % warning for the non restricted DTE20 in the example  above  is
normal  and  merely reminds you that the DTE20 for the Console Front
End always runs in privileged mode.

If the system has several of the same type of devices  arranged  one
after  the  other  on  the  UNIBUS  and  the  unit  numbers  are not
consecutive CHK11 will report these "holes"  in  the  addressing  as
missing  devices.   For  example  if  there  were eight DH11s in the
system and the software could only access units 0,1,2,and  6,7  then
units  3,4,and 5, would be reported as missing.  This might occur if
the addresses were set up wrong in the hardware or  more  frequently
if the missing units were not functioning properly.

The RH11 is merely addressed so  that  it  may  be  reported  to  be
present.   No testing is done on the device to avoid the possibility
of overwriting data on the disk should the hardware be broken.

More information on the options  available  when  booting  from  the
switch  register  are documented in the TOPS RSX20F SYSTEM REFERENCE
MANUAL.