diff options
| author | Dean Camera <dean@fourwalledcubicle.com> | 2010-09-24 06:45:11 +0000 |
|---|---|---|
| committer | Dean Camera <dean@fourwalledcubicle.com> | 2010-09-24 06:45:11 +0000 |
| commit | bd85422d2beb8b14e617839b7d05e7306df83edc (patch) | |
| tree | 0f3d77d6edb3549fafa5a6e89aea371be0697251 /LUFA/ManPages/WritingBoardDrivers.txt | |
| parent | b48095c0fbd9774413702b0226ef72926034e6c6 (diff) | |
| download | lufa-bd85422d2beb8b14e617839b7d05e7306df83edc.tar.gz lufa-bd85422d2beb8b14e617839b7d05e7306df83edc.tar.bz2 lufa-bd85422d2beb8b14e617839b7d05e7306df83edc.zip | |
Added the --suppress-bootloader-mem option to the makefile dfu target, to ensure that writes to the bootloader section of the AVR's flash memory are ignored (thanks to Axel Rohde).
Fixed incorrect command name for EEPROM memory programming in the makefile dfu-ee target.
Makefile whitespace fixes.
Diffstat (limited to 'LUFA/ManPages/WritingBoardDrivers.txt')
| -rw-r--r-- | LUFA/ManPages/WritingBoardDrivers.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/LUFA/ManPages/WritingBoardDrivers.txt b/LUFA/ManPages/WritingBoardDrivers.txt index c3371a93a..dd0ea47c7 100644 --- a/LUFA/ManPages/WritingBoardDrivers.txt +++ b/LUFA/ManPages/WritingBoardDrivers.txt @@ -18,9 +18,9 @@ * with the LUFA hardware API. To do this, the BOARD macro should be defined to the value BOARD_USER. This indicates * that the board level drivers should be located in a folder named "Board" located inside the application's folder. * - * When used, the driver stub files located in the DriverStubs folder should be copied to the user Board directory, - * and fleshed out to include the values and code needed to control the custom board hardware. Once done, the existing - * LUFA board level APIs (accessed in the regular LUFA/Drivers/Board/ folder) will redirect to the user board drivers, - * maintaining code compatibility and allowing for a different board to be selected through the project makefile with - * no code changes. + * When used, the driver stub files located in the LUFA/CodeTemplates/DriverStubs folder should be copied to the user + * Board/ directory, and fleshed out to include the values and code needed to control the custom board hardware. Once + * done, the existing LUFA board level APIs (accessed in the regular LUFA/Drivers/Board/ folder) will redirect to the + * user board drivers, maintaining code compatibility and allowing for a different board to be selected through the + * project makefile with no code changes. */ |