1 DMBS - Dean's Makefile Build System
2 ===================================
8 The HID module provides build targets to program a target running a PJRC Teensy
9 or LUFA compatible HID class bootloader.
11 ## Importing This Module into a Makefile:
13 To use this module in your application makefile, add the following code to your
16 include $(DMBS_PATH)/hid.mk
20 This module requires the `teensy_loader_cli` utility to be available in your
21 system's `PATH` variable. The `teensy_loader_cli` utility is distributed in
22 a modified form (from PJRC) in the LUFA project's
23 [official site](http://www.lufa-lib.org/), but is also
24 made available in its original form directly from the
25 [PJRC website](https://www.pjrc.com/teensy/loader_cli.html). Note that the
26 original tool works with Teensy boards only, and not LUFA HID bootloader
29 This module requires the `hid_bootloader_cli` utility to be available in your
30 system's `PATH` variable. The `hid_bootloader_cli` Python script utility is
31 distributed in LUFA project's [official site](http://www.lufa-lib.org/).
33 This module requires the AVR-GCC compiler to be installed and available in the
34 system's `PATH` variable.
38 The following targets are supported by this module:
44 <td>Program a LUFA HID class bootloader device, using the `hid_bootloader_cli.py` Python script.</td>
48 <td>Program a LUFA HID class bootloader device's EEPROM, using the `hid_bootloader_cli.py` Python script and a shim application which is programmed into the target's flash.</td>
52 <td>Program a LUFA HID class bootloader device or Teensy board, using the `teensy_loader_cli` tool.</td>
56 <td>Program a LUFA HID class bootloader device's EEPROM, using the `teensy_loader_cli` tool and a shim application which is programmed into the target's flash.</td>
61 ## Mandatory Variables:
63 The following variables must be defined (with a `NAME = VALUE` syntax, one
64 variable per line) in the user makefile to be able to use this module:
70 <td>Name of the Atmel processor model (e.g. `at90usb1287`).</td>
74 <td>Name of the application output file prefix (e.g. `TestApplication`).</td>
79 ## Optional Variables:
81 The following variables may be defined (with a `NAME = VALUE` syntax, one
82 variable per line) in the user makefile. If not specified, a default value will
89 <td>This module has no optional variables.</td>
94 ## Provided Variables:
96 The following variables may be referenced in a user makefile (via `$(NAME)`
97 syntax) if desired, as they are provided by this module.
103 <td>This module provides no variables.</td>
110 The following macros may be referenced in a user makefile (via
111 `$(call NAME, ARG1, ARG2, ...)` syntax) if desired, as they are provided by
118 <td>This module provides no macros.</td>
125 The changes to this module since its initial release are listed below, as of the
126 DMBS version where the change was made.