Installation Guide for DigiBoard MC/Xe and MC/Xi Intelligent Boards in SCO XENIX (legacy)


	Technical Support Drivers Firmware Upgrades FAQs Product Documentation Cabling Support Tools Legacy Products About Digi Support Knowledge Base Online Support Request FTP Site Related Links Inside Out Networks

Home > Support >kbase >

Installation Guide for DigiBoard MC/Xe and MC/Xi Intelligent Boards in SCO XENIX (legacy) Installation Guide for DigiBoard MC/Xe and MC/Xi Intelligent Boards in SCO XENIX (legacy)

Installation Guide for DigiBoard MC/Xe and MC/Xi Intelligent Boards SCO XENIX

Software Installation

Part One: Linking a New Kernel MC/Xe and MC/Xi Boards

1. Log onto the console as super user (root).
2. Insert the DigiWARE diskette and enter: custom
3. The system will now display the Custom menu. If the device driver has been previously installed, the Custom menu lists DigiWARE. Select this. If not, select Option 4 to add a supported product. The system will display:

Installing custom data files... Insert distribution volume 1, and press or enter q to quit:

4. Press and the system will display:

1. Install one or more packages
2. Remove one or more packages
3. List the available packages
4. List the files in a package
5. Install a single file
6. Select a new set to customize
7. Display current disk usage
8. Help

Select an option or press q to quit:

Select Option 1 to install the DigiWARE software. The system will display:

Name  Inst  Size  DigiWARE for PC/X* Board packages 
----------------------------------------------------------------- 
MCXX  NO    992   DigiBoard MC/X* async driver V5.2.0

Enter the package(s) to install or enter q to return to the menu:

Enter: mcxx (for MC/Xe or MC/Xi boards)

The system will then display:

Insert DigiWARE package volume 1 and press or enter q to return to the menu:

Volume 1 should still be in the diskette drive. Press , and the system will display:

Extracting files...

5. You will see the following (or similar) screen:

Each DigiBoard MC/X* board requires an I/O port address and an 8K to 128K block of memory. Please select these to avoid conflicts with other boards you may have installed in your system.

How many DigiBoard MC/X* boards do you wish to install (1-4)?

Enter the number of boards you are installing. Note that boards are installed by slot number; the board closest to slot 0 is board number 1, and so on.

6. You will now be asked for the number of ports on the board. Enter "2", "4", "8" or "16", as appropriate.

If you are installing multiple boards, step 6 will be repeated for each board.

7. You will now be shown the config you have chosen.

You have selected the following configuration:

        Board   I/O Address   Memory Address   Ports 
        -------------------------------------------- 
          1        0x328        0x000D0000       2 
          2        0xF1F0       0x00FA0000       16 
          3        0xF2F0       0x00FC0000       8 
          4        0x308        0x000D2000       4

Is this configuration acceptable (y or n)?

If the information is correct, answer "y". Otherwise, answer "n", and you will be returned to step 5.

8. Next, you need to select the altpin setting. This allows alternate wiring of the RJ-45 modular connectors. The default for altpin is OFF, giving you the standard DigiBoard RJ-45 pinouts. Setting altpin to ON enables the alternate RJ-45 pinouts.

The softw asks: default setting for altpin is off. Is this acceptable (y or n)?

Answer "y" or "n" as appropriate. Note that answering "n" here activates the altpin configuration for all ports.

altpin should be activated only on boards equipped with RJ- 45 connectors. If your board is equipped with DB-25 or DB- 9 connectors, altpin should be off.

9. Installing DigiScreen

DigiScreen is DigiBoard's multiple screen utility that allows a single physical terminal to be connected to several virtual terminal sessions (screens) at one time. The software installation script gives you the option of installing it.

The software asks: Do you wish to install DigiScreen (y or n)?

If you answer "n", proceed to Creating New Devices.

10. The software continues:

Each session under DigiScreen requires a DigiScreen device. How many DigiScreen devices do you wish installed? (max. 256, default is 32)

11. The software now asks: Do you wish to make new device nodes (y or n)?

