Installation Guide SCO OpenServer Async Products
Software Installation
Installation of the DigiBoard device drivers is a two-part procedure:
First, the MenuPort Interface (MPI) package is installed through the Custom
utility onto your system. Second, the MPI package is run and the appropriate
device drivers for your system are installed and configured.
Installing the MenuPort Interface (MPI) Package
From Diskettes:
1. Log in as super-user (root).
2. Run custom. Select "Software" followed by "Intall New".
Then select your current machine name for host machine [Continue].
3. Insert the first driver diskette into your diskette drive [Continue].
4. Select the "Floppy Disk Drive" for the Media Device [Continue]
5. Select the Digiware MPI software from the list [Install]
6. Insert the second diskette when prompted.
Running the MenuPort Interface (MPI) Program
To run the MenuPort Interface program, log in as root and enter:
mpi
After the restricted rights legend, you will see the Main menu. Items in
this menu are:
* Config, which lets you install, change and remove device drivers for
specific boards and operating systems.
* System, which lets you build a new kernel, update installed device
drivers and create an image of the kernel.
* Monitor, which runs DigiBoard Port Authority (DPA), a software diagnostic
tool that allows users to easily monitor the status of the Front End
Processor/Operating System (FEP/OS), which runs on all DigiBoard
intelligent serial port boards. The DPA software also shows the status
of the individual ports. With DPA, system managers can tell instantly
if a board is no longer working, if its performance level decreases, of
if a port is non-functional, enabling them to work more productively and
solve system errors more quickly. DPA also provides a loop back test to
confirm that the board can transmit and receive data.
* Notes, which displays the release notes for the supported device drivers.
MPI features context sensitive help screens; press at any
time for an explanation of the currently displayed information
and choices.
Device Names SCO UNIX
PC/Xe, PC/Xi, MC/Xe and MC/Xi Boards
Format used for port names: /dev/ttyibp, /dev/pribp
ttyi Base name.
pri Base name for DigiPrint transparent printing.
b Board number (1-4).
p 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. Primarily used with 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. Primarily used with modems.
For example, Port 4 Board 2 will be /dev/ttyi2d. The same port with
modem control enabled would be named /dev/ttyi2D.
C/X, EPC/X and Xem Systems
Format used for port names: /dev/ttycp, /dev/prcp
tty Base name.
pr Base name for DigiPrint transparent printing.
c Concentrator or EBI module letter I.D:
a-z (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. Primarily used with directly
connected terminals and printers.
A-Z (upper case) are used for modem control ports. These ports
require DCD (Data Carrier Detect) to be asserted before they can
transmit data. Primarily used with modems.
p Port number on the individual concentrator or EBI module (01-64).
For example, Port 4 on concentrator or PORTS module "b" will be
/dev/ttyb04. The same port with modem control enabled would be named
/dev/ttyB04.
Enabling the New Ports SCO UNIX
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 the date appears on the 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 (UNIX
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 /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.
If the port tests above work, but you still can't respawn a
getty, it is probably because DCD is not asserted.
Remember that modem controlled ports (where the port ID is
a capital letter; e.g. ttyi1A) must have Data Carrier Detect
(DCD) asserted before they can function. If DCD is not
connected to an active output line of the peripheral device, it
must be defeated, either by "tying it high" (e.g. connecting it
to the same port's DTR line) or by issuing the command
ditty forcedcd ttyi1A (assuming that the port in question is ttyi1A).
Another way to bypass the DCD requirement is to use non
modem control devices (where the port ID is a small letter;
e.g. ttyi1a). Non modem control devices function
identically to modem control devices, except that they do not
require DCD to be asserted in order to function.
2. The Terminal Control Database must be updated to include the new devices.
Add the DigiBoard device information using the following SCO UNIX
sysadmsh command sequence:
Accounts*Terminal:Create
Fill in the required information on the form displayed.
3. To activate a port for use with a terminal, enter the following command:
enable ttyi1a
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" serial line characteristics. This command is recommended for
any port that has a printer connected to it. The command may be placed in
one of the following files so that it is automatically executed whenever
the system is booted. SCO UNIX: /etc/rc.d/8/userdef
EXAMPLES:
The commands shown below result in 9600,8,1,N, with software flow control.
SCO UNIX:
ditty printer ixon opost onlcr ttyi1a
Uninstalling the MPI Software Package
Uninstalling the MPI software package is a two-part procedure. First, you must
remove any device drivers that were installed via the MPI software, then you
remove the MPI software package itself.
Removing Device Drivers
1. To run the MenuPort Interface program, log in as root and enter: mpi
2. From the Main menu, select Config.
3. Now select Remove, from the Config menu.
4. From the Pick List, select the device driver you wish to remove.
Repeat this step for all installed device drivers.
Removing the MPI Software Package SCO UNIX
1. Log onto the console as super-user (root), and enter the following
command: custom
2. When the operating system menu asks, choose REMOVE.
3. Select mpi. The software will respond with:
Removing DigiBoard MenuPort Interface Package.
4. Quit custom, and remove the perms file: rm /etc/perms/mpi
5. Now perform a system shutdown and reboot to activate the new kernel.
----------------------------------------------------------------------------
Error Messages
The following error messages are generated by the driver:
***WARNING*** No board found at port 0x320, check switch settings.
or
***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).
or
***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.
|
|
