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  *  - Series 7 USB AVRs (AT90USBxxx7)
 
  14  *  - Series 6 USB AVRs (AT90USBxxx6)
 
  15  *  - Series 4 USB AVRs (ATMEGAxxU4)
 
  16  *  - 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>Usable Speeds:</b></td>
 
  41  *   <td>Full Speed Mode</td>
 
  45  *  \section Sec_Description Project Description:
 
  47  *  This bootloader enumerates to the host as a DFU Class device, allowing for DFU-compatible programming
 
  48  *  software to load firmware onto the AVR.
 
  50  *  Out of the box this bootloader builds for the USB1287, and should fit into 4KB of bootloader space. If
 
  51  *  you wish to enlarge this space and/or change the AVR model, you will need to edit the BOOT_START and MCU
 
  52  *  values in the accompanying makefile.
 
  54  *  When the bootloader is running, the board's LED(s) will flash at regular intervals to distinguish the
 
  55  *  bootloader from the normal user application.
 
  57  *  \section Sec_Installation Driver Installation
 
  59  *  This bootloader is designed to be compatible with Atmel's provided Windows DFU class drivers. You will need to
 
  60  *  install Atmel's DFU drivers prior to using this bootloader on Windows platforms. If you are using a 64 bit Windows
 
  61  *  OS, you will need to either disable the driver signing requirement (see online tutorials for details) or use a
 
  62  *  digitally signed version of the official Atmel driver provided by a third party AVR user at
 
  63  *  <a>http://www.avrfreaks.net/index.php?module=Freaks%20Academy&func=viewItem&item_id=2196&item_type=project</a>.
 
  65  *  \note This device spoofs Atmel's DFU Bootloader USB VID and PID so that the Atmel DFU bootloader
 
  66  *        drivers included with FLIP will work. If you do not wish to use Atmel's ID codes, please
 
  67  *        manually change them in Descriptors.c and alter your driver's INF file accordingly.
 
  69  *  \section Sec_HostApp Host Controller Application
 
  71  *  This bootloader is compatible with Atmel's FLIP utility on Windows machines, and dfu-programmer on Linux machines.
 
  73  *  \subsection SSec_FLIP FLIP (Windows)
 
  75  *  FLIP (Flexible In-System Programmer) is a utility written by Atmel, and distributed for free on the Atmel website.
 
  76  *  The FLIP utility is designed to assist in the bootloader programming of a range of Atmel devices, through several
 
  77  *  popular physical interfaces including USB. It is written in Java, however makes use of native extensions for USB
 
  78  *  support and thus is only offered on Windows.
 
  80  *  To program a device using FLIP, refer to the Atmel FLIP documentation.
 
  82  *  \subsection SSec_DFUProgrammer dfu-programmer (Linux)
 
  84  *  dfu-programmer is an open-source command line solution for the bootloader programming of Atmel devices through a
 
  85  *  USB connection, using the DFU protocol, available for download at <a>http://sourceforge.net/projects/dfu-programmer/</a>.
 
  87  *  The following example loads a HEX file into the AVR's FLASH memory using dfu-programmer:
 
  89  *  dfu-programmer at90usb1287 erase flash Mouse.hex
 
  92  *  \section Sec_API User Application API
 
  94  *  Several user application functions for FLASH and other special memory area manipulations are exposed by the bootloader,
 
  95  *  allowing the user application to call into the bootloader at runtime to read and write FLASH data.
 
  97  *  \note The APIs exposed by the DFU class bootloader are \b NOT compatible with the API exposed by the official Atmel DFU bootloader.
 
  99  *  By default, the bootloader API jump table is located 32 bytes from the end of the device's FLASH memory, and follows the
 
 103  *  #define BOOTLOADER_API_START(Index)        (void*)(((FLASHEND - 32) + (2 * Index)) / 2)
 
 104  *  void    (*BootloaderAPI_ErasePage)(uint32_t Address)               = BOOTLOADER_API_START(0);
 
 105  *  void    (*BootloaderAPI_WritePage)(uint32_t Address)               = BOOTLOADER_API_START(1);
 
 106  *  void    (*BootloaderAPI_FillWord)(uint32_t Address, uint16_t Word) = BOOTLOADER_API_START(2);
 
 107  *  uint8_t (*BootloaderAPI_ReadSignature)(uint16_t Address)           = BOOTLOADER_API_START(3);
 
 108  *  uint8_t (*BootloaderAPI_ReadFuse)(uint16_t Address)                = BOOTLOADER_API_START(4);
 
 109  *  uint8_t (*BootloaderAPI_ReadLock)(void)                            = BOOTLOADER_API_START(5);
 
 110  *  void    (*BootloaderAPI_WriteLock)(uint8_t LockBits)               = BOOTLOADER_API_START(6);
 
 112  *  #define BOOTLOADER_SIG_START               (FLASHEND - 32)
 
 113  *  #define BOOTLOADER_SIGNATURE               0xDCFB
 
 116  *  From the application the API support of the bootloader can be detected by reading the FLASH memory bytes located at address
 
 117  *  \c BOOTLOADER_SIG_START and comparing them to the value \c BOOTLOADER_SIGNATURE.
 
 119  *  \section Sec_Options Project Options
 
 121  *  The following defines can be found in this demo, which can control the demo behaviour when defined, or changed in value.
 
 125  *    <td><b>Define Name:</b></td>
 
 126  *    <td><b>Location:</b></td>
 
 127  *    <td><b>Description:</b></td>
 
 130  *    <td>SECURE_MODE</td>
 
 131  *    <td>BootloaderDFU.h</td>
 
 132  *    <td>If defined to true, the bootloader will not accept any memory commands other than a chip erase on start-up, until an
 
 133  *        erase has been performed. This can be used in conjunction with the AVR's lockbits to prevent the AVRs firmware from
 
 134  *        being dumped by unauthorized persons.</td>