Most users will need to create the new devices at this time, and should answer y and proceed to Part Two: Creating New Devices.

Part Two: Creating New Devices

This portion of the installation procedure creates devices in /dev and edits /etc/ttys, giving the operating system the info it needs to use the ports.

The software displays:

This script also installs the information needed by XENIX to use these additional ports. The DigiBoard PC/X* async driver will support up to four boards for a maximum of sixty-four asynchronous serial ports.

By default, the ports are installed as ttyi1a through ttyi1p. Ports with modem control are installed as ttyi1A through ttyi1P. DigiPrint ports are installed as pri1a through pri1p. DigiPrint ports with modem control are installed as pri1A through pri1P.

Is this acceptable (y or n)?

Answer "y" if the default device names are acceptable. You may then proceed to Part Three: Installing the New Kernel. If you answer "n", you will see the following:

Device names will be a base name with the board number (1-4) and the port number (a-p) appended.

Please enter base name to use:

Enter the new base name.

You will then be asked for an alternative DigiPrint printer base name (the default is pri1a through pri4p). Enter the new DigiPrint base name. Now proceed to Part Three: Installing the New Kernel.

The devices are named according to the following conventions:

Format used for port names:

ttyibp, pribp 
ttyi	Default base name.  You may define a different one.   
pri	Default base name for DigiPrint transparent printing. 
b	Board number (1-4). 
p	Port identifier

Port Identifier - a-p (lower case) are used for non modem control ports. These ports do not require DCD (Data Carrier Detect) to be asserted before they can transmit data. These ports are used primarily for directly connected terminals and printers. A-P (upper case) are used for modem control ports. These ports require DCD (Data Carrier Detect) to be asserted before they can transmit data. These ports are used primarily for modems.

For example, if "ttyi" is the base name, Port 4 Board 2 will be ttyi2d. The same port with modem control enabled would be named ttyi2D.

Part Three: Installing the New Kernel The driver installation is now complete, and the new kernel must be installed.

1. You will see:

The new kernel with driver modifications is in /usr/sys/conf/xenix.

Do you want this kernel to boot by default (y or n)? If you enter "y", you will see:

The old kernel is installed in /xenix.old

The new kernel is installed in /xenix

Enter the following command to reboot your system and activate the new kernel:

shutdown 0

If you enter "n", you will see:

Changes will not be reflected unless /usr/sys/conf/xenix is copied to /xenix.

2. The system displays:

Select an option or press q to quit: Enter "q".

3. If you chose to have the new kernel boot by default, enter the following

command to boot the new kernel: shutdown 0

4. When the computer reboots, you should see messages which indicate the board is functioning. Your screen will look something like this:

device    address     vector   dma       comment 
------------------------------------------------------------ 
%pcxx     0x320         -       -     mem=0x000D0000 
                                      Ports=8 
                                      PC/Xe V x.x.x

Part Four: Enabling the New Ports

1. Connect terminals to the ports (using a null modem, if necessary) and test the connections to each terminal by entering the following command for each port added:

date > /dev/ttyi1a

(Assuming the terminal is connected to ttyi1a.)

(Please note that in the above, the "date" command is used as a simple test, to provide text output that can be redirected; there is no other significance to "date" in this test.)

* If date appears on terminal's screen, the device is properly connected.

* If the date does not appear on the terminal's screen, then that terminal is not receiving data; check the power, cables, connections, etc...

* If nonsense characters are printed on the terminal's screen, check the baud rates, data bits, stop bits, and parity setting on your terminal (the default parameters are 9600 baud, 8 data bits, 1 stop bit, and no parity).

Another test you can perform will verify that a port can both transmit and receive data: Connect the port's transmit and receive lines together (pins 2 and 3 of a DB-25 connector, or the middle two pins of an RJ-45 connector), and enter the following commands:

cat cat /etc/termcap > /dev/ttyi1a

The first command runs in the background, and directs all input from ttyi1a to stdout (your screen). The second command transmits the termcap file to ttyi1a. If the port is working, the data is sent out the port, received back by the same port and displayed on your screen. If the port fails, check another port. If more than one port fails, the problem is probably due to memory contention, rather than defective hardware. Try reinstalling the device driver with a different memory start address. Once you can redirect output to a terminal with the test above, perform the following steps to enable that port.

