Boot setup for the MVME6100

On the computer:

• First you need an image of a Linux distribution, which is compatible with the PowerPC architecture of a MVME6100, e.g. an image which can be obtained via wget:
  wget http://dpnc.unige.ch/ams/dhaas/basefs.tar.gz
  or download it directly at:
  http://dpnc.unige.ch/ams/dhaas/basefs.tar.gz
  and
  http://dpnc.unige.ch/ams/dhaas/zimage.6100
  

  You will need the image file and the un-tared filesystem. Move the imagefile into the /tftpboot folder and the image into the homedirectory (/home), otherwise you will have to replace the paths given below.

• Packages needed:
  dhcpd-4.0.0-20080101.src.rpm
• Download the packages with your packet-management programme (e.g YUM in Scientific Linux, Synaptic or aptitude in the shell)
• Open the dhcpd.conf as a root user (sudo nano /etc/dhcp.conf ; otherwise you wont be able to edit it) and add the new machine in the following way:
  host newhost
  
  {
  hardware ethernet 00:00:00:00:00:00;
  #MAC-Address
  fixed-address 123.456.789.000;
  #IP-Address
  option routers 123.456.789.000;
  #Gateway
  filename "zimage.6100";
  #Name of the image
  option root-path "/home/Basefs6100";
  #Path to the image
  }
  
  This will allow to accses the MVME the directory /home/Basefs6100 and to download the file zimage.6100 into its memory.

• Packages needed: tftp-server-0.39-1.i386.rpm
  tftp-0.39-1.i386.rpm
  
• Probably the tftp-Service is disabled by default, so edit the /etc/xinetd.d/tftp (as root) by typing:
  service tftp
  
  {
  disable = no
  socket_type = dgram
  protocol = udp
  wait = yes
  user = root
  server = /usr/sbin/in.tftpd
  server_args = -s /tftpboot
  per_source = 11
  cps = 100 2
  flags = Ipv4
  }
  
The service should then be enabled and the folder /tftpboot should be available in the network. The argument -s declares it as a chroot environment.

• Packages needed:
  nfs-utils.xxx.rpm
• Edit the file /etc/exports (as root), by adding the line:
  /home/Basefs6100 newhost(rw,sync,no_root_squash)
This will enable your computer to export the folder /home/Basefs6100 via the NFS protocoll in the network.

• Make sure your firewall forward the Ports for DHCPd:
  67/68 UDP/UDP, NFS 2049 UDP and TCP (up to V4.0), 69 UDP.
  Normally you should be able to configure your firewall in System Settings -> Security Settings -> Trusted Services, or in the GUI of your firewall if you are not using the default firewall.
  If not you have to add the ports manually to your IP-tables if the server won't send any data (attention: open ports can cause a security problem to your network!)

On the MVME6100:

• Open a console, become root and open minicom. First you probably have to change several options:
• Set the connection-mode to 9600 Baud per second, 8-Bit, no parity, 1-Stop-Bit.
  It is shown as 9600 8N1 in the baseline of minicom.
• Set the Terminal emulation to VT102.
• Set the interrupt line to blank.
• Save these settings as default and exit minicom and shutdown the computer.
• Connect the cable. Attention: Com-devices are NOT hotpluggable! Plug the RJ45-to-Sub-D cable to the computer and the ethernet-debug plug on the frontpanel of the MVME. Plug a normal ethernet-cable to the first LAN-port of the MVME and into your computer.
• Reboot your system.
• Start minicom as root and turn on the power of the VME-Crete. You now should see something like this:
Copyright Motorola Inc. 1999-2004, All Rights Reserved
MOTLoad RTOS Version 2.0, PAL Version 1.1 RM02
Fri Sep 17 09:44:47 MST 2004
MPU-Type =MPC74x7
MPU-Int Clock Speed =1266MHz
MPU-Ext Clock Speed =133MHz
MPU-Int Cache(L2) Enabled, 512KB, L2CR =C0000000
MPU-Ext Cache(L3) Enabled, 2MB, 211MHz, L3CR =DC026000


If you see this you have correctly assemled the cable and you are able to configure the MVME MOTLoad firmware via minicom.

• Give the IP-address of the new device with the gevEdit command:
  gevEdit mot-/dev/enet0-cipa
  "client ip-address"
  gevEdit mot-/dev/enet0-sipa
  "server ip-address"
  gevEdit mot-/dev/enet0-gipa
  "standard gateway adress"
  gevEdit mot-/dev/enet0-snma
  "subnet-mask"
  gevEdit mot-/dev/enet0-file
  "the image file, in our case zimage.6100"
  gevEdit mot-boot-device
  "the connection which is used for booting the client: eth0"
  gevEdit mot-boot-cipa
  "client ip-address"
  gevEdit mot-boot-sipa
  "server ip-address"
  gevEdit mot-boot-gipa
  "standard gateway adress"
  gevEdit mot-boot-snma
  "subnet-mask"
  gevEdit mot-boot-file
  "the image file, in our case zimage.6100"
  gevEditmot-script-boot
  "netBoot -p 0 -e0x400, which defines the netboot as default booting method and assures that he waits 0 s with asking for the file -p 0, -e0x400 determinates the start address in the memory into which the image is loaded"
  

