aboutsummaryrefslogtreecommitdiffstats
path: root/Bootloaders/MassStorage/BootloaderMassStorage.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Bootloaders/MassStorage/BootloaderMassStorage.txt')
-rw-r--r--Bootloaders/MassStorage/BootloaderMassStorage.txt21
1 files changed, 21 insertions, 0 deletions
diff --git a/Bootloaders/MassStorage/BootloaderMassStorage.txt b/Bootloaders/MassStorage/BootloaderMassStorage.txt
index 19751d3be..e072d2d24 100644
--- a/Bootloaders/MassStorage/BootloaderMassStorage.txt
+++ b/Bootloaders/MassStorage/BootloaderMassStorage.txt
@@ -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.