Installation Guide Reference Manual
for Universal QNX Device Driver
for DigiCHANNEL Intellegent Communications Boards

92000099B

Introduction
This QNX Operating System Universal Device Administrator software 
and documentation is for the PC/X* series (PC/Xi and PC/Xe), the
MC/Xi, the COM/Xi, the PC/Xem, the PC/Xm and the C/X (EISA, ISA
and MCA) Cluster Controllers.

The Device Administrator Task is invoked from the command line, or 
from the sys.init.0 file (or sys.init.{node#} file if part of a 
network).  It must be invoked only once and must include the 
necessary operating parameters for all DigiCHANNEL intelligent 
boards to be used in the system.

The Device Administrator Task can support up to the QNX maximum 
of 32 channels (devices) per node.

An additional utility program, SALT, is provided to set an alternate pin 
configuration to provide full modem control on 8-pin RJ-45 connectors 
(normally full modem control can only be achieved with 10-pin RJ-45 
connectors).
 
Before invoking the Universal Device Administrator 
software, you must complete the hardware installation 
of the board(s) according to the instructions in the 
associated Installation Guide and Reference Manual.

o	All legal I/O port and memory start addresses are 
	supported, as long as they do not conflict with 
	other devices (including other DigiCHANNEL 
	products) in the system.
o	PC/Xe, PC/Xi, PC/Xem, PC/Xm and C/X host 
	adapter boards may all have the same memory 
	start address.  COM/Xi and MC/Xi boards must 
	have unique memory start addresses.
o	All boards must have unique I/O port addresses.

The Distribution Diskette

The diskette accompanying this manual contains all of the files and 
documentation needed to install the DigiWARE QNX Universal 
Intelligent Device Driver in your system.  A list of these files follows:

qall		The executable administrator task
Install.doc	Installation instructions
Relnotes.doc	Release Notes
salt		Executable to set Alt-Pin modem control 
processing
salt.c		C source code for the SALT utility

The following are binary files needed to drive the various kinds of 
DigiBoard hardware.  These files need to be in a single directory and 
include (though are not necessarily limited to) the following:
	cxbios		sxbios		fxbios
	cxfep		sxfep		fxfep			mxfep
	cxrmt

All files on the distribution diskette must be loaded into a single 
directory (the default directory is /drivers/digi).

Copying Files to Your Hard Disk

From the root ("/") directory of the node from which you boot QNX, 
enter the following command to copy all files from the distribution 
diskette:

backup 1:/ /drivers/digi +a

The destination directory, /drivers/digi is important.  However, 
the files may be copied into any directory desired, as long as the full 
path is specified in the command line to invoke the driver-see 
description of option flags.


Invoking the Device Administrator

QALL takes all of its parameters from the command line.  The 
Administrator task should be called only once each time the QNX 
system is booted, and all boards to be driven by the task must be 
identified in the command line.  Any DigiCHANNEL intelligent board in 
the system that has not been identified by QALL will be ignored.

Note that QALL runs in the background, and that if it is invoked from 
the sys.init file, it is possible that other tasks may be started before 
QALL has completed initialization of the DigiCHANNEL boards.  This 
is fine unless those subsequent tasks expect the boards to be up and 
running.  To prevent this "race" condition, place a sleep after the QALL 
command in sys.init (10 seconds is a good initial value; this can be 
adjusted depending on the number and type of boards in the system).

Use the following command to start QALL:
qall p=io m=ms c=bd[, p=io m=ms c=bd] [, ... ] [f=digipath] [-v] &

Description of Parameters
p=io	Specifies the I/O port address of the board.  Every board 
	must have its own unique I/O address.  QALL supports all 
	legal I/O addresses (see the Hardware Installation manual 
	for your board for the available choices), as long as there is 
	no conflict with other devices in the system.
	p=300		Look for card at I/O address 0x300 (ISA, 
	MCA machines)
	p=2005	Look for card at I/O address 0x2005 (EISA 
	machines)  NOTE: I/O addresses for EISA 
	machines are always 4 digits.  The first digit 
	indicates the physical slot number.
m=ms	Specifies the starting address for the board's dual-ported 
	memory.  This is the full 32-bit address.  PC/Xi, PC/Xe, 
	EISA C/X and ISA C/X boards may share the same 
	memory addresses.  COM/Xi and Micro Channel boards 
	must have unique memory start addresses.
	m=d0000	Address the board's dual-ported memory at 
	0x000D0000 (in the BIOS expansion area 
	below 1 MB).
	m=e80000	Address the board at 0x00E80000 (14.5 
	MB-note that if your system has more than 14 
	megabytes of RAM this address is unavailable).


c=bd	Board type.  Used to identify the board and its 
	configuration.  If this parameter is omitted, board is 
	assumed to be a PC/X* (PC/Xi or PC/Xe) if the host is 
	an ISA or EISA machine, or an MC/Xi if the host is an 
	MCA (PS/2) machine.
c=x	COM/Xi with 1K buffers (no window swapping) 

c=X	COM/Xi with 8K buffers (employs window swapping) 

NOTE:  Using 8K buffers will result in a slight degradation of
performance in favor of larger capacity.  The COM/Xi accesses 
memory through a 32K window, so "window swapping" is necessary.
This is unnecessary with 1K buffers.

c=p	PC/Xem or PC/Xm
c=10	C/X with one Concentrator on line 1 only
c=01	C/X with one Concentrator on line 2 only
c=11	C/X with one Concentrator on each of lines 1 and 2 
c=20	C/X with two Concentrators, both on line 1
c=02	C/X with two Concentrators, both on line 2

f=digipath
	Directory in which driver and data files are located.  
	Default: /drivers/digi

-v	Non-Verbose - Suppress messages

Examples

Example 1:
For an ISA C/X at I/O port 0x228, memory start address 
0x000D8000, with one Concentrator on each of lines 1 and 2; driver 
and data files to be found in directory /dfiles.

qall p=228 m=d8000 c=11 f=/dfiles &

Example 2:
For an EISA C/X  at I/O port 0x3005, memory start address 
0x000D8000 with one Concentrator on line 2 plus a PC/Xi at I/O port 
0x320, memory start address 0x000D0000:

qall p=3005 m=d8000 c=01, p=320 m=d0000 &

Example 3:
For a COM/Xi with 8K buffers, addressed at I/O port 0x320 and 
memory start address 0x000D8000 plus an ISA C/X at I/O port 
0x228 and memory window 0x00E00000 with one Concentrator on 
line 1:

qall p=320 m=d8000 c=X, p=228 m=e00000 c=10 &

Installation Message

If the board is correctly installed, you should get a message similar to 
the following example (unless you have used the -v command-line 
option):

DigiChannel QALL QNX Device Administrator V1.0.0 
Card	  I/O Port Address   Shared Memory  Channels
PX/Xi	  0x320	             0x00e80000	    8
8 TTY Devices mounted.


If the driver reports an error, carefully check the configuration of the 
board.  The most common problem is with memory addressing.  Either 
the board is incorrectly addressed or there is a conflict between the 
board and some other device which may be trying to use the same 
memory addresses.  

Memory Cache

If your board is set to a memory address above 1 meg, be sure that the 
memory cache is disabled.  If the cache cannot be disabled, use a 
memory start address below 1 meg.  The most likely choices below 1 
meg are 0x000D0000 (for all EISA and ISA boards) and 
0x000D8000 (C/X, COM/Xi).


Activating the Ports

Once the administrator task is running, verify that each terminal 
connected to the board can log in to the system.  To get a login 
message, press .  If everything is set up correctly, a login 
message should appear on the screen.

If nothing happens after you press , check the cable 
connection between the board and the terminal.  If the terminal displays 
garbage characters, check the terminal set-up.  It should be set for 
9600 baud, 8 data bits, no parity and 1 stop bit.


Alternate RJ-45 Pin Assignments

DigiCHANNEL products use 10-pin RJ-45 connectors in order to 
support all of the signals normally available on a 9-wire RS-232 con-
nection.  However, many commercially available RJ-45 connectors 
have only 8 pins.  8-pin RJ-45 plugs will fit in a 10-pin jack, but the first 
and last pins (numbers 1 and 10) are not connected.  DigiBoard uses 
these pins for the modem control signals RI (Ring Indicator, pin 1) and 
DCD (Data Carrier Detect, pin 10). While Ring Indicator is rarely a 
concern (since most modems have auto-answer capability), Data 
Carrier Detect is often monitored to insure that the modem has 
established, and is maintaining, a valid connection with a remote 
modem.  

To facilitate the use of 8-pin RJ-45 connectors in modem applications, 
a special utility, SALT (for Set Alt-Pin), has been provided.  SALT 
instructs the device administrator to monitor pin 1 of an 8-pin RJ-45 
connector for DCD.

The format for salt is:

salt device_name on|off

where device_name is the name of the device to be affected (e.g. 
$tty23).

See the Hardware Installation guide for your board for cabling diagrams 
and pin assignment charts for DB-25 and RJ-45 connectors.


Error Messages

Certain error messages will be sent to the console if QALL has 
problems setting up the DigiCHANNEL ports.  The following table 
details the messages and the probable causes.

Failed to find data files
One or more files were missing from the digipath directory.  The 
default digipath directory is /drivers/digi.  If you have 
loaded the driver and data files into a different directory, that 
directory must be specified in the qall command line with the 
f=digipath parameter.

Driver needs Protected mode QNX!
This driver requires V.3.12 or later of QNX, running in protected 
mode.

Unable to find QNX port to attach to
Probably due to too many processes running on the system; the 
driver cannot find a free QNX port to which to attach.

Must be a super user
Only a user with SUPER-USER privileges can start up a privileged 
administrator task.

Failed to attach to name $QALL$
The qall administrator is already loaded and running on this node. 
Do a "tsk" to find its PID.

Failed to determine Hardware Architecture
System calls made to identify the system architecture (ISA, EISA, 
MCA) have failed.  Probably due to a hardware error.


No devices initialized or mounted!
No channels initialized successfully. Could be a memory conflict, or 
wrong card was identified in qall command (c= option).

Too many devices!
QNX only supports 32 local devices per node.

Failed to allocate Card Base Memory Selector
System call to map physical memory has failed.  Too many pro-
cesses in the system may be competing for memory handles.

Failed to RESET the I/O Port
I/O port address may be set incorrectly or conflict with another 
adapter.  Verify setting, or try another address.

Failed to BOOT the BIOS
BIOS on DigiBoard will not respond to commands from the driver. 
Usually means that the driver cannot reliably read/write to the dual-
ported RAM.  This could be due to a cache conflict (if the board is 
addressed above 1 meg) or a conflict with another device's 
memory. It could also mean that the wrong address was given in the 
qall command line.

Failed to BOOT the uploaded FEPOS
Card type specification is probably incorrect. Could also indicate an 
incorrect memory address specification or a dual-ported memory 
conflict.

Failed to Read Initialization Information
Shared memory conflict.  Try a different address.

Unable to adopt devices
Another device administrator has assumed the device names 
"DBQ," preventing this administrator from doing so.