Witam. Chciałbym dołożyć port RS232 do laptopa z Windows XP. Wygrzebałem zakupioną kilka lat temu kartę CARDBUS PCMCIA 2 x RS formy SUNWEIT która jest zbudowana na układzie OXFORD OXCF950 oraz Sipex SP3243ECA, niestety nie kojarzę, żebym przy zakupie dostał płytę ze sterownikami ;/ Chciałbym zapytać czy spotkał się ktoś może z kartami na tych podzespołach i posiada sterowniki do niej pod Win XP ? Udało mi się zainstalować sterowniki dołączone w załączniku, ale pod koniec instalacji pojawił się komunikat ze nie można uruchomić tego urządzenia ponieważ jest jakiś problem z konfiguracją ;/ Dodam, że po instalacji tych sterowników w Menadżerze urządzeń karta wykrywana jest teraz jako Karty wielofunkcyjne --> ! PCcard OX16CF950 (z żółtym wykrzyknikiem), dodam jeszcze, że karta posiada dwie diody, ale żadna z nich nie zaświeca się;/ Identyfikator wystąpienia urządzenia: PCMCIA\PC_CARD-GENERIC-1748\1 Identyfikatory sprzętu: PCMCIA\PC_CARD-GENERIC-1748 PCMCIA\PC_CARD-GENERIC-0279-950B PCMCIA\PC_CARD-0279-950B Komunikat podczas instalacji sterowników: http://obrazki.elektroda.pl/6894504600_1439987572_thumb.jpg Zdjęcie karty PCMCIA 2 x RS232: http://obrazki.elektroda.pl/7103445300_1439987526_thumb.jpg Bardzo proszę o pomoc czy tak karta do czegokolwiek się nadaje??
UART/parallel port Reference drivers
Windows 9x/ME drivers
---------------------
Features: Automatic enumeration of all 95x UARTs, both internal and local bus
95x-mode driver for enhanced serial port performance
GUI configuration for all serial ports
Hook to use generic driver for Parallel port
(can disable parallel port interrupt)
Windows 2000/XP drivers
-----------------------
Features: Automatic enumeration of all 95x UARTs
95x-mode driver for enhanced performance
GUI configuration for all serial ports
PCI serial ports run in memory-mapped mode for faster throughput
Parallel port driver
COM port remapping under port properties (Device Manager)
ACPI Power Management support
Windows NT4 drivers
-------------------
Features: Automatic enumeration of 95x UARTs
128-deep FIFO and fill level usage
Optimised interrupt handling, tx FIFO topped up on all interrupts
Registry or .inf-settable Vendor/Device IDs, trigger levels.
Memory-mapped operation for increased throughput.
Seperate parallel port driver and installer
To install the serial port driver, run " Install_Serial " from the \NT4_Serial directory
To install the parallel port driver, run " Install_Parallel " from the \NT4_Parallel directory
FILES IN THIS DIRECTORY
-----------------------
readme This file
oxpci.inf Hook for PCI device and logical functions
oxpci2.inf Hook for child devices (serial ports / parallel port)
oxser.inf Installation file for standalone ports
oxmf.vxd Bus enumerator for UARTs and local bus UARTs (Win9x)
oxmfcf.vxd Bus enumerator for CF950 in local bus mode (Win9x)
oxmf.sys Bus driver for UARTs and local bus UARTs (Win2000/XP)
oxmfuf.sys Filter driver for PCI ports
oxpp.vxd Bus enumerator for parallel port
oxppui.dll Parallel port configuration utility
oxser.vxd Serial port driver (Win9x)
oxser.sys Serial port driver (Win2000/XP)
oxserui.dll Serial port configuration utility (Win9x)
oxui.dll Serial port configuration utility (Win2000/XP)
oxpar_2k.sys Parallel port driver (Win2000) - renamed to oxpar.sys during installation
oxpar_xp.sys Parallel port driver (WinXP) - renamed to oxpar.sys during installation
oxpar.inf Installation file for PCI parallel ports
oxpar2.inf Additional installation file for parallel ports (win9x)
Windows NT4 PCI Port Driver Licence Agreement
=============================================
This software and the accompanying files are provided " as is " and without warranties as to performance or merchantability or any other warranties whether express or implied.
The receiver assumes all risk and liability for loss, damage, claims or expense resulting from use, possession or resale of any software products furnished by Oxford Semiconductor Ltd.
The receiver agrees to indemnify, defend and hold harmless Oxford Semiconductor Ltd. and its officers, agents, and employees from and against any and all claims, liability, loss, damage or expense, including reasonable attorney's fees, arising from or by reason of receivers' use, possession or resale with respect to any of the software products furnished by Oxford Semiconductor Ltd. pursuant to this agreement, and such obligation shall survive acceptance of said products therefore by receiver.
OX16PCI954
QUAD UART WITH PCI INTERFACE
CUSTOM DRIVERS
This document describes recommended procedures to reconfigure the OX16PCI954
hardware and reference drivers in order to identify custom add-in card configurations to
device drivers.
Version 1.1 (25 August 1999)
Custom solutions & drivers for the OX16PCI954
1
VERSION 1.1
OVERVIEW
The primary function of the OX16PCI954 is to provide four serial ports, and a local bus (with more serial ports) or a parallel port. However
the chip is very flexible, so it is possible to use it for other solutions, for example:• 2 serial, 1 parallel card
• 1 parallel card
• 4 serial ports + 1 custom FPGA synchronous I/O controller on the local bus
If a designer wishes to use the OX16PCI954 chip for another purpose, it is necessary to change the identification fields in PCI Configuration
space. These are the VENDOR ID, DEVICE ID, SUBSYSTEM VENDOR ID and SUBSYSTEM ID fields. In this way, it is possible for the
Plug ‘n’ Play system to identify different boards (even though they use the same chip) and load the correct drivers.
There are three recommended approaches to uniquely identify an add-in card using the OX16PCI954.
1.
2.
3.
The best solution is for the board manufacturer to obtain their own VENDOR ID from the PCI special interest group (PCISIG). Then
they should use the EEPROM facility on the OX16PCI954 to reprogram the VENDOR ID and SUBSYSTEM VENDOR ID fields with
this value, and they choose any DEVICE ID and SUBSYSTEM ID value.
Another recommended approach is to leave the VENDOR ID and DEVICE ID as the default values set by Oxford Semiconductor. The
SUBSYSTEM VENDOR ID should be set to board manufacturer’s unique value assigned by the PCISIG, then they can choose the
SUBSYSTEM ID.
For small vendors, it is sometimes possible to use Oxford Semiconductor’s identification fields. In these cases, Oxford Semiconductor
will assign a subsystem ID to the board vendor, which is the only value that needs to be changed using the EEPROM. To request a
subsystem ID value, please contact Oxford Semiconductor with a full functional description of the add-in card being designed.
The first solution is the best because Windows 95 and Windows NT do not recognise subsystem ID values. Therefore they will not be able
to distinguish between different add-in cards. Windows 98 and Windows 2000 will be able to identify different cards, provided that the driver
.inf file specifies the subsystem ID values, in the form of:
PCI\VEN_1415 & DEV_9501 & SUBSYS_00011415
Board vendors should NEVER assign a new DEVICE ID or SUBSYSTEM ID unless they have obtained their own VENDOR ID from the
PCISIG. Oxford Semiconductor reserve the right to refuse to allocate a subsystem ID to a board vendor.
Oxford Semiconductor Ltd.
2
Custom solutions & drivers for the OX16PCI954
VERSION 1.1
2 Examples
2.1
4-serial, 2 parallel card
To do this it is necessary to use the internal UARTs, and have two external parallel port chips on the local bus. In this case the board
vendor can use the default ID for the serial ports, but must have a different ID for the local bus. They can contact Oxford Semiconductor for
a subsystem ID for the local bus, or obtain their own VENDOR ID and define their own drivers for the entire card. The three possible
approaches are therefore:Use the board vendor’s own PCI VENDOR ID (in this example case, 0x1234)
VENDOR ID
DEVICE ID
SUBSYSTEM VENDOR ID
SUBSYSTEM ID
4 serial ports (internal UARTs)
FUNCTION 0
0x1234
Chosen by vendor
0x1234
Chosen by vendor
2 parallel ports (Local bus)
FUNCTION 1
0x1234
Chosen by vendor
0x1234
Chosen by vendor
In this case, the .inf file needs to identify the devices as:PCI\VEN_1234 & DEV_XXXX
PCI\VEN_1234 & DEV_YYYY
Use the board vendor’s own PCI VENDOR ID as the SUBSYSTEM VENDOR ID (in this case, 0x1234)
VENDOR ID
DEVICE ID
SUBSYSTEM VENDOR ID
SUBSYSTEM ID
4 serial ports (internal UARTs)
FUNCTION 0
0x1415 (default)
0x9501 (default)
0x1234
Chosen by vendor
2 parallel ports (Local bus)
FUNCTION 1
0x1415 (default)
0x9511 (default)
0x1234
Chosen by vendor
In this case, the .inf file needs to identify the devices as:PCI\VEN_1415 & DEV_9501 & SUBSYS_XXXX1234
PCI\VEN_1415 & DEV_9511 & SUBSYS_YYYY1234
Obtain subsystem ID from Oxford Semiconductor (example 0x00FF), and use other values as default
VENDOR ID
DEVICE ID
SUBSYSTEM VENDOR ID
SUBSYSTEM ID
4 serial ports (internal UARTs)
FUNCTION 0
0x1415 (default)
0x9501 (default)
0x1415 (default)
0x0001 (default)
2 parallel ports (Local bus)
FUNCTION 1
0x1415 (default)
0x9511 (default)
0x1415 (default)
0x00FF
In this case, the .inf file needs to identify the devices as:PCI\VEN_1415 & DEV_9501 & SUBSYS_00011415
PCI\VEN_1415 & DEV_9511 & SUBSYS_00FF1415
Oxford Semiconductor Ltd.
3
Custom solutions & drivers for the OX16PCI954
2.2
VERSION 1.1
2-serial, 1 parallel card
It is not possible to limit the hardware to only enable two serial ports, so this solution merely requires a driver in the enumerator driver,
which ensures that it only registers two ports. Oxford Semiconductor have assigned a DEVICE ID of 0x950A for this, so the recommended
solution is:-
VENDOR ID
DEVICE ID
SUBSYSTEM VENDOR ID
SUBSYSTEM ID
2 serial ports (internal UARTs)
FUNCTION 0
0x1415
0x950A
0x1415
Default
1 parallel ports (Local bus)
FUNCTION 1
0x1415
0x9513
0x1415
Default
The OX16PCI954 drivers version 2.51 and greater include identification of the 0x950A device ID as 2-serial ports.
The card designer should use the first two ports as these are the ones which will be used by the driver.
For Windows 9x, setting the device ID using the EEPROM will be the only modification required. For Windows NT4, the oxser.inf file needs
to be modified (all occurences of 9501 need to be changed to 950A, BEFORE INSTALLATION OF THE DRIVERS. Please contact
support@oxsemi.com for further details.
2.3
1 parallel port only
It is not possible to disable the UARTs on the device, so this solution will require the user to install a null driver for the UARTs. Again Oxford
Semiconductor already have assigned a DEVICE ID for this (value 0x9500), so the recommended solution is:-
VENDOR ID
DEVICE ID
SUBSYSTEM VENDOR ID
SUBSYSTEM ID
NULL function
FUNCTION 0
0x1415
0x9500
0x1415
Default
1 parallel ports (Local bus)
FUNCTION 1
0x1415
0x9513
0x1415
Default
The OX16PCI954 reference drivers will recognise the device ID 0x9500 as a null function, and load a null driver for this device.
Oxford Semiconductor Ltd.
4
OX16C95x
OX16PCI954
HIGH-PERFORMANCE UART FAMILY
ADVANCED TOPICS
This document describes the use of advanced features of the Oxford Semiconductor
reference drivers for the OX16C95x high performance UART family, including the
OX16PCI954 Quad UART with PCI interface.
Version 1.0 (08 February 2001)
Advanced Topics
VERSION 1.0
1 OVERVIEW
Reference drivers and utilities for the Oxford Semiconductor UART products are supplied to demonstrate functionality under Windows
95/98, Windows NT4 and Windows 2000. These drivers have been tested using Oxford Semiconductor development boards in a range of
PC systems.
This document describes the use of certain advanced features provided by the UART driver set.
2 LICENCE AGREEMENT
This software and the accompanying files are provided " as is " and without warranties as to performance or merchantability or any other
warranties whether express or implied. The receiver assumes all risk and liability for loss, damage, claims or expense resulting from use,
possession or resale of any software products furnished by Oxford Semiconductor Ltd.
The receiver agrees to indemnify, defend and hold harmless Oxford Semiconductor Ltd. and its officers, agents, and employees from and
against any and all claims, liability, loss, damage or expense, including reasonable attorney's fees, arising from or by reason of receivers'
use, possession or resale with respect to any of the software products furnished by Oxford Semiconductor Ltd. pursuant to this agreement,
and such obligation shall survive acceptance of said products therefore by receiver.
3 CONTENTS
1
OVERVIEW ....................................................................................................................................................................... 2
2
LICENCE AGREEMENT................................................................................................................................................. 2
3
CONTENTS ........................................................................................................................................................................ 2
4
DATA RATE CONFIGURATION................................................................................................................................... 3
4.1
WINDOWS 2000 DRIVERS .............................................................................................................................................. 3
5
CONTACT INFORMATION ........................................................................................................................................... 6
6
DISCLAIMER .................................................................................................................................................................... 6
Oxford Semiconductor Ltd.
2
Advanced Topics
VERSION 1.0
4 DATA RATE CONFIGURATION
4.1
Windows 2000 drivers
Baud Rates
Baud rates generated by the UART hardware are derived with the use the following formula (see also the Data Sheet for the UART being
used):
BaudRate =
InputClock
SC * Divisor * prescaler
Equation 4-1
The default InputClock is a crystal of 1.8432MHz, the default prescaler is 1, and the default SC (Sampling Clock) is 16.
Ports speeds are usually requested by an application with a desired BaudRate (as opposed to a desired Divisor). The formula for
calculating the Divisor is shown below:
Divisor =
InputClock
SC * BaudRate * prescaler
Equation 4-2
For example, to obtain a baud rate of 57.6Kbps, with default clock and prescaler, a Divisor of 2 is required (2 = 1.8432MHz / 16*57600*1).
The following sections explain in detail the use and adjustment of these parameters in order to obtain a variety of baud rates with the use of
various crystals.
Data Rate Overview
To perform advanced baud rate adjustments select the Properties for a port from the Device Manager. Selecting the Data rate tab should
result in a dialog box similar to that shown in Figure 4-1.
Oxford Semiconductor Ltd.
3
Advanced Topics
VERSION 1.0
Figure 4-1
Crystal frequencies from 1.8432MHz-60MHz may be used with the OX16C95x UART family, and if not known, the crystal speed can be
detected using the ‘Detect Crystal Frequency’ button.
Regardless of the crystal frequency the UART software driver will always attempt to provide the baud rate requested by an application.
Thus a request for a baud rate of 115.2Kbps with a crystal frequency of 14.7456MHz would result in a Divisor of 8 being used. With a
crystal frequency of 1.8432MHz the Divisor generated would be 1. This is transparent to the application level, and as long as the ‘Use
default baud rate’ box is ticked, the driver will behave in this manner (i.e. baud rates will be as requested).
A disadvantage of this is that baud rates are limited by what the application can request – typically a maximum of 115.2Kbps.
Advanced Baud Rate Selection
Generating non-standard baud rates can be achieved by clearing the ‘Use default baud rate’ box, which allows the Override Configuration
controls to be modified.
The Override Configuration controls are as follows (Figure 4-2 shows the controls in use):
•
Baud rate multiplier – when selected, a multiplication factor can be applied to baud rates (1, 2, 4, 8,10 and 16x are available). This
option has the effect of asking the driver to provide a baud rate n times that of the rate requested by the application. Custom
applications can request the driver to provide high baud rates; this option merely allows an application with no concept of the
baud rate capability of the OX19PCI954 to be used to open a port with a high baud rate.
For example, setting 115.2Kbps in the application with a multiplier of 8 will result in a true baud rate of 921.6Kbps.
•
Quad speed – when ticked, the true baud rate will be 4x that of the rate requested by the application. Quad speed uses a different
method than the Baud rate multiplier. The Caveats section explains this difference and why this setting may be required.
•
Baud rate divider (prescaler) – when selected, a new prescaler can be set (1 to 31.875 in steps of 0.125 are available). As can be
seen from Equation 4-2, higher prescalers will cause the baud rate to drop accordingly. For instance, an application requested
baud rate of 38.4Kbps with a prescaler of 2 would result in a true baud rate of 19.2Kbps. Because it can be set in steps of 0.125
the prescaler can be used to make minor adjustments to baud rates in order to achieve non-standard rates. This is useful
because Divisor values must always be integers and thus are limited in effecting minor baud rate steps – especially when a high
frequency crystal is in use.
Oxford Semiconductor Ltd.
4
Advanced Topics
VERSION 1.0
Figure 4-2
The second method for adjusting baud rates is to modify the reported speed of the crystal. The value in the Crystal Frequency (MHz) list
box can be modified – even though the true crystal speed remains unchanged. This has the effect of changing the InputClock value used in
Equation 4-2.
Setting the crystal frequency to half that of the true speed will result in a Divisor that is half of the ‘correct’ value. This will result in a true
baud rate twice that requested by the application. For instance, reporting a 60MHz crystal as 30MHz will modify a selected baud rate of
57.6Kbps into a true rate of 115.2Kbps. Reporting the same crystal at 20MHz will cause a 2.4Kbps baud rate to become 7.2Kbps.
Reporting a fast crystal as a low speed unit can be used to significantly increase the application requested baud rate and result in very high
true baud rates.
Caveats
It can be seen from Equation 4-2 that if a high baud rate is required with the use of a slow crystal the resulting Divisor may be less than 1.
For instance, trying to achieve baud rates in excess of 115.2Kbps with a 1.8432MHz crystal will result in an illegal Divisor.
An example of this would be if the Baud rate multiplier was set to 4 and the application software requested a rate of 115.2Kbps (with a
1.8432MHz crystal and all other settings at default). The driver would multiply the requested rate by 4, giving 460.8Kbps, and would
calculate a Divisor of 0.25. The driver would subsequently fail to open the required port. If an application was able to directly request a baud
rate of 460.8Kbps (thus requiring a default Baud rate multiplier of 1) the result would be the same, as the values used in the Divisor
calculation would be identical.
Whilst the Baud rate multiplier is a software step (simply multiplying the requested baud rate before being used to calculate the Divisor) the
Quad speed option changes the hardware Sample Clock parameter shown in Equation 4-2 from 16 down to 4. This allows baud rates four
times that which would be possible with a chosen crystal.
Finally, remember that the InputClock figure used in Equation 4-2 is the figure shown on the dialog box – which may be different from the
true crystal frequency. If in any doubt about the figure on the dialog, use the Detect Crystal Frequency button.
If 4 times oversampling is used then there will be a resulting decrease in noise margin. If 4 times oversampling is used high quality
transmission media must be used to avoid errors.
It is not possible to drive the device faster than the external clock.
It is not possible to drive the device at speeds that exceed the capacity of the external line driver.
Oxford Semiconductor Ltd.
5
Advanced Topics
VERSION 1.0
5 CONTACT INFORMATION
For further information please contact:
Oxford Semiconductor Ltd.
25 Milton Park
Abingdon
Oxfordshire
OX14 4SH
United Kingdom
Telephone:
Fax:
Sales e-mail:
Web site:
+44 (0)1235 824900
+44 (0)1235 821141
sales@oxsemi.com
http://www.oxsemi.com
6 DISCLAIMER
Oxford Semiconductor believes the information contained in this document to be accurate and reliable. However, it is subject to change
without notice. No responsibility is assumed by Oxford Semiconductor for its use, nor for infringement of patents or other rights of third
parties. No part of this publication may be reproduced, or transmitted in any form or by any means without the prior consent of Oxford
Semiconductor Ltd. Oxford Semiconductor’s terms and conditions of sale apply at all times.
Oxford Semiconductor Ltd.
6
Oxford Semiconductor Ltd.
Reference driver for PCI ports
To use the Windows NT4 driver for a 2-serial port solution, perform
the following steps:-
1) Use the EEPROM to program the deviceID for function 0 to 0x950A
2) Replace the oxser.inf file in the WinNT4 directory with the version
located in \doc\misc
3) Start up the system
4) Run the Install_Serial program from the WinNT4 directory
OX16C95x
OX16PCI954
HIGH-PERFORMANCE UART FAMILY
REFERENCE DRIVERS
This document describes installation and use of the Oxford Semiconductor reference
drivers for the OX16C95x high performance UART family, including the OX16PCI954
Quad UART with PCI interface.
Version 2.1 (21 May 2001)
Custom solutions & drivers for the OX16PCI954
VERSION 2.1
1 OVERVIEW
Reference drivers and utilities for the Oxford Semiconductor UART products are supplied to demonstrate functionality under Windows
95/98, Windows NT4 and Windows 2000. These drivers have been tested using Oxford Semiconductor development boards in a range of
PC systems.
2 LICENCE AGREEMENT
This software and the accompanying files are provided " as is " and without warranties as to performance or merchantability or any other
warranties whether express or implied. The receiver assumes all risk and liability for loss, damage, claims or expense resulting from use,
possession or resale of any software products furnished by Oxford Semiconductor Ltd.
The receiver agrees to indemnify, defend and hold harmless Oxford Semiconductor Ltd. and its officers, agents, and employees from and
against any and all claims, liability, loss, damage or expense, including reasonable attorney's fees, arising from or by reason of receivers'
use, possession or resale with respect to any of the software products furnished by Oxford Semiconductor Ltd. pursuant to this agreement,
and such obligation shall survive acceptance of said products therefore by receiver.
3 CONTENTS
1
OVERVIEW ................................................................................................................................................................ 2
2
LICENCE AGREEMENT........................................................................................................................................... 2
3
CONTENTS................................................................................................................................................................. 2
4
OVERVIEW AND INSTALLATION ......................................................................................................................... 3
4.1
OX16PCI954 ......................................................................................................................................................... 3
4.1.1
Windows 95/98 and Windows 2000 drivers for OX16PCI954 .......................................................................... 3
4.1.2
Windows NT4 driver for OX16PCI954 ............................................................................................................ 5
4.2
OX16C95X (STANDARD UARTS)............................................................................................................................ 6
4.2.1
Windows 95/98 and Windows 2000 drivers for standard UARTs...................................................................... 6
4.2.2
Windows NT4 note.......................................................................................................................................... 6
5
USING THE SERIAL DRIVER.................................................................................................................................. 7
5.1.1
5.1.2
Windows 95/98 configuration ......................................................................................................................... 7
Windows 2000 configuration .......................................................................................................................... 8
6
PARALLEL PORT DRIVER IN WINDOWS 95/98 .................................................................................................. 9
7
CONTACT INFORMATION.................................................................................................................................... 10
8
DISCLAIMER ........................................................................................................................................................... 10
Oxford Semiconductor Ltd.
2
Custom solutions & drivers for the OX16PCI954
VERSION 2.1
4 OVERVIEW and INSTALLATION
4.1
OX16PCI954
4.1.1 Windows 95/98 and Windows 2000 drivers for OX16PCI954
Overview
The architecture of the Windows 9x and Windows 2000 drivers is very similar. The driver set consists of Plug and Play bus drivers, which
create device objects for each UART / parallel port available. Each UART is hooked by a single-port driver, which enables the following
16C95x features:
• 128-byte receiver and transmitter FIFOs
• Adjustable receiver and transmitter interrupt trigger level
• Automatic flow control
• Quad speed (using Times clock register)
• Flexible baud rate generation up to 60Mbaud (50Mbaud on OX16C954)
• RS485 half-duplex configuration
• Memory-mapped operation (Windows 2000 driver only)
The parallel port is hooked to the generic driver supplied with Windows.
The drivers will recognise the OX16PCI954 in any of its default configurations, and also recognise the reserved device ID 0x950A as a two
serial port device (see application note “Custom Drivers” for more information).
Installation
Install the hardware by following system instructions. Power up the system. Then follow the instructions below depending on which
operating system is installed. To upgrade the Windows 9x driver from a previous release, first boot up the system with the existing drivers.
Right-click “My Computer”, select Properties, then Device Manager. Double-click “Multifunction” and remove all Oxford Semiconductor
devices from this category. Restart the machine, then follow the instructions below.
Windows 98
1. The system will detect the device and start the “Add new hardware” wizard. Click Next to continue.
2. The system will suggest that it searches for the best driver for the device. Click Next to confirm.
3. If the driver files are on a floppy disk, insert it into the drive now. If the driver files are on the hard disk, point the wizard at the
correct directory.
4. Click Next to continue.
5. The system searches for the driver. If it doesn’t find the Oxford Semiconductor device, make sure the driver files are present and
the Wizard knows where to find them.
6. Once the system has found the driver, click Next to continue.
7. The system installs the driver.
8. Click Finish.
9. If you are using the parallel port, the system will detect it next. Repeat steps 2-8 to install the parallel port drivers.
10. Once the main drivers are installed, the system installs the UART ports automatically.
Windows95 (OSR21)
Note: the system prompts may vary between different versions of Windows. If in doubt consult the user manual.
1. The system detects the device and starts the “Update Device Driver” wizard.
2. If you have the driver files on a floppy disk, insert it into the drive now. Click Next to continue.
3. The system searches for the driver. If it doesn’t find the Oxford Semiconductor device, click ‘Other Locations’ and enter the full
path to the driver files.
4. Once the system has found the driver, click Finish.
5. The system installs the device, and then goes through the same steps for the local bus / parallel port.
6. Once the main drivers are installed, the system installs the UART ports automatically. (Note: due to a Win95 bug you may have to
re-enter the path for it to find the files).
Oxford Semiconductor Ltd.
3
Custom solutions & drivers for the OX16PCI954
VERSION 2.1
Windows95 (original release1)
Note: the system prompts may vary between different versions of Windows. If in doubt consult the user manual.
1. The system will detect the device and ask which driver to install. Select “Driver from disk provided by hardware manufacturer”,
and click OK.
2. If you have the driver files on a floppy disk, insert it into the drive. Otherwise enter the full path to the driver files. Click OK.
3. The system installs the device, and then goes through the same steps for the local bus / parallel port.
4. Once the main drivers are installed, the system installs the UART ports automatically. (Note: due to a Win95 bug you may have to
re-enter the path for it to find the files).
Windows2000
1. The system will detect the device and ask which driver to install. Click Next
2. Select “Search for a suitable driver for my device”, and click Next.
3. If you have the driver files on a floppy disk, insert it into the drive and check the “Floppy disk drives” box. Otherwise check the
“Specify a location” box. Click Next
4. If “Specify a location” was checked, you will have to enter the path to search and click OK.
5. The system will search for a driver. When it finds it, click Next. The files will be copied and the driver installed. Click Finish. The
system then installs the other logical function (parallel port / local bus) in the same manner.
6. Once the PCI devices are installed, the system will install the UART ports automatically.
Note 1: To check your version of Windows 95, right-click on “My Computer” and select “Properties”. The System Properties page will appear. If
the version is 4.00.950 B or C, you are using OSR2. If the letter is A or is absent, you are running the original release.
Oxford Semiconductor Ltd.
4
Custom solutions & drivers for the OX16PCI954
VERSION 2.1
4.1.2 Windows NT4 driver for OX16PCI954
Overview
The Windows NT4 driver creates a Device Object for each port, and registers this with the operating system. The serial port driver enables
the following 16C95x features:
• 128-byte receiver and transmitter FIFOs
• Optimized receiver interrupt handling – uses readable fill levels and thresholds
• Automatic clock speed detection
• Memory-mapped operation for efficient throughput
A separate parallel port driver is provided, which creates the device Object and registers it with the Printer class driver.
The Windows NT4 driver searches the PCI bus for the VendorID / DeviceID combinations specified in the oxser.inf file. If the chip has been
reconfigured with the EEPROM (e.g. DeviceID reconfigured as 0x950A to be a two-serial port solution) the oxser.inf file will need to be
modified (see application note “Custom Drivers” for more information).
Installation
Install the hardware by following system instructions. Power up the system. Then follow the instructions below depending on which
functions are required. To upgrade the NT4 driver, simply install over the existing version.
Serial driver
1. Run “Install_Serial.exe” from the \NT4_Serial subdirectory on the disk.
2. When the install application starts, click Next to continue
3. Ensure ‘install’ is selected, then click Next.
4. Click OK to accept the licence agreement.
5. The system will install the driver and start it. The ports are immediately ready for use
Parallel driver
1. Run “Install_Parallel.exe” from the \NT4_Parallel subdirectory on the disk.
2. When the install application starts, click Next to continue
3. Ensure ‘install’ is selected, then click Next.
4. Click OK to accept the licence agreement.
5. The system will install the driver and prompt for a restart. The port is available for use after the restart.
Oxford Semiconductor Ltd.
5
Custom solutions & drivers for the OX16PCI954
4.2
VERSION 2.1
OX16C95x (standard UARTs)
4.2.1 Windows 95/98 and Windows 2000 drivers for standard UARTs
Overview
The drivers for standard ports use the same port driver as the OX16PCI954 set, therefore the same features are available:
• 128-byte receiver and transmitter FIFOs
• Adjustable receiver and transmitter interrupt trigger level
• Automatic flow control
• Quad speed (using Times clock register)
• Flexible baud rate generation up to 60Mbps (50Mbps on OX16C954)
• RS485 half-duplex configuration
Installation
Windows will identify all COM ports as standard communications ports. Once a 95x COM port is installed as a generic port, update the
driver as follows:
1. Click on Start / Settings / Control Panel
2. Double click “System” to bring up the system properties dialog box
3. Select the “Device Manager” tab of this dialog (with the “View devices by type” option selected.
4. Now click on the [+] next to the “Ports (COM & LPT)” icon to show the list of installed COM ports (If this section is not present or
no COM ports are listed, there are no serial devices installed in Windows. To install COM port hardware, consult your Windows /
Hardware documentation.)
5. Double click on the port you want to install the new driver for to bring up the settings dialog for that port
6. Select the driver tab and click the update/change driver button.
7. Windows 95
Click on “Have Disk” and specify the location of the driver files. Click OK
The files will now be copied and the driver installed.
8. Windows 98
When the “Update Device Driver Wizard” asks what you want Windows to do, select “Search for a better driver” and then click next.
When asked where to select the “Specify Location” box and type the location of the driver files. Click ‘next’ and the driver will be
installed.
9. Windows 2000
The system starts the Upgrade Device Driver Wizard. Click ‘Next’
Check “Search for a suitable driver for my device” and click Next. Point the wizard at the driver files (on floppy disk or fixed disk) and
click Next. You may have to enter a path to the driver files.
The system will find a selection of suitable drivers. Check “Install one of the other drivers” and then ‘Next’.
Install the “Oxford Semiconductor OX16C95x Communications port”
The files are copied. Click finish to exit the Wizard (and possibly restart)
Alternatively, the driver can be installed manually for a new device without running the auto-detect routines.
4.2.2 Windows NT4 note
There is no enhanced mode driver for standard UARTs in Windows NT4.0. This is because the generic driver will detect any ISA ports and
use them itself.
Oxford Semiconductor Ltd.
6
Custom solutions & drivers for the OX16PCI954
VERSION 2.1
5 USING THE SERIAL DRIVER
The serial drivers for Windows 9x and Windows 2000 make use of a number of enhanced 95x UART features, and are highly configurable.
This section describes the configuration utilities, accessible through Device Manager, which can be used to enable and configure the
various features
The driver will install the correct number of serial ports and Windows will assign COM numbers to them (e.g. COM5). You can then attach
modems etc. to the ports and make use of them in the same fashion as any other generic port. The serial driver has extra configuration
options available over and above the standard ‘settings’ tab supplied with the generic 16550 driver. To adjust any of the UART parameters,
follow these steps:
1. Click on Start / Settings / Control Panel
2. Double click “System” to bring up the system properties dialog box
3. Select the “Device Manager” tab of this dialog (with the “View devices by type” option selected
4. Now click on the [+] next to the “Ports (COM & LPT)” icon to show the list of installed COM ports
5. Double click on an Oxford Semiconductor port to display the settings dialog for that port
The enhanced features are configurable through three dialog pages:
Settings
- Standard port settings found on normal COM port settings pages
Data Rate
- Advanced data rate selection options
FIFOs
- Device mode selection and FIFO trigger level settings
5.1.1 Windows 95/98 configuration
Settings
This page contains the standard Baud rate / Data bits / Parity / Stop bits and Flow control options found on most COM port settings pages.
These settings modify the default settings used by Windows. Most applications that use COM ports will override these settings with their
own comms parameters. Note that the baud rate selected by an application will be scaled up if a faster crystal is used
This page also provides configurable RS485 half-duplex operation. RS232 applications will not use this, and the DTR pin should be
configured as ‘normal’. However if RS485 line drivers are used, the driver can configure the DTR pin to enable the transmitter, in active-high
or active-low form.
Data Rate
This page provides a list of common crystal values used with COM ports. Select “Detect crystal frequency” to detect the input clock
frequency to the UART. (This requires that the port is not currently in use by another application).
[Note: The “Automatic crystal selection” option will not work on COM10 and higher in Windows 9x; this is a limitation of 16-bit DLLs. For
high-numbered ports the user should select the crystal frequency manually.]
The quad speed option will multiply all application selected baud rates by 4 by utilising the OX16C95x Times clock register (TCR)
Selecting “User Defined Override Speed” enables the fully variable baud rate slider and “Clock Pre-Divisor” list box for more flexible baud
rate generation. The actual selected baud rate is displayed above the baud rate slider.
The clock pre-divisor is used to divide the input clock prior to baud rate generation. This means a high speed crystal (E.g 50MHz) can be
pre-divided to generate standard baud rates (In this case 50 / 27.125 = 1.8433 MHz, which will emulate a 1.8432 MHz crystal with less than
0.01% bit rate error). Alternatively, the pre-divisor could be switched off to allow data rates up to 12.5Mbps to be generated.
Oxford Semiconductor Ltd.
7
Custom solutions & drivers for the OX16PCI954
VERSION 2.1
FIFOs
This page provides three device modes. 450 mode, which forces the UART to operate in byte mode (i.e with the FIFO disabled), 550 mode
which operates with 16 byte deep FIFOs, 550 trigger levels and driver generated flow control (non-automated). Finally, 950 mode, which
operates with full 128 byte FIFOs, fully adjustable trigger levels and automated flow-control.
The four sliders allow adjustment of the various trigger levels in 550 and 950 modes. These are described below:
• Transmitter FIFO interrupt trigger level - When the level of data in the transmit FIFO falls below this value, a transmitter interrupt
is triggered. Setting this value to zero will not trigger an interrupt until the transmitter is completely idle. In 450 and 550 mode this
is fixed at 1.
• Receiver FIFO interrupt trigger level - When the level of data in the receiver FIFO reaches this value, a receiver data interrupt is
triggered. In 450 mode this is fixed at 1, In 550 mode it can take 4 discrete values 1,4,8 & 14.
• Flow On flow-control limit - When the level of data in the receiver FIFO reaches this value as data is read from the FIFO, a
handshake is triggered to instruct the remote transmitter that it is free to transmit data (E.g. Transmit an XON character to the
remote machine). In 450 and 550 mode this level is fixed at 1.
• Flow Off flow-control limit - When the level of data in the receiver FIFO reaches this value as it fills up, a handshake is triggered to
instruct the remote transmitter to stop sending data as the FIFO is becoming full. (E.g. Transmit an XOFF character to the remote
machine). In 450 mode this level is fixed at 1, in 550 mode it assumes the same value as the receiver FIFO interrupt trigger level.
The FIFO trigger levels can be fine tuned to gain optimum performance, depending on system performance, baud rate used, levels of serial
traffic etc. The default Receiver FIFO trigger level is preset at a value of 64; this should be increased for higher performance, but in some
cases a high trigger level will result in the port not detecting PnP serial devices.
5.1.2 Windows 2000 configuration
Settings
This page contains the standard Baud rate / Data bits / Parity / Stop bits and Flow control options found on most COM port settings pages.
These settings modify the default settings used by Windows. Most applications that use COM ports will override these settings with their
own comms parameters.
This page also provides configurable RS485 half-duplex operation. RS232 applications will not use this, and the DTR pin should be
configured as ‘normal’. However if RS485 line drivers are used, the driver can configure the DTR pin to enable the transmitter, in active-high
or active-low form. Note: if RS422/485 line drivers are selected, the driver will not allow DTR/DSR flow control, as these pins are not defined
in RS422 protocols.
Data Rate
This page provides a list of common crystal values used with COM ports. Select “Detect crystal frequency” to detect the input clock
frequency to the UART. (This requires that the port is not currently in use by another application).
The baud rate can optionally be adjusted according to the data rate required. To enable the advanced baud rate configuration options,
deselect the “Use default baud rate” box. In normal operation, the driver will generate the desired baud rate from the crystal frequency. The
quad speed option will multiply all application selected baud rates by 4 by utilising the OX16C95x Times clock register (TCR). The driver
can multiply this baud rate, or divide it using the Clock Prescaler register (CPR).
The clock pre-divisor is used to divide the input clock prior to baud rate generation. This means a high speed crystal (E.g 50MHz) can be
pre-divided to generate standard baud rates (In this case 50 / 27.125 = 1.8433 MHz, which will emulate a 1.8432 MHz crystal with less than
0.01% bit rate error). Alternatively, the pre-divisor could be switched off to allow data rates up to 12.5Mbps to be generated.
Oxford Semiconductor Ltd.
8
Custom solutions & drivers for the OX16PCI954
VERSION 2.1
FIFOs
This page is used to configure the FIFO trigger levels, i.e. at what fill levels the device will generate an interrupt, or apply automatic flow
control. In addition, the FIFOs can be completely disabled; although this is not recommended for normal operation.
The four sliders allow adjustment of the various trigger levels in 550 and 950 modes. These are described below:
• Transmitter FIFO interrupt trigger level - When the level of data in the transmit FIFO falls below this value, a transmitter interrupt
is triggered. Setting this value to zero will not trigger an interrupt until the transmitter is completely idle.
• Receiver FIFO interrupt trigger level - When the level of data in the receiver FIFO reaches this value, a receiver data interrupt is
triggered.
• Flow On flow-control limit - When the level of data in the receiver FIFO reaches this value as data is read from the FIFO, a
handshake is triggered to instruct the remote transmitter that it is free to transmit data (E.g. Transmit an XON character to the
remote machine).
• Flow Off flow-control limit - When the level of data in the receiver FIFO reaches this value as it fills up, a handshake is triggered to
instruct the remote transmitter to stop sending data as the FIFO is becoming full. (E.g. Transmit an XOFF character to the remote
machine).
The FIFO trigger levels can be fine tuned to gain optimum performance, depending on system performance, baud rate used, levels of serial
traffic etc.
6 Parallel port driver in Windows 95/98
The parallel port driver will set the hardware to use legacy addresses 378h if available, otherwise it will be forced to use the address
allocated by the system BIOS. Windows will allocate an LPT number (e.g. LPT2) to the port; then it can be used in the same fashion as any
generic parallel port. Note: some peripheral devices such as ZIP drives will not operate correctly if the parallel port is not located at address
278 or 378. In this case, the conflicting devices such as the motherboard port will need to be moved to other addresses.
Configuration
The parallel port interrupt can be enabled / disabled using the configuration applet found in Device Manager. This may be necessary if
using Windows 98 and Direct Cable connection. To adjust the setting, follow these steps:
1. Click on Start / Settings / Control Panel
2. Double click “System” to bring up the system properties dialog box
3. Select the “Device Manager” tab of this dialog (with the “View devices by type” option selected)
4. Now click on the [+] next to the “Multifunction Devices” icon to show the list of Oxford Semiconductor parts
5. Double click on the Oxford Semiconductor PCI Parallel port to display the settings dialog for that port
6. Click the “settings” tab of this dialog, and enable / disable the interrupt as required
It is also possible for the port to use address 278h/678h. However, many systems do not support this option due to a contention with
ISAPNP bus enumeration. Check this option to enable it; however be prepared to change it back if the port ceases to work.
Oxford Semiconductor Ltd.
9
Custom solutions & drivers for the OX16PCI954
VERSION 2.1
7 CONTACT INFORMATION
For further information please contact:
Oxford Semiconductor Ltd.
25 Milton Park
Abingdon
Oxfordshire
OX14 4SH
United Kingdom
Telephone:
Fax:
Sales e-mail:
Web site:
+44 (0)1235 824900
+44 (0)1235 821141
sales@oxsemi.com
http://www.oxsemi.com
8 DISCLAIMER
Oxford Semiconductor believes the information contained in this document to be accurate and reliable. However, it is subject to change
without notice. No responsibility is assumed by Oxford Semiconductor for its use, nor for infringement of patents or other rights of third
parties. No part of this publication may be reproduced, or transmitted in any form or by any means without the prior consent of Oxford
Semiconductor Ltd. Oxford Semiconductor’s terms and conditions of sale apply at all times.
Oxford Semiconductor Ltd.
10
OX16PCI954
QUAD UART WITH PCI INTERFACE
EVALUATION BOARD
This document describes the OX16PCI954 evaluation board, how to set its configuration,
install drivers and troubleshoot common problems.
Version 2.61 (21 May 2001)
Custom solutions & drivers for the OX16PCI954
1
VERSION 2.61
Table of Contents:
1
TABLE OF CONTENTS:............................................................................................................................................ 2
2
DESCRIPTION ........................................................................................................................................................... 2
3
BOARD LAYOUT....................................................................................................................................................... 3
KEY................................................................................................................................................................................... 3
4
OPERATION............................................................................................................................................................... 4
5
DRIVER INSTALLATION......................................................................................................................................... 4
6
CONFIGURATION..................................................................................................................................................... 5
7
MISCELLANEOUS LINK SETTINGS...................................................................................................................... 6
8
TROUBLESHOOTING COMMON PROBLEMS..................................................................................................... 9
9
REFERENCE DRIVER / UTILITY DISK ............................................................................................................... 10
10
NOTES ................................................................................................................................................................... 11
11
APPENDIX A: REFERENCE PCB ISSUE B DIFFERENCES ........................................................................... 12
12
CONTACT INFORMATION................................................................................................................................ 13
13
DISCLAIMER ....................................................................................................................................................... 13
2 DESCRIPTION
The development board for OX16PCI954 users provides an environment in which the various modes and features of the OX16PCI954
device can be demonstrated.
It provides a simple means of realising the following products:• 8-port serial card (using four internal UARTs and an OX16C954 on a local bus connection)
• 4-port serial / 1 parallel port card (using only functions internal to the OX16PCI954)
• 4-port serial card with pin-assignable Subsystem ID and subsystem Vendor ID
• 32-bit bridge
The specific features available include:•
•
•
•
•
•
•
•
Configuration into any of the four device modes available
Access to the four OX16C950 UARTs (2xRS232, 2xRS422) from a standard 37-way D-type interface
Use of the 8-bit local bus function to drive an external OX16C954 UART (2xRS232, 2xRS422) from a similar interface
Use of the parallel port function via a standard 25-way D-type header
A serial EEPROM socket to provide maximum device configurability
Use of the internal crystal oscillator, or any frequency via a TTL oscillator socket (switchable). The external OX16C954 can be driven
from the TTL module, or directly from the LB_Clk_Out pin of the PCI device.
Use of isochronous mode feature of the internal UARTs via simple connections
Test points so that all signals on any bus can be observed easily.
Oxford Semiconductor Ltd.
2
Custom solutions & drivers for the OX16PCI954
VERSION 2.61
3 BOARD LAYOUT
The layout of the development board is shown in figure 1.
1
CLKsel
1
P1: Test pin header
External
OX16C954
1
LK1
XT1
1
P4: Parallel port
P3: External 954 serial ports
P2: PCI954 serial ports
RIO link
1
XTALsel
1
LK 5
OX16PCI954
1
1
Serial
EEPROM
PCI connector
Figure 1: Evaluation board layout
Key
P1:
P2:
P3:
P4:
LK1:
LK5:
RIO link:
XT1:
XTALsel:
CLKsel:
Serial EEPROM:
Test pin header – all non-PCI pins can be accessed here
37-way ‘D’ connector for access to PCI UART serial ports
header for access to external UART serial ports
header for parallel port
DTR/DSR header for RS422 channels
configuration header
Connect RI from PCI UART channel 0 or external UART channel 0 to MIO0
socket for TTL crystal oscillator
select internal oscillator or TTL module
select TTL module or LB_Clk_Out
socket for serial EEPROM
All links settings are detailed from page 5 onwards. Please note that some boards also have a parallel-port data transceiver (IC13 next to
the parallel port header). This should be disabled if the local bus is being used.
Oxford Semiconductor Ltd.
3
VERSION 2.61
4 OPERATION
In any mode the device requires an external clock. Ensure a jumper is fitted to XTALsel, selecting either the crystal or a TTL module which
must be fitted to XT1. If the OX16C954 device is being used, a jumper must be fitted to CLKsel, selecting either the TTL module which must
be fitted, or the LB_Clk_Out of the 0X16PCI954; this must be enabled by writing to the configuration register.
To use the device as a Quad UART + 8-bit local bus, set the mode pins to ‘00’ and insert the OX16C954 device into the socket. Disable
the parallel port transceiver. For both the PCI UARTs and the local bus UARTs, channels 0 and 1 interface via RS232 connections, and
channels 2 and 3 interface via RS422 connections. The DTR and DSR signals of the RS422 ports are available via the LK1 header – an
extra cable is needed if these lines are required. Basic hardware flow control can be achieved without these, however they will be required
for DTR/DSR flow control or isochronous mode operation.
Connect the extra 37-way D connector to P3, and if the RS422 channels are required enable them via LK5.
The board is now ready for use.
To use the device as a Quad UART + parallel port, set the mode pins to ‘01’ and remove the OX16C954 device from the socket. Disable
the parallel port transceiver. The UART channels interface as above.
Connect the parallel port header to P4, and if the UART’s RS422 channels are required enable them via LK5. The board is now ready for
use.
To configure the OX16PCI954 via the serial EEPROM, merely insert the EEPROM into its socket. All features of the device can be
programmed into the PROM via the OXPROM.EXE utility.
The PCI UART can use the internal crystal oscillator or an external TTL clock source. Select the mode required using the XTALsel link. The
external UART can also use the TTL source or the LB_Clk_Out line from the OX16PCI954. Select the mode required using the CLKsel link,
and enable/disable the LB_Clk_Out line as appropriate via the local configuration registers. (This can be done with the Microsoft DEBUG
utility, or in the serial EEPROM.
To use the Local bus in Motorola mode, short the Intel/Motorola# link on the LK5 header. In this mode the default Local bus timing values
should be changed in the local configuration registers as follows:Read-not-Write De-assertion = 4
Read Data-strobe assertion = 1
Write data-strobe assertion = 1
Write data-strobe de-assertion = 3
Also, MIO[8] in the MIO configuration registers should be configured to an inverting input, and MIO[9-11] masked off. An EEPROM
configuration file, motorola.dat has been provided for this purpose.
5 DRIVER INSTALLATION
For detailed instructions on how to install the reference drivers, please refer to the application note “Reference Drivers” supplied with this
document.
Oxford Semiconductor Ltd.
4
Custom solutions & drivers for the OX16PCI954
VERSION 2.61
6 CONFIGURATION
The board and device are configured using the configuration header LK5. The pinout is shown in Figure 2. (All links are shown oriented with
Figure 1).
˜˜
˜˜
˜˜
˜˜
˜˜
˜˜
˜˜
˜˜
˜˜
˜˜
External FIFOSEL#
LPTBUF#
Low power enable
INTEN#
Intel/Motorola# mode
RS422 enable
TEST
MODE1
MODE0
PCI FIFOSEL
Figure 2: Configuration header LK5
The table below shows the function of each pair of pins
Pins
External FIFOSEL#
LPTBUF#
Low power enable
INTEN#
Short
External UART has 128-deep FIFOs
Parallel port transceiver disabled
Allow driver to shutdown RS232 line
drivers
External UART interrupts enabled
Intel/Motorola# mode
RS422 enable
TEST
MODE1
MODE0
PCI FIFOSEL
Motorola-type local bus
Enable RS422 line drivers
Always short
Mode[1] = 1
Mode[0] = 1
PCI UART has 128-deep FIFOs
Open
External UART has 16-deep FIFOs
Parallel port transceiver enabled
RS232 line drivers always enabled
External UART interrupts enabled
dependent on MCR[3]
Intel-type local bus
Disable RS422 line drivers
Do not open connection
Mode[1] = 0
Mode[0] = 0
PCI UART has 16-deep FIFOs
Select the device mode as follows:Mode[1:0] = ‘00’ : Quad UARTs & 8-bit local bus
Mode[1:0] = ‘01’ : Quad UARTs & parallel port
Mode[1:0] = ‘10’ : Quad UARTs & pin-assignable Subsystem ID and Subsystem Vendor ID
Mode[1:1] = ‘11’ : 32-bit bridge
Oxford Semiconductor Ltd.
5
Custom solutions & drivers for the OX16PCI954
VERSION 2.61
7 MISCELLANEOUS LINK SETTINGS
XTALsel: select oscillator for OX16PCI954
TTL oscillator
Crystal
Select desired oscillator by linking from centre to the pin required.
CLKsel: select oscillator for external UART
TTL module
˜ ˜ ˜
LB_Clk_Out
Select desired oscillator by linking from centre to the pin required
RIO link: connect MIO0 to RI of PCI UART channel 0 or external UART channel 0
PCI UART RI0
˜ ˜ ˜
External UART RI0
Select RI desired by linking centre to that desired. Default = no link. If this is used, MIO[0] should be reconfigured in the local configuration
registers otherwise an interrupt on function 0 will be constantly present.
Pinout of RS422 ports:
RS422 supports much higher data transfer rates due to its differential signalling. The RS422 ports are connected as follows on the 9way D-connectors:Pin
1
2
3
4
5
6
7
8
9
Signal
TXDTXD+
RTSRTS+
GND
RXDRXD+
CTSCTS+
LK1: The lines provided on the RS422 connectors only allow for CTS/RTS flow control. If DTR/DSR flow control is needed, header LK1
provides access to the extra hardware lines. The pinout is as follows:DSR2DSR2+
GND
DSR3DSR3+
˜˜
˜˜
˜˜
˜˜
˜˜
Oxford Semiconductor Ltd.
DTR2DTR2+
DTR3DTR3+
NC
6
Custom solutions & drivers for the OX16PCI954
VERSION 2.61
P1: Test pins
1
32
C ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜
B ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜
A ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
Oxford Semiconductor Ltd.
A
MIO0
MIO3
MIO6
PE
SLCT
LBCS1#
LBRD#
GND
SLIN#
STB#
PD0
PD3
PD5
MIO8
MIO11
DCD3
DTR3
GND
TXD3
DTR2
DCD2
GND
RXD2
DCD1
DTR1
TXD0
CTS0
RI0
GND
GND
GND
GND
B
MIO1
MIO4
MIO7
BUSY
ERR#
LBCS2#
LBWR#
LBCLK
INIT#
GND
PD1
GND
PD6
MIO9
RXD3
DSR3
RTS3
GND
TXD2
CTS2
RI2
LB_Clk_Out
RXD1
DSR1
RTS1
RTS0
DSR0
RXD0
FIFOSEL
TEST
MODE1
MODE0
C
MIO2
MIO5
LBRST#
ACK#
LBCS0#
LBCS3#
GND
GND
AFD#
LBDOUT
PD2
PD4
PD7
MIO10
RI3
CTS3
GND
GND
RTS2
DSR2
GND
GND
RI1
CTS1
TXD1
DTR0
DCD0
GND
VCC
VCC
VCC
VCC
7
Custom solutions & drivers for the OX16PCI954
VERSION 2.61
Pinout of 37-way D-type connector
The following pin description is the same for the PCI internal UARTs and the four ports from the OX16C954 local bus device
37-way D-type pin number
1
20
2
21
3
22
4
23
5
Port number / type
Port 1 / RS232
Port 1 / RS232
Port 1 / RS232
Port 1 / RS232
Port 1 / RS232
Port 1 / RS232
Port 1 / RS232
Port 1 / RS232
Port 1 / RS232
9-way D-type pin number
1
6
2
7
3
8
4
9
5
Description
DCD
DSR
RxD
RTS
TxD
CTS
DTR
RI
GND
24
6
25
7
26
8
27
9
28
Port 2 / RS232
Port 2 / RS232
Port 2 / RS232
Port 2 / RS232
Port 2 / RS232
Port 2 / RS232
Port 2 / RS232
Port 2 / RS232
Port 2 / RS232
1
6
2
7
3
8
4
9
5
DCD
DSR
RxD
RTS
TxD
CTS
DTR
RI
GND
10
29
11
30
12
31
13
32
14
Port 3 / RS422
Port 3 / RS422
Port 3 / RS422
Port 3 / RS422
Port 3 / RS422
Port 3 / RS422
Port 3 / RS422
Port 3 / RS422
Port 3 / RS422
1
6
2
7
3
8
4
9
5
TxDRxDTxD+
RxD+
RTSCTSRTS+
CTS+
GND
33
15
34
16
35
17
36
18
37
19
Port 3 / RS422
Port 3 / RS422
Port 3 / RS422
Port 3 / RS422
Port 3 / RS422
Port 3 / RS422
Port 3 / RS422
Port 3 / RS422
Port 3 / RS422
NC
1
6
2
7
3
8
4
9
5
NC
TxDRxDTxD+
RxD+
RTSCTSRTS+
CTS+
GND
NC
Oxford Semiconductor Ltd.
8
Custom solutions & drivers for the OX16PCI954
VERSION 2.61
8 TROUBLESHOOTING COMMON PROBLEMS
Problem: The system doesn’t detect the correct devices
Solution: Make sure the TEST link on LK5 is shorted, and the MODE links are set correctly
Problem: The system detects the ports but a terminal application will not recognise them.
Solution: Ensure that the application supports COM ports other than the four legacy addresses (3f8, 2f8, 3e8, 2e8). If not, use an
application that supports all COM devices, such as Quarterdeck Procomm Plus®, or Ericom PowerTerm®.
Problem: Some or all of the ports will not communicate with other devices
Solution: Ensure that the baud rates are correct. The OX16C95x family of UARTs has a very flexible baud rate generator, which can
accept differing crystal frequencies, prescalar values etc. The serial port configuration utility in the Windows 9x driver can set baud rate
multipliers etc. or completely override an application’s baud rate setting.
Solution: Two of the ports on each UART chip have RS422 line drivers. These support higher data transfer rates, but will not interface to
RS232 ports. Ensure that the correct ports are being used.
Solution: Ensure that the parallel port transceiver is disabled (link 2 on the LK5 block should be short)
Solution: Ensure that the port has a clock signal, either from the OX16PCI954 oscillator, or from the TTL clock module. This is selected
with XTALsel (internal UARTs) and CLKsel (local bus UARTs)
Problem: The parallel port is recognised, but will not communicate with the printer or other device
Solution: Ensure that the parallel port transceiver is enabled if present (link 2 on the LK5 block should be open), also remove the
OX16C954 from the PLCC socket
Problem: The local bus will not work in Motorola mode
Solution: there is a connection missing on the development board. Call Oxford Semiconductor for details
Problem: When the board is installed in a system, it complains of a resource clash.
Solution: PCI devices should be able to share interrupts, however, not all other devices have drivers written to handle this. If another
device is using one of the interrupts which is being assigned to the OX16PCI954, there are various things that can be done to work around
this problem.
1) Move the OX16PCI954 board to a different PCI slot
2) Change the settings in your system BIOS to allocate different resources (not all BIOSes have this feature)
3) Use the serial EEPROM to only allocate one interrupt to the two OX16PCI954 functions
4) Disable any non-critical device that is using the same interrupt – for instance USB controllers can often not share resources
adequately.
Problem: The PC will not turn off with the OX16PCI954 installed.
Solution: Apply a PME# pin isolator as recommended in the application notes. Newer demonstration boards have this modification
applied.
Oxford Semiconductor Ltd.
9
Custom solutions & drivers for the OX16PCI954
VERSION 2.61
9 REFERENCE DRIVER / UTILITY DISK
The disk supplied contains a reference Windows 9x driver, a reference Windows 2000 driver, and reference drivers for Windows NT4. It
also contains related utilities and documentation.
The contents are listed below:\
oxpar.inf
oxpar2.inf
oxpci.inf
oxpci2.inf
oxser.inf
oxmep.sys
oxmf.vxd/sys
oxmfuf.sys
oxpar.sys
oxpp.vxd
oxser.vxd/sys
oxppui.dll
oxserui.dll
oxui.dll
- driver .inf file
- driver .inf file (2)
- driver .inf file
- driver .inf file (2)
- driver .inf file
- PCI support driver
- bus enumerator
- Upper filter driver
- port driver
- parallel port enumerator
- port driver
- parallel port configuration utility
- driver configuration utility
- driver configuration utility
\oxprom
oxprom.exe
oxeeprom.sys
.dat files
- Serial EEPROM programming utility
- needed by oxprom.exe
- example EEPROM configuration files
\utils
readuart.exe
poke.exe
.vxd files
- dump UART registers from within Win9x.
- memory access utility
- needed by above utilities
\doc
devboard.pdf
- this file
advancedtopics.pdf - advanced baud rate configuration in Windows 2000
customdrivers.pdf - details on customising drivers
referencedrivers.pdf
- driver installation and use
\NT4_Parallel
Install_Parallel.exe - install program for Windows NT4 parallel port driver
oxpar.inf
- installation script
oxpar.sys
- port driver
licence.txt
- licence agreement
\NT4_Serial
Install_Serial.exe
oxser.inf
oxser.sys
licence.txt
Oxford Semiconductor Ltd.
- install program for Windows NT4 serial port driver
- installation script
- port driver
- licence agreement
10
Custom solutions & drivers for the OX16PCI954
VERSION 2.61
10 NOTES
This page has been intentionally left blank.
Oxford Semiconductor Ltd.
11
Custom solutions & drivers for the OX16PCI954
VERSION 2.61
11 Appendix A: Reference PCB Issue B differences
In line with its policy of continuing development Oxford Semiconductor has revised and re-issued the PCI 954 Reference PCB, providing a
board which is both easier to use and more reliable. The few changes visible to the end user are documented here.
The External OX16C954, labelled IC1 has been rotated 90° clockwise. Pin 1, marked by a dimple and a bevelled edge on the IC, should be
facing the right of the board, away from the serial connectors.
LK5 has been renamed JP3, but remains in the same position, and maintains the same functionality, with these exceptions:
The parallel port has no transceiver buffers, and hence LPTBUF# is not used.
The RS232 line drivers are permanently enabled, so Low Power Enable is no longer connected.
The RS422 line drivers also permanently enabled, so RS422 Enable is no longer required.
TEST has been permanently shorted on the PCB, and no jumper is required on this pin.
For compatibility these jumpers are physically present, but have no electrical function.
P4: the Parallel port, has been renamed JP7, but remains in the same place with the same connectivity and function.
P3: External 954 serial ports has been renamed JP1, but again retains the same position and connectivity.
P1: Test Pin Header has been renamed JDH1, with the pinout remaining the same.
XT1 is renamed to JS1.
Serial EEPROM has been renamed to IC7
Oxford Semiconductor Ltd.
12
Custom solutions & drivers for the OX16PCI954
VERSION 2.61
12 CONTACT INFORMATION
For further information please contact:
Oxford Semiconductor Ltd.
25 Milton Park
Abingdon
Oxfordshire
OX14 4SH
United Kingdom
Telephone:
Fax:
Sales e-mail:
Web site:
+44 (0)1235 824900
+44 (0)1235 821141
sales@oxsemi.com
http://www.oxsemi.com
13 DISCLAIMER
Oxford Semiconductor believes the information contained in this document to be accurate and reliable. However, it is subject to change
without notice. No responsibility is assumed by Oxford Semiconductor for its use, nor for infringement of patents or other rights of third
parties. No part of this publication may be reproduced, or transmitted in any form or by any means without the prior consent of Oxford
Semiconductor Ltd. Oxford Semiconductor’s terms and conditions of sale apply at all times.
Oxford Semiconductor Ltd.
13