Page 17 of 28
© Cambridge Silicon Radio Limited 2014
CS-310152-UGP1
www.csr.com
BlueC
or
e
A
D
K
3
.0
Subw
oo
fer
U
s
er
G
uide
4.4.2. Required LED Patterns
For the ADK 3.0 Subwoofer application, an LED pattern must exist for each state that has been implemented; this
allows the state manager to display a different LED pattern for each state (if required). Table 5.1 lists each
application state.
Each LED pattern must immediately follow the previous. The application parses the LED pattern configuration data
during the initialisation state.
The order the LED patterns are entered into the configuration data is very important, it must follow the state.
Table 4.9 lists the order LED patterns must appear for each application state:
State
Pattern Index
Description
subwoofer_init
0
LED Pattern for subwoofer_init
subwoofer_discoverable
1
LED Pattern for subwoofer_discoverable
subwoofer_connecting
2
LED Pattern for subwoofer_connecting
subwoofer_connected
3
LED Pattern for subwoofer_connected
subwoofer_open
4
LED Pattern for subwoofer_open
subwoofer_streaming
5
LED Pattern for subwoofer_streaming
Table 4.9: Order LED Patterns Must be Stored to the LED Configuration Data
4.5.
Button Configuration (PSKEY_USR4)
The button configuration can be used to modify the buttons supported by the ADK 3.0 Subwoofer application,
4 buttons can be configured for the application.
Table 4.10 lists the data structure required to configure the buttons supported by the ADK 3.0 Subwoofer application.
Word(s)
Bit(s)
Description
1
[0:15]
Long press timer
2
[0:15]
Enter DUT mode timer
3
[0:7]
PIO for
EQ select
button
[8:15]
PIO for
Start discoverable mode
button
4
[0:7]
PIO for
Volume down
button
[8:15]
PIO for
Volume up
button
5
[0:7]
Single PIO when held high to enter continuous TX DUT mode
[8:15]
Single PIO when held high to enter DUT mode
6-7
[0:31]
PIO bitmask for entering continuous DUT mode
8-9
[0:31]
PIO bitmask for entering DUT mode
Table 4.10: Structure Used for the Button Configuration Data
