comparison Bootloader/_buildvars.h @ 303:f9c406854bc2

Set DFU bootloader name Fixes #22 Each (dfu) interface may have more than one a ltsetting each with their own index and name. According to the DFU_1.1 pdf section 4.2.3, "* Alternate settings can be used by an application to access additional memory segments. In this case, it is suggested that each alternate setting employ a string descriptor to indicate the target memory segment; e.g., 'EEPROM'." Whether or not we end up using multiple memory segments it is still good to have a descriptive name incase there are other dfu devices connected. Edit: Fixed previous indentation
author Rowan Decker <Smasher816@gmail.com>
date Sun, 08 Mar 2015 16:59:34 -0700
parents fc6b5d0867b7
children 4617ef5e06f1
comparison
equal deleted inserted replaced
281:71882cd1c362 303:f9c406854bc2
30 30
31 // You can change these to give your code its own name. 31 // You can change these to give your code its own name.
32 #define STR_MANUFACTURER u"Kiibohd" 32 #define STR_MANUFACTURER u"Kiibohd"
33 #define STR_PRODUCT u"Kiibohd DFU Bootloader" 33 #define STR_PRODUCT u"Kiibohd DFU Bootloader"
34 #define STR_SERIAL u"@CHIP@" 34 #define STR_SERIAL u"@CHIP@"
35 #define STR_ALTNAME u"@BOOT_DFU_ALTNAME@"
35 36
36 37
37 // Mac OS-X and Linux automatically load the correct drivers. On 38 // Mac OS-X and Linux automatically load the correct drivers. On
38 // Windows, even though the driver is supplied by Microsoft, an 39 // Windows, even though the driver is supplied by Microsoft, an
39 // INF file is needed to load the driver. These numbers need to 40 // INF file is needed to load the driver. These numbers need to