This is the Readme file to Objective Development's firmware-only USB driverfor Atmel AVR microcontrollers. For more information please visithttp://www.obdev.at/avrusb/This directory contains the USB firmware only. Copy it as-is to your ownproject and add your own version of "usbconfig.h". A template for your own"usbconfig.h" can be found in "usbconfig-prototype.h" in this directory.TECHNICAL DOCUMENTATION=======================The technical documentation for the firmware driver is contained in the file"usbdrv.h". Please read all of it carefully!USB IDENTIFIERS===============Every USB device needs a vendor- and a product-identifier (VID and PID). VIDsare obtained from usb.org for a price of 1,500 USD. Once you have a VID, youcan assign PIDs at will.Since an entry level cost of 1,500 USD is too high for most small companiesand hobbyists, we provide a single VID/PID pair for free. If you want to useyour own VID and PID instead of our's, define the macros "USB_CFG_VENDOR_ID"and "USB_CFG_DEVICE_ID" accordingly in "usbconfig.h".To use our predefined VID/PID pair, you MUST conform to a couple ofrequirements. See the file "USBID-License.txt" for details.HOST DRIVER===========You have received this driver together with an example device implementationand an example host driver. The host driver is based on libusb and compileson various Unix flavors (Linux, BSD, Mac OS X). It also compiles natively onWindows using MinGW (see www.mingw.org) and libusb-win32 (seelibusb-win32.sourceforge.net). The "Automator" project contains a nativeWindows host driver (not based on libusb) for Human Interface Devices.DEVELOPMENT SYSTEM==================This driver has been developed and optimized for the GNU compiler version 3(gcc 3). It does work well with gcc 4 and future versions will probably beoptimized for gcc 4. We recommend that you use the GNU compiler suite becauseit is freely available. AVR-USB has also been ported to the IAR compiler andassembler. It has been tested with IAR 4.10B/W32 and 4.12A/W32 on an ATmega8with the "small" and "tiny" memory model. Please note that gcc is moreefficient for usbdrv.c because this module has been deliberately optimizedfor gcc.USING AVR-USB FOR FREE======================The AVR firmware driver is published under an Open Source compliant license.See the file "License.txt" for details. Since it is not obvious for manypeople how this license applies to their own projects, here's a short guide:(1) The USB driver and all your modifications to the driver itself are ownedby Objective Development. You must give us a worldwide, perpetual,irrevocable royalty free license for your modifications.(2) Since you own the code you have written (except where you modify ourdriver), you can (at least in principle) determine the license for it freely.However, to "pay" for the USB driver code you link against, we demand thatyou choose an Open Source compliant license (compatible with our license) foryour source code and the hardware circuit diagrams. Simply attach yourlicense of choice to your parts of the project and leave our "License.txt" inthe "usbdrv" subdirectory.(3) We also demand that you publish your work on the Internet and drop us anote with the URL. The publication must meet certain formal criteria (filesdistributed, file formats etc.). See the file "License.txt" for details.Other than that, you are allowed to manufacture any number of units and sellthem for any price. If you like our driver, we also encourage you to make adonation on our web site.COMMERCIAL LICENSES FOR AVR-USB===============================If you don't want to publish your source code and the circuit diagrams underan Open Source license, you can simply pay money for AVR-USB. As anadditional benefit you get USB PIDs for free, licensed exclusively to you.See http://www.obdev.at/products/avrusb/license.html for details.