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.
 
   7 /** \mainpage DFU Class USB AVR Bootloader
 
   9  *  \section Sec_Compat Demo Compatibility:
 
  11  *  The following list indicates what microcontrollers are compatible with this demo.
 
  13  *  \li Series 7 USB AVRs (AT90USBxxx7)
 
  14  *  \li Series 6 USB AVRs (AT90USBxxx6)
 
  15  *  \li Series 4 USB AVRs (ATMEGAxxU4)
 
  16  *  \li Series 2 USB AVRs (AT90USBxx2, ATMEGAxxU2)
 
  18  *  \section Sec_Info USB Information:
 
  20  *  The following table gives a rundown of the USB utilization of this demo.
 
  24  *   <td><b>USB Mode:</b></td>
 
  28  *   <td><b>USB Class:</b></td>
 
  29  *   <td>Device Firmware Update Class (DFU)</td>
 
  32  *   <td><b>USB Subclass:</b></td>
 
  36  *   <td><b>Relevant Standards:</b></td>
 
  37  *   <td>USBIF DFU Class Standard, Atmel USB Bootloader Datasheet</td>
 
  40  *   <td><b>Supported USB Speeds:</b></td>
 
  41  *   <td>Low Speed Mode \n
 
  42  *       Full Speed Mode</td>
 
  46  *  \section Sec_Description Project Description:
 
  48  *  This bootloader enumerates to the host as a DFU Class device, allowing for DFU-compatible programming
 
  49  *  software to load firmware onto the AVR.
 
  51  *  Out of the box this bootloader builds for the AT90USB1287 with an 8KB bootloader section size, and will fit
 
  52  *  into 4KB of bootloader space. If you wish to alter this size and/or change the AVR model, you will need to
 
  53  *  edit the MCU, FLASH_SIZE_KB and BOOT_SECTION_SIZE_KB values in the accompanying makefile.
 
  55  *  When the bootloader is running, the board's LED(s) will flash at regular intervals to distinguish the
 
  56  *  bootloader from the normal user application.
 
  58  *  \section Sec_Installation Driver Installation
 
  60  *  This bootloader is designed to be compatible with Atmel's provided Windows DFU class drivers. You will need to
 
  61  *  install Atmel's DFU drivers prior to using this bootloader on Windows platforms. If you are using a 64 bit Windows
 
  62  *  OS, you will need to either disable the driver signing requirement (see online tutorials for details) or use a
 
  63  *  digitally signed version of the official Atmel driver provided by a third party AVR user at
 
  64  *  <a>http://www.avrfreaks.net/index.php?module=Freaks%20Academy&func=viewItem&item_id=2196&item_type=project</a>.
 
  66  *  \note This device spoofs Atmel's DFU Bootloader USB VID and PID so that the Atmel DFU bootloader
 
  67  *        drivers included with FLIP will work. If you do not wish to use Atmel's ID codes, please
 
  68  *        manually change them in Descriptors.c and alter your driver's INF file accordingly.
 
  70  *  \section Sec_HostApp Host Controller Application
 
  72  *  This bootloader is compatible with Atmel's FLIP utility on Windows machines, and dfu-programmer on Linux machines.
 
  74  *  \subsection SSec_FLIP FLIP (Windows)
 
  76  *  FLIP (Flexible In-System Programmer) is a utility written by Atmel, and distributed for free on the Atmel website.
 
  77  *  The FLIP utility is designed to assist in the bootloader programming of a range of Atmel devices, through several
 
  78  *  popular physical interfaces including USB. It is written in Java, however makes use of native extensions for USB
 
  79  *  support and thus is only offered on Windows.
 
  81  *  To program a device using FLIP, refer to the Atmel FLIP documentation.
 
  83  *  \subsection SSec_DFUProgrammer dfu-programmer (Linux)
 
  85  *  dfu-programmer is an open-source command line solution for the bootloader programming of Atmel devices through a
 
  86  *  USB connection, using the DFU protocol, available for download at <a>http://sourceforge.net/projects/dfu-programmer/</a>.
 
  88  *  The following example loads a HEX file into the AVR's FLASH memory using dfu-programmer:
 
  90  *  dfu-programmer at90usb1287 erase flash Mouse.hex
 
  93  *  \section Sec_API User Application API
 
  95  *  Several user application functions for FLASH and other special memory area manipulations are exposed by the bootloader,
 
  96  *  allowing the user application to call into the bootloader at runtime to read and write FLASH data.
 
  98  *  \warning The APIs exposed by the DFU class bootloader are \b NOT compatible with the API exposed by the official Atmel DFU bootloader.
 
 100  *  By default, the bootloader API jump table is located 32 bytes from the end of the device's FLASH memory, and follows the
 
 104  *  #define BOOTLOADER_API_TABLE_SIZE          32
 
 105  *  #define BOOTLOADER_API_TABLE_START         ((FLASHEND + 1UL) - BOOTLOADER_API_TABLE_SIZE)
 
 106  *  #define BOOTLOADER_API_CALL(Index)         (void*)((BOOTLOADER_API_TABLE_START + (Index * 2)) / 2)
 
 108  *  void    (*BootloaderAPI_ErasePage)(uint32_t Address)               = BOOTLOADER_API_CALL(0);
 
 109  *  void    (*BootloaderAPI_WritePage)(uint32_t Address)               = BOOTLOADER_API_CALL(1);
 
 110  *  void    (*BootloaderAPI_FillWord)(uint32_t Address, uint16_t Word) = BOOTLOADER_API_CALL(2);
 
 111  *  uint8_t (*BootloaderAPI_ReadSignature)(uint16_t Address)           = BOOTLOADER_API_CALL(3);
 
 112  *  uint8_t (*BootloaderAPI_ReadFuse)(uint16_t Address)                = BOOTLOADER_API_CALL(4);
 
 113  *  uint8_t (*BootloaderAPI_ReadLock)(void)                            = BOOTLOADER_API_CALL(5);
 
 114  *  void    (*BootloaderAPI_WriteLock)(uint8_t LockBits)               = BOOTLOADER_API_CALL(6);
 
 116  *  #define BOOTLOADER_MAGIC_SIGNATURE_START   (BOOTLOADER_API_TABLE_START + (BOOTLOADER_API_TABLE_SIZE - 2))
 
 117  *  #define BOOTLOADER_MAGIC_SIGNATURE         0xDCFB
 
 119  *  #define BOOTLOADER_CLASS_SIGNATURE_START   (BOOTLOADER_API_TABLE_START + (BOOTLOADER_API_TABLE_SIZE - 4))
 
 120  *  #define BOOTLOADER_DFU_SIGNATURE           0xDF10
 
 122  *  #define BOOTLOADER_ADDRESS_START           (BOOTLOADER_API_TABLE_START + (BOOTLOADER_API_TABLE_SIZE - 8))
 
 123  *  #define BOOTLOADER_ADDRESS_LENGTH          4
 
 126  *  From the application the API support of the bootloader can be detected by reading the FLASH memory bytes located at address
 
 127  *  \c BOOTLOADER_MAGIC_SIGNATURE_START and comparing them to the value \c BOOTLOADER_MAGIC_SIGNATURE. The class of bootloader
 
 128  *  can be determined by reading the FLASH memory bytes located at address \c BOOTLOADER_CLASS_SIGNATURE_START and comparing them
 
 129  *  to the value \c BOOTLOADER_DFU_SIGNATURE. The start address of the bootloader can be retrieved by reading the bytes of FLASH
 
 130  *  memory starting from address \c BOOTLOADER_ADDRESS_START.
 
 132  *  \subsection SSec_API_MemLayout Device Memory Map
 
 133  *  The following illustration indicates the final memory map of the device when loaded with the bootloader.
 
 136  *  +----------------------------+ 0x0000
 
 145  *  |      User Application      |
 
 153  *  +----------------------------+ FLASHEND - BOOT_SECTION_SIZE
 
 155  *  |   Bootloader Application   |
 
 156  *  | (Not User App. Accessible) |
 
 158  *  +----------------------------+ FLASHEND - 96
 
 159  *  |   API Table Trampolines    |
 
 160  *  | (Not User App. Accessible) |
 
 161  *  +----------------------------+ FLASHEND - 32
 
 162  *  |    Bootloader API Table    |
 
 163  *  |   (User App. Accessible)   |
 
 164  *  +----------------------------+ FLASHEND - 8
 
 165  *  |   Bootloader ID Constants  |
 
 166  *  |   (User App. Accessible)   |
 
 167  *  +----------------------------+ FLASHEND
 
 170  *  \section Sec_Options Project Options
 
 172  *  The following defines can be found in this demo, which can control the demo behaviour when defined, or changed in value.
 
 176  *    <td><b>Define Name:</b></td>
 
 177  *    <td><b>Location:</b></td>
 
 178  *    <td><b>Description:</b></td>
 
 181  *    <td>SECURE_MODE</td>
 
 182  *    <td>AppConfig.h</td>
 
 183  *    <td>If defined to \c true, the bootloader will not accept any memory commands other than a chip erase on start-up, until an
 
 184  *        erase has been performed. This can be used in conjunction with the AVR's lockbits to prevent the AVRs firmware from
 
 185  *        being dumped by unauthorized persons. When false, all memory operations are allowed at any time.</td>