* <td>Build and link the application into an ELF debug file.</td>\r
* </tr>\r
* <tr>\r
+ * <td><tt>bin</tt></td>\r
+ * <td>Build and link the application and produce a BIN binary file.</td>\r
+ * </tr>\r
+ * <tr>\r
* <td><tt>hex</tt></td>\r
* <td>Build and link the application and produce HEX and EEP binary files.</td>\r
* </tr>\r
* <td>Error "<b><tt>Cannot build with OBJDIR parameter set - one or more object file name is not unique</tt></b>" shown when compiling.</td>\r
* <td>When a project is built with a non-empty <tt>OBJDIR</tt> object directory name set, all input source files must have unique names, excluding extension and path.\r
* This means that input files that are named identically and differ only by their path or extension are invalid when this mode is used.</td>\r
- * </tr> \r
+ * </tr>\r
* <tr>\r
* <td>Error "<b><tt>Source file does not exist: <i>{X}</i></tt></b>" shown when compiling.</td>\r
* <td>The nominated input source file, specified in the user project's <tt>SRC</tt> parameter, could not be found. Ensure the source file exists and the absolute or\r
* upgrade to the latest AVR-GCC. If the option is a valid linker option, use the prefix "-Wl," to ensure it is passed to the linker correctly.</td>\r
* </tr>\r
* <tr>\r
- * <td>Error "<b><tt>avr-gcc: error: unrecognized option '<i>{X}</i>'</tt></b>" shown when compiling.</td>\r
- * <td>An unrecognised option was supplied to the compiler, usually in the <tt>C_FLAGS</tt>, <tt>CPP_FLAGS</tt>, <tt>ASM_FLAGS</tt> or <tt>CC_FLAGS</tt> configuration\r
- * options. The nominated compiler switch may be invalid, or unsupported by the version of AVR-GCC on the host system. Remove the unrecognised flag if invalid, or\r
- * upgrade to the latest AVR-GCC. If the option is a valid linker option, use the prefix "-Wl," to ensure it is passed to the linker correctly.</td>\r
- * </tr>\r
- * <tr>\r
- * <td>Error "<b><tt>makefile:{X}: {Y}.mk: No such file or directory</tt></b>" shown when make is invoked.</td>\r
- * <td>The path to the nominated makefile module was incorrect. This usually indicates that the makefile <tt>LUFA_PATH</tt> option is not set to a valid relative or\r
- * absolute path to the LUFA library core.</td>\r
- * </tr>\r
- * <tr>\r
* <td>Error "<b><tt>makefile:{X}: {Y}.mk: No such file or directory</tt></b>" shown when make is invoked.</td>\r
* <td>The path to the nominated makefile module was incorrect. This usually indicates that the makefile <tt>LUFA_PATH</tt> option is not set to a valid relative or\r
* absolute path to the LUFA library core.</td>\r
* version of the compiler being used. Make sure the model name is correct, or upgrade to the latest Atmel Toolchain to obtain newer device support.</td>\r
* </tr>\r
* <tr>\r
- * <td>Error "<b><tt>error: invalid suffix "x" on integer constant</tt></b>" shown when compiling a bootloader.</td>\r
- * <td>This is usually caused by the <tt>bc.exe</tt> application not being found in the system's <tt>PATH</tt> variable. Make sure you have the <tt>bc.exe</tt> tool\r
- * installed correctly (see \ref Sec_Prerequisites).</td>\r
- * </tr>\r
- * <tr>\r
* <td>Error "<b><tt>undefined reference to `<i>{X}</i>'</tt></b>" shown when compiling.</td>\r
* <td>This is usually caused by a missing source file in the user application's <tt>SRC</tt> configuration parameter. If the indicated symbol is one from the LUFA\r
* library, you may be missing a LUFA source makefile module (see \ref Page_BuildModule_SOURCES).</td>\r
* </table>\r
*\r
* For troubleshooting other errors you encounter, please see \ref Sec_ProjectHelp.\r
- */
\ No newline at end of file
+ */\r
projects / pub / USBasp.git / blobdiff