2. To activate a port for use with a terminal, enter the following command:

enable ttyi1a

If you've assigned a new base name, replace the "tty" above with the name you chose. The above command will cause a login prompt to be sent to the terminal connected to ttyi1a. To activate the other ports, repeat the enable command with the appropriate port name.

Serial Printers

To prepare a port for connection to a printer, enter the following command:

ditty printer [baud rate and flow control options] ttyi1a

This command forces the specified port to stay open, thus preserving any "non- sticky" options complete descriptions of all ditty parameters) for that port. This command is recommended for any port that has a printer connected to it. The command may be placed in /etc/rc.d/8/userdef so that it is automatically executed whenever the system is booted.

EXAMPLE:

The command shown below results in 9600,8,1,N, with software flow control.

ditty printer ixon opost onlcr ttyi1a

Un-Installing the Device Driver

Removing the driver from the kernel is a two-part process. First, the driver references are removed from the system configuration files. Secondly, a new kernel is linked, and copied to the root directory.

Enter the following commands to un-install the device driver software:

1. Log on as super-user (root), and enter the following command: custom

2. When the operating system menu asks, choose REMOVE.

3. Select pcxx or mcxx.

4. Select the DigiBoard driver. The software will respond with:

Removing DigiBoard PC/XX intelligent async serial driver.

5. Next, the software asks:

Removing DigiScreen devices will affect ALL DigiBoard Drivers. Do you wish to remove DigiScreen devices (y or n)? Answer "y" or "n".

6. The software asks:

Do you wish to remove DigiBoard PC/XX entries from /etc/ttytype (y or n)?

Answer "y" if these entries are no longer needed (or if you are in doubt), or answer "n" if you wish to preserve the old entries.

7. You will see: Do you want this kernel to boot by default (y or n)?

Answer "y". The system displays: Do you want the kernel environment rebuilt (y or n)?

Answer "y". You will see:

The kernel has been successfully linked and installed. To activate it, reboot your system.

8. Remove the perms file: rm /etc/perms/pcxx

9. Enter the following command to boot the new kernel: shutdown 0

Error Messages

The following error messages are generated by the driver:

***WARNING*** No board found at port 0x320, check switch settings.

***WARNING*** PC/Xi at port 0x320 not resetting, check switch settings

What it means: The board doesn't respond to reset.

Action to take:

Make sure the board is fully seated in the computer's slot. Make sure the board's jumper settings and the device driver's settings match. Potential hardware problem.

***WARNING*** Driver memory allocation failed for PC/Xi at port 0x320.

What it means: The operating system would not allocate memory to the driver.

Action to take: Adjust kernel resources.

***WARNING*** No memory at 0xd8000 for PC/Xe at port 0x320, check switch settings

What it means: The driver cannot read the board's dual ported memory.

Action to take:

Make sure the board is fully seated in the computer's slot. Make sure the board's settings and the device driver's settings match. Make sure the jumpers or DIP switches are in their proper positions. Make sure that there is no memory contention with other devices. Make sure you haven't selected an 8K address for a 64K board. Potential hardware problem.

***WARNING*** PC/Xi at port 0x320 failed diagnostics. Error #(N1,N2).

What it means:

The driver encountered an error executing on-board BIOS. N1 and N2 are status bits at the time of the failure.

Action to take:

Make sure the jumpers or DIP switches are in their proper positions. Make sure there is no memory contention with other devices. Potential software problem. Potential hardware problem.

***WARNING*** PC/Xi at port 0x320 failed BIOS function #X. Error #(N1,N2).

***WARNING*** FEPOS for PC/Xe at port 0x320 not functioning. Error #(N1,N2).

What it means:

The driver encountered an error executing on-board FEPOS. X is the BIOS function that failed, N1 and N2 are status bits at the time of the failure.

Action to take:

Make sure the jumpers or DIP switches are in their proper positions. Make sure there is no memory contention with other devices. Potential software problem. Potential hardware problem.