Bootloaders/CDC/BootloaderCDC.txt

   1 /** \file
   2  *
   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.
   5  */
   6
   7 /** \mainpage CDC Class USB AVR Bootloader
   8  *
   9  *  \section Sec_Compat Demo Compatibility:
  10  *
  11  *  The following list indicates what microcontrollers are compatible with this demo.
  12  *
  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)
  17  *
  18  *  \section Sec_Info USB Information:
  19  *
  20  *  The following table gives a rundown of the USB utilization of this demo.
  21  *
  22  *  <table>
  23  *   <tr>
  24  *    <td><b>USB Mode:</b></td>
  25  *    <td>Device</td>
  26  *   </tr>
  27  *   <tr>
  28  *    <td><b>USB Class:</b></td>
  29  *    <td>Communications Device Class (CDC)</td>
  30  *   </tr>
  31  *   <tr>
  32  *    <td><b>USB Subclass:</b></td>
  33  *    <td>Abstract Control Model (ACM)</td>
  34  *   </tr>
  35  *   <tr>
  36  *    <td><b>Relevant Standards:</b></td>
  37  *    <td>USBIF CDC Class Standard</td>
  38  *   </tr>
  39  *   <tr>
  40  *    <td><b>Supported USB Speeds:</b></td>
  41  *    <td>Full Speed Mode</td>
  42  *   </tr>
  43  *  </table>
  44  *
  45  *  \section Sec_Description Project Description:
  46  *
  47  *  This bootloader enumerates to the host as a CDC Class device (virtual serial port), allowing for AVR109
  48  *  protocol compatible programming software to load firmware onto the AVR.
  49  *
  50  *  Out of the box this bootloader builds for the AT90USB1287 with an 8KB bootloader section size, and will fit
  51  *  into 4KB of bootloader space. If you wish to alter this size and/or change the AVR model, you will need to
  52  *  edit the MCU, FLASH_SIZE_KB and BOOT_SECTION_SIZE_KB values in the accompanying makefile.
  53  *
  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.
  56  *
  57  *  \section Sec_Installation Driver Installation
  58  *
  59  *  After running this bootloader for the first time on a new computer, you will need to supply the .INF
  60  *  file located in this bootloader project's directory as the device's driver when running under Windows.
  61  *  This will enable Windows to use its inbuilt CDC drivers, negating the need for custom drivers for the
  62  *  device. Other Operating Systems should automatically use their own inbuilt CDC-ACM drivers.
  63  *
  64  *  \section Sec_HostApp Host Controller Application
  65  *
  66  *  This bootloader is compatible with the open source application AVRDUDE, Atmel's AVRPROG, or other
  67  *  applications implementing the AVR109 protocol, which is documented on the Atmel website as an application
  68  *  note.
  69  *
  70  *  \subsection SSec_AVRDude AVRDUDE (Windows, Mac, Linux)
  71  *
  72  *  AVRDude is a free, cross-platform and open source command line programmer for Atmel and third party AVR
  73  *  programmers. It is available on the the Windows platform as part of the "WinAVR" package, or on other systems
  74  *  either from a build from the official source code, or in many distributions as a precompiled binary package.
  75  *
  76  *  To load a new HEX file with AVRDude, specify "AVR109" as the programmer, with the allocated COM port. On Windows
  77  *  platforms this will be a COMx port name:
  78  *  \code
  79  *  avrdude -c AVR109 -p at90usb1287 -P COM0 -U flash:w:Mouse.hex
  80  *  \endcode
  81  *
  82  *  On Linux systems, this will typically be a /dev/ttyACMx port name:
  83  *  \code
  84  *  avrdude -c AVR109 -p at90usb1287 -P /dev/ttyACM0 -U flash:w:Mouse.hex
  85  *  \endcode
  86  *
  87  *  Refer to the AVRDude project documentation for additional usage instructions.
  88  *
  89  *  \section Sec_API User Application API
  90  *
  91  *  Several user application functions for FLASH and other special memory area manipulations are exposed by the bootloader,
  92  *  allowing the user application to call into the bootloader at runtime to read and write FLASH data.
  93  *
  94  *  By default, the bootloader API jump table is located 32 bytes from the end of the device's FLASH memory, and follows the
  95  *  following layout:
  96  *
  97  *  \code
  98  *  #define BOOTLOADER_API_TABLE_SIZE          32
  99  *  #define BOOTLOADER_API_TABLE_START         ((FLASHEND + 1UL) - BOOTLOADER_API_TABLE_SIZE)
 100  *  #define BOOTLOADER_API_CALL(Index)         (void*)((BOOTLOADER_API_TABLE_START + (Index * 2)) / 2)
 101  *
 102  *  void    (*BootloaderAPI_ErasePage)(uint32_t Address)               = BOOTLOADER_API_CALL(0);
 103  *  void    (*BootloaderAPI_WritePage)(uint32_t Address)               = BOOTLOADER_API_CALL(1);
 104  *  void    (*BootloaderAPI_FillWord)(uint32_t Address, uint16_t Word) = BOOTLOADER_API_CALL(2);
 105  *  uint8_t (*BootloaderAPI_ReadSignature)(uint16_t Address)           = BOOTLOADER_API_CALL(3);
 106  *  uint8_t (*BootloaderAPI_ReadFuse)(uint16_t Address)                = BOOTLOADER_API_CALL(4);
 107  *  uint8_t (*BootloaderAPI_ReadLock)(void)                            = BOOTLOADER_API_CALL(5);
 108  *  void    (*BootloaderAPI_WriteLock)(uint8_t LockBits)               = BOOTLOADER_API_CALL(6);
 109  *
 110  *  #define BOOTLOADER_MAGIC_SIGNATURE_START   (BOOTLOADER_API_TABLE_START + (BOOTLOADER_API_TABLE_SIZE - 2))
 111  *  #define BOOTLOADER_MAGIC_SIGNATURE         0xDCFB
 112  *
 113  *  #define BOOTLOADER_CLASS_SIGNATURE_START   (BOOTLOADER_API_TABLE_START + (BOOTLOADER_API_TABLE_SIZE - 4))
 114  *  #define BOOTLOADER_CDC_SIGNATURE           0xCDC1
 115  *
 116  *  #define BOOTLOADER_ADDRESS_START           (BOOTLOADER_API_TABLE_START + (BOOTLOADER_API_TABLE_SIZE - 8))
 117  *  #define BOOTLOADER_ADDRESS_LENGTH          4
 118  *  \endcode
 119  *
 120  *  \subsection SSec_API_MemLayout Device Memory Map
 121  *  The following illustration indicates the final memory map of the device when loaded with the bootloader.
 122  *
 123  *  \verbatim
 124  *  +----------------------------+ 0x0000
 125  *  |                            |
 126  *  |                            |
 127  *  |                            |
 128  *  |                            |
 129  *  |                            |
 130  *  |                            |
 131  *  |                            |
 132  *  |                            |
 133  *  |      User Application      |
 134  *  |                            |
 135  *  |                            |
 136  *  |                            |
 137  *  |                            |
 138  *  |                            |
 139  *  |                            |
 140  *  |                            |
 141  *  +----------------------------+ FLASHEND - BOOT_SECTION_SIZE
 142  *  |                            |
 143  *  |   Bootloader Application   |
 144  *  | (Not User App. Accessible) |
 145  *  |                            |
 146  *  +----------------------------+ FLASHEND - 96
 147  *  |   API Table Trampolines    |
 148  *  | (Not User App. Accessible) |
 149  *  +----------------------------+ FLASHEND - 32
 150  *  |    Bootloader API Table    |
 151  *  |   (User App. Accessible)   |
 152  *  +----------------------------+ FLASHEND - 8
 153  *  |   Bootloader ID Constants  |
 154  *  |   (User App. Accessible)   |
 155  *  +----------------------------+ FLASHEND
 156  *  \endverbatim
 157  *
 158  *  Bootloaders reporting a device release revision number of 1.00 or greater are bootloader API enabled. From the application
 159  *  the API support of the bootloader can be detected by reading the FLASH memory bytes located at address \c BOOTLOADER_MAGIC_SIGNATURE_START
 160  *  and comparing them to the value \c BOOTLOADER_MAGIC_SIGNATURE. The class of bootloader can be determined by reading the
 161  *  FLASH memory bytes located at address \c BOOTLOADER_CLASS_SIGNATURE_START and comparing them to the value \c BOOTLOADER_CDC_SIGNATURE.
 162  *  The start address of the bootloader can be retrieved by reading the bytes of FLASH memory starting from address \c BOOTLOADER_ADDRESS_START.
 163  *
 164  *  \section Sec_Options Project Options
 165  *
 166  *  The following defines can be found in this demo, which can control the demo behaviour when defined, or changed in value.
 167  *
 168  *  <table>
 169  *   <tr>
 170  *    <td><b>Define Name:</b></td>
 171  *    <td><b>Location:</b></td>
 172  *    <td><b>Description:</b></td>
 173  *   </tr>
 174  *   <tr>
 175  *    <td>NO_BLOCK_SUPPORT</td>
 176  *    <td>AppConfig.h</td>
 177  *    <td>Define to disable memory block read/write support in the bootloader, requiring all reads and writes to be made
 178  *        using the byte-level commands.</td>
 179  *   </tr>
 180  *   <tr>
 181  *    <td>NO_EEPROM_BYTE_SUPPORT</td>
 182  *    <td>AppConfig.h</td>
 183  *    <td>Define to disable EEPROM memory byte read/write support in the bootloader, requiring all EEPROM reads and writes
 184  *        to be made using the block-level commands.</td>
 185  *   </tr>
 186  *   <tr>
 187  *    <td>NO_FLASH_BYTE_SUPPORT</td>
 188  *    <td>AppConfig.h</td>
 189  *    <td>Define to disable FLASH memory byte read/write support in the bootloader, requiring all FLASH reads and writes
 190  *        to be made using the block-level commands.</td>
 191  *   </tr>
 192  *   <tr>
 193  *    <td>NO_LOCK_BYTE_WRITE_SUPPORT</td>
 194  *    <td>AppConfig.h</td>
 195  *    <td>Define to disable lock byte write support in the bootloader, preventing the lock bits from being set programmatically.</td>
 196  *   </tr>
 197  *  </table>
 198  */
 199