Update for MVME167 support.

distrib/notes/mvme68k/contents

@@ -1,4 +1,4 @@
-	$NetBSD: contents,v 1.4 1999/01/25 23:34:23 garbled Exp $	
+	$NetBSD: contents,v 1.5 1999/02/20 16:18:10 scw Exp $	
 
 The mvme68k-specific portion of the NetBSD _VER release is found in the
 "mvme68k" subdirectory of the distribution.  That subdirectory is laid
@@ -20,15 +20,15 @@ out as follows:
 .../mvme68k/installation/
                         miniroot/       The miniroot filesystem image.
 
-						netboot/		Two programs needed to boot a
+			netboot/	Two programs needed to boot
-										VME147 kernel over the network.
+					mvme68k kernels over the network.
 
-						tapeimage/      Tape boot programs, and a RAMDISK
+			tapeimage/      Tape boot programs, and a RAMDISK
-									    kernel.
+					kernel.
 
 The NetBSD/mvme68k install distribution contains files that can be
-used to install NetBSD onto a completely "bare" VME147.  The files
+used to install NetBSD onto completely "bare" MVME147 and MVME167 boards.
-in the "mvme68k/installation/*" directories are described below:
+The files in the "mvme68k/installation/*" directories are described below:
 
         miniroot.gz     A gzipped copy of the miniroot filesystem.
                         This image is to be un-gzipped and copied
@@ -38,22 +38,24 @@ in the "mvme68k/installation/*" directories are described below:
                         for installing the miniroot filesystem.
 
         stboot          A tape boot-block, in the form required to
-                        allow 147-Bug to boot from tape. This is the
+                        allow the 1x7-Bug ROM to boot from tape. This
-                        first segment of a boot tape.
+                        is the first segment of a boot tape.
 
         bootst          A copy of the tape boot program, used
                         as the second segment of a boot tape.
 
-        sboot           A copy of the serial boot program. This is
+        sboot           A copy of the MVME147 serial boot program.
-                        necessary if you don't have a tape drive,
+			This is necessary if you don't have a tape
-                        but you _do_ have another system which can
+			drive, but you _do_ have another system which
-                        act as a boot and NFS server. This is also
+			can act as a boot and NFS server. This is also
                         useful if you are installing a diskless
-                        NetBSD/mvme68k system.
+                        NetBSD/MVME147 system.
 
         netboot         A copy of the network boot program. Used
-                        in conjunction with sboot to get your system
+                        in conjunction with sboot on the MVME147 to get
-                        booted over a network.
+                        your system booted over a network. The MVME167
+			can boot this directly using 167Bug's builtin
+			TFTP client.
 
 These files can be used to make a boot tape suitable for installing
 NetBSD/mvme68k. These files can also be used to configure an NFS server
@@ -63,9 +65,9 @@ the NetBSD System onto Useful Media" for instructions on either method.
 .../mvme68k/binary/sets
 
 The NetBSD/mvme68k binary distribution sets contain the binaries which
-comprise the NetBSD _VER release for the VME147. There are seven binary
+comprise the NetBSD _VER release for the MVME1x7 series of boards. There
-distribution sets, and the "security" distribution set. The binary
+are seven binary distribution sets, and the "security" distribution set.
-distribution sets are as follows:
+The binary distribution sets are as follows:
 
         base    The NetBSD/mvme68k _VER base binary distribution. You
                 MUST install this distribution set. It contains the
@@ -127,10 +129,11 @@ locations outside of the United States and Canada.)
 
 .../mvme68k/kernel/
 
-The mvme68k kernel directory contains a gzip'ed VME147 specific kernel
+The mvme68k kernel directory contains a gzip'ed kernel image which is
-image. This should be used when upgrading from a previous version of
+compatible with both MVME147 and MVME167 boards. This should be used when
-NetBSD. Before starting the upgrade, you should unzip and copy this
+upgrading from a previous version of NetBSD. Before starting the upgrade,
-kernel in place of your existing /netbsd image, then reboot.
+you should unzip and copy this kernel in place of your existing /netbsd
+image, then reboot.
 
 The mvme68k binary distribution sets are distributed as gzipped tar files.
 Each mvme68k binary distribution set also has its own "CKSUMS" file, just
