1. rev_300.zip Driver
2. readme.txt File Contents

readme.txt Driver File Contents (rev_300.zip)

DeVaSys USB-I2C/IO - Software

Release Version: 3.0
Release Date: 10/08/2003.


DISCLAIMER:

This version of the software is very new, has not undergone significant testing, and may in fact contain serious bugs.

DeVaSys makes ABSOLUTELY NO CLAIM to the suitability of this software for any use, whatsoever, and in fact, we DO NOT RECOMMEND that anyone install it on any system.  We will not accept ANY RESPONSIBILITY for any damages or losses you might encounter as a result of attempting to use this software.



WHO SHOULD INSTALL THIS UPGRADE:

Practically nobody.

If you don't have an existing plug and play issue with the old software, then there is absolutely no reason to risk installing this software.


WHO SHOULD NOT INSTALL THIS UPGRADE:

If you are not experiencing a critical problem with the old software, we recommend that you do not install this upgrade.

If you are running a customized version of DeVaSys firmware, you should NOT attempt to use this software, please contact DeVaSys to obtain an updated version of your customized firmware.



GENERAL INFORMATION ABOUT THIS RELEASE:

This version is primarily meant to be a fix for the existing plug and play problems, it does not provide any significant new features.

As the USB-I2C/IO software consists of three separate pieces, firmware, driver, and dll, we will subdivide the "New Features" accordingly.



NEW FEATURES IN THIS RELEASE OF THE FIRMWARE:

This version of the firmware is designed to load from the eeprom on startup, rather than be downloaded from the host as were previous versions.

This eliminates the need for a loader driver, and greatly simplifies what happens at the point when you connect the board to the Host.

We've also added support for a "GetFirmwareVersion" vendor request to the firmware.



NEW FEATURES IN THIS RELEASE OF THE DRIVER:

This release incorporates a completely re-written driver.

The driver has been tested with the driver verifier tool, and passed.

This driver provides greatly enhanced functionality, including support for BULK and INTERRUPT transfers, long CONTROL transfers, improved plug and play functionality, and suppression of the annoying "surprise removal" dialog box (Windows 2000).

The driver consists of a single dev03edb.sys file, which is intended to work with Windows 98, 98SE, ME, 2000, and XP.



NEW FEATURES IN THIS RELEASE OF THE DLL:

This dll provides support for two previously unimplemented functions, one to get the version of the installed driver, and another to get the version of the board firmware.



INSTALLATION:

The first step is to use the "Recovery" utility (recovery.exe) to program the new firmware into the board.

The DeVaSys "Recovery" utility uses the Cypress drivers (not our own drivers) to communicate with the board.

Using the Recovery utility with the Cypress drivers provides the ability to program a USB-I2C/IO board, even if it's current eeprom contents are corrupted.  The directory containing the recovery.exe file also has the Cypress drivers. 

IMPORTANT, If you are prompted for drivers when running the recovery.exe utility, you should point the windows installation wizard to the drivers contained in the recovery directory, NOT TO THE DEVASYS DRIVER.

Follow the instructions provided by the Recovery utility regarding jumper settings, and progress through the screens until prompted for a hex file.

The new firmware hex file (rev_300.hex) can be found in the "firmware" subdirectory.

Once you have programmed the board with the new firmware, disconnect it from the Host.

The next time you connect that board, the host should see it as a "new device".

You should then go through the typical driver installation for a new device, and point the installation wizard to the files in the "drv_dll" subdirectory (the DeVaSys driver).

This should install not only the new driver "dev03edb.sys" (in your \system32\drivers directory) but also the new usbi2cio.dll (in your \system32 directory).



WILL MY EXISTING APPLICATIONS WORK WITH THE NEW SOFTWARE?

Your existing application should "just work" with the new software.

We have provided updated usbi2cio.h and usbi2cio.lib files should a recompile of your code be necessary.



CAN YOU RUN BOTH OLD AND NEW SOFTWARE/BOARDS ON THE SAME SYSTEM?

Yes, it is possible to run both old boards (old firmware, old drivers, old dll) and new boards (new firmware, new driver, new dll) on the same machine.  The only really tricky part is the dll file, which has the same name for both old and new versions.

If you know about how Windows finds/loads dlls, then you should know how to solve the problem, if not...

Basically, you should keep the new dll in your \system32 directory.  To talk to boards that are using the old software... make a separate copy of your application(s), and put a copy of the old dll in the same directory as your applications executable.  When you run that copy of your application executable, it will find the old dll first, and use it.