Maxim Integrated 73S1217F Windows XP 32 USB CCID and DFU Drivers - Manual (Page 5)

UG_12xxF_030 73S1215F, 73S1217F Windows XP 32 USB CCID and DFU Drivers Installation Guide
Rev. 1.0 5
1 Introduction
This guide describes the installation of the USB-DFU driver and the USB-CCID driver. Teridian includes
all necessary installation and driver files to complete this driver installation. Follow the steps described in
this document to ensure a successful driver installation.
Figure 1 shows the flow of the USB-DFU and USB-CCID interface architecture.
USB - CCID
USB - DFU
DFU
Driver
CCID
Driver
C#
App
Host Controller 73S12xxF Device
Boot
Loader
CCID
App
TSC
Libraries
Figure 1: DFU and CCID Class Interface Architecture
The Windows
®
XP 32 Kernel mode DFU driver was developed using Microsoft
®
2 Installation
Device Driver
Development Kit (DDK) Version (3790.1830) Windows Server 2003. For more information on the DFU
driver, see the 73S1215F, 73S1217F DFU Host Driver/Application Development User’s Guide.
The USB-DFU and USB-CCID (with DFU Interface) driver files are TSCDFU.inf/TSCDFU.sys and
CCIDDFUTSC.inf/CCIDDFUTSC.sys respectively. Refer to the Release Notes for all the files associated
with these drivers.
2.1 Environments
Host Machine:
Operating System: Windows XP 32
Bus Interface: USB port
Device:
73S12xxF Evaluation Board (EVB) running either the DFU Boot Loader code or the CCID Application
code. See the 73S1215F, 73S1217F Boot Loader – DFU Class Firmware Application Note for more
detailed information about the two partitions (thus two executables) of firmware code, namely the DFU
Boot Loader code and the CCID Application Code.
It is important that the correct driver is matched up with the firmware code that is being executed on the
73S12xxF device. In other words, if the DFU Boot Loader code is running, the TSCDFU.sys driver should
be installed. If the CCID Application code is running, the CCIDDFUTSC.sys driver is installed.
Unexpected results occur if the firmware/driver pair are mismatched.
The first time the 73S12xxF EVB is connected to the Host Machine via a USB cable, there are two
possible and separate instances that require fresh driver installations. If the EVB is executing the DFU
Boot Loader code at power up, plugging the EVB in for the first time causes Windows to prompt the user