• You can check the settings with gevShow, which should look like this:

  MVME6100> gevShow
  mot-/dev/enet0-cipa=192.84.144.119
  mot-/dev/enet0-sipa=192.84.144.118
  mot-/dev/enet0-gipa=0.0.0.0
  mot-/dev/enet0-snma=255.255.255.0
  mot-/dev/enet0-file=zimage.6100
  mot-boot-device=/dev/enet0
  mot-boot-cipa=192.84.144.119
  mot-boot-sipa=192.84.144.118
  mot-boot-gipa=0.0.0.0
  mot-boot-snma=255.255.255.0
  mot-boot-file=zimage.6100
  mot-script-boot=netBoot -p 0 -e0x400 -y
  Total Number of GE Variables =12, Bytes Utilized =362, Bytes Free =3230
  

• Reboot the system by holding down the Interrupt/Reboot button on the front panel for several seconds. The system should boot like this:

  Copyright Motorola Inc. 1999-2004, All Rights Reserved
  MOTLoad RTOS Version 2.0, PAL Version 1.1 RM02
  Fri Sep 17 09:44:47 MST 2004
  MPU-Type =MPC74x7
  MPU-Int Clock Speed =1266MHz
  MPU-Ext Clock Speed =133MHz
  MPU-Int Cache(L2) Enabled, 512KB, L2CR =C0000000
  MPU-Ext Cache(L3) Enabled, 2MB, 211MHz, L3CR =DC026000
  PCI bus instance 0 =64 bit, 133 Mhz, PCI-X
  PCI bus instance 1 =64 bit, PCI
  Reset/Boot Vector =Flash1
  Local Memory Found =20000000 (&536870912)
  User Download Buffer =006B7000:008B6FFF
  Network Loading from: /dev/enet0
  Locating BOOTP Server... Found It!
  Copyright Motorola Inc. 1999-2004, All Rights Reserved
  MOTLoad RTOS Version 2.0, PAL Version 1.1 RM02
  Fri Sep 17 09:44:47 MST 2004
  MPU-Type =MPC74x7
  MPU-Int Clock Speed =1266MHz
  MPU-Ext Clock Speed =133MHz
  MPU-Int Cache(L2) Enabled, 512KB, L2CR =C0000000
  MPU-Ext Cache(L3) Enabled, 2MB, 211MHz, L3CR =DC026000
  PCI bus instance 0 =64 bit, 133 Mhz, PCI-X
  PCI bus instance 1 =64 bit, PCI
  Reset/Boot Vector =Flash1
  Local Memory Found =20000000 (&536870912)
  User Download Buffer =006B7000:008B6FFF
  Network Loading from: /dev/enet0
  Locating BOOTP Server... Found It!
  

Assembly of an RJ45-to-Sub-D Cable:

The debug port on the MVME looks like an ethernet port, but it is a serial port by which the MOTLoad firmware can be accessed. For this you need a special cable to connect it to the computer. For the cable you need:

• An ethernet cable
• A Sub-D-Plug (female)
• A Case for the Sub-D-Plug
If you don't have a serial port on your computer you will also need a USB-To-Serial adapter. The pins have to be soldered like this:

RJ-45	RJ-45 Socket Position	DB9 Socket Position	DB9 Signal
DCD	1	4	DTR
RTS	2	8	CTS
GND	3	5	GND
GND	6	5	GND
TxD	4	2	RxD
RxD	5	3	TxD
CTS	7	7	RTS
DTR	8	6	DSR
DTR	8	1	DCD

The positions on a Sub-DB9 socket are mostly marked by small numbers on it.
The positions on a RJ45 socket are 1 to 8 from left to right if you look on the plug with the notch upwards.

Picture 1: Sub-D9 connector	Picture 2: RJ45 connector

Troubleshooting

• The MVME6100 does not boot:
  • On the MVME:
  • gevEdit the network parameter in the following way:
    netBoot -p0 -e0x400 -r5 -y
    Important is the "-y" which forces DHCP (probably firmware dependent)
  • On the Mac/Linux:
  • Check the dhcp/bootp setup
  • Check the nfs setup
• Other checks
• Check if you have entered the MAC-Address of eth0 in the dhcp.conf.
• Doublecheck all cyphers in the dhcp.conf / the MVME (gevShow).
• Check if the daemons are running.
• Check if your firewall is set-up correctly.
• Check if all necessary files are in the right place.
• Check if you have set-up the nfs/tftp server correctly (e.g. spelling of the hostname etc.).

Author: I. Valls
Last update: I.Melzer-Pellmann / D. Haas
13.08.2008