Each example project for a device can support multiple configurations (i.e a. keys only, b. with rotors and sliders c.16 channel etc…). The configuration sets determine the configuration options for using the library and also the right library variant to link with the project.
Naming convention: <vP>g<Q>_<CH>qt_k_<RS>rs |
||
---|---|---|
Field Name |
Values |
Comments |
vP |
v1, v3, xmega, uc3a, uc3b, uc3c |
VersionP of the core AVR device supported by this library variant |
Q |
1 to 6 |
GroupQ of the core AVR device supported by this library variant |
CH |
4, 8, 12, 16, 32 |
Total number of channels supported by each library. |
RS |
1, 2, 3, 4, 8 |
Total number of rotors / sliders supported for the respective channel counts mentioned in previous row. |
Naming convention: <avrP>g<Q>_<CH>qt_k_<RS>rs |
||
---|---|---|
Field Name |
Values |
Comments |
avrP |
avr25, avr4, avr 51, avr5, xmega, uc3a, uc3b, uc3c |
VersionP of the core AVR device supported by this library variant |
Q |
1 to 6 |
GroupQ of the core AVR device supported by this library variant |
CH |
4, 8, 12, 16, 32 |
Total number of channels supported by each library. |
RS |
1, 2, 3, 4, 8 |
Total number of rotors / sliders supported for the respective channel counts mentioned in previous row. |
Depending on your need, you need to select the right configuration required and build the project.