Introduction
------------
This driver is provided for Texas Instruments internal development only. They are in no way ready to be shipped outside the company. Please talk to George Karabin (gkarabin@ti.com) if you need to distribute it. By the time anyone needs to distribute this, a newer version should be available that resolves some of its current problems.

bulkusb.inf is the file that tells windows how to identify a USB client capable of interfacing to Chimera, and then load the appropriate driver. It is currently looking for an invalid USB identification number (VID 0123, PID 4567). This number is probably owned by another company. It absolutely MUST BE REPLACED before shipping this code to another customer.

bulkusb.sys is a Microsoft-provided driver. It must be installed on any Windows computer that wishes to connect the Chimera application to a target board using USB.

The source code for bulkusb.sys comes from the Windows XP DDK. The driver is expected to work on Windows XP, 2000, and 98, but we've only tested it on Windows 2000 to date. The source code is not modified at all. The driver was compiled on Windows 2000 SP2 using Visual Studio 6, SP5.

Installation
------------
If using bsp_v63.00.20_m or newer (or a pre-release build in which you can read this notice), use these instructions. If using an older build, jump to the older build section.

1) Load a USB-capable esf build (esf_v64.00.22_m or later, or a pre-release build in which you can read this message) into the target board. (I.e., build nucleus_ccs_arm7tdmi_helendcevm from /vobs/global/esf, or build any other product that uses that version of esf or newer, with -DTHIF_BUILD and -DTHIF_BUFFERED_SEND enabled).

2) If running an ESF build, run the build, and wait until it tells you that it's waiting to connect to THIF peer (i.e., a PC).

3) Connect the PC via a USB cable.

4) Run the build and wait for it to give you instructions in the debugger's Window. If it tells you to start Chimera, ignore this request for now, but connect the USB cable when it tells you to. If it doesn't tell you when to connect it, connect it at any time.

5) Windows should request drivers for this device once a USB cable is connected to a running target build. Windows doesn't have any by default, so point it to the "bulkusb.inf" file provided here. It's best to install the driver from a local disk. For example, sometimes Windows will refuse to install the driver if the files are located on a Samba server.


If using an older build:
------------------------
Builds with a BSP version older than bsp_v63.00.20_m need special care when connecting the USB cable. Follow these instructions for them, and them jump to instruction 4 above.

1) Enable full-speed mode on your target board. This is mandatory for old builds. For a Helen-DC EVM or OMAP1510DC EVM board, this is accomplished by closing pins 1 & 2 of the jumper labeled JP12. Many boards don't come with spare jumpers - you may need to find your own. Pin one is always labelled. Pin 2 isn't labelled on my boards. So, install it so that the long edge of the jumper is parallel with the nearby dip switch, SW2.

2) Disconnect the USB cable from the target board. 
 
3) Load a USB-capable esf build (esf_v64.00.16_m or later) into the target board. (I.e., build nucleus_ccs_arm7tdmi_helendcevm from /vobs/global/esf, or build any other product that uses that version of esf or newer, with -DTHIF_BUILD and -DTHIF_BUFFERED_SEND enabled).

Post-Installation
-----------------
After Windows tells you that the driver is installed, you may use a USB-configured (via th.conf) chimera build (compiled using 
th_v60.00.16_m or later).

