* Out of the box, LUFA contains a large number of pre-made class demos for you to test, experiment with and\r
* ultimately build upon for your own projects. All the demos come pre-configured to build and run correctly\r
* on the AT90USB1287 AVR microcontroller, mounted on the Atmel USBKEY board and running at an 8MHz master clock.\r
* Out of the box, LUFA contains a large number of pre-made class demos for you to test, experiment with and\r
* ultimately build upon for your own projects. All the demos come pre-configured to build and run correctly\r
* on the AT90USB1287 AVR microcontroller, mounted on the Atmel USBKEY board and running at an 8MHz master clock.\r
- * This is due to two reasons; one, it is the hardware the author posesses, and two, it is the most popular Atmel\r
+ * This is due to two reasons; one, it is the hardware the author possesses, and two, it is the most popular Atmel\r
* and the project recompiled from the source code before being programmed into the AVR microcontroller. Most project\r
* configuration options are located in the "makefile" build script inside each LUFA application's folder, however some\r
* demo or application-specific configuration settings (such as the output format in the AudioOut demo) are located in the\r
* and the project recompiled from the source code before being programmed into the AVR microcontroller. Most project\r
* configuration options are located in the "makefile" build script inside each LUFA application's folder, however some\r
* demo or application-specific configuration settings (such as the output format in the AudioOut demo) are located in the\r
* build configuration settings may be altered.\r
*\r
* Inside each makefile, a number of configuration variables are located, with the format "<VARIABLE NAME> = <VALUE>". For\r
* build configuration settings may be altered.\r
*\r
* Inside each makefile, a number of configuration variables are located, with the format "<VARIABLE NAME> = <VALUE>". For\r
*\r
* <b>Note that this value does not actually *alter* the AVR's input clock frequency</b>, it is just a way to indicate to the library the clock frequency\r
* of the AVR as set by the AVR's fuses. If this value does not reflect the actual running frequency of the AVR, incorrect operation of one of more\r
*\r
* <b>Note that this value does not actually *alter* the AVR's input clock frequency</b>, it is just a way to indicate to the library the clock frequency\r
* of the AVR as set by the AVR's fuses. If this value does not reflect the actual running frequency of the AVR, incorrect operation of one of more\r
*\r
* \subsection SSec_F_CPU The F_CPU Parameter\r
* This parameter indicates the target AVR's master CPU clock frequency, in Hz.\r
*\r
* <b>Note that this value does not actually *alter* the AVR's CPU clock frequency</b>, it is just a way to indicate to the library the clock frequency\r
* of the AVR core as set by the AVR's fuses. If this value does not reflect the actual running frequency of the AVR, incorrect operation of one of more\r
*\r
* \subsection SSec_F_CPU The F_CPU Parameter\r
* This parameter indicates the target AVR's master CPU clock frequency, in Hz.\r
*\r
* <b>Note that this value does not actually *alter* the AVR's CPU clock frequency</b>, it is just a way to indicate to the library the clock frequency\r
* of the AVR core as set by the AVR's fuses. If this value does not reflect the actual running frequency of the AVR, incorrect operation of one of more\r
*\r
* \subsection SSec_CDEFS The CDEFS Parameter\r
* Most applications will actually have multiple CDEF lines, which are concatenated together with the "+=" operator. This ensures that large\r
*\r
* \subsection SSec_CDEFS The CDEFS Parameter\r
* Most applications will actually have multiple CDEF lines, which are concatenated together with the "+=" operator. This ensures that large\r
*\r
* Normally, these options do not need to be altered to allow an application to compile and run correctly on a different board or AVR to the\r
* current configuration - if the options are incorrect, then the demo is most likely incompatible with the chosen USB AVR model and cannot be\r
*\r
* Normally, these options do not need to be altered to allow an application to compile and run correctly on a different board or AVR to the\r
* current configuration - if the options are incorrect, then the demo is most likely incompatible with the chosen USB AVR model and cannot be\r
*\r
* \subsection SSec_CommandLine Via the Command Line\r
* To build a project from the source via the command line, the command <b>"make all"</b> should be executed from the command line in the directory\r
*\r
* \subsection SSec_CommandLine Via the Command Line\r
* To build a project from the source via the command line, the command <b>"make all"</b> should be executed from the command line in the directory\r
* files), execute <b>"make clean"</b>. Once a "make all" has been run and no errors were encountered, the resulting binary will\r
* be located in the generated ".HEX" file. If your project makes use of pre-initialized EEPROM variables, the generated ".EEP"\r
* file will contain the project's EEPROM data.\r
* files), execute <b>"make clean"</b>. Once a "make all" has been run and no errors were encountered, the resulting binary will\r
* be located in the generated ".HEX" file. If your project makes use of pre-initialized EEPROM variables, the generated ".EEP"\r
* file will contain the project's EEPROM data.\r
projects / pub / lufa.git / blobdiff