readme.txt

Texas Instruments的TUSB3410芯片接键盘输入的固件程序源码和驱动程序源码。

This sample code provides a start point to develop the firmware for TUSB3410. Basically it uses TUSB3410 as a special USB keyboard, only number of keypads and LEDs, the advantages are device driver free and easily to see the result.

The sample code supports two well-known development environments: KEIL and IAR. "Sample.Uv2" is a project file of KEIL. "Sample.prj" is a project file of IAR.
In the IAR environment, after compiling, the file "TUSB3410.bin" will be generated and copied to c:\winnt\system32\drivers. For Win9x/XP systems, 'winnt' directory should be changed to 'windows.' 
During firmware development, the firmware is usually downloaded from the host via USB. Therefore, when one first plugs in the TUSB3410 EVM to the USB port, Windows will ask for a device driver. In 'Sample\Debug\Exe' directory, there is a "BootLoader" device driver which will enable download of the "TUSB3410.bin" object file to the TUSB3410 chip. The "TUSB3410.inf" file will make Windows copy "TIUpDatr.sys" and "TUSB3410.bin" to 'winnt\system32\driver' if the operating system (OS) is Win2000. After TUSB3410 loads the firmware, it will disconnect from the USB Bus and jump to the starting point of the downloaded firmware. The default compiled sample code "TUSB3410.bin" is essentially a type of USB keyboard firmware, and when the downloaded firmware starts running, it will reconnect to the USB Bus. Windows will then re-enumerate this new firmware, and when Windows recognizes it as a USB keyboard, Windows will load the USB HID-class device driver for keyboards. (To better understand HID-class device drivers, see www.usb.org.) 

Only upon first time use with Windows will it need to copy the "BootLoader" device driver to the system directory. If one changes the firmware source code, one must recompile it and by default it will be copied to 'c:\winnt\system32\driver.' After resetting the TUSB3410 EVM, the new firmware will be loaded. It's a convenient way to develop firmware for this 8052-based MCU.

The TUSB3410 GPIO EVM board (sold as a kit as "TUSB3410GPIOPDK") has 4 buttons and 4 LEDs connected to TUSB3410 General Purpose I/Os. From the factory, the EVM has 4 jumpers installed, which are for "serial interface for debugging enabled" (2 jumpers) and "suspend LED" (LED will turn on in suspend mode if this jumper is installed) and "I2C SCL connected." When the EVM is plugged into the USB port of a USB enabled OS, it will be enumerated as a USB keyboard. However, only the SW6 button is for keypad testing. If SW6 is pressed, TUSB3410 will send a "TIUSB" string to USB and serial interface(with baudrate 9600N81 configuration), and turn on LED D5. Although LED D4 and D6 are also turned on, they are not controlled by firmware, but  are controlled by hardware. D4 is directly connected to SW6. D6 may flash because it indicates operation of the TXD on the serial interface, and when TUSB3410 sends the "TIUSB" string to the serial port, D6 will be appear to be turned on.In the KEIL environment, after compiling firmware, it will call "HEXBIN" utility which can convert the hexdecimal format file to binary format to convert the output file to binary format. The "HEXBIN" utility can be found in the public domain.