Omega Products DSP-225 Installation Manual

Table of Contents
7-1
7 . Specifications
.......................................
..
6-1
5-6
5.6 PCMCIA Configuration Register
5-5
5.5 Half Duplex Operation
5-4
5.4 Termination Resistors
5-3
5.3.2 Auxiliary Channel: Handshaking Disabled.
5-2
5.3.1 Auxiliary Channel: RTS-CTS Handshaking.
5-2
5.3 Auxiliary Channel Configuration
5-1
5.2 Scratchpad Register
5-1
5.1 I/O Addressing Modes
5-1
5 . Hardware Information
4-7
4.3 Common Problems and Important Notes
4-6
4.2 Monitoring The Status Of PCMCIA Cards
4-6
4.1.6 Applying Options to All The DSP-225 Cards
4-5
4.1.5 Using Multiple Options
4-5
4.1.4 Options
4-4
4.1.3 Advanced Configuration Topics
4-3
4.1.2 Configuring With "User Assigned" Resources
4-2
4.1.1 Configuring With "System Assigned" Resources
4-2
4.1 Command Line Options
4-1
4 . OS/2 Installation
3-8
3.3 Common Problems
3-4
3.2.2 Changing Resource Settings with Device Manager
3-3
3.2.1 Viewing Resource Settings with Device Manager
3-2
3.2 DSP-225 Resource Settings in Windows 95
3-1
3.1 Installing a DSP-225 Under Windows 95.
3-1
3 . Windows 95 Installation
2-15
2.2.2 Common Problems
2-10
2.2.1 Command Line Options
2-9
2.2 DSP-225 Enabler for DOS
2-8
2.1.3 Common Problems
2-3
2.1.2 Command Line Options
2-2
2.1.1 Client Driver Installation
2-1
2 . DOS / Windows 3.x Installation
1-1
1 . Introduction
........................................
.....................
...........................
............................
................................
...............................
...........................
...............................
............................
..................
.................
.......
....................................
....................................
................................
........
..........
.....................
..........................................
............................
...........
.................
.................
..............................
.................................
....................................
........................
...........
...........
..................................
.................................
.........................
...............................
.. ..
..
......
..
..
..
DSP-225 User's Manual iii
List of Figures
6-1
Figure 17. Connector Signal Assignment.
.......................
6-1
Figure 16. DSP-225 Adapter Cable
6-6
Figure 15. PCMCIA Configuration Options Register
5-5
Figure 14. RS-422/485 Driver Enable Options
5-4
Figure 13. RS-422/485 Termination
5-3
Figure 12. Auxiliary Channel Handshaking Disabled
5-2
Figure 11. Auxiliary Channel RTS-CTS Handshaking.
5-1
Figure 10. Interrupt Status Register.
5-1
Figure 9. Block Mode Addressing.
4-6
Figure 8. OS/2 Plug and Play GUI
3-7
Figure 7. Windows 95 Resource Allocation
3-6
Figure 6. DSP-225 Basic Configuration Table.
3-4
Figure 5. Windows 95 Device Manager
2-11
Figure 4. DOS Enabler Output Enable Options.
2-4
Figure 3. DOS Client Output Enable Options.
2-1
Figure 2. Client Driver versus Enabler for DOS/Windows 3.x.
1-1
Figure 1. DSP-225 Configuration
..............................
.........................
....................
......................
............................
.............................
............................
............................
.....
...................
.................
............
.............
...................
..............
.............................
iv
1. Introduction
The DSP-225 is a dual channel RS-232 and RS-422/485 asynchronous serial adapter for systems equipped with PCMCIA Type II and/or Type III expansion sockets. The DSP-225 is a PCMCIA Type II (5 mm) card and is PCMCIA PC Card Standard Specification 2.1 compliant.
The figure below illustrates a complete DSP-225 system. The system includes a cable assembly which converts the DSP-225’s 0.8mm I/O connector into standard D-9 male and D-9 female connectors.
PCMCIA Card Cable Assembly
Standard D-9 Male
Standard D-9 Female
Figure 1. DSP-225 Configuration
The DSP-225'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 RS-422/485 serial port may be configured to operate in either the Full Duplex or Half Duplex mode; RTS or DTR may be used to enable the output drivers, or the RS-422/485 serial ports may be configured so that the output drivers are always enabled. Another option provided in the RS-422/485 serial ports is an RTS-CTS modem control handshake. This handshake may be enabled or disabled when the DSP-225 is configured.
DSP-225 User's Manual 1-1
The DSP-225'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 on these topics.
1-2
2. DOS / Windows 3.x Installation
Socket Services software
Services software
upon insertion (Hot Swapping)
(Hot Swapping)
host adapters
host adapter independent)
File type: DOS executable
File type: DOS device driver
File name: DSP225EN.EXE
File name: DSP225CL.SYS
Enabler (not recommended)
Client Driver (recommended)
Two configuration software programs are provided with the DSP-225: a Client Driver, DSP225CL.SYS, and a card Enabler, DSP225EN.EXE. Both of these programs are executed from DOS (before entering Windows) and allow operation of the DSP-225 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.
Interfaces to PCMCIA Card and Socket Services software (PCMCIA
Allows automatic configuration of DSP-225 adapters upon insertion
Requires PCMCIA Card and Socket
Interfaces directly to Intel 82365SL and other PCIC compatible PCMCIA
Does not support automatic configuration of DSP-225 adapters
Does not require PCMCIA Card and
Figure 2. 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-225 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-225 User's Manual 2-1
2.1 DSP-225 Client Driver for DOS
Card and Socket Services may be required.
In order to use the DSP-225 Client Driver, the system must be configured with Card and Socket Services software. Card and Socket Services software is not provided with the DSP-225 but is available from Omega.
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-225 does not configure or operate properly, an updated version of
2.1.1 Client Driver Installation
The following procedure is used to install the DSP-225 Client Driver:
1. Copy the file DSP225CL.SYS from the DSP-225 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 software, add the following line to the CONFIG.SYS file:
DEVICE = drive:\path\DSP225CL.SYS options
where options are the DSP-225 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-225 into one of the system's PCMCIA slots. NOTE: Since the DSP-225 Client Driver supports "Hot Swapping",
it is not necessary to have the DSP-225 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.
the line(s) installing the Card and Socket Services
7. Reboot the system and note the message displayed when the DSP-225 Client Driver is loaded. If the Client Driver reports an
2-2
"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-225 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-225 may be removed and / or inserted from the system as desired. On each insertion into the PCMCIA socket, the DSP-225 will be automatically reconfigured according to the command line options.
2.1.2 Command Line Options
The DSP-225 Client Driver accepts up to eight command line arguments from the user to determine the configuration of the DSP-225. If any arguments are provided, the Client Driver will attempt to configure any DSP-225s 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 Within each argument, any or all of the following parameters may be specified using a comma
(no spaces) to separate each parameter:
on the command line.
Baddress specifies a "block mode" base I/O address of the DSP-225 in
hexadecimal. This address must reside on an even 16-byte (10H) boundary. This option must 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-225. The D1 option configures the DSP-225 at COM1/COM3 (3F8 / 3E8), and the D2 option configures the DSP-225 at COM2/COM4 (2F8 / 2E8). This option must 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-225 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.
be omitted if using the
be
DSP-225 User's Manual 2-3
Ssocket specifies which PCMCIA socket the DSP-225 must be inserted
DTR Controlled
o2
RTS Controlled
o1
Always Enabled
o0
RS-422/485 Output Drivers
Option
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-225s inserted into any socket.
Odriver specifies the output driver enable option for the RS-422/485
port. The DSP-225's RS-422/485 port may be configured for either full duplex or half duplex operation with this option. In half duplex mode, the RS-422/485 transmitter may be enabled and disabled via the RTS (request to send) or DTR (data terminal ready) signals. Both RTS and DTR are controlled through the Modem Control Register of the 16550. If this option is omitted, the default setting is the RS-422/485 port configured for full duplex operation with the RS-422/485 output drivers always enabled. See the Hardware Information section for more information.
Figure 3. DOS Client Output Enable Options.
H instructs the client driver to enable the RTS-CTS modem
control handshake for the RS-422/485 port. When modem control handshaking in enabled, the 16C550 UART's RTS and CTS signals are connected to the RS-422/485 auxiliary channel. The auxiliary channel may then be used for handshaking between the DSP-225's RS-422/485 port and a peripheral device. When modem control handshaking is disabled, the RTS and CTS signals from the 16C550 UART are looped back to each other. If this option is omitted, the default setting is RTS-CTS modem control handshake disabled. See the Hardware Information section for more information.
U instructs the Client Driver to disable the DSP-225'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-225's interrupt status register is enabled and the UARTs' Scratchpad registers are disabled.
2-4
F instructs the Client Driver to switch the I/O locations of the
RS-232 port and the RS-422/485 port.
RS-232 Port I/O = (base + 8h) - (base + Fh), COM3/4
RS-422/485 Port I/O = (base) - (base +7h), COM1,2
By using 'F' option, the RS-422/485 port may be located at the
lower I/O address location in the 'Block Mode' (or the lower COM Port number in the 'COM Mode'). This option moves the RS-232 port to the upper I/O address location in the 'Block Mode' (or the higher COM number in the 'COM Mode'). If this option is omitted, the DSP-225's RS-232 port is located at the lower I/O address location (or lower COM Port number).
.1.2.1 Example 1
2
DEVICE = C:\DSP-225\DSP225CL.SYS
In example 1, no command line arguments are specified. The Client Driver will configure a DSP-225 inserted into any socket in "block mode" with a base address and IRQ assigned by Card and Socket Services. The DSP-225's interrupt status register will be enabled, the RS-422/485 output drivers for the RS-422/485 port will always be enabled, RTS-CTS modem control handshaking will be disabled, and the RS-232 port will be located at the lower I/O address location.
.1.2.2 Example 2
2
DEVICE = C:\DSP-225\DSP225CL.SYS (d1,f)
In example 2, a single command line argument is provided. The Client Driver will attempt to configure a DSP-225 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-225 will not be configured. If the Client Driver can successfully configure the DSP-225, its interrupt status register will be enabled, the RS-422/485 output drivers for the RS-422/485 port will always be enabled, RTS-CTS modem control handshaking will be disabled, and the I/O locations of the RS-232 port and the RS-422/485 port will be switched (RS-422/485 port assigned COM1, RS-232 port assigned COM3).
DSP-225 User's Manual 2-5
2.1.2.3 Example 3
DEVICE = C:\DSP-225\DSP225CL.SYS (s0,b300,i5,o2)
In example 3, a single command line argument is provided. The Client Driver will attempt to configure a DSP-225 inserted into socket 0 with a base address of 300H and IRQ 5. If address 300H or IRQ 5 is unavailable, the DSP-225 will not be configured. In addition, if a DSP-225 is inserted into any other socket, it will not be configured. If the Client Driver can successfully configure the DSP-225, its interrupt status register will be enabled, the RS-422/485 port output drivers will be enabled and disabled via the DTR signal, RTS-CTS modem control handshaking will be disabled, and the RS-232 port will be located at the lower I/O address location.
.1.2.4 Example 4
2
DEVICE = C:\DSP-225\DSP225CL.SYS (i5,h,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-225 inserted into any socket with a base address of 300H and IRQ 5. If address 300H or IRQ 5 is unavailable, the DSP-225 will not be configured. If the Client Driver can successfully configure the DSP-225, its interrupt status register will be disabled (Scratchpad registers enabled), the RS-422/485 output drivers for the RS-422/485 port will always be enabled, RTS-CTS modem control handshaking will be enabled on the RS-422/485 port's auxiliary channel, and the RS-232 port will be located at the lower I/O address location.
.1.2.5 Example 5
2
DEVICE = C:\DSP-225\DSP225CL.SYS (b300,i5) (i10) ( )
In example 5, three command line arguments are provided. The Client Driver will first attempt to configure a DSP-225 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-225 with a base address and
an IRQ
2-6
assigned by Card and Socket Services. If the Client Driver can successfully configure the DSP-225, its interrupt status register will be enabled, the RS-422/485 output drivers for the RS-422/485 port will always be enabled , and RTS-CTS modem control handshaking will be disabled.
.1.2.6 Example 6
2
DEVICE = C:\DSP-225\DSP225CL.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-225 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.
.1.2.7 Example 7
2
DEVICE = C:\DSP-225\DSP225CL.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-225 is to be installed. In this example, the Client Driver will attempt to configure a DSP-225 inserted into socket 0 with a base address of 300H and IRQ 5. If the DSP-225 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-225'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-225 will not be configured.
DSP-225 User's Manual 2-7
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-225 causing the DSP-225 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-225 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-225 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 Omega.
2-8
2.2 DSP-225 Enabler for DOS
with the device(s) it controls.
exclude this memory region.
For systems that are not operating PCMCIA Card and Socket Services software, the DSP-225 DOS Enabler may be used to enable and configure the adapter. This Enabler, DSP225EN.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.
IMPORTANT:
In order to use the DSP-225 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-225 Enabler may interfere with its operation and
The DSP-225 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 DSP225EN.EXE. If more than one adapter is installed in a system, the Enabler must be executed separately for each adapter. Furthermore, DSP225EN.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.
DSP-225 User's Manual 2-9
IMPORTANT:
The Enabler requires a region of high DOS memory when configuring a DSP-225. 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
2.2.1 Command Line Options
To configure a DSP-225 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-225 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-225 in
hexadecimal. This address must reside on an even 16-byte (10H) boundary. Specify only one options: Baddress, Dmode, or 'R'. Use of one of theses options is
always
Dmode specifies a "COM" mode" base I/O address configuration for
the DSP-225. The 'D1' option configures the DSP-225 at COM1/COM3 (3F8 / 3E8), and the 'D2' option configures the DSP-225 at COM2/COM4 (2F8 / 2E8). Specify only one following three options: Baddress, Dmode, or 'R'. Use of one of theses options is always
required.
required.
of the following three
of the
Iirq specifies the interrupt level (IRQ) of the DSP-225 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-225. 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.
2-10
Loading...
+ 30 hidden pages