diff options
| author | Drashna Jaelre <drashna@live.com> | 2019-08-02 14:02:40 -0700 |
|---|---|---|
| committer | skullydazed <skullydazed@users.noreply.github.com> | 2019-08-30 15:01:52 -0700 |
| commit | cf4575b94a3c65e6535a159fc71fc885aebc2620 (patch) | |
| tree | 2354f2b7a200e02246a564afefedc32357e62b8e /lib/lufa/LUFA/DoxygenPages/ProgrammingApps.txt | |
| parent | 75ee8df19e0f14ba466f41ab673dde2fe2fdae9c (diff) | |
| download | qmk_firmware-cf4575b94a3c65e6535a159fc71fc885aebc2620.tar.gz qmk_firmware-cf4575b94a3c65e6535a159fc71fc885aebc2620.zip | |
Fix the LUFA lib to use a submodule instead of just files (#6245)
* Remove LUFA files
* Update descriptions for newer version of LUFA
* Create PR6245.md
* Fix CDC(Serial) type errors
* Fix missed merge conflict for AUDIO_DTYPE_CSInterface
Diffstat (limited to 'lib/lufa/LUFA/DoxygenPages/ProgrammingApps.txt')
| -rw-r--r-- | lib/lufa/LUFA/DoxygenPages/ProgrammingApps.txt | 27 |
1 files changed, 0 insertions, 27 deletions
diff --git a/lib/lufa/LUFA/DoxygenPages/ProgrammingApps.txt b/lib/lufa/LUFA/DoxygenPages/ProgrammingApps.txt deleted file mode 100644 index 653b4ad04..000000000 --- a/lib/lufa/LUFA/DoxygenPages/ProgrammingApps.txt +++ /dev/null | |||
| @@ -1,27 +0,0 @@ | |||
| 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 | /** \page Page_ProgrammingApps Programming an Application into a USB AVR | ||
| 8 | * | ||
| 9 | * Once you have built an application, you will need a way to program in the resulting ".HEX" file (and, if your | ||
| 10 | * application uses EEPROM variables with initial values, also a ".EEP" file) into your USB AVR. Normally, the | ||
| 11 | * reprogramming of an AVR device must be performed using a special piece of programming hardware, through one of the | ||
| 12 | * supported AVR programming protocols - ISP, HVSP, HVPP, JTAG, dW or PDI. This can be done through a custom programmer, | ||
| 13 | * a third party programmer, or an official Atmel AVR tool - for more information, see the <a>atmel.com</a> website. | ||
| 14 | * | ||
| 15 | * Alternatively, you can use the bootloader. From the Atmel factory, each USB AVR comes preloaded with the Atmel | ||
| 16 | * DFU (Device Firmware Update) class bootloader, a small piece of AVR firmware which allows the remainder of the | ||
| 17 | * AVR to be programmed through a non-standard interface such as the serial USART port, SPI, or (in this case) USB. | ||
| 18 | * Bootloaders have the advantage of not requiring any special hardware for programming, and cannot usually be erased | ||
| 19 | * or broken without an external programming device. They have disadvantages however; they cannot change the fuses of | ||
| 20 | * the AVR (special configuration settings that control the operation of the chip itself) and a small portion of the | ||
| 21 | * AVR's FLASH program memory must be reserved to contain the bootloader firmware, and thus cannot be used by the | ||
| 22 | * loaded application. | ||
| 23 | * | ||
| 24 | * If you wish to use the DFU bootloader to program in your application, refer to your DFU programmer's documentation. | ||
| 25 | * Atmel provides a free utility called FLIP which is USB AVR compatible, and an open source (Linux compatible) | ||
| 26 | * alternative exists called "dfu-programmer". | ||
| 27 | */ | ||
