Last modified 11-Mar-96 by M. Welsh
These are the installation notes for U-Net version 2.0, 10-March-1996. Please see the U-Net documentation tree and release notes first.
Installation of U-Net is not automated, but it's meant to be quite easy. There are two steps: Compiling the code, and installing the various pieces. Compilation is covered in the next section, and installation for each implementation is covered later in this document.
The first step is to unpack the U-Net release distribution; this will create the unet-2 directory with the subdirectories as described in the Release Notes.
If you are using a FORE 200-series ATM board, please edit the file uload/Makefile and modify the TOOLIBPATH variable for your system. You need to have toolib.a as compiled from the GNU i960 tools distribution (see the release notes for details). The subdirectory uload/i960-binaries contains a binary of this library which may work for you; however, you need to modify the TOOLIBPATH in this Makefile anyway.
Other than this we hope that no other Makefile changes are necessary. Please let us know if this isn't so.
To compile the release, issue the command
make ARCH=architecture DEV=device
from the top-level unet-2 directory, where architecture is one of
and device is one of
This does not imply that all combinations of the above are supported.
For example, to compile for the PCA-200 under Linux, issue
make ARCH=linux DEV=pca200
This should compile all of the components for a particular operating system. You can also issue this command in the various subdirectories of unet-2, although no checks are made that ARCH and DEV are set in that case. Be careful!
To remove all binary files for a given architecture/device, use
make ARCH=architecture DEV=device clean
Once compiled, the various binary files will be left in the subdirectories
bin-device-architecture
of each subdirectory of unet-2. You will need to follow the installation instructions below to make use of the binaries.
Notes on installing each U-Net driver are included below.
insmod tulip.o
Once installed the device should print messages such as the following:
tulip: Found device index 0, bus 0, function 160. tulip: Revision 0x12, using IRQ 9. tulip: CBIO: 0xfc00, CBMA: 0xf0cffc00 tulip: Setting latency timer from 64 to 100 clocks. tulip: MAC address 00:00:c0:17:bc:c7 tulip0: Rx ring at 0x00a34034, Tx ring at 0x00a34434 tulip: 1 devices found.
If you see error messages which you don't understand, please contact us.
In order to use the device you need to create device nodes in /dev. The major number of the U-Net device is defined in devtulip.h. If this major number conflicts with your system, change it and recompile the driver.
The device numbering scheme works as follows: The minor number of the device corresponds to a single endpoint. devtulip.h contains a definition for TULIP_MAX_ENDPTS, the maximum number of endpoints supported by each physical Tulip device. If TULIP_MAX_ENDPTS is 10, minor numbers 0 through 9 correspond to the first Tulip device in the system, 10 through 19 to the second, and so forth.
You should create at least one minor device node in order to use the system; you may wish to create one for each potential endpoint. For each, execute the command
mknod /dev/tulipN c major N
Where major is the major number (say, 33) and N is the minor number as described above.
You should also chmod 777 the device entries, so that non-root users can use them.
Now you're ready to test it out; see the section Testing below.
First, patch your kernel with the unetarea patch in install/linux. This adds several files to /usr/src/linux/init to allocate physical memory at boot time (the amount is controlled in init/unet.h) which can be used for U-Net endpoint mappings. I hope to produce a nicer solution to this soon. This has been tested under kernel 1.3.45, and should work on later kernels. Install the new kernel and reboot.
The PCA-200 device driver is located in unet-2/dev-pca200/pca200.o. It is a stand-alone kernel module. Simply load it with
insmod pca200.o
Once installed the device should print messages such as the following:
pca200: Found device index 0, bus 0, function 144. pca200: Revision 0x0, using IRQ 11. pca200: Board memory at 0xf0d00000 mapped at 0x0181c000. pca200: Setting latency timer from 0 to 100 clocks. pca200: MAC address prom of device 0 reads 00:20:48:17:03:27
In order to use the device you need to create device nodes in /dev. The major number of the U-Net device is defined in devpca200.h. If this major number conflicts with your system, change it and recompile the driver.
You should create at least one minor device node in order to use the system; you may wish to create one for each potential endpoint. For each, execute the command
mknod /dev/pcaN c major N
Where major is the major number (say, 33) and N is the minor number as described above.
You should also chmod 777 the device entries, so that non-root users can use them.
The next step is to load the i960 firmware onto the board. This can be done at any time after the PCA-200 device driver is loaded. See Loading the Firmware, below.
The SBA-200 device driver is a standalone kernel module, located in unet-2/dev-sba200-sunos/sba200.o. Simply load it with a command such as
modload -o /tmp/sba200.o sba200.o
Once installed the device should print messages such as the following:
sba200 U-Net driver loaded. FORE,sba-2000 at SBus slot 0 0x800000 and SBus slot 0 0x1000000 pri 3 (sbus level 2)
In order to use the device you need to create device nodes in /dev. The major number of the U-Net device is defined in devsba200-sunos.h. If this major number conflicts with your system, change it and recompile the driver.
You should create at least one minor device node in order to use the system; you may wish to create one for each potential endpoint. For each, execute the command
mknod /dev/sbaN c major N
Where major is the major number (say, 33) and N is the minor number as described above.
You should also chmod 777 the device entries, so that non-root users can use them.
The next step is to load the i960 firmware onto the board. This can be done at any time after the SBA-200 device driver is loaded. See Loading the Firmware, below.
Note that use of the U-Net driver for SunOS is probably incompatible with use of the FORE Systems SBA-200 kernel driver. For best results unload the FORE Systems driver before loading the U-Net driver, and vice versa.
The SBA_200 device driver is a standalone kernel module, located in unet-2/dev-sba200-solaris/sba200. Use of the U-Net SBA-200 driver is probably incompatible with use of the original FORE SBA-200 driver (as they attach to the same device properties). You should uninstall your original FORE driver first, saving copies of the various files modified below. To install the driver,
# U-Net/SBA-200 driver
type=ddi_pseudo;name=FORE,sba-200 sba\N0
Be sure to delete any lines associated with the FORE SBA-200 driver.
exclude: drv/sba200
If installation or use of the U-Net driver causes problems, you can always boot using the etc/system.nounet file to prevent the driver from being loaded at boot time.
add_drv -i 'FORE,sba-200' -m '* 0666 root bin' sba200
This will load the device driver into the system, and automatically create /dev/sbaNNN entries for each endpoint, with the numbering system described above.
The next step is to load the i960 firmware onto the board. This can be done at any time after the SBA-200 device driver is loaded. See Loading the Firmware, below.
Note that use of the U-Net driver for SunOS is probably incompatible with use of the FORE Systems SBA-200 kernel driver. For best results unload the FORE Systems driver before loading the U-Net driver, and vice versa.
There are different firmware binaries for each FORE architecture. They are:
To download the i960 firmware using uload, do the following:
You should see messages such as the following:
Downloading /tmp/comma00531 Sending /tmp/comma00531, 311 blocks: Sector 311 38k
pca0: U-Net reset pca0: U-Net firmware magic is 0xf00d. pca0: U-Net firmware version is 0x5.
Mon960 Mon960 monitor for the Intel i960 CA (step 04) Version 1.0 HPA-200 V1.1 (12), Fore Systems, Inc. Apr 4 1994 Copyright 1992, Intel Corporation =>
In this way you can verify that uload is at least talking to the i960 monitor correctly.
At this point the i960 firmware should be running and you're ready to test the system out.
The addr argument is a string corresponding to the address of some other machine communicating via U-Net. It is converted by routines in libunet to the appropriate format for U-Net channel addresses (see U-Net Device Reference). This argument should be a string in one of two formats:
xx:xx:xx:xx:xx:xx.yy
Where xx are hexadecimal digits corresponding to the Ethernet MAC address of your controller, and yy is the hex value of a single-byte ``port'' address on the receiving end. Port addresses are used to allow multiple endpoints/channels to use one physical device; the sending and receiving ends of a U-Net connection over Fast Ethernet should agree on the port address(es) used. Note that only one endpoint on a single physical network device can listen to a particular port.
The size argument is limited by the maximum size of a PDU supported by the U-Net device; see Device Reference for details.
For example, to pingpong 40-byte messages between two systems (one at VCI 100, the other at VCI 200), you would execute the commands:
Receiver: pingpong recv /dev/sba0 200 1000 40
Sender: pingpong send /dev/sba0 100 1000 40
The ``receiver'' should be started before the ``sender''. In pingpong, both stations send and receive packets, but the receiver receives first, while the sender sends first.
On the sending end you should see something like:
Activated channel 0. Sending 1000 40-byte messages. Sent 1000 40-byte messages in 0.107453 seconds. 107.452989 usec/message or 2.840086 Mbit/sec Deactivating channel... Destroying endpoint... Closing and exiting...
This time corresponds to the round-trip ping-pong time, so divide by two for the one-way latency per message.
The syntax for loopback is
loopback device addr num size
With arguments are as described above. For loopback on ATM, you should have the VCI addr configured at the switch for send/receive, or use a loopback cable (connect send/receive ends of the fibre to both ports on the card), in which case the VCI is arbitrary. For loopback on Fast Ethernet, the Tulip driver must be compiled for full duplex operation and a loopback cable used (hack up a UTP5 and twist the Rx and Tx lines together).
You should see something like:
Got channel 0. Sending 10000 40-byte messages. Sent 10000 40-byte messages in 0.441592 seconds. 44.159210 usec/message or 6.910807 Mbit/sec Deactivating channel... Destroying endpoint... Closing and exiting...
The syntax for window is
window [send | recv] device addr num size window-size
With arguments as described above. The sender sends window-size messages of size bytes each to the receiver, which sends a single (small) acknowdledgement after receiving window-size messages. This is repeated num times.
Note that for large values of window-size messages may be silently dropped, either in your switch or by the U-Net implementation (if not enough free buffers or receive FIFO entries are available, for example). There is some practical limit to the arguments to window which should be determined empirically; no intelligent flow-control is being used here!
On the sending end you should see something like:
Sending 3000 1000-byte messages, window size 30. Sent 3000 1000-byte messages (window size 30) in 0.346486 seconds. 115.495324 usec/message or 69.266873 Mbit/sec Deactivating channel... Destroying endpoint... Closing and exiting...
U-Net should now be working for you; you can modify your system boot scripts to automatically load the drivers and firmware, if you wish. Please see the Device Reference for information on programming the U-Net device.
Return to U-Net Documentation.