______________________________________________________________________________
Windows CE 5.0 UART Driver for PCI Devices
Copyright (C) 2008 Oxford Semiconductor Inc.
Supported devices: OXuPCI952, OXuPCI954,
OXmPCI952, OXmPCI954,
OX16PCI952, OX16PCI954
______________________________________________________________________________
_____________________________________
Driver Installation: Using CEC File
_____________________________________
1. Install Windows CE 5.00 Platform Builder (PB) to development PC
2. Double click the batch file "CopyDriverToWinCERoot.bat" to execute it.
This batch file will prompt the user to enter the WINCEROOT (e.g. C:\WINCE500).
The batch file will then copy all files and sub-folders of the driver to the
WINCEROOT. The following directory structure shall be seen:
C:\WINCE500\OXSEMI
|------UARTS
| |
| |-----....
| |-----PCI16950
| |-----PDD16950
| |-----SER16950
| |-----MDD16950
| |-----INC
| \-----....
|
\------....
3. Start PB and open a OS image workspace. It is assumed that a OS image is already
built and sysgened.
4. Click “File->Manage Catalog Items” to start “Manage Catalog Items” dialog
5. Click “Import…” button to start “Import Catalog Features” dialog and import
cec file, “pci16950.cec”, present under %WINCEROOT%\OXSEMI\UART\PCI16950.
Next, click OK.
6. In the 'Catalog' window, PCI16950 catalog item will be present under "Third Party\device drivers\serial".
Add "PCI16950" feature to the platform by right-clicking on it and choosing “Add to OS Design”
7. Click "Project->Set Project Build Order.." to start a "Workspace Projects
Build Order" dialog and, if required, rearrange the project build order as shown:
ISR16950
PDD16950
SER16950
MDD16950
PCI16950
8. Next, make sure "Make Run-Time Image After Build" is selected and "Clean Before Building" is deselected.
These options are found under “Build Project".
9. Next, to build the project into the Run-Time OS image, click on "Build Project -> Build All Projects"
10. The OS image named NK.BIN will be generated which will contain the pci16950.dll
driver.
11. Download the OS image to the target (CEPC).
12. The 1st 9 installed (PCI16950) devices are given conventional names of COM1:
to COM9: and all subsequently installed PCI16950 devices will be named as
CMx1: to CMx9: accordingly, where x is a digit of 1 to 9.
______________________________________________________________________________
Modifying the reg file - com16950.reg
______________________________________________________________________________
Crystal Frequency
_________________
The driver performs auto detection of the crystal frequency if no value for the frequency
has been specified in the reg file (i.e. com16950.reg). Please note that the auto detection
algorithm is very accurate but involves time consuming operations. This will delay the
loading of the driver (and in turn the OS) depending on the number of ports.
The value of the crystal frequency can be specified in the registry. This is done
by using the subkey "CrystalFrequency" in the reg file.
For example: "CrystalFrequency"=dword:1194000
where in the value '1194000' is the hexadecimal value for 18,432,000Hz.
The crystal value are expressed in HEXADECIMAL, and NOT DECIMAL.
Here's a list of likely frequencies, and their hexadecimal equivalents:
Frequency (Hz) Hexadecimal equivalent
-------------- ----------------------
60,000,000 3938700
50,000,000 2FAF080
48,000,000 2DC6C00
18,432,000 1194000
16,000,000 F42400
14,745,600 E10000
7,372,800 708000
1,843,200 1C2000
Interrupt triggering and flow control levels
____________________________________________
Four level control values can be defined in "com16950.reg" file (brackets indicate
the corresponding 16950 registers, to where the values will be stored when device
driver being loaded):
"RxIntTrigLevel" ------ Receive Interrupt Triggering Level (RTL)
"TxIntTrigLevel" ------ Transmit Interrupt Triggering Level (TTL)
"FlowCtrlLowLevel" ---- Automatic Flow Control Lower Trigger Level (FCL)
"FlowCtrlHighLevel" --- Automatic Flow Control Higher Trigger Level (FCH)
The level value are expressed in HEXADECIMAL, and NOT DECIMAL. For example, to set
the Receive Interrupt Triggering Level to 95, the following line should exist
under the corresponging key:
"RxIntTrigLevel"=dword:5F
________________________________________________________________________________
Branding / Configuration File using Oxide:
___________________________________________
The driver supports branding and customization. The user can generate a branding
(or configuration) file using Oxford Semiconductor's Oxide tool. Using this file,
the user can specify values for crystal frequency, fifo levels, line driver values
etc.
To support branding files, a few changes need to be made to the reg file:
Add the following two entries to the reg file:
"BrandingFile"="pci_branding_file.oxbc"
"ReadBrandFile"=dword:1
Where "pci_branding_file.oxbc" is the name of the branding file. This
branding file must be stored in the following folder:
%WINCEROOT%\OXSEMI\UARTS\BrandingFiles
The subkey "ReadBrandFile" specifies the driver whether to read the
mentioned branding file or not. The value of '1' means the driver will
read the file.
The branding file is also used by the Set Uart (SUART) Configuration utility to
modify its user interface.
________________________________________________________________________________
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.