1. Introduction
This serial driver supports following multiport boards.
– Xtreme/104
– Xtreme/104 Opto
– Xtreme/104 Iso (12-Port)
– DFlex & DFlex/104
This driver and installation procedure have been developed upon Linux kernel
2.4.x.
All the drivers and utilities are published in form of source code under
GNU General Public License in this version. Please refer to GNU General
Public License announcement in each source code file for more detail.
The driver can be installed as a loadable module. Before you install the
driver, please refer to hardware installation procedure in the User’s Manual.
Once the driver is installed there are some utilties that will allow to use
some of the extra features of the driver in the utilities directory found in
this driver package.
—————————————————————————–
2. System Requirement
– Hardware platform: Intel x86
– Kernel version: 2.4.x
– gcc version 2.72 or later
– Maximum 8 boards can be installed, with a combined maximum of 64 ports
—————————————————————————–
3. Installation
3.1 Hardware Installation
You may need to adjust IRQ usage in BIOS to avoid IRQ conflict with legacy
ISA devices.
3.2 Driver files and device naming convention
The driver file may be obtained from ftp, CD-ROM or floppy disk. The
first step is to copy the driver file “ctixt-24-X.XX.tar.gz”
onto your hard disk, then execute ‘tar -xzf ctixt-24-X.XX.tar.gz’,
where X.XX is the version of the driver package. This directory will be referred to as {ctiroot}.
3.3 Software Installation
1. Install Serial Driver In The Kernel
Go to the serial source code directory
# cd {ctiroot}/serial/
Run the installer
# ./install-in-kernel
You should have the linux kernel source in a subdirectory. This is
usually /usr/src/linux but may be different for your system. This
directory will be referenced by {linux}.
The install script assumes {linux} is /usr/src/linux; if it is not,
you can supply the proper path on the command line:
# install-in-kernel {linux}
2. Configure CTI Board(s)
Go to the config directory
# cd {ctiroot}/config
Run the configuration script
# ./ctix-config
3. Recompile Your Linux Kernel
Please refer to our KDB guide for this located in the config directory, or on our website here:
https://connecttech.com/KnowledgeDatabase/kdb307.htm
4. Make Device Nodes
After you’ve booted the new kernel:
# vi {log_path}/messages
where {log_path} is where the system logs are stored. This is usually
/var/log
Go to the bottom of the file and seach backwards for references to
“ttySxx” where xx is a number. You should see ttyS0 and ttyS1 for the
standard serial ports, as well as a ttySxx entrie for each installed
Xtreme port. In order to use the new ports, these ttySxx
entries must exist in the /dev directory. If they do not exist (they
aren’t created automatically, but do persist after reboots) you must
make them with the following command:
# mknod -m {mode} /dev/ttySxx c 4 yy
where {mode} is the file mode (permissions) you wish the device to
have (600 is often good), xx is the number from the log file and
yy = xx + 64.
NOTE: Some /dev entries may already exist on some distributions. If
they do exist, then they don’t need to be created with this step.
You may also wish to make the corresponding cuaxx devices, but they
are being phased out:
# mknod -m {mode} /dev/cuaxx c 5 yy
xx and yy should match the xx and yy from the previous mknod command.
For example: if you installed a 4 port DFlex and you found ttyS12-15
listed in the messages log, you would execute:
# mknod -m 600 /dev/ttyS12 c 4 76
# mknod -m 600 /dev/ttyS13 c 4 77
# mknod -m 600 /dev/ttyS14 c 4 78
# mknod -m 600 /dev/ttyS15 c 4 79
and optionally execute:
# mknod -m 600 /dev/cua12 c 5 76
# mknod -m 600 /dev/cua13 c 5 77
# mknod -m 600 /dev/cua14 c 5 78
# mknod -m 600 /dev/cua15 c 5 79
3.5 Verify driver installation
You may refer to /var/log/messages to check the latest status
log reported by this driver whenever it’s activated. Also, you can
retrieve board and port information from the proc filesystem. To
view this information do the following:
# cat /proc/tty/driver/serial
You can also veryfiy the port have been correct installed by checking
your dmesg. You can do that by issuing the following:
# dmesg | grep ttyS
3.6 RS485 modes
When using RS485, you must tell the driver what mode the port has
been jumpered as. This is accomplished in one of two ways.
3.6.1 Use CTI’s set485 utility
Connect Tech has a small utility called set485 which comes packaged
with the BlueStorm driver. This utility allows you to set each port
to full duplex, half duplex, or multi-drop slave. The utilites can
be found in the utilties directory contained in our package. More
information can be found on this in the REAME in that directory.
3.6.2 Send IOCTLs from your app
Included with the driver source is ‘cti485.h’. This header
includes defines for IOCTLs used to get and set the 485 mode
of a port. See ‘cti485.h’ for more information.