W załączniku masz downloader
Download DLL release note
Version 4.55.x.x
SMS01221639: The error print-out is fixed for protocol 3.32.
Version 4.54.x.x
SMS01240042: Print out of boot response details for XMM1100 projects.
SMS01224729: " Flashloader logging is very slow (7 times slower) " . The log file is now only opened
once instead of opening,appending and closing every time something is logged. This makes tracing
much faster, but we have not measured how much faster it is - this is all we can do to speed trace up
without omitting information in the trace.
Version 4.53.x.x
SMS01242479 Made support for odd length certificate.
SMS01236598 Fix for download/upload to/from NAND in binary mode.
Version 4.52.x.x
SMS01229586 Binary mode does now works with FFC files as reference.
SMS01229609 Check of HW details against the info in signature is now OK for XMM1100 platform.
Version 4.51.x.x
SMS00936291: “Flashing Certificates – Flashtool”
First working version of all current certificates features.
Added support for a larger COM port string, and made sure that a large string does not cause over
writes.
Version 4.50.x.x
SMS00934737 Added support for write, read and erasure of certificates.
Version 4.49.x.x
SMS00954652 " DLL Trace crashes on some PC's " FlashToolE2 v.4.49.3.38” solved. Moreover, extra
trace information about OS and driver versions, and added the possibility for any program using the
Download DLL to inject data/messages into the DLL trace file (needed for GUI module test).
Version 4.48.x.x
SMS00947647 Testing found an error when using XMM6180 EBL2’s older than version 10.8 whan
loading SW with support for NVM.
Version 4.47.x.x
SMS00943701 Sending separate SetAddress for read operations to satisfy security requirements in
EBL2 for uploading from phone in secure mode.
Version 4.46.x.x
SMS00887853 Support for the storage NVM concept.
SMS00906364 Download speed via USB is enhanced by using protocol 3.32 (length 32bit and constant
package length) and by skipping the write data packs (using USB handshake)
Version 4.45.x.x
SMS00897775 Download DLL: automated release test: Major clean up of trace code and inserting of
COM port emulation. Various communication errors have been corrected in this process.
This version is only compatible with FlashToolE2 version 3.37 or above, since the DLL interface has
been changed.
Version 4.44.x.x
SMS00933679: The DLL now handles Protocol type 2 correctly, so the enhanced protocol features and
erase modes will work as expected.
Version 4.43.x.x
SMS00913256: Check for dynamic EEPROM entry in the memory map (from PRG file) and do not
attempt to erase this area if there is no entry.
SMS00932160: Fix side effect on XMM1100 download, from expanding the boot RX buffer for
XMM6180 downloads.
Version 4.42.x.x
SMS00882099: “Support for extended bootcore response” fixed.
Version 4.41.x.x
SMS00916912: " wrong IMEI / SimLocks after Flashing " fixed (ebl_xgold213.h updated).
Version 4.40.x.x
SMS00837188:
ifwd_comm.c: updated to support usb boot using usb bootrom.
ifwd_comport.c: purge of internal buffers not done for usb port.
ifwd_boot_sgold.c: boot using usb bootrom added.
Version 4.39.x.x
SMS00882793: Download DLL's protocol handler is missing a range check on error codes returned by
target.
SMS00879966: XMM6180 Modem Express Card Software Reset for triggering flash procedure (added
GP0 control)
SMS00879804: Disable option for setting test mode in FlashTool (added parameter to ban EEPROM
writes).
Version 4.38.x.x
Solved SMS00844023 Update download DLL to support xgold110
Version 4.37.x.x
Solved SMS00843392, SMS00849017, SMS00837477, SMS00857427, SMS00849017,
SMS00847521:
Flashtool auto detect if the chip is ES1.x or ES2.0 and select the correct EBL_Loader/EBL
Download with support for XG618 for XMM6180 and ICE3 hardware.
Updated I2C driver for SGOLD2, so not found I2C devices will not stop download process
No Lint & compiler warnings policy is now enforced!
Version 4.36.x.x
SMS00849017: " Handle ES2 Link Establishment Response " Implement support for new XM618 ES2
Link Establishment (Boot) Response in the Download DLL.
Version 4.35.x.x
SMS00844023: “Update download DLL to support xgold110”. The support is added under the
assumption that XG110 behave like XG102 download wise.
Version 4.34.x.x
SMS00827942: “[Download Tool Chain] Release Planning - INI file handling”. Support for Injected
ZIP file in DLL added. Note that the FlashToolE2.exe may not yet support this feature, so this is only
part of the solution.
SMS00833907: “Download DLL for XG213 in CC”. XG213/XMM213 chip download support added.
Version 4.33.x.x
Fixed SMS00831325: “Spansion MCP/NOR support”.
Removed ripple on TX for XMM6180. Support for spansion AAD mux flash chips on XMM6180.
Version 4.32.x.x
Fixes SMS00782492: " Support for Spansion NOR flash for XMM6180 platform. "
Version 4.31.x.x
Fixes SMS00802281:
Fixed problem with upload of large data packages ( & gt; 16KB).
Support faster usb download and upload of largeblock NAND based target.
Total progress indication is merged from other branches (this has been a popular customer request that
should be on the common branch also).
Version 4.30.x.x
- SMS799062 Bug in 'Check file signature HW cfg value'
- SMS764778 Handling of unfinished download ... (need MMI update to close the UTP).
- Misleading errors are removed.
- Support for total progress.
Version 4.29.x.x
- Solution for SMS00780830: Support for XGOLD618. Autodetect if hardware is set for AD or AAD
flash mux mode. PRG file must contain correct EBU setting for AD or AAD flash mux mode.
- Fixed correct length of last upload request for binary upload.
Version 4.28.x.x
- Solution for SMS774668 is excluded from this release as it is not requested by one customer.
- All other solutions were included in the test release (4.27_test_4) approved by the same customer.
Version 4.27.x.x
- More support for EGoldVoice Ver2
- Linerarize problem of SGold systems fixed. (SMS767873)
- Length of protocol enhancements structure is corrected (SMS774668)
- Handling of injected EBL and RAM-PSI in binary mode is fixed. (SMS768449)
Version 4.26.x.x
Fixed bug in EEPROM update linearize function.
Prepare for support of XGold102 and XGold 213 chipsets.
Version 4.25.x.x
Default RAM-PSI was included in the previous release, use same as in 4.23.
Version 4.24.x.x
Load of EBL with higher baudrates added (instead of 115200).
Fixed bug in certificate validation for EGold.
Version 4.23.x.x
EBL-Loader with support for high speed loading of EGoldVoice EBL is removed from the release
again as download can not start unless the new EBL2 is injected.
Version 4.22.x.x
Support for high speed loading of EGoldVoice EBL.
Updated target error handling for EGoldVoice.
Error, in handling of encrypted sec-pack when using HW-dongle, is fixed.
Code warnings removed.
Support for more baudrates.
Version 4.21.x.x
UTP: SMS00750796, SMS00741345:
- Base address of ‘Erase whole flash’ is fixed for EGold Voice.
Speed optimization:
- Support for high speed load of EBL
- Support for target conditional skip erase.
- Support for target skip write-package CRC check.
- Support for high voltage programming.
API readout of flash programming voltage. EFP
Support for download of FFC files.
Check of USER_ID HW bits against bits in the certificate in secure mode on EGOLD Voice.
Version 4.20.x.x
Return error if USB device is not found when using USB auto download mode.
Fixed problem with overwriting allocated memory in function COMPORT_open() located in IFWD_comport.c
when trying to open can USBx port multiple times. This is related to Port swapping issues.
Version 4.19.x.x
Now support for two identical flash devices on Sgold3 in the default EBL.
Error, in ‘Erase whole flash before download’, is fixed.
Version 4.18.x.x
Sideeffect found in the changed CRC handling in previous version. It is now fixed.
Version 4.17.x.x
Error, in the “erase whole flash” option for SGold3 NOR systems, is fixed.
Error, not downloading the last byte if size is odd, is fixed.
Error, in CRC check handling, is fixed.
Version 4.16.x.x
Binary Mode Upload for NAND can now generate a pre-flash image (controlled by the parameter
IFWD_DL_dll_parameter_upload_mbn_data).
Added parameter IFWD_DL_dll_parameter_force_plain_upload to control that uploads should only
include the specified data itself (no extra added EBL’s or MBN at the end).
Support for downloading external EBL with USB added.
Version 4.15.x.x
Error in binary mode preflashing download fixed.
Error in binary upload fixed.
Added time stamps to function traces.
Version 4.14.x.x
Updated to handle RAM-PSI code to be taken from the EBL appended to a BIN file.
Version 4.13.x.x
Further corrections to fix problems with multi USB download in automatic mode.
Version 4.12.x.x
Fix for problem with multi USB download in automatic mode.
File API interface functions are fixed so they support file streams.
Version 4.11.x.x
Error in the EEPROM patch concept for EGoldRadio is fixed.
Version 4.10.x.x
Same as version 4.9; due to confusion when using our new automatic release tool.
Version 4.9.x.x
Unstable boot on SG3 is fixed.
Error – no erase of dynamic eeprom after download of bootcode FLS file, is fixed.
Version 4.8.x.x
UTP SMS00661541, problem with core voltage level, is fixed.
UTP SMS00703073, Support for new EEPROM patch concept.
Memory leaks eliminated.
Error, in conditional erase of dynamic EEPROM vs download of FLB files, is fixed.
Version 4.7.x.x
Error in erase-all mode for NOR flash is fixed.
Version 4.6.x.x
Added support for trace on Single File Handler state-machine and handling flags.
Support for flash memory type SST32HF64A2
Communication buffers size doubled to 32K to support USB transfer using 16K block size.
Error in RX trace function is fixed
Version 4.5.x.x
Fixed repeated injection of EBL for EGold.
SGold timer duration for EBL transfer increased to 30000 milliseconds to avoid timeouts on large
EBL’s.
Added support for trace of DLL actions (Function calls and IO).
Version 4.4.x.x
Support for binary mode NAND system pre-flashing and cloning is finalized.
Support for NAND erase all option to include erases of bad-blocks also.
Conditional erasure of dynamic eeprom is fixed so it will work correctly on NAND systems.
EGoldVoice boot handler is updated so “HandshakeMode” values from the PRG files does not cause
CRC errors.
Version 4.3
Fixed the last functions that didn’t check for invalid header format, so that the DLL does not enter an
endless loop on invalid data.
Version 4.02
Made DLL more robust against getting files without a proper header on the interface (needed to allow
Binary mode download).
Version 4.01
Must be used with tool chain version 2.x
Speed optimizations:
IMPOTRANT: PC USB driver “10/07/2007,1.0.0.4” (or newer) must be installed before the
speed optimizations will have full effect. This driver is included in the release.
•
•
•
Support for 16Kbytes protocol packages.
Protocol CRC calculation and check can now be disabled if USB-loader in target supports this
feature.
File data CRC calculation and check can now be disabled if USB-loader in target supports this
feature.
Erase of total area length.
Erase of whole flash.
Multi TOC file handling finalized.
Version 3.10 (Version should have been 4.00)
Support for new prg format added due to file format change. It will not be backwards compatible!
Version 3.09
Support for Sgold-Radio ES2 also on NAND systems (only small block NAND’s at the moment)
Version 3.08
Support for Sgold-Radio ES2
Version 3.07
Error in bootloader for MPE-Lite is fixed.
Support for Sgold-Radio ES2 is prepared – still only support for ES1
Version 3.06
Error in updating the static EEPROM on NAND systems is fixed.
Version 3.05
Support of SG3H added.
Error, in checksum handling for multi load region files, is fixed.
Checksum error in EEPROM download when “Test mode” is enabled.
Version 3.04
Error, preventing DFFS files to be downloaded correctly, is fixed.
Version 3.03
Error, in handling of DSP code download, is fixed.
Error, in handling of injected EBL-loader, is fixed.
Version 3.02
Now the whole flash can be erased when downloading boot-system files to a NAND system. (UTP
SMS00443803)
Version 3.01
Fixed bug in DFFS handling.
Version 3.00
Added support for E2 Tool chain (new PRG file header format).
Added support for NAND disk system (.dfat files).
Compiled the stand-alone library with Visual Studio .Net (VC7) instead of VC6.
Version 2.15
Bugfix to avoid damage of NAND board (forced timeout if no partition found).
The bootload cannot be overwritten if this “don’t touch” flag is set by FlsSign.exe.
Version 2.14
Close comport handling is improved.
Interval between AT sync word transmit is now 20ms
NULL pointer check added to EEP update mem array.
Version 2.13
Added support for S-Gold Radio.
Version 2.12
Added 20ms delay after device synchronized to make boot more stable.
Functions to send 'End of process' pack to the target, is added.
New release including major cleanup and use of new MAC NAND interface introducing PSI and SLB
partition handling.
Now the correct CFG file is selected for eeprom update in case no FLS file is downloaded.
Removed unused define, change sending time from 20ms - & gt; 1ms (will not have much effect in
Windows XP).
Version 2.10
Added support for SG3 bootcore 3
Error check and 32 bit alignment introduced to the EEPROM linearize function.
Support for HASH check on EEP files is added.
Support for separate download of dynamic and static part of DFFS files is added.
Version 2.9
Fixed USB boot problem by polling as before when booting on USB.
Version 2.8
Fixed problem during multi channel boot: a boot would erase target capability all channels (not just the
current). This resulted in checksum errors if a channel was booted while others were downloading.
Fixed COM ports that remain open when open has failed (e.g. open a normal COM1 with higher speeds
than 115200 would fail, and leave the port open).
Error in EBL Memory configuration fixed.
Speed optimization: removed run-time debug from main loop.
Version 2.7
Reduced CPU load while booting by not polling in rx result on every clock.
Fixed problem with Protocol handler that will keep on failing once it has failed once.
Fixed problem with using 32 channels (last channel will now open)
HW reset and power down functionality added
New release supporting 4k NAND alignment for the PI region in the code sw partition.
Version 2.6
Added extra reset timeout to avoid repeated downloads on the same phone during USB autoboot
download.
Fixed COM port open bug, where a port open fail would cause it to fail forever until the program is
closed and run again.
Handling of 1Gbit BIN files are now correct.
Handling of Load Regions is changed to use addresses instead of total length.
Sec End now only send on Erase dyn EEP for NAND.
Source of PC-crash in BIN mode is fixed.
Support for SST flash is now OK.
Version 2.5_test2
Patch/test release to overcome problems with EEPROM Update on the MPEH platform.
Version 2.5
Handling of 1Gbit BIN files is now correct. The DLL now waits after the reset command has been sent,
so auto boot with USB does detect the same target right after a download.
Version 2.4
Error, preventing boot on SGold2 systems (introduced in version 2.3), is fixed.
Error, preventing stable boot via USB, is fixed.
Version 2.3
Now support for NAND flash on the SGold3 (safe mode) platform.
External timeout set-up has effect now.
The result of the target-PC capability negotiation is now shown during download.
Additional EEP checksum error is now fixed.
Version 2.2
Problems with multi channel download are fixed.
Error, when using DEP/CFG files with long lines, is fixed.
Checksum error after EEP download is fixed.
Path length for DEP and CFG files are now 300 chars.
Version 2.1
Better detection of idle state, and when in idle no CPU power is used.
Optimized code for speed
Added 3 parameters to " IFWD_DL_set_dll_parameter() " :
IFWD_DL_dll_parameter_skip_empty_blocks (faster downloads)
IFWD_DL_dll_parameter_faster_crc_method (faster downloads)
IFWD_DL_dll_parameter_lower_multichannel_CPU_load (less CPU usage)
Fixed problem when opening multiple USB ports
SGold 2 EBL is updated for better support of Sibley flash.
SGold 3 EBL is updated due to automatic detection of muxed or non-muxed bus.
Version 2.0
UTP SMS00360820 is resolved with this release.
Support for ‘Enhanced protocol’ where the PC and the target negotiate capabilities before
download starts.
Protocol enhancements:
- Overall download speed is increased by sending write response before the actual write.
- DFFS file download speed is increased by avoiding the transmission and target side
handling of packages containing only 0xFF as this is the value in the flash after erase
anyway.
Instruction cache is enabled on SGold for faster execution.
General optimizations are made different places in the code.
Support for EGold Voice.
Support for external RAM on CS3 or CS4 on EGold Radio and Voice.
Generic support for both multiplexed and non-multiplexed flash interface on SGold3.
Version 1.22
PEC is disabled for EGold communication to fix rare download failure.
Flash handling is changed to fix delay with AMD devices
Version 1.21
The COM port driver will now no longer try to change parameters that the device says are unsupported.
This fixes crash problems on devices that e.g. could not change baud rate. Updating EEPROM data has
been made more robust. The DLL will now use 0% CPU time while no COM ports are open.
Version 1.20
Fixed crash problems when updating some EEPROM data.
Version 1.19
DLL Interface has changed to version 1.12. Enum types that are not int’s have been removed from the
interface, and replaced with basic ANSI C types. This is done to ensure compatibility with MSVC.
Made boot and COM port handling more robust, and COM1 is now supported again. Cleaned up source
code to make the DLL code compliable in MSVC++6.0 as a library. The recently added support for
SST FLASH chips has been temporarily removed to avoid stability issues.
The Download DLL code is now available as a MSVC++6.0 library stored in the
“Download_DLL.zip” file under the “VisualStudio” folder. This folder contains both the MSVC
projects that generated the library and a binary release and debug version of the library. A small
console test application with source and executable is also stored there as a reference as to how the
library could be used.
Version 1.18
Support for IFWD_coder DLL. This enables customers to protect their files from unauthorized
download by giving the choice of dongle protection.
Version 1.17
Support for automatic download start mode is added.
Version 1.16
Support for static EEPROM update is added.
An error in the low-level AT command handling is fixed.
Version 1.15
EGold EBL is updated to read OTP flash area and to handle SLB lock/unlocked flag.
AT mode commands are implemented.
Error handling is updated for boot and comm handlers.
Version 1.14
EGold EBL is updated to fix download problems, related to size of last download data package.
Version 1.13
Function to read SW version data can now read from file without the need for COM-port open and
connected target.
Function to force a HW reset on the target is implemented.
Version 1.12
Temporary fix for improving download speed.
Fixed in handling of binary download, upload and erase.
Older versions
For the versions before version 1.12 there have not been any release notes.
FlashTool E2 Release Note
Version x.x.3.44
Same as version 3.43, but has merged more code from other branches to minimize the differences
between branches.
Version x.x.3.43
SMS01224677: " Batch version of Flash tool must support flashing in Ptest mode " :
The IFX_DL.exe (command line version 3.23) has now been updated to support FLS file with NVM
information. Normal mode is default, and the Fixed area is now always erased incase NVM is
supported in the FLS files to ensure that either normal- or test mode is set on download.
SMS01242488: " Certificate flashing menu supports read after storage erase " .
A warning is issued if the user tries to format the certificate area, and then following read or erase
individual areas.
SMS01241912: " FlashToolE2 MMI Improvements "
Many minor MMI improvements have been implemented in FlashToolE2.exe.
Version x.x.3.42
SMS00936291: " Flashing Certificates - Flashtool " .
Finalizing the first working version of FlashTool that supports Certificate handling.
Added preliminary version of the Quantum USB download that uses Quantum’s own USB driver (but
it requires a change in the DLL to work or the support of the calls that the current DLL uses). This
release is only for the Quantum customer.
Version x.x.3.40
SMS00936291: " Quantum needs to be able to flash the security certificates (RnD, CC & HWC).
Added a Certificate tab (either enable it in settings, or right-click on the title bar of the “Download
List” in the Setup window).
Note, that no certificate settings will appear unless the selected file contains an injected certificate
settings file (which is injected as part of the release procedure).
Version x.x.3.38
SMS00954652 " DLL Trace crashes on some PC's " . Changed “trace on” indicator to red to increase
readability. Added injected program and serial driver versions into DLL trace.
Version x.x.3.37
SMS00897775 Download DLL: automated release test
SMS00932195 Start-up mode support with NVM
Various graphical glitches have been corrected, and loading of many files has been speeded up.
“Remove All” option on right-click menu on file list, and added shortcut to add new files (Ctrl+O).
Version x.x.3.35
SMS00903003: " [DRV/FlashTool_E2]When setting " Auto Start(DSR/USB detection) " , we cannot
download SW via UART " (Remove the not working auto start when a COM port is selected).
SMS00903004: " [DRV/FlashTool_E2]SPK file name erase after the settings menu was displayed. "
(added a check if the settings really are changed before removing the SPK file name).
This release should also fix the issues with the progress bar in Binary Mode, but this is not verified.
Version x.x.3.33
SMS00893203: SMS00879804 needs a zip file to be injected in all downloadable files
(fixed instability when the injected “.ini” files are loaded).
Version x.x.3.32
SMS00879804: Disable option for setting test mode in FlashTool (EEPROM)
SMS00879966: XMM6180 Modem Express Card Software Reset for triggering flash procedure
Version x.x.3.29
SMS00847521: " Need to remove Lint warnings... " . We cannot currently run Lint on the GUI source
code, but it is compiler warning free.
As requested:
1) It no longer requires 7-zip installed to zip and unzip files (built-in zip used).
2) When downloading to one channel only, the progress is show in the taskbar, and taskbar flashes
when download is done to indicate that user interaction is required (if program is not active or
minimized).
3) The download window will minimize the whole application and not just the download form.
Version x.x.3.24
Fixed: SMS00846054: [Download Tool Chain] Support for injected zip files. See help file for details
on how to inject files an use this feature.
Version x.x.3.23
By customer request: Added help text on errors in the download window that gives more details on
what the error is and what to do about it.
Version x.x.3.22
Fixes the following UTP’s:
SMS00764778:
SMS00764792:
SMS00804534:
SMS00775159:
SMS00707604:
" Secure mode target unfinished download - show appropriate warning "
" OMSI auto detect of download file expected by secure mode target "
" UNC naming not supported in 4.30.3.21 "
" Complete progress indication during download needed "
" Analysis and design of OMSI module for Pathfinder "
Version x.x.3.21
Complete progress indication during download needed. Error when used with large channel numbers is
fixed.
Version x.x.3.20
Complete progress indication during download needed. There are now two progress bars: a large one
for total progress and a smaller one for partial progress.
Version x.x.3.19
Added an easy Trace start/stop button that also makes it easy to send or view traces.
Added TraceViewer.exe to the install package, so customers can view traces without having to send
them to use first (still beta).
Updated help file and made sure that context sensitive help is shown in the program.
Removed the not working NAND erase tab (SMS00767906).
Version x.x.3.18
Added a setup setting to force marking of a memory class in the download list. This can be used to
ensure that no one is able to unmark important files that need to be downloaded always (if present).
Version x.x.3.17
Added extra baud rates (see help file for documentation on the command line to enable these options).
Update Help File with how to trace and the new extended command line.
Remove automatic selection of added file elements that are repeated, e.g. if there are two cust packs,
then none of them are selected, so the user is made aware that only one of them should be selected.
This does not apply to FLS and EEP files, since they are allowed.
Fixed problem with “index out of bound” when deleting items in the download list.
Added filter for downloading files with extension “.all”.
Fixed multiple highlights on text fields at one time (to avoid confusion of what has focus).
Version x.x.3.15
Update Help File with installation issues and new features.
Support for extra erase modes added (a drop down list is added instead of some of the checkboxes)
Added better support for USB downloads when using auto start (requires the corresponding DLL to
work), that should make it much more reliable.
Added parameters two extra parameters (IFWD_DL_dll_parameter_skip_wr_prak_crc,
IFWD_DL_dll_parameter_check_sign_hw_cfg_value) to settings.
Added warning button in case NAND partitions are specified as preserved during download (since this
feature would otherwise be hidden and could get surprises if users forgot it was setup to preserve
partitions)
Added a Trace button to setup/download that (if enabled in settings) will give the user an easy way of
starting/stopping trace.
Added ballon hints on setup window to help the understanding of how to add files to the download.
Version x.x.3.14
Added much more user friendly way of specifying NAND partitions.
Added an easy way to upload data before proceeding with the downloads (this requires customer
specific changes to the source code: 1) Add the define ALLOW_VERIFY to the project. 2) Correct the
dummy function " CustomVerify() " in the bottom of " download.cpp " to suit your needs. 3) Change the
defines " VERIFY_BEFORE_DL_START " and " VERIFY_BEFORE_DL_LENGTH " to suit your
needs in Info.h.
Version x.x.3.13
Fixed problem with NAND binary mode download where nothing was downloaded. The next version
will include a much more user friendly way of selecting partitions.
Version x.x.3.12
Improved Binary Mode partition inclusion/exclusion MMI.
Fixed minor bug on the binary mode panel when a “skin” was applied.
Help file updated.
Version x.x.3.11
•
Added a setting (‘File’- & gt; ’Settings’- & gt; ’Auto start’- & gt; ’Restart Hold-off’) added to provide variable
hold-off time from download is finished to a new phone connection will be detected during
USB Auto boot.
Version x.x.3.10
•
Further fixes for USB auto start.
Version x.x.3.9
•
•
•
Further fixes for USB auto start.
Show the Prolific USB-COM port driver version in the About box.
Check the USB driver version and give warning if its too old.
Version x.x.3.8
•
•
•
•
Made USB auto start much more reliable.
Added flashing warning: “Erases Calibration”, when “Erase Whole Flash” is checked to warn
user, and made sure that erase is default off (but last settings will naturally be remembered).
File Sort order in list is now more like the order it is downloaded in.
Added “Remove All” button to quickly empty the download list
Version x.x.3.7
•
Minor cosmetic changes.
Version x.x.3.6
•
•
Removed red EEPROM text warning about erasing calibration data.
Fixed minor problem: It will not complain about invalid NOR settings in binary mode, when
NAND is selected.
Version x.x.3.5
•
•
•
•
•
•
Ported to new version numbering system (MMI uses the last two digits, the DLL uses the first
two). This gives one 4 digit version number that both describes the DLL and MMI.
Added NAND/NOR option in binary mode to make sure that only the features supported are
shown.
Added NAND option to erase not only the whole logical FLASH, but also blocks marked as
bad (low level format of FLASH). This should not normally be used.
Added “Copy” button to copy version number in about box.
Removed annoying text highlights of all text fields on startup.
Updated Help file.
Version 3.3
•
•
•
Added possibility to select and add multiple files at once in the “Browse” for files dialog.
Fixed bug where the binary mode project was always set as “external file” regardless of what
was selected.
Updated help file
Version 3.01
•
•
The setup screen is completely re-done to support ‘Multi TOC’ files.
Otherwise the functions are equal to release 2.16
Version 2.16
•
The option to erase the whole flash before download is now also valid when downloading FLS
files to NOR system. So the text “NAND only” is removed.
Version 2.15
•
Fixed error preventing the selection of option “Conditional erase of dynamic eeprom”.
Version 2.14
•
•
•
•
Added better Prolific driver version number warnings (Windows XP and Windows 2000 have
different recommended versions).
Opening/closing of COM ports will now display information given from the Download.dll.
Removed duplicated COM ports in the drop down list of detected COM ports.
Prepared the MMI for handling Protocol checksum change, but it is not fully supported yet.
Version 2.13
•
•
Fixed path problem when browsing for files in the NAND section of the setup form.
Added option to skip COM port descriptions, since this caused delays on PC’s with many COM
ports.
Version 2.12
•
Added new project headers (used in binary mode)
•
Output Control in settings now includes a " OnCOMPortopen " event to control outputs right
after the COM port is opened. This enables the DSR auto start detection to work better on
phones that require e.g. DTR to go high to power it on.
•
Settings now include an”auto log” function to log all text from download logs into separate files
for each channel with timestamps. If less detailed log text is wanted then turn off “Detailed
Log” if not already.
•
Added support for both EEPROM download and update in one download sequence (at not just
one of them)
•
Added option to do EEPROM update after Add-Ons are downloaded (if any).
•
Added Read-only mode to options, that will only allow user to see what is downloaded, but is
unable to change it (until the option is turned off). This is useful in the production.
•
Bug Fix: FlashTool_E2 no longer always resets when using COM ports (it now respects the
user settings).
•
Bug Fix: The MMI now supports the “Force Pre-erase of written areas” option.
•
Removed invalid hints in settings when hovering over controls.
Version 2.11
Option " Force pre-erase of written area " was disabled by mistake. It’s enabled again.
Version 2.10
- When downloading via USB with auto-start, the log is no longer clear automatically if an error
occurred less then 300ms before disconnect. This prevents errors from being cleared in case of lowbattery.
- The file used to boot with is now chosen in the same order as the files are listed in the setup window,
so there is no longer any doubt which files EBL is injected.
Version 2.7
- The download log and progress bar is cleared when the USB cable is disconnected when using auto
start.
- The COM port used is now stored even if USB is used (it previously stored COM1).
- Multi screen users: the about box position is changed to main screen center.
Version 2.6
- Added file checksum in download window for all files (in bottom status window).
- Added Prolific driver version check at startup to warn people using an driver version different for the
recommended one.
- Made maximum allowed download panel size bigger to allow more text to fit in each channel panel
(if possible given the number of channels used).
- Updated help file to describe the problem with some Prolific driver versions for the PL-2303X chip.
Version 2.5
- Added file checksum in file hints (hover mouse over a file to see).
- Added option to get more detailed information from target in case of errors.
- Added option to verify FLASH erase.
- Fixed problem with the “…” browse buttons where they displayed the last filename selected (e.g. a fls
filename could be displayed in the EEP field if the FLS file was browsed for last).
- Updated help file.
Note: the DLL interface has been expanded with one function so the GUI can get the checksum. This
means that the .exe can’t be used with older DLL’s (since they don’t have that function).
Version 2.4
- Added panels for downloading NAND boot system and DSP files.
- Updated help file.
Version 2.2
- Added two settings: " pre-erase FLASH before writing " , and " Check file size " (will prevent
potential phone locks ups if e.g. a 64MB fls file is attempted to be downloaded into a 32MB phone).
- Added help short cuts for each tab in settings (on the F1 key).
- Fixed screen flickering problems, specially on Windows XP.
- Rearranged settings tabs
- Updated help file
Version 2.1
- Added " Tools " panel with " whole chip erase " option.
- Added word wrap in download window details, so filenames are not truncated in screenshots
- Added OS version in Error Report information, and cleaned the text up so not unsupported characters
appear when pasted into a text editor.
- Fixed minor problem with double titles when running on XP when enabling and disabling binary
mode
Version 2.0
Added support for NAND disk files (.dfat files).
Ported application to the BDS 2006 compiler (from BCB 6.0).
Added .NET look and feel on XP machines.
Added Pink skin
Moved version display from form caption to bottom.
Version 1.12
Fixed “Default” button in settings, so it changes the values correctly.
Version 1.11
Changed default values for transmission timeout from 6s to 12s, and made RTS 1 by default (these
changes will not appear unless the .ini file is erased). Made is impossible to press the “Start” button
after download has completed and while target is being reset (this could result in unwanted behavior).
Added version information to title bar of the main windows.
Version 1.10
Fixed problem with file date when uploading files (Borland showed a confusing pop up when trying to
get the file date of a none existing file).
Version 1.9
It is now possible to select Static and dynamic parts of the File System Files separately.
Version 1.8
Added version information in download window title.
Made previous status bar color (red/green) remain from previous downloades when using auto click
start without time out (will be erased on next boot syncronication).
Version 1.7
Removed unused button “Make Error Report” (functionality is available on right-click in log window).
Version 1.6
Added hint on most filename fields that show file date and size. Added file date of downloaded files in
the download window overview. The newest file on disk will always be used, regardless of what is
written in the overview (it is possible to update the file in between downloads while the program is still
running). Changed version numbers to only two digits.
Version 1.5.6
1) Extra project added in binary mode, so there is support for S-Gold2 512 and 1024 Mbit.
2) Avoided calling " IFWD_DL_set_get_control_signal() " when using USB ports.
3) Fixed minor bug in COM ports drop down when using arrow keys.
Known problems: There are rare occasions where the COM port " hangs " , i.e. the program must be
closed before the port can be used again. This will be investigated.
Version 1.5.5
Fixed “Index Out of Bounds” error that could occur after having used the USB Wizard and downloaded
to multiple channels.
Added a standalone command line tool: IFX_DL.exe., that is intended for batch file downloads. See
FlashTool_E2.chm help file for details (Command Line chapter).
Added an debug feature to better test COM port issues in settings (for internal use).
Version 1.5.4
Fixed problem with logs being erased doing multi channel download with Auto Start with no time out.
Added check that one does not try to used the Auto Start intended for COM ports while using USB
ports.
Version 1.5.3
Added an auto start mode for COM ports that does not require any external hardware to any key
presses in the program to get a phone to boot and download. An “Auto Start” tab has been added in
settings to control this.
Version 1.5.1
1) Fixed problem with opening USB ports again after a completed download.
2) Added boot and communication timeout to program settings to allow users to increase timeout
in case of problems (should not occur, but now it can be circumvented without having to wait
for a new release).
3) Better target reset handling added (waits until it gets a callback before closing the com port).
Version 1.5.0
Added a USB Map wizard that takes care of mapping physical USB ports to channel numbers in the
same way each time during an automatic multi channel USB Infineon download.
Made normal (as apposed to auto boot) USB Infineon downloads work multiple times without needing
to close the download window in between downloads.
Added an auto boot detection during USB Infineon download that uses the USB mapping defined in the
USB Wizard.
Added options to control how download is done:
1) Skip Empty Blocks (faster download)
2) Faster CRC Method (faster download)
3) Multi Channel Low CPU Usage (less CPU usage on multi channel download)
Leave all options checked unless you are experiencing download problems.
Version 1.4.3
The COM port drop down list now provides details about the COM ports, so that it should no longer be
a need to go to Device Manager to see which COM port is what.
Version 1.4.0
•
Added new concept for changing communication driver – it is now a drop down list in the
communication setup panel.
•
Removed many nagging prompts like. “Are you sure?” on exit, since no data will be lost if user
accidentally exits the program (and the program will quickly launch again).
•
Changed default behavior in case the .INI is missing (it will now show communication settings
on startup as default, since this is the first thing one wants to check on startup).
•
Moved the “Settings” menu item to the “File” menu.
Version 1.3.14
Added .flb support to FLS download. Added better USB handling: It is now decided in settings how
USB is handled (Edit & gt; Settings & gt; USB Handling). Currently there are two options: “Infineon driver”
and a list of customer specific drivers. Please select “Infineon driver” unless otherwise specified. The
USB setting will only have an effect if “Native USB Port” is checked.
Version 1.3.13
Removed valid com port caching, so newly available ports are detected without needing to restart the
program.
Version 1.3.12
Fixed program freeze on auto boot mode that could occur if polling port status took too long.
Version 1.3.11
Support for automatic download start is added.
Version 1.3.10
Errors in the handling of static EEPROM update are fixed.
Version 1.3.9
Support for static EEPROM update is added.
Version 1.3.8
Fixed bug were the Comport would sometimes be cleared on program start -Added the option to return
to setup windows when the download window was closed (old Flash tool behaviour).
Added AT-mode test interface (only needed for test purposes).
Some users were experiences difficulties when the " Skip unused ports " was activated. This feature has
been deactivated until the cause can be found.
Older versions
For the versions before version 1.3.8 there have not been any release notes.
FT2232C USB Serial Port Driver Release Notes
Contents
Introduction
Release Contents
Further Information
Revision History
Introduction
This zip archive contains drivers and associated documentation to
support FTDI's FT2232C Dual USB UART/FIFO.
Release Contents
Windows 98 and Windows ME
The following files are provided as a standard release.
FTCSER98.SYS - serial port driver
FTCSENUM.SYS - serial port enumerator
FTCCOMMS.VXD - port driver
FTCSENUM.VXP - port enumerator
FTCSMOU.VXD - serial mouse driver
FTCSUI.DLL - serial port user interface
FTCUSB.INF - USB driver installation file
FTCSER.INF - serial port driver installation file
FTCSMOU.INF - serial mouse driver installation file
FTCUNIN.EXE - uninstaller
FTCUN98.INI - uninstaller information file
Windows 2000 and Windows XP
The following files are provided as a standard release.
FTCUSB.SYS - USB driver
FTCSER2K.SYS - serial port driver
FTCSUI2.DLL - serial port user interface
FTCSERCO.DLL - serial port coinstaller
FTCUSB.INF - USB driver installation file
FTCSER.INF - serial port driver installation file
FTCUNIN.EXE - uninstaller
FTCUN2K.INI - uninstaller information file
Further Information
Further information about FTDI's products as well as updates of drivers
can be obtained from FTDI's web site at URL http://www.ftdichip.com
We recommend that customers join the FTDI Newsletter. The FTDI
NewsLetter is an e-mail based service which allows you to receive the
latest FTDI related news, product releases, and current driver version
information. To join the FTDI NewsLetter, go to our web site
http://www.ftdichip.com and click on the " FTDI NewsLetter " button on the
LHS navigation panel.
For technical support on our products and drivers, please e-mail
support@ftdichip.com
For sales enquiries please e-mail sales@ftdichip.com
For general enquiries please e-mail admin@ftdichip.com
Revision History
Windows 98 and Windows ME
1.00.00 March 12, 2004
First Release.
Windows 2000 and Windows XP
1.00.03 May 5, 2004
Added coinstaller.
1.00.00 March 12, 2004
First Release.
Prolific Driver Problems
------------------------
Using the Prolific " USB-to-Serial Comm Port " driver from http://www.prolific.tw/ for
the PL-2303X chip can give stability problems (blue screen of death or reboots).
If you are experiencing those kinds of problems, then try a different driver version.
If you already have a driver installed, then run " DRemover98ME2KXP.exe " to remove the
old driver. After a reboot, you can run the installer for another driver version.
Version 2.0.2.1 should work for both Windows XP and 2000. Windows XP run well with
version 2.0.0.26 (on most systems).
Version 2.0.2.8 has not been tested at Infineon, but it is currently the newest
version available.
Future Technology Devices
International Ltd.
Windows 98 Installation Guide
© Future Technology Devices International Ltd. 2005
I
Windows 98 Installation Guide
Table of Contents
Part I Welcome to the Windows 98 Installation Guide
2
Part II Installing FT232BM, FT245BM, FT8U232AM and
FT8U245AM Devices
3
1 Installing D2XX Drivers
................................................................................................................................... 4
2 Installing VCP Drivers
................................................................................................................................... 8
13
Part III Installing FT2232C Devices
1 Installing D2XX Drivers
................................................................................................................................... 14
2 Installing VCP Drivers
................................................................................................................................... 21
Part IV Uninstalling FT232BM, FT245BM, FT8U232AM and
FT8U245AM Devices
31
1 Uninstalling D2XX Drivers
................................................................................................................................... 32
2 Uninstalling VCP Drivers
................................................................................................................................... 34
36
Part V Uninstalling FT2232C Devices
1 Uninstalling D2XX Drivers
................................................................................................................................... 37
2 Uninstalling VCP Drivers
................................................................................................................................... 39
41
Part VI Troubleshooting
1 Windows 98 cannot find drivers for my device
................................................................................................................................... 41
2 Windows 98 forces a reboot after installing a device
................................................................................................................................... 42
3 Driver installation fails and Windows 98 gives error code 10
................................................................................................................................... 43
4 FT232BM or FT245BM device hangs randomly during operation under Windows
98
................................................................................................................................... 44
5 Windows 98 complains about missing .CAT files
................................................................................................................................... 45
6 Windows 98 complains about missing ftccomms.vxd file
................................................................................................................................... 46
7 Windows 98 installs FT2232C device as VCP even though D2XX drivers are
selected ................................................................................................................................... 47
in the EEPROM
48
Part VII Revision History
49
Index
© Future Technology Devices International Ltd. 2005
Welcome to the Windows 98 Installation Guide
1
2
Welcome to the Windows 98 Installation Guide
The purpose of this document is to provide users of FTDI chips with a simple procedure for
installing drivers for their devices under Windows 98. The procedure is also applicable to Windows
ME.
Please note that if Windows 98 Gold Edition is being used, you must have all the latest patches
from the Microsoft website installed for the system to be USB compatible.
© Future Technology Devices International Ltd. 2005
3
2
Windows 98 Installation Guide
Installing FT232BM, FT245BM, FT8U232AM and
FT8U245AM Devices
FTDI's 1st and 2nd generation of USB UART and USB FIFO chips can be installed with one of two
sets of drivers.
The first driver type is the D2XX direct driver. This provides direct access to the device via a
dynamic link library (DLL) supplied with the driver. Applications can then be written which use the
functions available in the DLL to directly control the device.
The second driver type is the virtual COM port (VCP) driver. The VCP drivers emulate a standard
PC COM port. These can be communicated with in the same manner as any other COM port on
the PC.
Under Windows 98 and ME, the Found New Hardware Wizard should be used to install devices
when they are connected to the PC for the first time as this is the recommended procedure for
reliable device operation.
© Future Technology Devices International Ltd. 2005
Installing FT232BM, FT245BM, FT8U232AM and FT8U245AM Devices
2.1
4
Installing D2XX Drivers
To install D2XX drivers for an FT232BM, FT245BM, FT8U232AM or FT8U245AM device under
Windows 98, follow the instructions below:
· If a device of the same type has been installed on your machine before and the drivers that are
about to be installed are different from those installed already, the original drivers need to be
uninstalled. Please refer to the
Uninstalling FT232BM, FT245BM, FT8U232AM and FT8U245AM 32 Devices section of this
document for further details of this procedure.
· Download the latest available D2XX drivers from the FTDI website and unzip them to a location
on your PC.
· Connect the device to a spare USB port on your PC. This will launch the Windows Add New
Hardware Wizard. Windows may display a message reading " Building driver database " at this
point which may take a few minutes to pass. Click " Next " to proceed with the installation.
· Select " Search for the best driver for your device. (Recommended). " as shown below and then
click " Next " .
© Future Technology Devices International Ltd. 2005
5
Windows 98 Installation Guide
· Check the box next to " Specify a location " and uncheck all others as shown below. Click
" Browse " and locate the driver files. Once the files have been located, click " Next " to proceed
with the installation.
· Windows may display a message reading " Building driver database " at this point which may take
a few minutes to pass. Once Windows has found the required files, click " Next " to install the
device.
© Future Technology Devices International Ltd. 2005
Installing FT232BM, FT245BM, FT8U232AM and FT8U245AM Devices
6
· Windows should then display a message indicating that the installation was successful. Click
" Finish " to complete the installation. The device is now ready for use.
· Open the Device Manager (located in " Control Panel\System " then select the " " Device Manger "
tab) and select " View devices by type " . The device appears as a FT8U2XX Device connected to
a USB port.
© Future Technology Devices International Ltd. 2005
7
Windows 98 Installation Guide
© Future Technology Devices International Ltd. 2005
Installing FT232BM, FT245BM, FT8U232AM and FT8U245AM Devices
2.2
8
Installing VCP Drivers
To install VCP drivers for an FT232BM, FT245BM, FT8U232AM or FT8U245AM device under
Windows 98, follow the instructions below:
· If a device of the same type has been installed on your machine before and the drivers that are
about to be installed are different from those installed already, the original drivers need to be
uninstalled. Please refer to the
Uninstalling FT232BM, FT245BM, FT8U232AM and FT8U245AM 34 Devices section of this
document for further details of this procedure.
· Download the latest available VCP drivers from the FTDI website and unzip them to a location
on your PC.
· Connect the device to a spare USB port on your PC. This will launch the Windows Add New
Hardware Wizard. Windows may display a message reading " Building driver database " at this
point which may take a few minutes to pass. Click " Next " to proceed with the installation.
· Select " Search for the best driver for your device. (Recommended). " as shown below and then
click " Next " .
© Future Technology Devices International Ltd. 2005
9
Windows 98 Installation Guide
· Check the box next to " Specify a location " and uncheck all others as shown below. Click
" Browse " and locate the driver files. Once the files have been located, click " Next " to proceed
with the installation.
· Windows may display a message reading " Building driver database " at this point which may take
a few minutes to pass. Once Windows has found the required files, click " Next " to install the
device.
© Future Technology Devices International Ltd. 2005
Installing FT232BM, FT245BM, FT8U232AM and FT8U245AM Devices
10
· If the driver being installed does not have Microsoft WHQL signature files (.CAT files), the wizard
will request a driver disk to attempt to find them. Click " OK " on the " Insert Disk " message box.
The following window will appear to assist in locating the file. To proceed with the installation
without the .CAT file, click " Skip File " .
If the driver being installed is Microsoft WHQL certified, then the .CAT files will be located with
the other driver files and should be installed automatically.
© Future Technology Devices International Ltd. 2005
11
Windows 98 Installation Guide
· Windows should then display a message indicating that the installation of the serial converter
driver was successful. The COM port emulation driver must now be installed. Click " Finish " to
complete the installation of the serial converter and proceed to the COM port emulation driver.
· Under Windows 98, the COM port emulation driver will be automatically installed from the same
location as the serial converter driver. However, if the driver is not WHQL certified as explained
above for the serial converter driver, the wizard will ask for the location of .CAT files. Click " OK "
on the " Insert Disk " message box.
The following window will appear to assist in locating the file. To proceed with the installation
without the .CAT file, click " Skip File " .
© Future Technology Devices International Ltd. 2005
Installing FT232BM, FT245BM, FT8U232AM and FT8U245AM Devices
12
If the driver being installed is Microsoft WHQL certified, then the .CAT files will be located with
the other driver files and should be installed automatically.
· Open the Device Manager (located in " Control Panel\System " then select the " " Device Manger "
tab) and select " View devices by type " . The device appears as an additional COM port with the
label " USB Serial Port " .
© Future Technology Devices International Ltd. 2005
13
3
Windows 98 Installation Guide
Installing FT2232C Devices
FTDI's 3rd generation chip, the FT2232C, is a composite device with two ports that can be
configured to behave as a USB UART or a USB FIFO interface by configuring an external
EEPROM. In addition, the FT2232C EEPROM determines which drivers the device will use.
The EEPROM is read on power-up and will configure the chip accordingly before the device is
enumerated. If no EEPROM is fitted, the device will default to both channels configured as USB to
UART interfaces using VCP drivers.
Under Windows 98 and ME, the Found New Hardware Wizard should be used to install devices
when they are connected to the PC for the first time as this is the recommended procedure for
reliable device operation.
© Future Technology Devices International Ltd. 2005
Installing FT2232C Devices
3.1
14
Installing D2XX Drivers
To install D2XX drivers for an FT2232C device under Windows 98, follow the instructions below:
· If a device of the same type has been installed on your machine before and the drivers that are
about to be installed are different from those installed already, the original drivers need to be
uninstalled. Please refer to the Uninstalling FT2232C Devices 37 section of this document for
further details of this procedure.
· Download the latest available FTCD2XX drivers from the FTDI website and unzip them to a
location on your PC. Please note that attempting to install the FTC combined D2XX and VCP
driver will result in an unsuccessful installation if the device EEPROM is configured for D2XX
drivers.
· Connect the device to a spare USB port on your PC. As the FT2232C is a composite device, the
Microsoft composite device driver must be loaded first. This is not done automatically under
Windows 98. The Windows Add New Hardware Wizard will detect the new USB device as a
composite device and will guide the user through the installation. Click " Next " on the screen
below to continue with the installation.
· Select " Search for the best driver for your device. (Recommended). " as shown below and then
click " Next " .
© Future Technology Devices International Ltd. 2005
15
Windows 98 Installation Guide
· Check the box next to " Specify a location " and uncheck all others as shown below. Normally,
Windows will find the composite driver already available in the system. If the composite driver is
not available on the PC, the " Microsoft Windows Update " option may be selected and a
composite driver will be downloaded from the Microsoft Windows update website.
· Windows will display a message indicating that a composite driver file has been found. In the
case below, Windows has found a newer version of the composite driver already installed. It is
safe to install this. Continue by clicking " Next " .
© Future Technology Devices International Ltd. 2005
Installing FT2232C Devices
16
· To install the composite driver click " Next " .
· Windows should then display a message indicating that the composite driver installation was
successful. Click " Finish " to complete the composite driver installation.
© Future Technology Devices International Ltd. 2005
17
Windows 98 Installation Guide
· Once the composite driver is installed, the Add New Hardware Wizard will then detect a port of
the FT2232C device. Windows may display a message reading " Building driver database " at this
point which may take a few minutes to pass. Click " Next " when the screen below is shown.
· Select " Search for the best driver for your device. (Recommended). " as shown below and then
click " Next " .
© Future Technology Devices International Ltd. 2005
Installing FT2232C Devices
18
· Check the box next to " Specify a location " and uncheck all others as shown below. Click
" Browse " and locate the driver files. Once the files have been located, click " Next " to proceed
with the installation.
· Windows may display a message reading " Building driver database " at this point which may take
a few minutes to pass. Once Windows has found the required files, click " Next " to install the
device.
© Future Technology Devices International Ltd. 2005
19
Windows 98 Installation Guide
· Windows should then display a message indicating that the installation was successful. Click
" Finish " to complete the installation.
· As the FT2232C has 2 ports available, the second port must also be installed. Under Windows
98, this will occur automatically.
· Open the Device Manager (located in " Control Panel\System " then select the " " Device Manger "
tab) and select " View devices by connection " . The device appears as a " USB Composite
Device " connected to a USB port with ports A and B respectively denoted as " FTCUSB.SYS
© Future Technology Devices International Ltd. 2005
Installing FT2232C Devices
FTDI Dual 232A USB Test Board " and " FTCUSB.SYS FTDI Dual 232B USB Test Board " .
© Future Technology Devices International Ltd. 2005
20
21
3.2
Windows 98 Installation Guide
Installing VCP Drivers
To install D2XX drivers for an FT2232C device under Windows 98, follow the instructions below:
· If a device of the same type has been installed on your machine before and the drivers that are
about to be installed are different from those installed already, the original drivers need to be
uninstalled. Please refer to the Uninstalling FT2232C Devices 37 section of this document for
further details of this procedure.
· Download the latest available FTCD2XX drivers from the FTDI website and unzip them to a
location on your PC. Please note that attempting to install the FTC combined D2XX and VCP
driver will result in an unsuccessful installation if the device EEPROM is configured for D2XX
drivers.
· Connect the device to a spare USB port on your PC. As the FT2232C is a composite device, the
Microsoft composite device driver must be loaded first. This is not done automatically under
Windows 98. The Windows Add New Hardware Wizard will detect the new USB device as a
composite device and will guide the user through the installation. Click " Next " on the screen
below to continue with the installation.
· Select " Search for the best driver for your device. (Recommended). " as shown below and then
click " Next " .
© Future Technology Devices International Ltd. 2005
Installing FT2232C Devices
22
· Check the box next to " Specify a location " and uncheck all others as shown below. Normally,
Windows will find the composite driver already available in the system. If the composite driver is
not available on the PC, the " Microsoft Windows Update " option may be selected and a
composite driver will be downloaded from the Microsoft Windows update website.
· Windows will display a message indicating that a composite driver file has been found. In the
case below, Windows has found a newer version of the composite driver already installed. It is
safe to install this. Continue by clicking " Next " .
© Future Technology Devices International Ltd. 2005
23
Windows 98 Installation Guide
· To install the composite driver click " Next " .
· Windows should then display a message indicating that the composite driver installation was
successful. Click " Finish " to complete the composite driver installation.
© Future Technology Devices International Ltd. 2005
Installing FT2232C Devices
24
· Once the composite driver is installed, the Add New Hardware Wizard will then detect a port of
the FT2232C device. Windows may display a message reading " Building driver database " at this
point which may take a few minutes to pass. Click " Next " when the screen below is shown.
· Select " Search for the best driver for your device. (Recommended). " as shown below and then
click " Next " .
© Future Technology Devices International Ltd. 2005
25
Windows 98 Installation Guide
· Check the box next to " Specify a location " and uncheck all others as shown below. Click
" Browse " and locate the driver files. Once the files have been located, click " Next " to proceed
with the installation.
· Windows may display a message reading " Building driver database " at this point which may take
a few minutes to pass. Once Windows has found the required files, click " Next " to install the
device.
© Future Technology Devices International Ltd. 2005
Installing FT2232C Devices
26
· If the driver being installed does not have Microsoft WHQL signature files (.CAT files), the wizard
will request a driver disk to attempt to find them. Click " OK " on the " Insert Disk " message box.
The following window will appear to assist in locating the file. To proceed with the installation
without the .CAT file, click " Skip File " .
If the driver being installed is Microsoft WHQL certified, then the .CAT files will be located with
the other driver files and should be installed automatically.
© Future Technology Devices International Ltd. 2005
27
Windows 98 Installation Guide
· Windows should then display a message indicating that the installation of the serial converter
driver was successful. The COM port emulation driver must now be installed. Click " Finish " to
complete the installation of the serial converter driver for the first port of the FT2232C device.
· As the FT2232C device has two ports available, the serial converter driver must also be installed
for the second port. This occurs automatically in Windows 98 with the exception of the .cat file
warnings. As above, click " OK " on the " Insert Disk " message box.
To continue with the installation, click " Skip File " .
© Future Technology Devices International Ltd. 2005
Installing FT2232C Devices
28
This will complete the installation of the serial converter driver for the second port of the
FT2232C device.
· Once the serial converter drivers are installed, the Add New Hardware Wizard will detect the
USB serial ports and will automatically find the drivers for these in the same location as the serial
converter drivers. As before, the wizard will prompt for the .cat files if they cannot be found.
Click " OK " on the " Insert Disk " dialog box to proceed.
Click " Skip File " to continue with the installation.
This will complete the installation of the COM port emulation driver for the first port of the
FT2232C device.
· As with the serial converter driver above, the wizard will detect the second port and install the
COM port emulation driver automatically. Click " OK " on the " Insert Disk " dialog box to proceed.
© Future Technology Devices International Ltd. 2005
29
Windows 98 Installation Guide
Click " Skip File " to continue with the installation.
· This will complete the installation of the FT2232C device. The device is now ready to use.
· Open the Device Manager (located in " Control Panel\System " then select the " " Device Manger "
tab) and select " View devices by connection " . The device appears as 2 additional COM ports
with the labels " USB Serial Port " . Please note that there is no co-installer available for Windows
98 so port B of the FT2232C may have a lower COM port number assigned than that assigned to
port A as in the screen shot below.
© Future Technology Devices International Ltd. 2005
Installing FT2232C Devices
© Future Technology Devices International Ltd. 2005
30
31
4
Windows 98 Installation Guide
Uninstalling FT232BM, FT245BM, FT8U232AM and
FT8U245AM Devices
When uninstalling devices from Windows 98, it should always be done through the Add/Remove
Programs utility as this uses the FTDI driver uninstaller program to remove files and registry entries
to leave a clean system. Other methods may leave fragments of the driver that may interfere with
future installations.
© Future Technology Devices International Ltd. 2005
Uninstalling FT232BM, FT245BM, FT8U232AM and FT8U245AM Devices
4.1
32
Uninstalling D2XX Drivers
To uninstall D2XX drivers for FT232BM, FT245BM, FT8U232AM and FT8U245AM devices, follow
the instructions below:
· Disconnect any FTDI devices that are attached to the PC.
· Open the Add/Remove Programs utility located in " Control Panel\Add/Remove Programs " .
Select " FTDI FTD2XX USB Drivers " from the list of installed programs.
· Click the " Add/Remove " button. This will run the FTDI uninstaller program. Click " Continue " to
run the uninstaller or " Cancel " to exit.
© Future Technology Devices International Ltd. 2005
33
Windows 98 Installation Guide
· When the uninstaller has finished removing the device from the system, the caption on the
" Cancel " button will change to " Finish " . Click " Finish " to complete the process.
© Future Technology Devices International Ltd. 2005
Uninstalling FT232BM, FT245BM, FT8U232AM and FT8U245AM Devices
4.2
34
Uninstalling VCP Drivers
To uninstall VCP drivers for FT232BM, FT245BM, FT8U232AM and FT8U245AM devices, follow
the instructions below:
· Disconnect any FTDI devices that are attached to the PC.
· Open the Add/Remove Programs utility located in " Control Panel\Add/Remove Programs " .
Select " FTDI USB-Serial Converter Drivers " from the list of installed programs.
· Click the " Add/Remove " button. This will run the FTDI uninstaller program. Click " Continue " to
run the uninstaller or " Cancel " to exit.
© Future Technology Devices International Ltd. 2005
35
Windows 98 Installation Guide
· When the uninstaller has finished removing the device from the system, the caption on the
" Cancel " button will change to " Finish " . Click " Finish " to complete the process.
© Future Technology Devices International Ltd. 2005
Uninstalling FT2232C Devices
5
36
Uninstalling FT2232C Devices
When uninstalling devices from Windows 98, it should always be done through the Add/Remove
Programs utility as this uses the FTDI driver uninstaller program to remove files and registry entries
to leave a clean system. Other methods may leave fragments of the driver that may interfere with
future installations.
© Future Technology Devices International Ltd. 2005
37
5.1
Windows 98 Installation Guide
Uninstalling D2XX Drivers
To uninstall D2XX drivers for FT2232C devices, follow the instructions below:
· Disconnect any FTDI devices that are attached to the PC.
· Open the Add/Remove Programs utility located in " Control Panel\Add/Remove Programs " .
Select " FTDI FT2232C Direct Driver " from the list of installed programs.
· Click the " Change/Remove " button. This will run the FTDI uninstaller program. Click " Continue "
to run the uninstaller or " Cancel " to exit.
© Future Technology Devices International Ltd. 2005
Uninstalling FT2232C Devices
· When the uninstaller has finished removing the device from the system, the caption on the
" Cancel " button will change to " Finish " . Click " Finish " to complete the process.
© Future Technology Devices International Ltd. 2005
38
39
5.2
Windows 98 Installation Guide
Uninstalling VCP Drivers
To uninstall VCP drivers for FT2232C devices, follow the instructions below:
· Disconnect any FTDI devices that are attached to the PC.
· Open the Add/Remove Programs utility located in " Control Panel\Add/Remove Programs " .
Select " FTDI FT2232C USB Drivers " from the list of installed programs.
· Click the " Change/Remove " button. This will run the FTDI uninstaller program. Click " Continue "
to run the uninstaller or " Cancel " to exit.
© Future Technology Devices International Ltd. 2005
Uninstalling FT2232C Devices
· When the uninstaller has finished removing the device from the system, the caption on the
" Cancel " button will change to " Finish " . Click " Finish " to complete the process.
© Future Technology Devices International Ltd. 2005
40
41
Windows 98 Installation Guide
6
Troubleshooting
6.1
Windows 98 cannot find drivers for my device
This error can occur if the VID and PID programmed into the device EEPROM do not match those
listed in the INF files for the driver. The VID and PID programmed into the device EEPROM may
be found by using the USBView utility from the FTDI website. These can then be checked against
the VID and PID entries in the driver INF files. If they do not match, that driver cannot be installed
for that device without either re-programming the device EEPROM or modifying the list of VID and
PID numbers in the INF files.
Please note that only your own company VID and PID or FTDI's VID (0x0403) and FTDI PID issued
for use by your company should be used in the EEPROM and INF/INI files.
© Future Technology Devices International Ltd. 2005
Troubleshooting
6.2
42
Windows 98 forces a reboot after installing a device
This problem can occur if an application is accessing a file while the New Hardware Wizard is
trying to copy it. This usually occurs with the FTD2XX.DLL file. If installing a D2XX device,
selecting not to restart the computer then unplugging and re-plugging the device may allow the
device to function properly without restarting. Restarting the machine will allow the device to work
correctly.
© Future Technology Devices International Ltd. 2005
43
6.3
Windows 98 Installation Guide
Driver installation fails and Windows 98 gives error code 10
Windows error code 10 indicates a hardware error or failed driver installation. This error may
appear if a device has insufficient power to operate correctly (e.g. plugged into a bus powered hub
with other devices), or may indicate a more serious hardware problem. Also, it may be indicative of
USB root hub drivers being incorrectly installed.
Please refer to the example schematics on the FTDI website for standard device configurations. If
the error persists, please contact the FTDI support department.
© Future Technology Devices International Ltd. 2005
Troubleshooting
6.4
44
FT232BM or FT245BM device hangs randomly during operation
under Windows 98
This is not caused by the driver, but is a hardware compatibility problem. Some newer USB 2.0
hubs and host controllers can be susceptible to noise and can cause random device failures. This
can be overcome by fitting 47pF capacitors to ground on the USBDP and USBDM lines on the USB
connector side of the 27W series resistors.
© Future Technology Devices International Ltd. 2005
45
6.5
Windows 98 Installation Guide
Windows 98 complains about missing .CAT files
Files with the .cat extension are signature files issued by Microsoft that indicate a device driver is
WHQL certified. If a driver is not certified, there will be no .cat files available.
When installing drivers in Windows 98 or Windows ME, the user is prompted to locate the .cat files
if the operating system cannot find them. If the driver is not certified but you wish to install it
anyway, the files may be skipped by clicking the " Skip " button.
© Future Technology Devices International Ltd. 2005
Troubleshooting
6.6
46
Windows 98 complains about missing ftccomms.vxd file
This can occur when the USB Composite driver has been installed if the user has not browsed to
the location of the driver files. If this message appears, do not skip it but browse to the driver file
location. The wizard will then be able to correctly install the device.
© Future Technology Devices International Ltd. 2005
47
6.7
Windows 98 Installation Guide
Windows 98 installs FT2232C device as VCP even though D2XX
drivers are selected in the EEPROM
This problem can occur when the device EEPROM is set to use D2XX drivers and the user is
attempting to install using the combined FTC drivers for D2XX and VCP for Windows 2000 and
Windows XP. The combined drivers will only provide VCP functionality under Windows 98 and will
always install an FT2232C device with VCP drivers.
To install a FT2232C device configured to use D2XX drivers under Windows 98, the FTCD2XX
drivers must be used. This driver release will provide D2XX drivers for Windows 98 and will also
install D2XX devices under Windows 2000 and Windows XP.
© Future Technology Devices International Ltd. 2005
Revision History
7
Revision History
Version
Release Date
Comments
1.0
January 2005
Initial release
© Future Technology Devices International Ltd. 2005
48
Windows 98 Installation Guide
49
Index
-DDrivers
4, 8, 14, 21, 41, 42, 43, 44, 45, 46, 47
-FFT2232C 14, 21
FT232BM 4, 8
FT245BM 4, 8
FT8U232AM 4, 8
FT8U245AM 4, 8
-IInstallation 2, 3, 4, 8, 13, 14, 21
Introduction 2
-TTroubleshooting
41, 42, 43, 44, 45, 46, 47
-UUninstall
31, 32, 34, 36, 37, 39
-WWelcome 2
Windows 98 2, 3, 4, 8, 13, 14, 21, 31, 32, 34, 36,
37, 39, 41, 42, 43, 44, 45, 46, 47
Windows ME 2, 3, 4, 8, 13, 14, 21, 31, 32, 34, 36,
37, 39, 41, 42, 43, 44, 45, 46, 47
© Future Technology Devices International Ltd. 2005
FTDI Win 2k Drivers - Revision Comments December 12, 2005
C:WINDOWSDesktopReleasesDriversBeta Release 906 2176 Dec12,20052176
Release Info.doc
FTDI's drivers have been changed to accommodate the support of Windows
98 and Windows 2000 for all three of FTDI's USB controllers from a
single INF file.
New drivers will be posted on the support page of FTDI's web page - in
ZIP format, following the following naming convention - Rxxyy where xx
is the version of the Windows 98 drivers and yy is the version of the
Windows 2000 drivers. The first release of the common INF drivers was
named R0855.zip - which is version 10208 of the Windows 98 drivers and
version 2055 of the Windows 2000 drivers.
There are now six files which are provided as a standard release
FTDIBUS.SYS (two driver files)
FTSER2K.SYS
FTDIUNIN.EXE (uninstaller and associated ini file)
FTDIUN2K.INI
FTDIBUS.INF (two shared INF files for Win98 and Win2k)
FTDIPORT.INF
On making a new release the files will also be posted onto FTDI's web
page http://www.ftdichip.com.
Proceed to the support page to download drivers (select Support tab at
top of screen).
Release versions
1.00.2176 (December 12, 2005)
Fixed installation problem.
WHQL candidate.
1.00.2172 (October 31, 2005)
Support for FT2232C devices.
1.00.2170 (October 27, 2005)
Fixed write request synchronization issue.
1.00.2169 (September 1, 2005)
Fixed flow control issues.
Changed cancel processing to fix blue screen.
1.00.2168 (June 8, 2005)
Fixed lockup condition on port close.
1.00.2166 (May 23, 2005)
Fixed bug in software flow control.
1.00.2163 (February 7, 2005)
Support for buffered writes.
Fixed property page.
1.00.2162 (November 25, 2004)
Tested with HCT 12.0.
1.00.2160 (October 26, 2004)
Added option to prevent modem control signals following legacy port
behaviour at startup.
1.00.2159 (October 15, 2004)
Fixed delay on disconnect under WinXP.
1.00.2157 (September 28, 2004)
Fixed bug that could cause computer to hang during closedown.
1.00.2156 (September 9, 2004)
Fixed bug in baud rate divisor calculation for AM devices.
Location Ids supported is no longer restricted to 10 or less.
Fixed bug that could cause computer to hang on surprise removal.
Fixed bug that caused device handle notification to fail.
1.00.2154 (April 20, 2004)
Fixed initialization problem on WinXP SP1.
Fixed IOCTL_SERIAL_GET_DTRRTS.
1.00.2151 (February 4, 2004)
Fixed problem with signalling events on disconnect with open port.
1.00.2150 (January 19, 2004)
Fixed problem with signalling line status errors.
Fixed problem with Location IDs and external hubs.
1.00.2148 (November 11, 2003)
More fixes for WHQL.
Fixed problem that prevented RXCHAR event being signalled when buffers
were full.
1.00.2146 (October 28, 2003)
Various fixes for WHQL.
Added option for immediate processing of vendor commands.
1.00.2145 (October 20, 2003)
Fixed power-level problem with VCP serializer DLL interface.
1.00.2143 (September 24, 2003)
Fixed problem with RTS control toggle mode.
Fixed problem with device state after suspend/resume.
1.00.2140 (September 11, 2003)
Fixed problem with uninstall from DeviceManager.
Fixed problem with Sandstorm software.
Improved device request processing.
Fixed problem with modem control signal state on open.
Fixed cancel write request problem.
Added reset pipe retry count.
Added maximum devices option.
Added supported locations option.
1.00.2134 (June 16, 2003)
More changes for BusHound.
1.00.2133 (June 12, 2003)
Fixed BusHound compatibility problem.
Updated properties page with serial enumerator option.
1.00.2132 (June 09, 2003)
Bug fixes for substitution mode.
Fixed problem where laptops could not enter standby mode.
Fixed problem with Lexmark printer.
Added " Set RTS on Close " flag.
Updated properties page.
1.00.2126 (April 10, 2003)
Support substitution mode.
Restore device state on return from suspend or hibernate.
Fixed device naming problem.
Fixed bug in purge when receive buffer full.
Fixed bug in properties page.
1.00.2115 (February 25, 2003)
Beta release includes drivers that have passed Microsoft certification
tests.
1.00.2115 (December 20, 2002)
Beta release.
Support force XON/XOFF option.
New properties page.
1.00.2114 (November 1, 2002)
Beta release.
Correctly identifies unserialized FT232BM and FT245BM devices.
Fixed remote wakeup.
1.00.2112 (October 25, 2002)
Beta release.
Support for FT232BM and FT245BM.
Uses location information to enumerate non-serialized devices.
1.00.2104 (July 22, 2002)
Drivers digitally signed.
1.00.2101 (February 1, 2002)
Fixed problem that resulted in some devices not coming out of hibernate.
Fixed divide-by-zero problem zero baud rate.
1.00.2099 (January 7, 2002)
Fixed problem with aliased baud rates.
1.00.2098 (December 20, 2001)
Improved transmit throughput.
Support serial printers through Registry setting.
Support for non-standard baud rates.
Support Transmit Immediate.
Disable modem control signals on port close.
Fixed serial mouse disconnect problem in Standby mode.
Runs under driver verifier.
1.00.2088 (October 30, 2001)
Fixed connect/disconnect problem in Windows XP.
Runs under driver verifier in Windows XP.
1.00.2086 (October 5, 2001)
Fixed write request timeout processing.
Fixed problem with restarting writes after port close.
Fixed no space in read buffer problem.
1.00.2084 (October 2, 2001)
Passes HCT tests (required for Windows XP Logo).
Uses common uninstaller FTDIUNIN.EXE.
Fixed minimum timeout problem.
Fixed write request blue screen.
Fixed write request timeout processing.
Fixed data loss at low baud rates.
1.00.2078 (July 27, 2001)
Fixed support for Logitech mice.
Enhanced write request processing.
1.00.2072 (May 2, 2001)
Runs under Windows XP.
Fixed receive buffer full problem.
1.00.2071 (Apr 26, 2001)
Enhanced BREAK condition processing.
1.00.2069 (Mar 28, 2001)
Fixed hyper-terminal re-boot problem seen when transmitting files at low
baud rates.
1.00.2068 (Mar 23, 2001)
Drop modem status signals on disconnect
1.00.2067 (Feb 26, 2001)
Fixed disconnect with open port problems
Support multiple devices attached at the same time
Fixed hyper-terminal re-boot problem seen when typing characters in
terminal screen
Enabled for surprise removal (removes unexpected removal dialogue box)
1.00.2060 (Jan 19, 2001)
Change to modem status register set up to improve port initialisation
1.00.2058 (Nov 7, 2000)
Fix to changing buffer size under Windows 2000 for FT8U232AM and
FT8U245AM
1.00.2057 (Oct 19, 2000)
Fix to enable speeds greater then 115k baud for FT8U232AM and FT8U245AM
1.00.2055 (Sept 7, 2000)
Support for common INF for Win98 and Win2k drivers
Update of INF to support FT8U232AM and FT8U245AM
1.00.2054 (Aug 10, 2000)
Increased time out delay to make enumerator performance more robust
1.00.2053 (Aug 9, 2000)
Fixed transmit toggle problem
1.00.2052 (July 24, 2000)
Driver stack made consistent to fix device power state failure
INF changes to add serial services
1.00.2051 (June 15, 2000)
Fixed problem with 230k baud select, IN transfer restriction of 64
bytes removed
Fixed X-ON/X-OFF handshaking problem, added support for serial mouse
1.00.2049 (Mar 25, 2000)
Install / uninstall for new naming (ftser2k)
1.00.2046 (Mar 15, 2000)
New naming format: ftserial - & gt; ftser2k
1.00.2044 (Mar 8, 2000)
Update to fix problem with Direct Cable Connect
1.00.2041 (Mar 3, 2000)
Fixed problem with baud rate selection
1.00.2040 (Mar 1, 2000)
Removed FTDI uninstaller
1.00.0 Beta (Feb 21, 2000)
Update to improve flow control
Alpha100 (Feb 18, 2000) - first release
Connects to ISP. Some flow control problems.
?
FTDI Win 98 Drivers - Revision Comments April 20, 2004
C:WINDOWSDesktopReleasesDriversWeb Release 905 2154 Apr20,2004905
Release Info.doc
FTDI's drivers have been changed to accommodate the support of Windows
98 and Windows 2000 for all three of FTDI's USB controllers from a
single INF file.
New drivers will be posted on the support page of FTDI's web page - in
ZIP format, following the following naming convention - Rxxyy where xx
is the version of the Windows 98 drivers and yy is the version of the
Windows 2000 drivers. The first release of the common INF drivers was
named R0855.zip - which is version 10208 of the Windows 98 drivers and
version 2055 of the Windows 2000 drivers.
There are now eleven files which are provided as a standard release
FTSERIAL.SYS (driver files)
FTSENUM.SYS
FTSENUM.VXD
FTCOMMS.VXD
FTSERMOU.INF
FTSERMOU.VXD
FTSERUI.DLL
FTDIUNIN.EXE (uninstaller and associated ini file)
FTDIUNIN.INI
FTDIBUS.INF (two shared INF files for Win98 and Win2k)
FTDIPORT.INF
On making a new release the files will also be posted onto FTDI's web
page http://www.ftdichip.com.
Proceed to the support page to download drivers (select Support tab at
top of screen).
Release versions
R10905 (December 17, 2003)
Fixed Win98 suspend problem.
R10904 (December 1, 2003)
Fixed problem with XON/XOFF handshake.
R10903 (October 20, 2003)
Added option to bypass queueing of vendor commands.
R10902 (October 7, 2003)
Fixed problem with reconnect after disconnect with open port.
R10901 (June 12, 2003)
Fixed bug in receive timeouts.
R10900 (June 09, 2003)
Bug fixes for substitution mode.
Improved command processing synchronization.
Update device map with port name.
R10808 (April 10, 2003)
Support for substitution mode.
Fixed disconnect problem where all open ports were lost if an open port
was disconnected..
R10804 (December 20, 2002)
Beta release.
Support for location ID.
New properties page.
R10802 (November 1, 2002)
Beta release.
Correctly identifies unserialized FT232BM and FT245BM devices.
R10801 (October 25, 2002)
Beta release.
Support for baud rates for FT232BM and FT245BM devices.
R10800 (July 18, 2002)
Enhanced event notification.
Fixed disconnect processing.
Fixed problems with WinFax.
Support for FT232BM.
Fixed serial mouse lockup in WinME.
R10701 (February 1, 2002)
Fixed divide-by-zero problem for zero baud rate.
Fixed blue screen in DOS FTP.
Fixed performance degradation problem for FTP.
R10514 (December 20, 2001)
Support non-standard baud rates.
Support Transmit Immediate.
R10512 (November 13, 2001)
Fixed disconnect problem introduced in R10511.
R10511 (October 30, 2001)
PortSetState function made compatible with serial driver.
R10510 (October 2, 2001)
PnP controlled from Registry.
Enumerator enhanced.
Mouse driver fixed to restore mouse function after reconnection.
Uses common uninstaller FTDIUNIN.EXE.
R10508 (July 27, 2001)
Fixed BREAK event received notification.
Changed receive triggering to fix PalmPilot problems.
Enhanced read and write processing.
R10502 (April 26, 2001)
Enhanced BREAK condition processing.
Improved support for serial mice.
Fixed HyperTerminal lockup problem when transmitting with USB
disconnected.
Fixed enumeration problem with SerialCardReader class.
R10408 (March 28, 2001)
Fixed performance problems when receiving data.
R10407 (March 23, 2001)
Added support for EV_TXEMPTY command
removed buffer size depends on baud rate change
introduced in R10402
R10405 (February 26, 2001)
Fixed disconnect with open port problem
R10402 (January 19, 2001)
Setting of in buffer size changed to be dependent on baud rate
?B7 64 bytes for rate & lt; 115kbps
?B7 controller by ConfigData entry in INF file for rate & gt; 115k
Synchronisation of vendor commands for improved driver robustness
R10301 (November 7, 2000)
Update to fix `access denied' problem under Windows Millennium
R10212 (October 19, 2000)
Updates to fix `port already open' and `modem not responding' problems
found under Windows Millennium and Windows 98
R10208 (September 7, 2000)
Support for common INF for Win98 and Win2k drivers
Update of INF to support FT8U232AM and FT8U245AM
R10207 (July 21, 2000)
Addition of mouse mini-driver to support serial mouse of FTDI serial
port
Addition of properties page to enable changing of allocated COM port -
see ComPort.doc
R10206 (Nov 10, 1999)
Update to fix problem with Hyperterminal
?