Quatech DSP-100 User Manual

DSP-100
Dual Channel RS-232 PCMCIA
Asynchronous Adapter
for PCMCIA Card Standard compatible machines
User's Manual
INTERFACE CARDS FOR IBM PC/AT AND PS/2
QUATECH, INC. TEL: (330) 434-3154 662 Wolf Ledges Parkway FAX: (330) 434-1409 Akron, Ohio 44311 www.Quatech.com
Warranty Information
Quatech Inc. warrants the DSP-100 to be free of defects for five (5) year from the date of
purchase. Quatech Inc. will repair or replace any adapter that fails to perform under normal operating conditions and in accordance with the procedures outlined in this document during the warranty period. Any damage that results from improper installation, operation, or general misuse voids all warranty rights.
The authors have taken due care in the preparation of this document and any associated software program(s). In no event will Quatech Inc. be liable for damages of any kind, incidental or consequential, in regard to or arising out of the performance or form of the materials presented herein and in the program(s) accompanying this document. No representation is made regarding the suitability of this product for any particular purpose.
Quatech Inc. reserves the right to edit or append to this document or the product(s) to which it refers at any time and without notice.
Please complete the following information and retain for your records. Have this information available when requesting warranty service.
Date of purchase:
Model Number: DSP-100
Product Description: Two Channel Asynchronous RS-232 Communications PCMCIA Adapter
Serial Number:
Declaration of Conformity
Manufacturer's Name: Quatech Inc.
Manufacturer's Address: 662 Wolf Ledges Parkway
Akron, OH 44311 (USA)
Application of Council Directive: 89/336/EEC
Standards to which Conformity is Declared: * EN50081-1
(EN55022)
* EN50082-1 (IEC 801-2, IEC 801-3, & IEC 801-4)
Type of Equipment: Information Technology Equipment
Equipment Class: Commercial, Residential, & Light
Industrial
Product Name: PCMCIA Card
Model Number : DSP-100
Table of Contents
11 . Introduction ........................................................
32 . DOS / Windows 3.x Installation .................................
42.1 DSP-100 Client Driver for DOS ...................................
42.1.1 Client Driver Installation ....................................
52.1.2 Command Line Options ....................................
92.1.3 Common Problems .........................................
102.2 DSP-100 Enabler for DOS .......................................
112.2.1 Command Line Options ...................................
142.2.2 Common Problems ........................................
153 . Windows 95 Installation .........................................
153.1 Installing a DSP-100 Under Windows 95. .........................
163.2 DSP-100 Resource Settings in Windows 95 ........................
163.2.1 Viewing Resource Settings with Device Manager ..............
183.2.2 Changing Resource Settings with Device Manager .............
214 . Windows 98/Millennium (ME) Installation ...................
214.1 Installing a DSP-100 Under Windows 98/ME. .....................
224.2 DSP-100 Resource Settings in Windows 98/ME ....................
224.2.1 Viewing Resource Settings with Device Manager ..............
244.2.2 Changing Resource Settings with Device Manager .............
275 . Windows 2000 Installation .....................................
275.1 Installing a DSP-100 Under Windows 2000. .......................
285.2 DSP-100 Resource Settings in Windows 2000 ......................
285.2.1 Viewing Resource Settings with Device Manager ..............
295.2.2 Changing Resource Settings with Device Manager .............
326 Windows NT ......................................................
326.1 Installing DSP-100 Under Windows NT ...........................
367 Windows CE .......................................................
388 OS/2 Installation ..................................................
398.1 Command Line Options ........................................
398.1.1 Configuring With "System Assigned" Resources ..............
408.1.2 Configuring With "User Assigned" Resources .................
418.1.3 Advanced Configuration Topics ............................
428.2 Monitoring The Status Of PCMCIA Cards .........................
428.3 Common Problems ............................................
449 . Unix Support ......................................................
449.1 UNIX Enhanced Serial Device Driver .............................
4610 . Hardware Information ..........................................
4811 . External Connections ............................................
5012 . Specifications ....................................................
1. Introduction
The DSP-100 provides two independent RS-232 asynchronous serial communications interfaces for systems equipped with PCMCIA Type II and/or Type III expansion sockets. The DSP-100 is a PCMCIA Type II (5 mm) card and is PCMCIA PC Card Standard Specification 2.1 compliant.
The DSP-100's serial ports are implemented using 16C550 Universal Asynchronous Receiver/Transmitters (UARTs) which are the recommended communications interface for multitasking environments and with applications involving high data transfer rates.
The DSP-100's two serial ports are addressable in two modes:
1. 'Block Mode': The two serial ports are configured in one 16-byte continuous
block of I/O address space. The block must begin on an even 16-byte
division. Both serial ports share one IRQ level.
2. 'COM Mode': The two serial ports are configured at the standard COM port
I/O address locations. The ports may be configured as COM1 and COM3;
also, the ports may be configured as COM2 and COM4. Both serial ports
share one IRQ level.
A special interrupt status register is also available to simplify the software required to service multiple serial ports in an interrupt driven environments. See the Hardware Information section for details.
DSP-100 User's Manual 1
DSP-100 User's Manual 2
2. DOS / Windows 3.x Installation
Interfaces directly to Intel
82365SL
and
Interfaces to PCMCIA Card and Socket
File type: DOS executable
File type: DOS device driver
Enabler
(not recommended)
Client Driver
(recommended)
Two configuration software programs are provided with the DSP-100: a Client Driver, DSP100CL.SYS, and a card Enabler, DSP100EN.EXE. Both of these programs are executed from DOS (before entering Windows) and allow operation of the DSP-100 in both the DOS and Windows 3.x environments. For optimal operation, however, the Client Driver is the preferred method of installation and configuration. The table below highlights the differences between these programs.
File name: DSP100EN.EXEFile name: DSP100CL.SYS
Services software (PCMCIA host adapter independent)
Allows automatic configuration of DSP-100 adapters upon insertion (Hot Swapping)
Requires PCMCIA Card and Socket Services software
other PCIC compatible PCMCIA host adapters
Does not support automatic configuration of DSP-100 adapters upon insertion (Hot Swapping)
Does not require PCMCIA Card and Socket Services software
Figure 1. Client Driver versus Enabler for DOS/Windows 3.x.
Card and Socket Services software is commercially available from several vendors for most desktop and laptop PCs. If you are unsure whether Card and Socket Services software is currently installed on your system, install the DSP-100 Client Driver as discussed in following section. When loaded, the Client Driver will display an error message if Card and Socket Services software is not detected.
DSP-100 User's Manual 3
2.1 DSP-100 Client Driver for DOS
Socket Services software is available from
Quatech
Inc.
In order to use the DSP-100 Client Driver, the system must be configured with Card and Socket Services software. Card and Socket Services software is not provided with the DSP-100 but is available from Quatech.
IMPORTANT:
Some versions of Card and Socket Services dated before 1993 do not support general purpose I/O cards. If after careful installation of the Client Driver the DSP-100 does not configure or operate properly, an updated version of Card and Socket Services may be required. Card and
2.1.1 Client Driver Installation
The following procedure is used to install the DSP-100 Client Driver:
1. Copy the file DSP100CL.SYS from the DSP-100 distribution diskette onto the system's hard drive.
2. Using an ASCII text editor, open the system's CONFIG.SYS file located in the root directory of the boot drive.
3. Locate the line(s) in the CONFIG.SYS file where the Card and Socket Services software is installed.
4. AFTER the line(s) installing the Card and Socket Services software, add the following line to the CONFIG.SYS file: DEVICE = drive:\path\DSP100CL.SYS options where options are the DSP-100 Client Driver command line options discussed on the following pages.
5. Save the CONFIG.SYS file and exit the text editor.
6. Insert the DSP-100 into one of the system's PCMCIA slots. NOTE: Since the DSP-100 Client Driver supports "Hot Swapping", it is not
necessary to have the DSP-100 installed when booting the system. By inserting the card before booting, however, the Client Driver will report the adapter configuration during the boot process thereby verifying the changes made to the CONFIG.SYS.
DSP-100 User's Manual 4
7. Reboot the system and note the message displayed when the DSP-100 Client Driver is loaded. If the Client Driver reports an "invalid command line option", correct the entry in the CONFIG.SYS file and reboot the system again. If the Client Driver reports "Card and Socket Services not found", a version of Card and Socket Services must be installed on the system or the DSP-100 Enabler program must be used to configure the adapter. If the Client Driver reports the desired adapter configuration, the installation process is complete and the DSP-100 may be removed and / or inserted from the system as desired. On each insertion into the PCMCIA socket, the DSP-100 will be automatically reconfigured according to the command line options.
2.1.2 Command Line Options
The DSP-100 Client Driver accepts up to eight command line arguments from the user to determine the configuration of the DSP-100. If any arguments are provided, the Client Driver will attempt to configure any DSP-100s with the options specified in the order they are entered on the command line. Each argument must be enclosed in parenthesis and must be separated from other arguments by a space on the command line. Within each argument, any or all of the following parameters may be specified using a comma (no spaces) to separate each parameter:
Baddress specifies a “block mode” base I/O address of the DSP-100 in hexadecimal.
This address must reside on an even 16-byte (10H) boundary. This option must be omitted if using the Dmode option. If both the Dmode and Baddress options are omitted, a “block mode” base address will be assigned by Card and Socket Services.
Dmode specifies a “COM” mode” base I/O address configuration for the DSP-100.
The D1 option configures the DSP-100 at COM1/COM3 (3F8 / 3E8), and the
D2 option configures the DSP-100 at COM2/COM4 (2F8 / 2E8). This option must be omitted if using the Baddress option. If both the Dmode and
Baddress options are omitted, a “block mode” base address will be assigned by Card and Socket Services.
Iirq specifies the interrupt level (IRQ) of the DSP-100 in decimal. irq must be
one of the following values: 3, 4, 5, 7, 9, 10, 11, 12, 14, 15, or 0 if no IRQ is desired. If this option is omitted, an interrupt level will be assigned by Card and Socket Services.
Ssocket specifies which PCMCIA socket the DSP-100 must be inserted into for this
configuration argument to be used. socket must be in the range 0 - 15. If this option is omitted, the configuration argument will apply to DSP-100s inserted into any socket.
DSP-100 User's Manual 5
U instructs the Client Driver to disable the DSP-100's interrupt status register
and enable the Scratchpad registers of the individual UARTs. This option is only required in very rare cases where an application program requires access to the UART's Scratchpad register. If this option is omitted, the DSP-100's interrupt status register is enabled and the UARTs' Scratchpad registers are disabled.
2.1.2.1 Example 1
DEVICE = C:\DSP-100\DSP100CL.SYS
In example 1, no command line arguments are specified. The Client Driver will configure a DSP-100 inserted into any socket in “block mode” with a base address and IRQ assigned by Card and Socket Services. The DSP-100's interrupt status register will be enabled.
2.1.2.2 Example 2
DEVICE = C:\DSP-100\DSP100CL.SYS (d1)
In example 2, a single command line argument is provided. The Client Driver will attempt to configure a DSP-100 inserted into any socket in “COM mode” at COM1/COM3 and an IRQ assigned by Card and Socket Services. If address COM1 (3F8) or COM3 (3E8) are unavailable, the DSP-100 will not be configured. If the Client Driver can successfully configure the DSP-100 its interrupt status register will be enabled.
DSP-100 User's Manual 6
2.1.2.3 Example 3
DEVICE = C:\DSP-100\DSP100CL.SYS (s0,b300,i5)
In example 3, a single command line argument is provided. The Client Driver will attempt to configure a DSP-100 inserted into socket 0 with a base address of 300H and IRQ 5. If address 300H or IRQ 5 is unavailable, the DSP-100 will not be configured. In addition, if a DSP-100 is inserted into any other socket, it will not be configured. If the Client Driver can successfully configure the DSP-100 its interrupt status register will be enabled.
2.1.2.4 Example 4
DEVICE = C:\DSP-100\DSP100CL.SYS (i5,u,b300)
In example 4, a single command line argument is provided. Because the parameter order is not significant, the Client Driver will attempt to configure a DSP-100 inserted into any socket with a base address of 300H and IRQ 5. If address 300H or IRQ 5 is unavailable, the DSP-100 will not be configured. If the Client Driver can successfully configure the DSP-100, its interrupt status register will be disabled (Scratchpad registers enabled).
2.1.2.5 Example 5
DEVICE = C:\DSP-100\DSP100CL.SYS (b300,i5) (i10) ( )
In example 5, three command line arguments are provided. The Client Driver will first attempt to configure a DSP-100 inserted into any socket with a base address of 300H and IRQ 5. If address 300H or IRQ 5 is unavailable, the Client Driver will proceed to the second command line argument and attempt to configure the card with a base address assigned by Card and Socket Services and IRQ 10. If IRQ 10 is also unavailable, the Client Driver will proceed to the third command line argument and attempt to configure the DSP-100 with a base address and an IRQ assigned by Card and Socket Services. If the DSP-100 is successfully configured, its interrupt status register will be enabled.
DSP-100 User's Manual 7
2.1.2.6 Example 6
DEVICE = C:\DSP-100\DSP100CL.SYS (b300,i5) ( ) (i10)
In example 6, the three command line arguments of example 5 have been rearranged. The Client Driver will first attempt to configure a DSP-100 inserted into any socket with a base address of 300H and IRQ 5. If address 300H or IRQ 5 is unavailable, the Client Driver will proceed to the second command line argument and attempt to configure the card with a base address and IRQ assigned by Card and Socket Services. Since the second command line argument includes all available address and IRQ resources, the third command line argument will never be reached by the Client Driver. It is the user's responsibility to place the command line arguments in a logical order.
2.1.2.7 Example 7
DEVICE = C:\DSP-100\DSP100CL.SYS (s0,b300,i5) (s1,b340,i10)
The type of configuration shown in example 7 may be desirable in systems where more than one DSP-100 is to be installed. In this example, the Client Driver will attempt to configure a DSP-100 inserted into socket 0 with a base address of 300H and IRQ 5. If the DSP-100 is inserted into socket 1, the Client Driver will attempt to configure it with base address 340H and IRQ 10. This allows the user to force the DSP-100's address and IRQ settings to be socket specific which may simplify cable connections and software development. As in the previous examples, however, if the requested address or interrupt resources are not available, the DSP-100 will not be configured.
DSP-100 User's Manual 8
2.1.3 Common Problems
Generic Client Drivers:
Many Card and Socket Services packages include a generic client driver (or SuperClient) which configures standard I/O devices. If one of these generic client drivers is installed, it may configure the DSP-100 causing the DSP-100 client driver to fail installation. In these cases, the user should do one of the following:
1. modify the operation of the generic client driver to disable the configuration of modem/serial port cards. Consult the Card and Socket Services documentation for availability and details of this feature.
2. place the DSP-100 client driver before the generic client driver in the CONFIG.SYS.
Available Resources:
One function of the Card and Socket Services software is to track which system resources (memory addresses, I/O addresses, IRQs, etc.) are available for assignment to inserted PCMCIA cards. Sometimes, however, the Card Services software assumes or incorrectly determines that a particular resource is used when it is actually available. Most Card and Socket Services generate a resource table in a file (typically in the form of an .INI file) which the user can modify to adjust the available system resources. Consult the Card and Socket Services documentation for availability and details of this feature.
Multiple Configuration Attempts:
Some Card and Socket Services have a setting which aborts the configuration process after a single configuration failure (such as a request for an unavailable resource). The user should change this setting to allow for multiple configuration attempts. Consult the Card and Socket Services documentation for availability and details of this feature.
Older Versions of Card and Socket Services:
Some versions of Card and Socket Services dated before 1993 do not support general purpose I/O cards. If after careful installation of the Client Driver the DSP-100 does not configure or operate properly, an updated version of Card and Socket Services may be required. Card and Socket Services software is available from Quatech.
DSP-100 User's Manual 9
2.2 DSP-100 Enabler for DOS
IMPORTANT:
IMPORTANT:
exclude this memory region.
For systems that are not operating PCMCIA Card and Socket Services software, the DSP-100 DOS Enabler may be used to enable and configure the adapter. This Enabler, DSP100EN.EXE, will operate on any DOS system using an Intel 82365SL or PCIC compatible PCMCIA host adapter including the Cirrus Logic CL-PD6710 / 6720, the VLSI VL82C146, and the Vadem VG-365 among others.
In order to use the DSP-100 Enabler for DOS, the system MUST NOT be configured with Card and Socket Services software. If a Card and Socket Services software is installed, the DSP-100 Enabler may interfere with its operation and with the device(s) it controls.
The DSP-100 Enabler does not support automatic configuration of adapters upon insertion, more commonly referred to as "Hot Swapping". This means the adapter must be installed in one of the system's PCMCIA sockets before executing DSP100EN.EXE. If more than one adapter is installed in a system, the Enabler must be executed separately for each adapter. Furthermore, DSP100EN.EXE should be executed to release the resources used by the adapter before it is removed from the PCMCIA socket. Since PCMCIA adapters do not retain their configuration after removal, any adapter that is removed from the system must be reconfigured with the Enabler after re-inserting it into a PCMCIA socket.
The Enabler requires a region of high DOS memory when configuring a DSP-100. This region is 1000H bytes (4KB) long and by default begins at address D0000H (the default address may be changed using the "W" option). If a memory manager such as EMM386, QEMM, or 386Max is installed on the system, this region of DOS memory must be excluded from the memory manager's control. Consult the documentation provided with the memory manager software for instructions on how to
DSP-100 User's Manual 10
2.2.1 Command Line Options
To configure a DSP-100 in the system, the Enabler requires one command line argument from the user to determine the configuration of the card. This argument must be enclosed in parenthesis and within the argument, any or all of the following parameters may be specified using a comma (no spaces) to separate each parameter:
Ssocket specifies which PCMCIA socket the DSP-100 must be inserted into for this
configuration argument to be used. socket must be in the range 0 - 15. This option is always required.
Baddress specifies a “block mode” base I/O address of the DSP-100 in hexadecimal.
This address must reside on an even 16-byte (10H) boundary. Specify only one of the following three options: Baddress, Dmode, or ‘R’. Use of one of these options is always required.
Dmode specifies a “COM” mode” base I/O address configuration for the DSP-100.
The ‘D1’ option configures the DSP-100 at COM1/COM3 (3F8 / 3E8), and the ‘D2’ option configures the DSP-100 at COM2/COM4 (2F8 / 2E8). Specify only one of the following three options: Baddress, Dmode, or ‘R’. Use of one of these options is always required.
Iirq specifies the interrupt level (IRQ) of the DSP-100 in decimal. irq must be
one of the following values: 3, 4, 5, 7, 9, 10, 11, 12, 14, 15, or 0 if no IRQ is desired. This option is required if the 'R' option is not used.
Waddress specifies the base address of the memory window required to configure the
DSP-100. Set address = D0 for a memory window at segment D000, address = D8 for a memory window at segment D800, etc. Valid settings for address are C8, CC, D0, D4, D8, and DC. If this option is omitted, a memory window at segment D000 will be used.
U instructs the Enabler to disable the DSP-100's interrupt status register and
enable the Scratchpad registers of the individual UARTs. This option is only required in very rare cases where an application program requires access to the UART's Scratchpad register. If this option is omitted, the DSP-100's interrupt status register is enabled and the UARTs' Scratchpad registers are disabled.
Before removing a DSP-100 from its PCMCIA socket, the Enabler should be executed to free the system resources allocated when the card was installed. For this operation the Enabler provides on additional command line option:
DSP-100 User's Manual 11
R instructs the Enabler to release the resources previously allocated to the
DSP-100. When the 'R' option is used, any settings specified by the 'B', 'I', and 'U' options are ignored.
2.2.1.1 Example 1
DSP100EN.EXE
In example 1, no command line argument is specified. The Enabler will report an error and display the proper usage of the command.
2.2.1.2 Example 2
DSP100EN.EXE (s0,b300,i5)
In example 2, the Enabler will configure the DSP-100 in socket 0 with a base address of 300H and IRQ 5 using a configuration memory window at segment D000. The DSP-100's interrupt status register will be enabled.
2.2.1.3 Example 3
DSP100EN.EXE (i10,u,b340,s1)
In example 3, the Enabler will configure the DSP-100 in socket 1 with a base address of 340H and IRQ 10 using a configuration memory window at segment D000. The DSP-100's interrupt status register will be disabled (Scratchpad registers enabled). Note that the parameter order is not significant.
DSP-100 User's Manual 12
Loading...
+ 39 hidden pages