LUFA/DoxygenPages/ConfiguringApps.txt

   1 /** \file
   2  *
   3  *  This file contains special DoxyGen information for the generation of the main page and other special
   4  *  documentation pages. It is not a project source file.
   5  */
   6
   7 /** \page Page_ConfiguringApps Configuring the Demos, Bootloaders and Projects
   8  *
   9  *  If the target microcontroller model, architecture, clock speed, board or other settings are different from the current
  10  *  settings, they must be changed and the project recompiled from the source code before being programmed into the microcontroller.
  11  *  Most project configuration options are located in the "makefile" build script inside each LUFA application's folder, however
  12  *  some demo or application-specific configuration settings (such as the output format in the AudioOut demo) are located in one or
  13  *  more of the source files of the project. See each project's individual documentation for application-specific configuration
  14  *  values.
  15  *
  16  *  Each project "makefile" contains all the script and configuration data required to compile each project. When opened with
  17  *  any regular basic text editor such as Notepad or WordPad (ensure that the save format is a pure ASCII text format) the
  18  *  build configuration settings may be altered.
  19  *
  20  *  Inside each makefile, a number of configuration variables are located, with the format "<VARIABLE NAME> = <VALUE>". For
  21  *  each application, the important variables which should be altered are:
  22  *
  23  *    - <b>MCU</b>, the target processor model
  24  *    - <b>ARCH</b>, the target microcontroller architecture
  25  *    - <b>BOARD</b>, the target board hardware
  26  *    - <b>F_CPU</b>, the target CPU master clock frequency, after any prescaling
  27  *    - <b>F_USB</b>, the target raw input clock to the USB module of the processor
  28  *    - <b>OPTIMIZATION</b>, the level of optimization to compile with
  29  *    - <b>TARGET</b>, the name of the target output binary and other files
  30  *    - <b>SRC</b>, the list of source files to compile/assemble/link
  31  *    - <b>LUFA_PATH</b>, the path to the LUFA library core source code
  32  *    - <b>CC_FLAGS</b>, the common command line flags to pass to the C/C++ compiler, assembler and linker
  33  *    - <b>LD_FLAGS</b>, the command line flags to pass to the linker
  34  *
  35  *  These values should be changed to reflect the build hardware.
  36  *
  37  *  \section Sec_MCU The MCU Parameter
  38  *  This parameter indicates the target microcontroller model for the compiled application. This should be set to the model of the target
  39  *  microcontroller (such as the AT90USB1287, or the ATMEGA32U4), in all lower-case (e.g. "at90usb1287"). Note that not all demos support all the
  40  *  microcontroller models and architectures, as they may make use of peripherals or modes only present in some devices.
  41  *
  42  *  For supported processor models, see \ref Page_DeviceSupport.
  43  *
  44  *  \section Sec_ARCH The ARCH Parameter
  45  *  This parameter indicates the target microcontroller architecture the library is to be compiled for. Different microcontroller
  46  *  architectures require different source files to be compiled into the final binary, and so this option must be set to the correct
  47  *  architecture for the selected platform.
  48  *
  49  *  For supported processor architectures, see \ref Page_DeviceSupport.
  50  *
  51  *  \section Sec_BOARD The BOARD Parameter
  52  *  This parameter indicates the target board hardware for the compiled application. Some LUFA library drivers are board-specific,
  53  *  such as the LED driver, and the library needs to know the layout of the target board. If you are using one of the board models listed
  54  *  on the main library page, change this parameter to the board name in all UPPER-case.
  55  *
  56  *  If you are not using any board-specific drivers in the LUFA library, or you are using a custom board layout, change this to read
  57  *  "USER" (no quotes) instead of a standard board name. If the USER board type is selected and the application makes use of one or more
  58  *  board-specific hardware drivers inside the LUFA library, then the appropriate stub drives files should be copied from the \c /CodeTemplates/DriverStubs/
  59  *  directory into a /Board/ folder inside the application directory, and the stub driver completed with the appropriate code to drive the
  60  *  custom board's hardware.
  61  *
  62  *  For boards with built in hardware driver support within the LUFA library, see \ref Page_DeviceSupport.
  63  *
  64  *  \section Sec_F_CPU The F_CPU Parameter
  65  *  This parameter indicates the target microcontroller's main CPU clock frequency, in Hz. This is used by many libraries (and applications) for
  66  *  timing related purposes, and should reflect the actual CPU speed after any prescaling or adjustments are performed.
  67  *
  68  *  \section Sec_F_USB The F_USB Parameter
  69  *  This parameter indicates the raw input clock frequency to the USB module within the microcontroller in Hz. This may be very different on some platforms
  70  *  to the main CPU clock or other peripheral/bus clocks.
  71  *
  72  *  \section Sec_OPTIMIZATION The OPTIMIZATION Parameter
  73  *  This parameter indicates the level of optimization to use when compiling the application. This will allow you to compile with an optimization level
  74  *  supported by GCC, from <tt>0</tt> (no optimization) to <tt>3</tt> (fastest runtime optimization) or <tt>s</tt> (smallest size).
  75  *
  76  *  \section Sec_TARGET The TARGET Parameter
  77  *  This parameter indicates the application target name, which is used as the base filename for the build binary and debugging files. This will be the
  78  *  name of the output files once linked together into the final application, ready to load into the target.
  79  *
  80  *  \section Sec_SRC The SRC Parameter
  81  *  This parameter indicates the source files used to compile the application, as a list of C (<tt>*.c</tt>), C++ (<tt>*.cpp</tt>) and Assembly (<tt>*.S</tt>) files. Note that
  82  *  all assembly files must end in a <b>capital</b> .S extension, as lowercase .s files are reserved for GCC intermediate files.
  83  *
  84  *  \section Sec_LUFA_PATH The LUFA_PATH Parameter
  85  *  As each LUFA program requires the LUFA library source code to compile correctly, the application must know where the LUFA library is located. This
  86  *  value specifies the path to the LUFA library core. This path may be relative or absolute, however note than even under Windows based systems the
  87  *  forward-slash (/) path seperator must be used.
  88  *
  89  *  \section Sec_CC_FLAGS The CC_FLAGS Parameter
  90  *  This parameter lists the compiler flags passed to the C/C++ compiler, the assembler and the linker. These are used as-is directly to GCC and thus
  91  *  must match GCC's command line options as given in the GCC manual. This variable may be used to define tokens directly on the command line, enable or
  92  *  disable warnings, adjust the target-specific tuning parameters or other options.
  93  *
  94  *  \section Sec_LD_FLAGS The LD_FLAGS Parameter
  95  *  This parameter lists the linker flags passed exclusively to the linker. These are used as-is directly to GCC and thus must match GCC's command line
  96  *  linker options as given in the GCC manual. This variable may be used to create or relocate custom data sections, or enable linker specific behaviors.
  97  */