Add known-issues documentation section to the various LUFA bootloaders.

This commit is contained in:
Dean Camera 2013-03-22 23:24:02 +00:00
parent 54e46d7818
commit 141f24b4a1
5 changed files with 82 additions and 4 deletions

View file

@ -166,6 +166,27 @@
* +----------------------------+ FLASHEND
* \endverbatim
*
* \section Sec_KnownIssues Known Issues:
*
* \par In some cases, the application is not fully loaded into the device.
* Write-caching on some operating systems may interfere with the normal
* operation of the bootloader. Write caching should be disabled when using the
* Mass Storage bootloader, or the filesystem synced via an appropriate command
* (such as the OS's normal disk ejection command) before disconnecting the device.
*
* \par On Linux machines, written data may be corrupted.
* Linux systems appear to attempt a full filesystem re-write when the virtual
* firmware file of the bootloader is written to normally, causing corrupt
* device programming. On Linux systems, new firmware should be copied over
* in-place via the \c dd command on the virtual file to ensure the filesystem
* is left intact.
*
* \par After loading an application, it is not run automatically on startup.
* Some USB AVR boards ship with the BOOTRST fuse set, causing the bootloader
* to run automatically when the device is reset. In most cases, the BOOTRST
* fuse should be disabled and the HWBE fuse used instead to run the bootloader
* when needed.
*
* \section Sec_Options Project Options
*
* The following defines can be found in this demo, which can control the demo behaviour when defined, or changed in value.