This document currently only covers Motorola MVME16x boards. I guess MVME17x boards are the same. --------------------------------------------------------------------------- ---------------- Section 1 - Hardware configuration ---------------------- --------------------------------------------------------------------------- First you need to configure your hardware. The MVME166/7 card needs configuring so that the 16xBug executes from SRAM rather than DRAM. this is done via a jumper setting. On my MVME167 board, this means removing the jumper from position 1 (nearest the edge of the board) on the jumper block behind the LEDs. Power up the board and break into the monitor, 16x-Bug. Depending on how your board has been configured, it may start up in an auto-boot mode, running self-tests, or with a menu. You can switch between the Diag and Bug prompts with the SD command. Anyway, you must get to the stage where you have a 16x-Bug prompt: > Copyright Motorola Inc. 1988 - 1993, All Rights Reserved > > MVME166 Debugger/Diagnostics Release Version 1.2 - 03/24/93 > COLD Start > > Local Memory Found =01000000 (&16777216) > > MPU Clock Speed =33Mhz > > Autoboot in progress... To abort hit > --Break Detected-- > 166-Bug> Initialise the configuration data: > 166-Bug>cnfg;i > > Update Non-Volatile RAM (Y/N)? y > 166-Bug>cnfg > Board (PWA) Serial Number = "1308394 " > Board Identifier = "mvme166-11 " > Artwork (PWA) Identifier = "01-w3834b01b " > MPU Clock Speed = "3300" > Ethernet Address = 08003E21DB47 > Local SCSI Identifier = "07" > Optional Board 1 Artwork (PWA) Identifier = "3800b01a" > Optional Board 1 (PWA) Serial Number = "1296349 " > Optional Board 2 Artwork (PWA) Identifier = "0 " > Optional Board 2 (PWA) Serial Number = "0 " > 166-Bug> The things to check here are that the SCSI ID is 7, and that the ethernet address is reasonable (it should match a label stuck to the board, somewhere). Now set the default environment parameters: > 166-Bug>env;d > Update with Auto-Configuration Defaults > > Update Non-Volatile RAM (Y/N)? y > > Reset Local System (CPU) (Y/N)? n > WARNING: Updates will not be in effect until a RESET is performed. We didn't request a reset at this point, because we need to adjust some of the default values: > 166-Bug>env >> Bug or System environment [B/S] = S? b >> Field Service Menu Enable [Y/N] = Y? n > Remote Start Method Switch [G/M/B/N] = B? > Probe System for Supported I/O Controllers [Y/N] = Y? > Negate VMEbus SYSFAIL* Always [Y/N] = N? >> Local SCSI Bus Reset on Debugger Startup [Y/N] = N? y > Local SCSI Bus Negotiations Type [A/S/N] = A? > Ignore CFGA Block on a Hard Disk Boot [Y/N] = Y? > Auto Boot Enable [Y/N] = N? >> Auto Boot at power-up only [Y/N] = Y? n > Auto Boot Controller LUN = 00? > Auto Boot Device LUN = 00? > Auto Boot Abort Delay = 15? > Auto Boot Default String [NULL for a empty string] = ? > ROM Boot Enable [Y/N] = N? > ROM Boot at power-up only [Y/N] = Y? > ROM Boot Enable search of VMEbus [Y/N] = N? > ROM Boot Abort Delay = 0? > ROM Boot Direct Starting Address = FF800000? > ROM Boot Direct Ending Address = FFBFFFFC? > Network Auto Boot Enable [Y/N] = N? >> Network Auto Boot at power-up only [Y/N] = Y? n > Network Auto Boot Controller LUN = 00? > Network Auto Boot Device LUN = 00? > Network Auto Boot Abort Delay = 5? >> Network Auto Boot Configuration Parameters Pointer (NVRAM) = 00000000? fffc0800 >> Memory Search Starting Address = 00000000? . > >> Update Non-Volatile RAM (Y/N)? y > >> Reset Local System (CPU) (Y/N)? y The board will now reset again, and the serial port speed will be 9600. The above prompt sequence will vary, depending on your Bug version. Once you are back at the 166-Bug prompt, change the terminal speed to 19200 as follows: > 166-Bug>pf 0 > Baud Rate [110,300,600,1200,2400,4800,9600,19200] = 9600? 19200 > Even, Odd, or No Parity [E,O,N] = N? > Character Width [5,6,7,8] = 8? > Stop Bits [1,2] = 1? > Auto Xmit enable on CTS* [Y,N] = N? > Auto negate RTS* when Recv FIFO full [Y,N] = N? > XON/XOFF Protocol [Y,N] = Y? n > XON = $11=^Q? > XOFF = $13=^S? > Baud Rate [110,300,600,1200,2400,4800,9600,19200] = 19200? . > OK to proceed (y/n)? y > > Update Non-Volatile RAM (Y/N)? y That will obviously require that you change your terminal to 19200, at which point you should again have a 166-Bug prompt. --------------------------------------------------------------------------- ---------------- Section 2 - NFS/TFTP parameters ------------------------ --------------------------------------------------------------------------- If you are going to use the network interface, it must be configured. Configure the network parameters to allow it to pull the kernel in from your hosts system, obviously the IP addresses you enter are likely to differ from mine. The Client is the MVME166 board, and the Server is the system on which the filesystem is mounted. I have chosen to use the IP address 10.1.1.1 for my host system (a Linux PC) and 10.1.1.2 for my MVME166 board: > 166-Bug>niot > Controller LUN =00? > Device LUN =00? > Node Control Memory Address =FFE10000? > Client IP Address =0.0.0.0? 10.1.1.2 > Server IP Address =0.0.0.0? 10.1.1.1 > Subnet IP Address Mask =255.255.255.0? > Broadcast IP Address =255.255.255.255? > Gateway IP Address =0.0.0.0? > Boot File Name ("NULL" for None) =? /usr/m68k/vmlinux > Argument File Name ("NULL" for None) ="NULL"? NULL > Boot File Load Address =00000000? 0 > Boot File Execution Address =00000000? 800 > Boot File Execution Delay =0000000A? 0 > Boot File Length =00000000? > Boot File Byte Offset =00000000? > BOOTP/RARP Request Retry =00? > TFTP/ARP Request Retry =00? > Trace Character Buffer Address =00000000? > BOOTP/RARP Request Control: Always/When-Needed (A/W)=W? > BOOTP/RARP Reply Update Control: Yes/No (Y/N) =Y? > > Update Non-Volatile RAM (Y/N)? y > 166-Bug> You can now check that the ethernet link works. I am assuming that you have enabled TFTP access to /usr/m68k on your host: > 166-Bug>niop > Controller LUN =00? > Device LUN =00? > Get/Put =G? > File Name =? /usr/m68k/somefile > Memory Address =FFE0E000? 0 > Length =00000000? > Byte Offset =00000000? > > Bytes Received =&734377, Bytes Loaded =&734377 > Bytes/Second =&146875, Elapsed Time =5 Second(s) Note that to allow tftp access on my linux PC I had to uncomment the tftp line in my /etc/inetd.conf. --------------------------------------------------------------------------- richard@sleepie.demon.co.uk 4th May 1998