@@ -144,7 +147,7 @@ replace the system binaries with them, you have to run the command:
 
         pax -zrvpe -f set.tar.gz
 
-from /.
+while in the root directory of your system (/).
 
 For best results, it is recommended that you follow the installation
 and/or upgrade procedures documented in this file.

distrib/notes/mvme68k/hardware

@@ -1,7 +1,7 @@
-.\"	$NetBSD: hardware,v 1.3 1999/01/13 07:30:06 ross Exp $	
+.\"	$NetBSD: hardware,v 1.4 1999/02/20 16:18:11 scw Exp $	
 .
 NetBSD/mvme68k \*V runs on Motorola
-.Tn MVME147 No boards.
+.Tn MVME147 No and MVME167 No Single Board Computers.
 .Pp
 The minimal configuration requires 4M of RAM and ~100MB of disk space.
 To install the entire system requires much more disk space (approx.
@@ -28,7 +28,7 @@ The following
 .Tn VME147 No hardware is supported:
 .Bl -tag -width Parallel
 .It Em Serial ports (RS232):
-built-in console, tty01, tty02 and tty03
+built-in console, ttyZ1, ttyZ2 and ttyZ3
 .It Em Parallel port:
 On-board centronics style printer port
 .It Em Network interfaces:
@@ -41,4 +41,20 @@ Battery-backed real-time clock.
 VMEbus RAM cards.
 .El
 .Pp
-If it's not on this list, there is no support for it in this release.
+The following
+.Tn VME167 No hardware is supported:
+.Bl -tag -width Parallel
+.It Em Serial ports (RS232):
+built-in console, ttyC1, ttyC2 and ttyC3
+.It Em Parallel port:
+On-board centronics style printer port
+.It Em Network interfaces:
+On-board Ethernet (ie)
+.It Em SCSI: 
+(Most SCSI disks, tapes, CD-ROMs, etc.)
+On-board ncr53c710 SCSI I/O Processor chip.
+.It Em Miscellaneous:
+Battery-backed real-time clock.
+.El
+.Pp
+If it's not on the above lists, there is no support for it in this release.

distrib/notes/mvme68k/install

@@ -1,4 +1,4 @@
-.\"	$NetBSD: install,v 1.4 1999/01/13 07:30:06 ross Exp $
+.\"	$NetBSD: install,v 1.5 1999/02/20 16:18:11 scw Exp $
 .\"
 .\" Copyright (c) 1999 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -43,7 +43,7 @@ onto your disk. If your
 machine has a tape drive the easiest way is "Installing from tape"
 (details below). If your machine is on a network with a suitable
 NFS server, then "Installing from NFS" is the next best method.
-Otherwise, if you have another VME147 machine running
+Otherwise, if you have another mvme68k machine running
 .Nx
 you can
 initialize the disk on that machine and then move the disk.
@@ -52,9 +52,9 @@ initialize the disk on that machine and then move the disk.
 .
 Create the NetBSD/mvme68k _VER boot tape as described in the section
 entitled "Preparing a boot tape". Then, with the tape in the drive,
-type the following at the 147Bug prompt:
+type the following at the 1x7Bug prompt:
 .Pp
-.Dl 147-Bug\*> Ic bo 5
+.Dl 1x7-Bug\*> Ic bo 5
 .Pp
 As mentioned earlier, this assumes your tape is jumpered for SCSI-id 5.
 .Pp
@@ -80,7 +80,7 @@ Loading: Operating System
 Volume: NBSD
 
 IPL loaded at:  $003F0000
-\*>\*> BSD MVME147 tapeboot [$Revision: 1.4 $]
+\*>\*> BSD MVME147 tapeboot [$Revision: 1.5 $]
 578616+422344+55540+[46032+51284]=0x11a6e4
 Start @ 0x8000 ...
 Copyright (c) 1996, 1997 The NetBSD Foundation, Inc.  All rights reserved.
@@ -103,7 +103,7 @@ clock0 at pcc0 offset 0x0 ipl 5: Mostek MK48T02, 2048 bytes of NVRAM
 .Pp
 .(Note
 The exact text of the messages will vary depending on which
-MVME147 variant you're using.
+MVME147 or MVME167 variant you're using.
 .Note)
 .Pp
 Finally, you will see the following "welcome" message:
@@ -128,7 +128,7 @@ The easiest is loading from tape, which is done as follows:
 
 To reboot using the swap partition after running installboot, first
 use "halt", then at the Bug monitor prompt use a command like:
-        bo 0,,b:
+        147Bug> bo 0,,b:   OR   167Bug> bo 0,,,b:
 
 To view this message again, type:  cat /.welcome
 ssh:
@@ -330,6 +330,7 @@ You can now shutdown the system.
 .Dl Cold/Warm Reset flag [C,W] = C?
 .Dl Execute Soft Reset [Y,N] N? Ic y
 .Pp
+Resetting the MVME167 board is very similar.
 You should now reboot from that just installed miniroot. See the section
 entitled "Booting the miniroot" for details.
 .
@@ -340,13 +341,14 @@ your NFS server to support your machine as a bootable client.
 Instructions for configuring the server are found in the section
 entitled "Getting the NetBSD System onto Useful Media" above.
 .Pp
-To get started, you need to download "sboot" into RAM (you will find
+To get started on the MVME147, you need to download "sboot" into RAM
+(you will find
 .Ic sboot
 in the 
 .Pa install
 directory of the mvme68k distribution).
 You can either do that through the console line or through a 2nd serial
-connection. For example, a VME147 connected to a sun4/110 and accessed via
+connection. For example, an MVME147 connected to a sun4/110 and accessed via
 .Xr tip 1
 can be loaded as follows:
 .Pp
@@ -367,7 +369,7 @@ Which will look like this:
 .Dl 147-Bug\*> Ic g 4000
 .Dl Effective address: 00004000
 .Pp
-.Dl sboot:\ serial\ line\ bootstrap\ program\ (\*&end\ =\ 6018)
+.Dl sboot: serial line bootstrap program (end = 6018)
 .Pp
 .Dl \*>\*>\*>
 .Pp
@@ -393,8 +395,25 @@ My ip address is: 192.168.1.4
 Server ip address is: 192.168.1.1
 4800
 Download was a success!
+.Ed
+.Pp
+See below for the next step in booting MVME147.
+.Pp
+The MVME167 is able to download netboot directly using TFTP.
+To enable this, you must first configure the networking parameters
+on the board as described in the section entitled "Preparing your System
+for
+.Nx
+Installation. On a properly configured MVME167, all you need
+to type is:
+.Pp
+.Dl 167-Bug\*> Ic nbo
+.Pp
+For both boards, the boot messages are very similar:
+.Pp
+.Bd -literal -offset indent
 Start @ 0x8000 ...
-\*>\*> BSD MVME147 netboot (via sboot) [$Revision: 1.4 $]
+\*>\*> BSD MVME147 netboot (via sboot) [$Revision: 1.5 $]
 device: le0 attached to 08:00:3e:20:cb:87
 boot: client IP address: 192.168.1.4
 boot: client name: soapy
@@ -432,7 +451,13 @@ NFS server containing the miniroot image. For example the command:
 .Pp
 .Dl ssh: Ic ifconfig\ le0\ inet\ 192.168.1.4 up
 .Pp
-will bring up the network interface 'le0' with that address. The next
+will bring up the MVME147 network interface 'le0' with that address.
+The command:
+.Pp
+.Dl ssh: Ic ifconfig\ ie0\ inet\ 192.168.1.4 up
+.Pp
+will bring up the MVME167 network interface 'ie0' with that address.
+The next
 step is to copy the miniroot from your server. This can be done using
 either NFS or remote shell. (In the examples that follow, the server has
 IP address 192.168.1.1) You may then need to add a default route if the
@@ -480,12 +505,15 @@ Assuming the miniroot is installed on partition 'b' of the disk with
 SCSI-id 0, then the 147Bug boot command is:
 .Dl 147-Bug\*> Ic bo 0,,b:
 .Pp
+The corresponding 167Bug boot command is:
+.Dl 167-Bug\*> Ic bo 0,,,b:
+.Pp
 The command line parameters above are:
 .Pp
 .Bl -tag -width xxx
 .It Ic 0
 controller (usually zero)
-.It Ic ,,
+.It Ic ,, or ,,,
 bug argument separators
 .It Ic \&b:\&
 tell the bootstrap code to boot from partition
@@ -502,17 +530,16 @@ return twice to accept the defaults. When asked to enter a terminal
 type, either accept the default, or use whatever the TERM environment
 variable is set to in the shell of your host system:
 .Pp
-.DL vmel0 at vmechip0
+.Dl boot device: sd0
-.DL boot device: sd0
+.Dl root device (default sd0a): Ic sd0b
-.DL root device (default sd0a): Ic sd0b
+.Dl dump device (default sd0b):  Em (return)
-.DL dump device (default sd0b):  Em (return)
+.Dl file system (default generic): Em (return)
-.DL file system (default generic): Em (return)
+.Dl root on sd0b dumps on sd0b
-.DL root on sd0b dumps on sd0b
+.Dl mountroot: trying ffs...
-.DL mountroot: trying ffs...
+.Dl root file system type: ffs
-.DL root file system type: ffs
+.Dl init: copying out path `/sbin/init' 11
-.DL init: copying out path `/sbin/init' 11
+.Dl erase ^H, werase ^W, kill ^U, intr ^C
-.DL erase ^H, werase ^W, kill ^U, intr ^C
+.Dl Terminal type? [vt100] Em return
-.DL Terminal type? [vt100] Em return
 .Pp
 Congratulations! The system should now be running the miniroot
 installation program.

distrib/notes/mvme68k/prep

@@ -1,4 +1,4 @@
-.\"	$NetBSD: prep,v 1.3 1999/01/13 07:30:07 ross Exp $	
+.\"	$NetBSD: prep,v 1.4 1999/02/20 16:18:11 scw Exp $	
 .
 mvme68k machines usually need little or no preparation before installing
 .Nx "" ,
@@ -8,7 +8,7 @@ on any attached storage devices.
 .Pp
 The following instructions should make your machine "NetBSD Ready".
 .Pp
-Power-up your VME147. You should have the 
+Power-up your MVME147 board. You should have the 
 .Em bug No prompt:
 .Bdlit
 
@@ -19,46 +19,62 @@ Onboard  RAM start = $00000000,  stop = $007FFFFF
 147-Bug\*>
 
 .Ed
-Make sure the value for "stop" looks ok (if you've got 8MB you should
+Or, if you have an MVME167 board:
+.Bdlit
+
+MVME167 Debugger/Diagnostics Release Version 2.3 - 02/25/94
+COLD Start
+
+Local Memory Found =02000000 (&33554432)
+
+MPU Clock Speed =33Mhz
+
+167-Bug\*>
+
+.Ed
+Make sure the RAM size looks ok (if you've got an 8Mb MVME147 or a
+32Mb MVME167 you should
 have the same value as I do). Also make sure the clock is ticking:
 .Pp
-.Dl 147-Bug\*> Ns Ic time
+.Dl 1x7-Bug\*> Ns Ic time
 .Dl Sunday   12/21/29   16:25:14
-.Dl 147-Bug\*> Ns Ic time
+.Dl 1x7-Bug\*> Ns Ic time
 .Dl Sunday   12/21/29   16:25:15
-.Dl 147-Bug\*>
+.Dl 1x7-Bug\*>
 .Pp
 Note that
 .Nx
 bases its year at 1968, and adds the year offset in
-the VME147's real-time clock to get the current year. So the '29' here
+the MVME1x7's real-time clock to get the current year. So the '29' here
 equates to 1997. You may have to adjust your clock using the 'set'
 command to comply with
 .Nx "" 's
 requirements. Don't worry if the "Day of the week" is not correct,
 .Nx
 doesn't use it.
-Motorola has acknowledged a year 2000 bug whereby the day of the week
+Motorola has acknowledged a year 2000 bug in some versions of the MVME147
+whereby the day of the week
 doesn't get set correctly by the 147Bug PROM.
 .Em It does not affect
 .Nx "" !
 .Pp
-Also make sure that your VME147's ethernet address is initialised to
+Also make sure that your board's ethernet address is initialised to
 the correct value. You'll find the address on a label on the inside of
-the board's front panel. Enter the last five digits of the address
+the MVME147's front panel, and on the VMEbus P2 connector of the MVME167.
-using the 'lsad' command.
+On the MVME147, enter the last five digits of the address
+using the 'lsad' command. On the MVME167, you should use the 'cnfg' command.
 .Pp
 To install successfully to a local SCSI disk, you need to ensure that
-147Bug is aware of what targets are connected to the SCSI bus. This
+1x7Bug is aware of what targets are connected to the SCSI bus. This
 can be done by issueing the following command:
 .Pp
-.Dl 147-Bug\*> Ic iot;t
+.Dl 1x7-Bug\*> Ic iot;t
 .Pp
-At this point, 147Bug will scan for any attached SCSI devices. After
+At this point, 1x7Bug will scan for any attached SCSI devices. After
-a short delay, a list of SCSI devices will be displayed. You will be
+a short delay, a list of SCSI devices will be displayed. 147Bug will
-asked if Bug should assign LUNs to SCSI ids, to which you should
+ask if LUNs should be assigned from SCSI ids, to which you should
 answer Y. You should also answer Y when asked if the information is
-to be saved to NVRAM.
+to be saved to NVRAM. 167Bug does not prompt for this information.
 .Pp
 The following installation instructions will assume that your target
 SCSI disk drive appears at SCSI-id 0. If you have a tape drive, the

distrib/notes/mvme68k/whatis

@@ -1,5 +1,5 @@
-.\"	$NetBSD: whatis,v 1.3 1999/01/13 07:30:07 ross Exp $	
+.\"	$NetBSD: whatis,v 1.4 1999/02/20 16:18:11 scw Exp $	
 .
-This is the fourth public release of
+This is the fifth public release of
 .Nx
-for the VME147.
+for the mvme68k series of boards, and the first to support MVME167.

distrib/notes/mvme68k/xfer

@@ -1,4 +1,4 @@
-.\"	$NetBSD: xfer,v 1.4 1999/01/13 07:30:07 ross Exp $	
+.\"	$NetBSD: xfer,v 1.5 1999/02/20 16:18:11 scw Exp $	
 .
 Installation is supported from several media types, including:
 .Bl -bullet -compact
@@ -13,7 +13,8 @@ CD-ROM
 FTP
 .El
 Note that installing on a "bare" machine requires either a bootable
-tape drive or an ethernet and RS232 connection to a compatible NFS server.
+tape drive or an ethernet to a compatible NFS server. MVME147 may
+also need to be booted over an RS232 connection.
 .Pp
 The procedure for transferring the distribution sets onto installation
 media depends on the type of media. Instructions for each type of media
@@ -78,7 +79,7 @@ manual page for guidelines on how to proceed with
 this. If the server runs another operating system, consult the
 documentation that came with it (i.e. add_client(8) on SunOS).
 .Pp
-Booting a VME147 from ethernet is not possible without first downloading
+Booting an MVME147 from ethernet is not possible without first downloading
 a small bootstrap program (sboot) via RS232. See the section entitiled
 "Installing from NFS" for details on how to accomplish this.
 .Pp
@@ -86,13 +87,17 @@ sboot expects to be able to download a second stage bootstrap
 program via TFTP after having acquired its IP address through RARP
 It will look for a filename derived from the machine's IP address
 expressed in hexadecimal, with an extension of ".147". For example,
-a VME147 with IP address 130.115.144.11 will make an TFTP request for
+an MVME147 with IP address 130.115.144.11 will make an TFTP request for
 `8273900B.147'. Normally, this file is just a symbolic link to the
 NetBSD/mvme68k "netboot" program, which should be located in a place
 where the TFTP daemon can find it (remember, many TFTP daemons run in
 a chroot'ed environment). The netboot program may be found in the
 install directory of this distribution.
 .Pp
+The MVME167 boot ROM has code builtin to boot over ethernet from a
+TFTP server. You should configure it to download the same "netboot"
+program as is used for MVME147.
+.Pp
 The netboot program will query a bootparamd server to find the NFS
 server address and path name for its root, and then load a kernel from
 that location. The server should have a copy of the netbsd-rd kernel in
@@ -149,5 +154,5 @@ server, you may want to keep the following information handy:
 .(Note
 If you're not using a nameserver duing installation,
 you might find 204.152.184.75 handy; it's the IP address of
-ftp.NetBSD.ORG as of January 3, 1997.
+ftp.NetBSD.ORG as of January, 1999.
 .Note)