* This is due to two reasons; one, it is the hardware the author posesses, and two, it is the most popular Atmel\r
* USB demonstration board to date.\r
*\r
+ *\r
* \section Sec_Prerequisites Prerequisites\r
* Before you can compile any of the LUFA library code or demos, you will need a recent distribution of avr-libc (1.6.2+)\r
* and the AVR-GCC (4.2+) compiler. For Windows users, the best way to obtain these is the WinAVR project\r
* (http://winavr.sourceforge.net) as this provides a single-file setup for everything required to compile your\r
* own AVR projects.\r
*\r
+ *\r
* \section Sec_Configuring Configuring the Demos, Bootloaders and Projects\r
* If the target AVR model, clock speed, board or other settings are different to the current settings, they must be changed\r
* and the project recompiled from the source code before being programmed into the AVR microcontroller. Most project\r
* interface speed (Low or Full speed) and other LUFA configuration options can be set here - refer to the library documentation for details on the\r
* configuration parameters.\r
*\r
+ *\r
* \section Sec_Compiling Compiling a LUFA Application\r
* Compiling the LUFA demos, applications and/or bootloaders is very simple. LUFA comes with makefile scripts for\r
* each individual demo, bootloader and project folder, as well as scripts in the /Demos/, /Bootloaders/, /Projects/\r
* in AVRStudio, the project can be built and cleaned using the GUI buttons or menus. Note that the AVRStudio project files make\r
* use of the external project makefile, thus the procedure for configuring a demo remains the same regardless of the build environment.\r
*\r
+ *\r
* \section Sec_Programming Programming a USB AVR\r
* Once you have built an application, you will need a way to program in the resulting ".HEX" file (and, if your\r
* application uses EEPROM variables with initial values, also a ".EEP" file) into your USB AVR. Normally, the\r
projects / pub / lufa.git / blobdiff