-------------------------------------------------------------------------------- Installing the IMSB014 in the Silicon Graphics Personal Iris ============================================================ Directions for installing the device driver for the Inmos B014 VME Board. 1. Add following line to /usr/sysgen/system VECTOR: module=b014 unit=51 base=0xBD006000 The physical VME address of the boards should be calculated from the virtual addresses used in the file /usr/sysgen/system and the table of physical to virtual address maps provided in the appendix of the Irix device driver writing manual. The unit number is dependent upon the major device numbers you already have assigned to character devices on your system and must be unique. The 0xBD00 denotes a 16-bit VME address generated by the host processor. The low order 0x6000 represents the VME address that the B014 responds to. The B014 dials are set to 0 and 6 to match the high-order bytes of the VME address. 2. Build /usr/sysgen/boot/b014.o from b014.c and b014.h by the command sequence: cc -c b014.c -DKERNEL cp b014.o /usr/sysgen/boot The b014.c and b014.h driver code is provided in this package. This is a polled driver at this time which costs high utilization on the IRIS. We are looking at an interrupt-driven driver for the future. We installed this under IRIX 3.2.2 where it is working fine. We have given IRIX 3.3 a low priority although from customer upgrades we have found the new line should be: cc -c B014.c -D_KERNEL cp b014.o /usr/sysgen/boot 3. Add the file /usr/sysgen/master.d/b014. It must contain the lines: c b014_ 51 - $$$ A sample "b014" file has been included for your convenience. Copy this file into the master.d directory. Please note that the 51 in the first line of this file must match the unit number in /usr/sysgen/system and the major node number in the file add.devices. The "mknod" command must now be executed to create a B014 entry in the /dev directory. This can either be typed in or executed from the script file "add.devices" by the line: source add.devices Note that you must be the superuser to create devices. The B014 file in /dev that was created requires a mode change before it can be used as the B014 gateway. This can be done by: cd /dev chmod 666 b014 4. Make a new kernel, and preserve a copy of the old, by using the commands: mv unix unix_before_b014 lboot -u /unix.install mv unix.install unix 5. Reboot the system, using the system shutdown option in the window menu. The LINK.C interface for this driver is incorporated into the file sgi_link.c. This interface is standard across all of our software products and allows the iserver to be easily ported to new hosts. An IRIS hosted version of iserver that uses the B014 driver is provided in this package. The module sgi_link.c was also used in the manufacture of the "check" tools provided. The physical installation of the B014 inside the IRIS is straightforward. Please refer to the IRIS manual, do a system shutdown and power off. The side panel is easily removable by turning the circular lock on the back and sliding the side panel backwards. Unscrewing the large metal plate reveals the P1, P2 connectors of the single VME slot inside. Normally one would mount any TRAMs that are to go on the B014 first. It is advisable to include the 3-pin subsystem connector under slot 0. Select the dials for the correct VME address and push the board into the VME connectors. The external PCB D-shell connector used to break-out the B014 external links can be attached to the upper of the remaining connectors. From here one can use Inmos link and reset cables to control transputer subsystems. The connector is a very tight fit under the outer plastic casing although it seems to work fine. If you have no external transputers to connect then the D-shell connector can be omitted. Reassemble the cabinet, taking care not to apply pressure on the D-shell connector if installed, and restart the machine. As the IRIS bootstraps the user should receive a message saying the device driver correctly located the B014 hardware. Executing the command "check" from this package should describe transputer availability. If you do not have the "check" documentation from the archive-server I recommend just three confidence tests. 1/ Type "check" to see if transputers are present. 2/ Type "check | ftest" to see if the transputers are functionally ok. 3/ Type "check | mtest" to test the transputer RAM and size it. Alex Driker, Laurie Pegrum SGS-THOMSON Dec 1990. EMAIL "drikera@isnet.inmos.COM" and "pegruml@isnet.inmos.COM" Directions for adding the device driver for the Parsytec Transputer Board 1. Add following line to /usr/sysgen/system VECTOR: module=vmtm unit=50 base=0xB4000000 The unit number is dependent upon the major device numbers you already have assigned to character devices on your system. 2. Build /usr/sysgen/boot/vmtm.o from vmtm.c and vmtm.h by the command sequence cc -c vmtm.c cp vmtm.o /usr/sysgen/boot 3. Add the file /usr/sysgen/master.d/vmtm. It must contain the lines c vmtm_ 50 - $$$ Please note that the 50 in the first line of this file must match the unit number in /usr/sysgen/system and the major node number in the file add.devices. A sample "vmtm" file has been included for your convenience. 4. Make a new kernel by using the command lboot -u /unix.install 5. Reboot the system! The files config* are used to build a program which sets up the C004 on the Parsytec board to allow all four transputers to be available from the host. This program assumes that transputer 'A', link 0 is connected to link adapter '0' and that transputer 'A', link 1 is connected to the control link of the C004. The program connects transputer 'B', link 0 to link adapter 1, transputer 'C', link 0 to link adapter 2 and transputer 'D', link 0 to link adapter 3. It was build using the Tool Set but could be easily modified to work with the TDS. To use the existing executable enter iserver -sb config.b8h -sl /dev/vmtm1 This will boot transputer 'A' and will cause the link adaptor to be configured as described above.