_äìÉ`çêÉ»
BlueVOX2 Configurator User Guide September 2006
CSR Cambridge Science Park Milton Road Cambridge CB4 0WH United Kingdom Registered in England 4187346
Part Part o f th e BlueVOX BlueVOX2 2 Audio Solutio n CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Tel: +44 (0)1223 692000 Fax: +44 (0)1223 692001 www.csr.com
Contents
Contents 1
Introduction Introduction .................................................................................................................................................... .................................................................................................................................................... 3 1.1 General.................................................................................................................................................... General.................................................................................................................................................... 3
2
Description Description of Bl ueVOX ueVOX Configurator Configurator Workspace...................................................................................... Workspace...................................................................................... 4
3
2.1 Functionalit Functionality y ............................................................................................................................................ ............................................................................................................................................ 5 2.1.1 File File Menu ..................................................................................................................................... ..................................................................................................................................... 5 2.1.2 Output Output Menu Menu ................................................................................................................................ ................................................................................................................................ 5 2.1.3 Properties Menu........................................................................................................................... Menu........................................................................................................................... 6 2.1.4 View Menu ................................................................................................................................... ................................................................................................................................... 6 2.1.5 Help Menu.................................................................................................................................... Menu.................................................................................................................................... 6 Opening Opening a Default Default Configuration ................................................................................................................... ............................................................................................................... 7
4
Advan Ad van ced Con fi gu rat io n Paramet Par amet ers ........................................................................................................... ........................................................................................................... 8
5
EEPROM EEPROM Initialisati on.................................................................................................................................... on.................................................................................................................................... 9 5.1 Downloading Persistent Store Values to EEPROM EEPROM ............................................................................... ............................................................................... 10
6
Document References References ................................................................................................................................. ................................................................................................................................. 11
App end ix A
Description of PS Keys............................................................................................................ Keys............................................................................................................ 12
A.1 Battery Configuration............................................................................................................................. Configuration............................................................................................................................. 14 A.2 Button Configuration.............................................................................................................................. Configuration.............................................................................................................................. 15 A.3 Button Sequence Configuration............................................................................................................. Configuration............................................................................................................. 15 A.4 Supported Features............................................................................................................................... Features............................................................................................................................... 16 A.5 PIO Input Configuration ......................................................................................................................... ......................................................................................................................... 16 A.6 HFP 1.5 Feature Configuration.............................................................................................................. Configuration.............................................................................................................. 17 A.7 Enabling HFP 1.5 Support..................................................................................................................... Support..................................................................................................................... 18 A.8 Headset Headset Timeouts Timeouts ................................................................................................................................. ................................................................................................................................. 19 A.9 Radio Configuration............................................................................................................................... Configuration............................................................................................................................... 20 A.10 NiMH Charger Configuration ................................................................................................................. ................................................................................................................. 21 A.11 Feature Configuration............................................................................................................................ Configuration............................................................................................................................ 22 A.12 Audio A.12 Audio Gain Mapping .............................................................................................................................. .............................................................................................................................. 28 A.13 LED State Configuration........................................................................................................................ Configuration........................................................................................................................ 33 A.14 LED Event Event Configuration Configuration ....................................................................................................................... ....................................................................................................................... 36 A.15 LED Filter Configuratio Configuration n ........................................................................................................................ ........................................................................................................................ 39 A.16 Event Configuration ............................................................................................................................... ............................................................................................................................... 44 A.17 Tone Configuration ................................................................................................................................ ................................................................................................................................ 46 A.18 PIO Output Configurati Configuration on ...................................................................................................................... ...................................................................................................................... 46 A.19 Tri Colour LED Information.................................................................................................................... Information.................................................................................................................... 48 A.20 Power Power Table Settings Settings ............................................................................................................................ ............................................................................................................................ 49 App end ix B
BlueVOX2 BlueVOX2 System System Events ....................................................................................................... ....................................................................................................... 51
App end ix C
BlueVOX2 BlueVOX2 Tones ...................................................................................................................... ...................................................................................................................... 54
App end ix D
BlueVOX2 BlueVOX2 Headset States ....................................................................................................... ....................................................................................................... 56
Terms Terms and Definitions Definitions ... ........................................................................................................................................ 57 Document Document History ... ............................................................................................................................................... 58
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 2 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Contents
Contents 1
Introduction Introduction .................................................................................................................................................... .................................................................................................................................................... 3 1.1 General.................................................................................................................................................... General.................................................................................................................................................... 3
2
Description Description of Bl ueVOX ueVOX Configurator Configurator Workspace...................................................................................... Workspace...................................................................................... 4
3
2.1 Functionalit Functionality y ............................................................................................................................................ ............................................................................................................................................ 5 2.1.1 File File Menu ..................................................................................................................................... ..................................................................................................................................... 5 2.1.2 Output Output Menu Menu ................................................................................................................................ ................................................................................................................................ 5 2.1.3 Properties Menu........................................................................................................................... Menu........................................................................................................................... 6 2.1.4 View Menu ................................................................................................................................... ................................................................................................................................... 6 2.1.5 Help Menu.................................................................................................................................... Menu.................................................................................................................................... 6 Opening Opening a Default Default Configuration ................................................................................................................... ............................................................................................................... 7
4
Advan Ad van ced Con fi gu rat io n Paramet Par amet ers ........................................................................................................... ........................................................................................................... 8
5
EEPROM EEPROM Initialisati on.................................................................................................................................... on.................................................................................................................................... 9 5.1 Downloading Persistent Store Values to EEPROM EEPROM ............................................................................... ............................................................................... 10
6
Document References References ................................................................................................................................. ................................................................................................................................. 11
App end ix A
Description of PS Keys............................................................................................................ Keys............................................................................................................ 12
A.1 Battery Configuration............................................................................................................................. Configuration............................................................................................................................. 14 A.2 Button Configuration.............................................................................................................................. Configuration.............................................................................................................................. 15 A.3 Button Sequence Configuration............................................................................................................. Configuration............................................................................................................. 15 A.4 Supported Features............................................................................................................................... Features............................................................................................................................... 16 A.5 PIO Input Configuration ......................................................................................................................... ......................................................................................................................... 16 A.6 HFP 1.5 Feature Configuration.............................................................................................................. Configuration.............................................................................................................. 17 A.7 Enabling HFP 1.5 Support..................................................................................................................... Support..................................................................................................................... 18 A.8 Headset Headset Timeouts Timeouts ................................................................................................................................. ................................................................................................................................. 19 A.9 Radio Configuration............................................................................................................................... Configuration............................................................................................................................... 20 A.10 NiMH Charger Configuration ................................................................................................................. ................................................................................................................. 21 A.11 Feature Configuration............................................................................................................................ Configuration............................................................................................................................ 22 A.12 Audio A.12 Audio Gain Mapping .............................................................................................................................. .............................................................................................................................. 28 A.13 LED State Configuration........................................................................................................................ Configuration........................................................................................................................ 33 A.14 LED Event Event Configuration Configuration ....................................................................................................................... ....................................................................................................................... 36 A.15 LED Filter Configuratio Configuration n ........................................................................................................................ ........................................................................................................................ 39 A.16 Event Configuration ............................................................................................................................... ............................................................................................................................... 44 A.17 Tone Configuration ................................................................................................................................ ................................................................................................................................ 46 A.18 PIO Output Configurati Configuration on ...................................................................................................................... ...................................................................................................................... 46 A.19 Tri Colour LED Information.................................................................................................................... Information.................................................................................................................... 48 A.20 Power Power Table Settings Settings ............................................................................................................................ ............................................................................................................................ 49 App end ix B
BlueVOX2 BlueVOX2 System System Events ....................................................................................................... ....................................................................................................... 51
App end ix C
BlueVOX2 BlueVOX2 Tones ...................................................................................................................... ...................................................................................................................... 54
App end ix D
BlueVOX2 BlueVOX2 Headset States ....................................................................................................... ....................................................................................................... 56
Terms Terms and Definitions Definitions ... ........................................................................................................................................ 57 Document Document History ... ............................................................................................................................................... 58
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 2 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Introduction
1
Introduction
BlueVOX is the generic name for CSR’s mono headset solutions. BlueVOX provides a fast-track Bluetooth headset solution allowing manufacturers to rapidly develop their own unique mono headset designs. This document describes BlueVOX2 Configurator. BlueVOX2 Configurator is a user-friendly tool developed to configure the Headset V4 and Headset V4 Refresh mono headset software to suit the manufacture’s Human Machine Interface (HMI) design. The Headset v4 and Headset v4 Refresh software is designed to run on CSR’s BlueCore4-Audio ROM and BlueCore3-Audio Flash chips. Note: BlueCore4-Audio ROM implementations require require an external EEPROM to store the Persistent Store values that configure the HMI. Chapter 5 describes how to initialise the EEPROM for use with the Headset V4 software.
To allow manufacturers to distinguish their final product in the market place the Headset v4 and Headset V4 Refresh software is designed with a highly configurable HMI. Developers can readily:
1.1
Define PIO functionality to suit their hardware design. Associate device control with different button configurations. Define unique LED patterns and audio tones to indicate:
User actions
System states
System events
General
The BlueVOX Configurator can be used to customise the full range of Headset v4 and Headset V4 Refresh HMI settings. PS Key configuration settings can be read into the BlueVOX Configurator from the default options, a previously saved user-generated . ps r file or a connected device. Default configurations are provided for two, three and four-button headset designs. When BlueVOX Configurator is opened, developers can select the button configuration that matches their hardware design and suitable default settings for the selected hardware design are loaded into the BlueVOX Configurator application. Note: The default button assignment, functionality and user user events can then be viewed in the User Events tab.
The default settings provide a viable HMI that can be used as supplied or can be customised, by the manufacturer, using the BlueVOX Configurator advanced option. Settings defined in the BlueVOX Configurator can be saved as a . ps r file or downloaded directly to the Persistent Store of a connected device.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 3 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of BlueVOX Configurator Workspace
2
Descri Descri ptio n of BlueV Blu eVOX OX Conf igur ator Work space
BlueVox Configurator supports two modes of operation:
Simple mode: allows mode: allows configuration values for default two, three and four-button headsets to be loaded into the BlueVOX Configurator, and the input and output PIOs corresponding to the hardware design to be assigned. allows developers access to the full range of configuration parameters supported by Ad vanced van ced mode: mo de: allows the Headset V4 software.
The configuration parameters in BlueVOX Configurator can be wriiten to a . ps r file or downloaded to a connected device in both modes. Menu Bar
Buttons
Workspace
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Debug Output Pane
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 4 of 58
Description of BlueVOX Configurator Workspace
2.1
Functionality
The full functionality provided by BlueVOX Configurator is accessed through menus in the menu bar. Buttons are also provided to support the most commonly required functions. This section describes the menus, menu items and their functions.
2.1.1
File Fil e Menu
The File menu contains:
Open from Device : loads the configuration settings on a co nnected device into the BlueVOX Configurator and displays them in the advanced vie w. Note: A suitable connection to the device is required and and the appropriate transport transport method must be set using Transport from the Properties menu. See section 2.1.3. 2.1.3.
Open from Default: loads configuration parameters for the default button options listed i n a submenu:
Open Two Button: loads default configuration settings for a two-button headset into BlueVOX
Configurator.
Open Three Butt on: loads default configuration settings for a three-button headset into BlueVOX
Configurator.
Open Open Four B utton: loads default configuration settings for a four-button headset into BlueVOX
Configurator.
Open from PSR file: loads configuration settings from a .
ps r file. An Open dialogue box allows the user
to browse to a location and select the . ps r file to be used.
Exit: Closes the BlueVOX Configurator application. Note: Exit does Exit does not automatically save changes made to values in the BlueVOX Configurator.
Buttons displayed on the left of the BlueVOX Configurator application window also provide Open from Default , Open from File and Open from Device functionality.
2.1.2 2.1.2
Output Outp ut Menu
The Output menu contains:
Write PSR File: Allows the currently displayed settings to be saved as a .
ps r file.
Note: A Save As dialogue As dialogue opens. Select the location to save the file and enter a filename then click Save to Save to write the . ps r file to the selected location.
Write to Device: Downloads the currently displayed settings to a connected device. Note: A suitable connection to the device is required and and the appropriate transport transport method must be set using Transport from the Properties menu. See section 2.1.3. 2.1.3.
Buttons displayed on the left of the BlueVOX Configurator application window also provide Write PSR and Write Device functionality.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 5 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of BlueVOX Configurator Workspace
2.1.3
Properti es Menu
The Properties menu contains:
Transport: Allows the transport protocol used to communicate with a connected BlueCore device to be
defined. Selecting Transport opens a Choose Transport window:
_ ä ì É ` ç ê É
Note: The application’s default transport as shipped is BCSP, Serial Port Com1 and Baud Rate 115200. If the Transport method is changed, the newly applied transport method is retained until manually changed.
2.1.4
View Menu
The View menu contains:
Ad van ced : Select this option to display the additional tabs available for advanced configuration.
The advanced configuration tabs can also be accessed usi ng the Ad vanc ed Vi ew button.
2.1.5
Help Menu
The Help menu contains:
Ab ou t: Displays version information about the BlueVOX Configurator.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 6 of 58
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Opening a Default Configuration
3
Opening a Default Configuration
When BlueVOX Configurator is opened for the first time, a simple view of the application is displayed. Note: Subsequently BlueVOX Configurator opens in the simple or advanced view depending on the active mode when the application is closed.
To open a default configuration for a two, three or four-button device select the required option button on the left of the Configurator screen. The default settings are loaded into the BlueVOX Configurator and displayed in the simple view:
The simple view provides access to a subset of the configuration parameters that allow engineers to set output and input PIOs to match their hardware design and to select the the device platform, V4 version or V4 Refresh version. A view-only User Events tab allows the engineer to see details of the user event configuration. To adjust these or other configuration settings click the Ad van ced View button.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 7 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Advanced Configuration Parameters
4
Advanced Configuration Parameters
To access the full range of configuration options click the Ad vanc ed Vi ew button or select Ad van ced from the View menu. The advanced view includes 11 tabs that group related configuration parameters and provide a user-friendly interface. When set as required, parameters configured in the BlueVOX Configurator can be written to a . ps r file or downloaded directly to a connected device.
_ ä ì É ` ç ê É
The parameters set in the BlueVOX Configurator tabs map to PS Keys that control the Headset v4 software’s HMI configuration. The PS Keys and the parameters they hold are described in Appendix A To edit User Event, Leds (States), Leds (Events), Leds (Filter) and Audio Tones tabs click on an entry. An editor window opens allowing an existing entry to be adjusted or a new entry created.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 8 of 58
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
EEPROM Initialisation
5
EEPROM Initialisation
When using BlueCore4-Audio ROM to implement the Headset v4 software, a small external EEPROM is required to store the HMI configuration data. This chapter describes ho w to initialise the EEPROM so that BlueCore can read and write data to the EEPROM correctly. The development engineer must write a special header into the EEPROM to inform the BlueCore device which type of EEPROM is being used. Note: CSR’s BlueCore4-Audio ROM is compatible with EEPROM devices from many different manufacturers and with many different capacities.
e2write is a command line application that initialis es an external EEPROM. e2write is included in the BlueSuite Development Tools download available from the Headset section of www.csrsupport.com. The syntax for this application is: e2write –DEVICE Log2Bytes AddrMask 2
For I C EEPROM devices manufactured by ST, Rohm and Microchip, the appropriate Log2Bytes AddrMask parameters depend on the memory capacity shown in Table 5.1. Device size (kbit)
16
512
Device
e2_Device parameters
Manufacturer
Part numb er
Rohm
BR24E16
ST
ST24E16 ST25E16
Microchip
24AA515 24LC515 24FC515
Log2Byt es
Addr Mask
11
0
16
4
Table 5.1: e2write Parameters fo r EEPROMs Manufactu red by Rohm, ST and Microch ip For all other common EEPROM devices, the Log2Bytes AddrMask parameters depend on the memory capacity shown in Table 5.2. e2_Device Parameters Device size (kbit)
Log 2Bytes
Addr Mask
1
7
0
2
8
0
4
9
1
8
10
3
16
11
7
32
12
0
64
13
0
128
14
0
256
15
0
512
16
0
1024
17
1
Table 5.2: e2write Parameters for EEPROMs fro m All Other Manufacturers
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 9 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
EEPROM Initialisation
To ini tialis e the EEPROM: 1.
Download the BlueSuite Development Tools from the Headset section ofwww.csrsupport.com. Unzip the downloaded file into a new folder.
2.
Power On the headset board.
3.
Make an SPI connection between the headset board and the parallel port of the PC (also known as the printer port).
4.
Open a command prompt and change directory to the folder containing thee2wr i t e application.
5.
Look up the correct values of Log2Byt es and Addr Mask for the EEPROM device. Refer to Table 5.1 and Table 5.2 for details.
6.
Enter the e2wr i t e syntax replacing Log2Byt es and Addr Mask with the correct values for the appropriate EEPROM device. For example, to initialise an ST24E16 EEPROM device enter: e2write -DEVICE 11 0
The EEPROM is now initialised and is suitable for use as the Persistent Store.
5.1
Downlo ading Persi stent Store Values to EEPROM
When the EEPROM is initialised, the Persistent Store settings for the headset can be downloaded to it. This is done using the PSTool utility. Both the system . ps r file and the HMI . ps r file generated using BlueVOX Configurator must be downloaded. Note: The PSTool utility is shipped as part of BlueLab or can be downloaded from the CSR support website.
To download the Persistent Store settings: 1.
Make an SPI connection to the headset board.
2.
Open the PSTool utility.
3.
Select SPI BCCMD and the port to connect to in the Choose Transport dialogue. ClickOK .
4.
Select Merge from the File Menu and select the system . ps r file to be downloaded. Click Open . Repeat to download the HMI . ps r file. Note: The syst em. psr file is located in the BlueVOX Configurator install directory.
A more detailed description of the PSTool utility and the merge facility is available in the PSTool User Guide (CSR ref: blab-ug-008P) which can be downloaded from www.csrsupport.com.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 10 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Document References
6
Document References
Document
Reference
PSTool User Guide
blab-ug-008P
BlueVOX QuickStart Guide
bcore-ug-016P
BlueCore4-Headset Software Release Note Headset V4
bcore-srn-081P
BlueCore4-Headset Software Release Note Headset V4 Refresh RC4
bcore-srn-087P
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 11 of 58
Description of PS Keys
Appendix A
Description of PS Keys
Table 5.1 describes the Persistent Store Keys dedicated to the configuration in the Bluecore4-Headset application. PS Key
Descripti on
Units
USR0
Battery Configuration
Structure
See Appendix A.1.
USR1
Button Configuration
Structure
See Appendix A.2.
USR2
Button Sequence Configuration
Structure
See Appendix A.3.
USR3
HFP Supported Features
uint16
See Appendix A.4.
USR4
PIO Input configuration
Uint16
See Appendix A.5.
USR5
HFP 1.5 Features Enabled
Structure
See Appendix A.6.
USR6
Timers/Counters
structure
See Appendix A.8
USR7
Unused
n/a
n/a
n/a
n/a
USR8
Unused
n/a
n/a
n/a
n/a
USR9
Unused
n/a
n/a
n/a
n/a
USR10
Stores whether the vo l buttons are inverted or not
True/false
false
This key is written to by the application when the volume orientation is changed i.e. to allow users to swap the vol+ and vol- buttons.
USR11
Unused
n/a
n/a
n/a
n/a
USR12
Unused
n/a
n/a
n/a
n/a
USR13
Radio Configuration
Structure
See Appendix A.9.
USR14
NiMH Battery Charger Configuration
Structure
See Appendix A.10.
USR15
Feature Configuration
Structure
See Appendix A.11.
USR16
Audio Gain Mapping
Structure
See Appendix A.12.
USR17
Number of LED Filters
Integer
USR18
LED Filter Definition
Structure
USR19
Number of LED State Definitions
Integer
USR20
LED State Definition
Structure
USR21
Number of LED Event Definitions
Integer
USR22
LED Event Definitions
Structure
CS-110372-UGP1
Valid Range
0-20
Default Value
4
Notes
Defines the number of LED filters used by the application, see Appendix A.15. See Appendix A.15.
0-13
8
Defines the number of LED States used by the application. See Appendix A.13. See Appendix A.13.
0-20
8
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Defines the number of LED Events. See Appendix A.14. See Appendix A.14.
Page 12 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
PS Key
Descripti on
Units
Valid Range
USR23
System Event Configuration A
Structure
Defines configuration of up to 20 System Events. See Appendix A.16.
USR24
System Event Configuration B
Structure
Defines configuration of up to another 20 System Events. See Appendix A.16.
USR25
Number of Event Tones
Integer
USR26
Event Tone configuration
Structure
See Appendix A.17.
USR27
PIO Output Setup
Structure
See Appendix A.18.
USR28
Tri colour LED information
Structure
See Appendix A.19.
USR29
Last Used AG
BDADDR
Stores the Bluetooth Address of the last device connected with the headset.
USR30
Default AG
BDADDR
Stores the Bluetooth Address of the first device paired with the headset (after the last reset).
USR31
Configuration ID
Integer
Holds the ID of the required default configuration stored in constant space.
HFP_POWER_TABLE
Power Table Settings
Structure
See Appendix A.20.
0-40
Default Value
20
Notes
Stores the number of Event Tones defined in USR26.
Table A.1: Descripti on of PS Keys used for B lueVox2
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 13 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.1
Bat ter y Conf ig ur ati on
PS Key USR0 holds data defining the battery monitoring parameters. The parameters are held in the following bit fields: Label
Divider Ratio
Minimum Threshold
Shutdown Threshold
Gas Gauge Level 1
Type
uint16
uint16 (D15-D8)
(D7-D0)
uint16 (D15-D8)
Range
200-1000, 0.2-1.0
0-5100 (mV in +20mV steps)
0-5100 (mV in +20mV steps)
0-5100mV (mV in +20mV steps)
Default Value
405 (0x0195)
165 (0x00a5)
150 (0x0096)
170 (0x00aa)
Gas Gauge Level 2
Gas Gauge Level 3
Unused
Monitor ing period
Reminder Time
(D7-D0)
uint16 (D15-D8)
(D7-D0)
uint16 (D15-D8)
(D7-D0)
0-5100mV (mV in +20mV steps)
0-5100mV (mV in +20mV steps)
0
1-255 secs
1-255 secs
185 (0x00b9)
200 (0x00c8)
0
30 (0x001e )
5 (0x0005)
Table A.2: PS Key USR0 – Battery Conf igur ation Bit Field s Notes: (1) (2)
(3)
(4)
(5)
(6)
(7)
The Battery monitoring will occur every Monitoring Period time. If the battery voltage is below Shutdown threshold then the headset will perform a clean disconnect and will power off. If the battery voltage is above Shutdown threshold and below Minimum threshold then eventBatteryLow will be reported. If the battery voltage is above Minimum threshold and below Gas Gauge Level 1 then the headset will report eventbatteryOK and EventGasGauge0 If the battery voltage is above Gas Gauge Level 1 and below Gas Gauge Level 2 then the headset will report eventbatteryOK and EventGasGauge1 If the battery voltage is above Gas Gauge Level 2 and below Gas Gauge Level 3 then the headset will report eventbatteryOK and EventGasGauge2 If the battery voltage is above Gas Gauge Level 3 then the headset will report eventbatteryOK and EventGasGauge3
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 14 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.2
Bu tt on Config ur ati on
PS Key USR1 holds data that configures button press definitions. The parameters are held in the following bit fields: Label
Double Press Time
Long Press Time
Very Long Press Time
Repeat Time
Very Very Long PressTime
Type
uint16
uint16
uint16
uint16
uint16
Range
100-1000 (ms)
500-8000 (ms)
1000-12000 (ms)
100-5000 (ms)
1000-12000 (ms)
Default Value
500 (0x01f 4)
1000 (0x03e8)
35000 (0x0dac )
800 (0x0320)
5000 (0x1388)
Table A.3: PS Key USR1 – Butto n Confi gurati on Bi t Fields Note: Default values quoted are for Headset v4 four button configuration.
A.3
Bu tt on Sequence Con fi gu rat io n
PS Key USR2 allows two sequences of up to six button presses to be defined and used to generate a system event. Every time a PIO is pressed the code checks for a match to the defined pattern. If the sequence of button presses matches the sequence in the key then the specified event is sent to the main message loop. Note: There is no limit to the time between button presses and no distinction is made between short or long button presses.
The key can contain up to two event sequences in the form: Label
Event to be Generated
Key 1
Key 2
Key 3
Key 4
Key 5
Key 6
Type
uint16
uint16
uint16
uint16
uint16
uint16
uint16
Range
0x6001 - 0x603f
Default Value
N/a
Set bit pattern for required button press sequence N/a
N/a
N/a
N/a
N/a
N/a
Table A.4: PS Key USR2 – Butto n Sequence Configu ration Bit Field s Example To configure the event Event Ent er DUTmode as a result of 6 presses of PIO[0] the key would hold the hex value:
6015 0001 0001 0001 0001 0001 0001 0000 0000 0000 0000 0000 0000 0000 The second sequence is not used in this example and is initialised to 0. Note: Normal system events should be configured using PS Keys USR23 and USR24. See A.15 Event Configuration.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 15 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.4
Suppo rted Features
PS Key USR3 maps directly onto the supported features reported as part of the AT+BRSF command used during registration and connection setup sequence. A 16-bit unsigned integer bitmask is used to report support for the following features:
#def i #def i #def i #def i #def i #def i #def i
ne ne ne ne ne ne ne
HFP_ NREC_FUNCTI ON ( 1) HFP_ THREE_WAY_CALLI NG ( 1<<1) HFP_ CLI _PRESENTATI ON ( 1<<2) HFP_ VOI CE_RECOGNI TI ON ( 1<<3) HFP_ REMOTE_ VOL_CONTROL ( 1<<4) HFP_ ENHANCED_CALL_ STATUS ( 1<<5) HFP_ ENHANCED_CALL_ CONTROL ( 1<<6)
_ ä ì É ` ç ê É
Example To indicate support for three way calling and remote v oice control the bitmask would be set as:
0000 0000 0000 1010 ( i . e. hex val ue 000a)
A.5
PIO Inp ut Con fi gu rati on
PS Key USR4 configures the PIOs to be used to trigger a charger event or to put the device into DUT (Device Under Test) mode on power on. The PS Key specifies the PIO which when held high indicates the event. Label
Reserved
Reserved
Charger Input PIO
DUT Mode PIO
Type
uint16 (D15-12)
(D11-8)
(D7-4)
(D3-0)
Range
Not used
Not used
0-11 (0x0 - 0xb)
0-11 (0x0 - 0xb)
Default Value
0xf (not used)
0xf (not used)
0xf (not used)
0xf (not used)
Table A.5: PS Key USR4 – PIO Input Conf igur ation Bit Fields Note: Default values quoted are for Headset v4 four-button configuration.
Description of Bit Fields
Charger Input PIO: the pin specified in this field is polled on power up. If the pin is held high it indicates that the charger is connected and the charger event message will be received by the application. Note: Charger events still need to be configured for charging indications such as LED patterns etc.
DUT Mode PIO: when the pin specified in this field is held high on power on the device enters Device under Test mode. This feature can be useful during production line testing.
Example To configure PIO[0] as the Charger Input PIO and PIO[11] as the DUT Mode, PS Key USR4 would hold the hex value:
ff0b
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 16 of 58
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.6
HFP 1.5 Feature Co nf igu rat io n
PS Key USR5 must be set when developing a device that will support version 1.5 of the Handsfree Profile (HFP 1.5). The feature configuration data is held in the following bit fields: Label
Is HFP 1.5 Enabled
Type
uint16 (D15)
Values
0x1
Reserved
(D14-1)
enabled
Additional Au di o Params Sync Used Packet Types
Bandwidth
(D0)
uint32
uint16
Voice Settings
Retransmission Effort
uint16
uint16
uint16
See Audio Packet Types Bitmask
n/a
0x0
Max Latency
disabled
Table A.6: PS Key USR4 – HFP 1.5 Feature Con figu ration Bit Fields Au di o Packet Types Bit mask This bitmask is used for SCO/eSCO negotiation. The headset will automatically negotiate the best audio package type that can be achieved from the activated package types. Bi t
D15
D14
D13
D12
D11
D10
D9
D8
Packet Type
reserved
reserved
reserved
reserved
reserved
reserved
sync_3ev5
sync_3ev3
Mask Value
n/a
n/a
n/a
n/a
n/a
n/a
0x0200
0x0100
D7
D6
D5
D4
D3
D2
D1
D0
sync_2ev5
sync_2ev3
sync_ev5
sync_ev4
sync_ev3
sync_hv3
sync_hv2
sync_hv1
0x0080
0x0040
0x0020
0x0010
0x0008
0x0004
0x0002
0x0001
Table A.7: PS Key USR5 – Audio Packet Type Bi tmask
Bit = 1: The packet type will be included in audio negotiation. Note: eSCO packet types are only available if HFP 1.5 support is enabled see below.
Bit = 0: The packet type will not be included i n audio negotiation.
IMPORTANT NOTE: The enable bits are inverted for D6, D7, D8, and D9 i.e. 0 = included in audio negotiation, 1 = not included in audio negotiation.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 17 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.7
Enabli ng HFP 1.5 Sup po rt
To enable HFP 1.5 support, an additional PS Key must also be set. If the BlueVOX Configurator HFP Features tab is used to configure the Audio Packet Types and the Enable HFP 1.5 Features option is checked this key is written automatically. To enable HFP 1.5 if USR5 is set manually, the following PS Key must also be set manually: To enable eSco EV3, EV4 and EV5:
_ ä ì É ` ç ê É
PS Key LOCAL_ SUPPORTED_FEATURES = f ef c 800f 880b 0000 To enable eSCO plus 2M EDR: PS Key LOCAL_ SUPPORTED_FEATURES = f ef c 800f A80b 0000 To enable eSCO plus 3M EDR: PS Key LOCAL_ SUPPORTED_FEATURES = f ef c 800f E80b 0000 If HFP 1.5 support is not required the value should be: PS Key LOCAL_ SUPPORTED_FEATURES = f ef c 000f 0808 0000 Retransmission Effort Enumeration values:
sync_r et x_di sabl ed No retransmissions.
sync_r et x_power _usage At least one retransmission, optimise for power consumption.
s ync _ r et x_ l i nk_ qual i t y At least one retransmission, optimise for link quality.
sync_r et x_dont _care Don't care.
Example The following entry:
8001 003f 0000 1f 40 000c 0000 0002 in PS Key USER5 configures:
eSCO enabled
all packet types supported
8000Hz Bandwidth
latency of 12
retransmission effort = link quality
Headset with eSCO enabled , all packet types supported 8000Hz Bandwidth latency of 12 and retransmision effort = link quality
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 18 of 58
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.8
Headset Tim eou ts
PS Key USR6 configures the Timers and Counters used in the application.
s _ e m i T f f O h c t i w S o t u A
l e b a L
s t_ u o e m i T n O r e w o P o t u A
s _ e m i T t a e p e R r o t a c i d n I e c i v r e S k r o w t e N
s _ e m i T n O r e w o P r e t f A f f O r e w o P e l b a s i D
s t_ u o e m i T e d o M r i a P
s _ e m i T d n i m e R e t u M
s _ s e i r t e R m u N s s o L k n o i L
s _ y a l e D r e f s n a r T o i d u A r o F k c e h C
Type
uint16
uint16
uint16
uint16
uint16
uint16
uint16
uint16
Range
0-600 (secs)
0-60 (secs)
0-3600 (secs)
0-60 (secs)
0-65536 (secs)
0-60 (secs)
0-60 (secs)
0-30 (secs)
Default Value
600 (0x0258)
12 (0x000c)
10 (0x000a)
0 (0x0000)
65536 (0xffff)
5 (0x0005)
5 (0x0005)
1 (0x0001)
Table A.8: PS Key USR6 –Timers and Counters Description of Timers and Counters Au to Swi tchOf fTi me_s: The Time in seconds after which the headset will switch off if not connected. if==0 then headset remains on indefinitely. Au to Pow erOnTimeou t_s : The value in seconds that the headset waits after powering up to see if a power on event occurs. After this time, the headset will return to the off state. NetworkServiceIndicatorRepeatTime_s: The time in seconds after which the network service indication will be replayed if there is no network present in the connected AG. DisablePowerOffAfterPowerOnTime_s: The time after Power On for which the Power Off event has no effect. This is used for example, if the UI specifies that a long press on Power On enters pairing mode but a long press at any other time (including in the connectable state) should Power Off the headset. PairModeTimeout_s: The time in seconds that the headset remains in the connectable / discoverable state (pairing mode). Setting this to 0 will result in the headset entering and immediately exiting discoverable mode, with the result that the device cannot be discovered. If the headset is to always be discoverable whilst not connected, then the feature bit Automatic Pairing Mode Enable (see PS Key USER15 on page 22) should be used in conjunction with this timeout. MuteRemindTime_s: The time between mute reminder updates. This is used for LED and Tone reminders to indicate that the headset is muted. LinkLossNumRetries: Specifies the Number of retries to be made if an abnormal disconnect (link loss) occurs. Each retry is initiated after a 10 second delay. CheckForAudioTransferDelay: Timeout after an SLC establishment before the V4 software attempts to create a SCO link to the AG device.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 19 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.9
Radio Co nf ig ur ati on
PS Key USR13 determines the radio Inquiry and Page scan characteristics: Label
Inquiry Scan Interval (slots)
Inquiry Scan Window (slots)
Inquiry Scan Interval (slots)
Inquiry Scan Window (slots)
Type
uint16
uint16
uint16
uint16
Range
18-4096 (0x0012 – 0x1000)
18-4096 (0x0012 – 0x1000)
18-4096 (0x0012 – 0x1000)
2048 (0x0800)
18 (0x0012)
2048 (0x0800)
Default Value
18-4096 (0x0012 –
0x1000) 18 (0x0012)
Table A.9: PS Key USR13 – Radio Conf igur ation Bit Field s Note: Default values quoted are for Headset v4 four button configuration.
BlueVOX Configurator does not provide an interface to this PS Key. The default values have been selected to give the best performance characteristics and it i s not recommended that these are changed in most circumstances.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 20 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.10 NiMH Ch arg er Co nf igu rat io n PS Key USR14 holds the required parameter values used to configure the quick charge cycle for a NiMH battery. Note: NiMH batteries are either trickle or quick charged. The parameters configured in this PS Key are associated with the quick charge cycle and are very important in order to protect the lifetime of the battery.
QC Min Battery (Temp o C)
QC Temp Update Period (mins)
uint16 (D15-8)
(D7-0)
uint16 (D15-8)
1-32
0-60
0
1-10
15 (0x0f )
40 (0x28)
00 (0x00)
4 (0x04)
QC Min Voltage (mV)
QC Max Voltage (mV)
QC –dV Voltage (mV)
QC –dV Inhibit Time
QC Max Battery o (Temp C)
Type
uint16
uint16
uint16 (D15-8)
(D7-0)
Range
900-3500
1800-3500
0-60
Default Value
1800 (0x0708)
3300 (0x0ce4)
7 (0x07)
Label
Thermister m
Thermister c
VDet m
VDet c
dT Threshold o ( C)
int16
int16
int16
int16
int16
0-15
-100 to 100
-1000 to 1000
-100 to 100
-1000 to 1000
0-10
4 (0x04)
-48 (0xf f d0)
68 (0x0044)
0 (0x0000)
0 (0x0000)
1 (0x0001)
QC Td o ( C)
QC Time (mins)
Thermister Enable PIO
(D7-0)
uint16 (D15-8)
(D7-0)
0-180
0-15
0 (0x00)
120 (0x78)
Table A.10: PS Key USR14 – NiMH Charger Conf igu ration Bit Fields Note: Default values quoted are for Headset v4 four-button configuration.
The default PS Key’s hex value is:
0708 0ce4 070f 2800 0400 7804 f f d0 0044 0000 0000 0001
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 21 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.11 Feature Co nf ig ur ati on PS Key USR15 holds three words used to configure features as described in this section. Word 1
Word 2
Word 3
General Features
Reconnection Policy
Extended Features
Word 1 – General Features Bi t
D15
D14
D13
D12
D11
D10
D9
Feature
Mic Bias uses LDO
Codec Gain Scale
Mute Control Speaker Gain
Play Tones at Fixed Volume
Reboot after Reset
Remain Discoverable at all times
Disable Power Off after Power On
Default
0
0
0
1
1
0
0
D7
D6
D5
Use User defined Codec Gain Values
Power On uses Internal LDO
Power On uses Internal SMPS
1
0
1
D4 Mute Local Volume Action 0
D3
D2
D1
Mute Override
NiMH Battery Charger Enable
LiON Battery Charger Enable
0
0
1
D8 Auto Answer on Connect 0
D0 Automatic Pairing Mode Enable 0
Table A.11: PS Key USR15 – Feature Confi gurati on Bi t Fields Description of Bit Fields Mic Bias Uses LDO:
Bit = 1: The internal LDO is used for the mic bias.
Bit = 0: The PIO defined in the PS Key CODEC_ PI O is used for the mic bias.
If this is not set correctly for a particular hardware design microphone audiopath may not work correctly. - the Internal LDO can also be enabled on Power On via the Power On Internal LDO feature bit (D6). The use of the LDO for the Mic Bias is not generally recommended as it can reduce audio quality. Codec Gain Scale:
Bit = 1: The Profile Volumes are scaled across the full range of Speaker Gain Values (0-23). This provides the full audible range for the headset. Bit = 0: The Profile Volumes use the Speaker Gain range 4-19. This provides equal steps of around 2.5/3dB per Profile Volume Setting.
Mute Control s Speaker Gain:
Bit = 1: Mute will mute the Speaker and the Microphone of the headset.
Bit = 0: Only the Microphone will be muted.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 22 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
Play Tones at Fixed Volume:
Bit = 1: Tones are played at a nominal fixed volume regardless of the current Profile Volume level. Note: By default the fixed volume at which the tones will be played if this bit is set is HFP Volume Level 1.
Bit = 0: Tones are played at the current Profile Volume level.
Reboot after Reset:
Bit = 1: The headset powers off after a Reset has been issued.
Bit = 0: The headset does not power off after a Reset has been issued. Note: Reset clears the Default and Last user together with the list of Paired devices.
Auto Answ er on Co nn ect: This allows the headset to send an answer (ATA) AT command if an incoming call is detected on connection.
Bit = 1: Headset sends answer (ATA) AT command.
Bit = 0: Headset does not respond to an incoming call detected on connection. Note: Some AGs will attempt to auto answer the call on connection.
Use User defi ned Codec Gain Values:
Bit = 1: The application uses the CODEC Gain settings set in PS Key USR16 (Speaker Gain Mapping, see Appendix A.12). Bit = 0: Gains are scaled according to the Codec Gain Scale feature bit (D14).
Disable Power Off after Power On:
Bit = 1: Disables Power Off for 20 seconds after Power On. Note: This is used for example, if the UI specifies that a long press on Power On enters pairing mode but a long press at any other time (including in the connectable state) should Power Off the headset.
Bit = 0: Power Off is not disabled during Power On.
Mute Override: If the headset is muted (via the Event Mut eToggl e or Event Mut eOn), then this bit controls the action to take when an Event Vol umeUp/Event Vol umeDown or an AG volume indication message occurs:
Bit = 1: Volume events cause the headset to unmute and set the volume to the new level. Bit = 0: Volume events do not unmute the headset and the local headset volume value is updated according to the Mute Local Volume Action feature b it (D4).
Mute Local Volume Action: This controls whether or not an Event Vol umeUp, Event Vol umeDown or an AG volume indication message updates the headset’s local volume variable (when the headset is muted):
Bit = 1: The headset updates the volume variable and the next time the headset is unmuted, the new volume will take effect. Bit = 0: The headset ignores any volume requests until it is unmuted.
Power On Internal LDO: This controls whether the Power On event latches on the internal Linear Regulator (LDO: Low Drop Out):
Bit = 1: Latched on
Bit = 0: Not Latched on
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 23 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
Power On Internal SMPS: This controls whether the Power On event latches on the internal Switch Mode Power Supply (SMPS):
Bit = 1: Latched on
Bit = 0: Not Latched on
Word two - Reconnection Policy Bi t
D15
D14
Feature
Default different to Last AG
Paired Device List is Shuffled on Connection
AutoReconnect – Power On
Range
0-1
n/a
0-1
0-1
0-6
BlueVOX default
0x0
0x0
0x0
0x1
0x01
(1)
D13
D12 AutoReconnect – Link Loss
D11:D8 Reconnect Action on Connect (1)
D7:D4 Reconnect Action on Call Transfer 0-6
(1)
0x01
D3:D0 Reconnect Action on Power On 0-6
(1)
0x01
See Reconnect Action for descriptions of options Table A.12: PS K ey USR15 Word two - Reconnection Policy Bit Fields
Note: Default values quoted are for Headset v4 four-button configuration.
Description of Bit Fields Default Different to Last AG: This bit field defines how the application interprets theDefault and Last connected AGs:
Bit = 1: Default is the first ever paired AG and the Last is the last connected AG (BUT ONLY if the last was different to the default) Bit = 0: Default is the first ever paired AG and the Last is the last connected AG (i.e any device - can be the same as the default).
Paired Device is Shuffled on Connections: This controls the order in which the reconnect action - list attempts to connect to the 8 devices in the paired device list 0 - paired device list will contain the order of pairing 1 - paired device list will contain the order of connecting.
Bit = 1: Paired device list will contain the order of connecting.
Bit = 0: Paired device list will contain the order of pairing.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 24 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
Reconnect Acti on There are eight Reconnection Action options. The option required can be set separately for Power On and following Disconnect and Call Transfer events: Note: The Call Transfer Reconnect Action is evoked when the headset is used to transfer a call to the AG then back to the headset.
Reconnect entry
Action
0 (0x00)
Attempt to Reconnect to the last connected AG
1 (0x01)
Attempt to Reconnect to LAST connected AG
2 (0x02)
Attempt to Reconnect to DEFAULT AG
3 (0x03)
Attempt to Reconnect to LAST AG then DEFAULT AG
4 (0x04)
Attempt to Reconnect to DEFAULT AG then LAST AG
5 (0x05)
Attempt to Swap AG i.e if was DEFAULT then now LAST AG etc
6 (0x06)
Attempt to Swap then swap again AG i.e if was DEFAULT then now LAST then DEFAULT AG etc
7 (0x07)
Attempt to connect to all 8 devices in the paired device list. If we have just been cleanly disconnected then the list does not include the device just dropped
Where: last = Last connected device ( i .e The LAST or DEFAULT or none if freshly powered On). LAST = This is defined in Default Different to Last, if:
Bit =1: Then this is the last connected device that is not the DEFAULT
Bit =0: Then this is the last co nnected device (can be the DEFAULT device)
DEFAULT = First device ever connected Table A.13: PS Key USR15 Word two - Reconn ection Actio n Au to Reconn ect – Pow er o n: Defines the Auto Reconnect action when the headset receives a Power On event: Auto Reconn ect – Li nk Lo ss: Defines the Auto Reconnect action when the headset loses the SLC connection to an AG with a resulting Link Loss Error code: Reconnect Action on Connect: Defines the AG that the device will try to connect to when an Establish SLC event is received. i.e. when a user generated event requiring a connection is received by an unconnected headset e.g. Connect, Voice dial or Last Number Redial events. Reconnect Action on Call Transfer: Defines the AG that the device will try to connect to when a call that has been transferred to an AG is transferred back to the headset (using the headset). Note: i.e. the Call Transfer Reconnect Action is evoked when the headset is used to transfer a call to the AG then back to the headset. This only applies to A gs that disconnect the headset when it transfers a call.
Reconnect Action on Power On: Defines the AG that the device will try to connect to at next Power On event. If The Auto Reconnect – Power On bit field is s et to 1.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 25 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
Word t hree– Extended Features Bit
D15 to D12
D11
D10
D9
Feature
DiscoIfPDLLessThan:4
Reserved
Reserved
ListConnectNextButOne
Default
0000
0
0
0
D8
D7
D6
D5
D4
EncryptOnSLCEstablishment
VGSDoesNotSetMicGain
Play Volume Tone on Remote Indication
Secure Pairing
Use Raw Mic Gains
1
0
0
0
0
D3
D2
D1
D0
Use Raw Speaker Gains
Queue Tone Events
Queue LED Events
Use Last Paired user as well as Last Connected user
1
0
0
0
Table A.14: PS Key USR15 Word th ree – Extended Features Bit Fields
Description of Bit Fields DiscoIfPDLLessThan: This forces the headset to Enter Discoverable mode (pairing) if the paired device list is less than the entry here. i.e. an entry of 2 would mean that if the headset has previously paired with either 0 or 1 devices, then the headset will enter discoverable mode.
Bit = 0: Feature disabled.
Bit = 1 - 7: Feature enabled.
ListConnectNextButOne: On a disconnect when using the list reconnection policy:
Bit = 0: Attempt connect to the first item in the list and then all others.
Bit = 1: Attempt connect to the second item in the list and then all others
EncryptOnSLCEstablishment: This forces Encryption on SLC establishment. Some Nokia S40 phones now do not force encryption on the SLC. Setting this bit ensures that encryption is used.
Bit = 0: Encryption not enforced.
Bit = 1: Ensures that encryption is used.
VGSDoesNotSetMicGain: This configures how the local microphone gain level behaves.
Bit = 0: The mic level will be updated according to policy in Word 1 & PSKEY_USR_16, see A.12Speaker Gain Mapping. Bit = 1: The local microphone gain level will not be set on a VGS command from the AG.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 26 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
Play volume tone on remote indication: This forces the headset to play a tone when the volume is adjusted from the remote end if tones are configured to be played.
Bit = 0: Feature disabled.
Bit = 1: Feature enabled.
Secure Pairing: This bit enables secure pairing mode. If set, then the headset will only accept pin code requests when in pairing mode (connectable/discoverable state). This prevents a remote user from pairing with the headset without the headset being specifically placed into paring mode. This is over-ridden if the headset initiates the connection. ie - if a headset attempts to connect to a remote AG without the correct link key (or has the bdaddr but not the link key) then the headset will accept a pin code request.
Bit = 0: Feature disabled.
Bit = 1: Feature enabled.
Use Raw Mic Gains: This allows the user gain defined in PS Key USR16 to be split into a separate analogue and digital gain for control of the mic gain The Set Raw API is used to control the mic gain.
Bit = 0: Feature disabled.
Bit = 1: Feature enabled.
Use Raw Speaker Gains: This allows the user gain defined in PS Key USR16 to be split into a separate analogue and digital gain for control of the speaker gain. This must be used in conjunction with Use User defined Codec Gain Values.
Bit = 0: Feature disabled.
Bit = 1: Feature enabled.
Use Last Paired User as well as Last Con nected User: This will cause the HS to store the pairing information for the last paired user as well as the last connected user.
Bit = 0: The HS will only attempt to the last connected us er and ignore any users that have been paired but not connected. Bit = 1: and an AG is paired to the HS but not connected, then the HS will attempt to reconnect to the last paired device on power on.
Queue Tone Events: This allows tones to be queued in the headset:
Bit = 1: Queued tones will be played in sequence. Note: Up to 4 tones can be held in the queue.
Bit = 0: Any request to play a tone whilst another is playing, will be ignored.
Queue LED Events: This allows LED indicator patterns (up to four) to be queued in the headset.
Bit = 1: Queued LED patterns will be displayed in sequence. Note: Up to 4 LED patterns can be held in the queue.
Bit = 0: Any request to display an LED sequence whilst is active will be ignored.
Use Last Paired User as well as Last Connected User: This causes the headset to store the pairing information for the last paired user as well as the last connected user.
bit = 1: If an AG is paired to the headset but has not been previously connected, then the headset will use this information to attempt to connect to the last paired device on Power On if bit D13 (AutoReconnect – Power On) in word two is set. Note: If this bit is not set, pairing information for an AG that has been paired but not connected will be discarded when the headset is powered off.
bit = 0: The headset will attempt to connect to the last connected AG and will ignore any AGs that have been paired (but not connected) since the last connection.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 27 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.12 Au di o Gai n Map pi ng PS Key USR16 holds values that configure the Speaker/Mic Gain behaviour of the applic ation. PS Key USR16 supports both Predefined Gains and Raw Gains. Two feature bits govern which method is used to configure PS Key USER16. Check the Use Raw Speaker Gains and Use Raw Mic Gains options in the Configurator’s Features tab to configure Raw Gains, leave th ese options unchecked to configure the audio gain using Predined Gains. A.11.1 PS Key USER16 con fi gu red to use Predefi ned Gain s Label
Increase Act io n
Decrease Acti on
Type
uint16 (D15-12)
(D11-8)
Range
0 - 15 (0x0 - 0xf )
0 - 15 (0x0 - 0xf )
Mic Gain Level
Tones
Speaker Gain
Mic Gain
(D7-4)
(D3-0)
uint16 8)
(D7-0)
0 - 15 (0x0 - 0xf )
0 - 15 (0x0 - 0xf )
(D15-
0 - 22 (0x00 0x16)
0 - 22 (0x00 0x16)
Table A.15: PS Key USR16 – Predefined Aud io Gain Mappin g Bit Fields The PS Key contains a total of 128 Hex numbers representing each of the 16 (0-15) Profile Volume settings in the AG profile. Each volume button press adjusts the Profile Volume setting by one level. Example A single volume press configuration entry for Profile Volume Level 7 might be0x8671 090a and would equate to: Label
Configuration Value
Action
Increase action
0x8
Go to Profile Volume level 8
Decrease action
0x6
Go to Profile Volume level 6
Mic Gain level
0x7
Set Mic Gain Level to 7 for this Profile Volume level
Tones
0x1
Play Middle 0, see Appendix C
Speaker Gain
0x09
Set the CODEC Gain for the Speaker to 9 (-18dBr)
Mic Gain
0x0a
Set the CODEC Gain for Mic to 10 (-15dBr)
Table A.16: Volume Press Conf igur ation Example Entries for each of the other 16 (0-15) Volume Gain settings appear in sequence in the PS Key.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 28 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
CODEC Gain Settings Speaker and Mic Gain values support the range 0 to 22 (0x00 to 0x16) these values equate to the gain settings: CODEC (Speaker /Mic) Gain (0-22)
Digital Gain
Analog ue Gain
GAIN (dBr)
Value to set
Internal
Internal
Gain achieved at Speaker/Mic
22
7
7
+21.5
21
6
7
+18
20
5
7
+15.5
19
4
7
+12
18
3
7
+9.5
17
2
7
+6
16
1
7
+3.5
15
0
7
0
14
0
6
-3
13
0
5
-6
12
0
4
-9
11
0
3
-12
10
0
2
-15
9
0
1
-18
8
0
0
-21
7
15
0
-23.5
6
14
0
-27
5
13
0
-29.5
4
12
0
-33
3
11
0
-35.5
2
10
0
-39
1
9
0
-41.5
0
8
0
-45
Table A.17: CODEC Predefined Gain Settings Note: For simplicity the BlueVOX Configurator allows engineers to set the Speaker or Microphone Gains from a drop down list of Gain (dBr) values.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 29 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
Typical Values Table A.17 shows a typical set of values for the gain settings of a headset application: Profile Volume
Increase Act io n
Decrease Acti on
Mic Gain Level
Tone
Speaker Codec Gain
Mic Codec Gain
0
4
0
0
1
0x04
0x11
1
4
0
1
4
0x06
0x11
2
4
0
2
4
0x06
0x11
3
4
0
3
4
0x06
0x11
4
5
0
4
4
0x06
0x11
5
6
4
5
4
0x07
0x11
6
7
5
6
4
0x08
0x11
7
8
6
7
4
0x09
0x12
8
9
7
8
4
0x0a
0x12
9
a
8
9
4
0x0b
0x12
a
b
9
a
4
0x0c
0x12
b
f
a
b
4
0x0d
0x12
c
f
b
c
4
0x0f
0x12
d
f
b
d
4
0x0f
0x12
e
f
b
e
4
0x0f
0x12
f
f
b
f
a
0x0f
0x13
Table A.18: CODEC Gain Typi cal Settin gs This equates to a PS Key hex value of:
4001 0411 4014 0611 4024 0611 4034 0611 5044 0611 6454 0711 7564 0811 8674 0912 9784 0a12 a894 0b12 b9a4 0c12 f ab4 0d12 f bc4 0f 12 f bd4 0f 12 f be4 0f 12 f bf a 0f 13 Note: This is used as the default value for PS Key USR16 in the BlueCore4-Headset.
A.11.2 PS Key USER16 con fi gu red to us e Raw Gain s When the Use Raw Gain feature bit set the user must provide values of analogue and digital gain values to create the attenuation level required for the application.
Decrease Acti on
Mic Gain Level (HFP)
Tones
Raw An alo gu e Speaker Gain
Raw Digital Speaker Gain
Raw Analo gu e Mic Gain
Raw Digital Mic Gain
Label
Increase Acti on
Type
uint16 (D15-12)
(D11-8)
(D7-4)
(D3-0)
uint16 (D15-12)
(D11-8)
(D7-4)
(D3-0)
Range
0 - 15 (0x0 0xf )
0 - 15 (0x0 0xf )
0 - 15 (0x0 0xf )
0 - 15 (0x0 0xf )
0-7 (0x0 0x7)
0 - 15 (0x0 0xf )
0-7 (0x0 0x7)
0 - 15 (0x0 0xf )
Table A.19: PS Key USR16 –Raw Au dio Gain Mapping Bit Fields
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 30 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
The separate digital and analogue values each provide an attenuation level in dBr, the values of both of these fields are added together to produce an overall gain for speaker and mic, there are separate entries for speaker and mic gains. The digital gain can be set to one of 15 values. The values provide the attenuation values shown in Table A.20: Digital Gain
Gain (dBr)
Internal
Gain achieved at speaker/mic
0
0
1
+3.5
2
+6
3
+9.5
4
+12
5
+15.5
6
+18
7
+21.5
8
-24
9
-20.5
10
-18
11
-14.5
12
-12
13
-8.5
14
-6
15
-2.5
_ ä ì É ` ç ê É
Table A.20: Raw Digit al Gain Values The Raw analogue gain component can have 1 of 8 values: Analo gu e
Gain (dB r)
Internal
Gain achieved at speaker/mic
0
-21
1
-18
2
-15
3
-12
4
-9
5
-6
6
-3
7
0 Table A.21: Raw Analo gue Gain Values
Using a combination of analogue and digital gains from the raw gain tables it is possible to set smaller step sizes than those available when using the predefined gain tables. However, the range of available step sizes available is still limited and it may still be impossible to achieve the exact gain required, in some cases a near to value is the best that can be achieved.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 31 of 58
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
For example to achieve an attenuation level of -11dB, two approaches would be to set the gains as shown: 1.
Set Raw Analogue Gain to 4, giving an attenuation value of -9dB Set Raw Digital Gain to 15, giving an attenuation value of -2.5dB Combining the analogue and digital gain results in an actual attenuation of -11.5dB
2.
Set Raw Analogue Gain to 6, giving an attenuation value of -3dB Set Raw Digital Gain to 13, giving an attenuation value of -8.5dB Combining the analogue and digital gain results in an actual attenuation of -11.5dB
An example of a typical single HFP level entry in PSkey USR16 might be:
FCE1 4F4F This entry would define HFP Mic Gain Level 14 with the attenuation of -11.5dB (as in the first example configuration above), Increase action = go to level 15, Decrease action = go to level 13, headset tone = middle 0. Setting the Audio Gain using the Raw configuration, whilst providing more precise control, is more time intensive as engineers must consider the possible combinations that can be used to achieve the required Gain le vel. Engineers should be aware that the use of positive digital gain settings should be avoided as they ar e likely to result in audio distortion.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 32 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.13 LED St ate Co nf igu rat io n Each headset state can be associated with a unique LED flashing pattern. The necessary configuration is defined in two PS Keys:
USR19: specifies the number of LED flashing patterns (entries) defined in PS Key USR20.
USR20: holds the attributes of 1 to n entries defined as follows. Word 1
Word 2
Label
Headset State
LED On time (x10ms)
LED off tim (x10ms)e
LED repeat time (x50ms)
Type
uint16 (D15-8)
(D7-0)
uint16 (D15-8)
(D7-0)
Range/Description
See Appendix Appendix B
0-2550ms (in 10ms steps)
0-2550ms (in 10ms steps)
0-10000ms (in 50ms steps)
Word 3
Word 4
LED Dim Time
Time out
Number of flashes
LED_A
LED_B
Colour
uint16 (D15-8)
(D7-0)
uint16 (D15-12)
(D11-8)
(D7-4)
(D3-0)
0-255ms
0-255 ms
0-15
see below
see below
see below
Table A.22: PS Key USR20 - LED State Configu ration Bit Fields Description of Bit Fields Headset State: System state associated with the LED pattern being defined, see Appendix D On time, Off time, Number of fl ashes and Repeat tim e values:
Figure 1: LED Pattern
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 33 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
Dimming LEDs: Dimming / Ramping LEDs are available if running on BlueCore4 Audio ROM and BlueCore4 Headset-based hardware. Dimming LEDs can be enabled by entering a value in the LED Dimming field. This value is the time between ramp steps to use. There are 16 ramping steps used to Dim on or off an LED. It is important to ensure that the (Dim time * 16) is less than the on time / off ti me for the ramp to complete. E.g. For a 1 second on 1 second off pattern, then a good Dim time to use would be 800ms / 16 = 50 =0x32. Time out: This field specifies the number of times the sequence, specified by the entry, will repeat (unless superseded by another event) before it times out. When set to 0 the sequence will not tim e out. LED_A: This field is a bitmask that specifies the PIO that will be referred to in the PS Key attributes as LED_A. Bit
D15
D14
D13
D12
D11
D10
D9
Mask value
LED_1
LED_0
Tricol_a LEDs *
Tricol_b LEDs *
Tricol_c LEDs *
PIO_10
PIO_9
D8
D7
D6
D5
D4
D3
D2
D1
D0
PIO_8
PIO_7
PIO_6
PIO_5
PIO_4
PIO_3
PIO_2
PIO_1
PIO_0
Table A.23: PS Key USR20 – LED_A Bitmask LED_B: This field is a bitmask that specifies the PIO that will be referred to in the PS Key attributes as LED_B. Bi t
D15
D14
D13
D12
D11
D10
D9
Mask value
LED_1
LED_0
Tricol_a LEDs *
Tricol_b LEDs *
Tricol_c LEDs *
PIO_10
PIO_9
D8
D7
D6
D5
D4
D3
D2
D1
D0
PIO_8
PIO_7
PIO_6
PIO_5
PIO_4
PIO_3
PIO_2
PIO_1
PIO_0
Table A.24: PS Key USR20 – LED_B Bitmask Colour: This field defines the LED(s) that the sequence will display when a filter is not applied. The options for this field are defined as:
bit value = 0000: Reserved
bit value = 0001: LED_A
bit value = 0010: LED_B
bit value = 0011: Alternate
bit value = 0100: LED_BOTH
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 34 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
Example A typical example of an LED State configuration is the default LED indication for the Connectable state in BlueVOX2 headsets: Label
Headset State
LED On time
LED off time
LED repeat time
Type
uint16 (D15-8)
(D7-0)
uint16 (D15-8)
(D7-0)
Binary value
00000001
00001010
00001010
00101000
Hex value
0x010a
Defines
Connectable
0x0a28 (1)
100ms
(1)
(2)
100ms
2000ms
LED Dim Time
Time out
Number of flashes
LED_A
LED_B
Colour
uint16 (D15-12)
(D11-8)
uint16 (D15-12)
(D11-8)
(D7-4)
(D3-0)
00000000
00000000
0010
1111
1110
0001
0x0000
0x0000
0x2f e1
0
0
2
LED_1
LED_0
LED_A
Table A.25: PS Key USR20 – Example Entry Notes:
(1) (2)
The software multiplies the value entered in this field by 10 i.e. 10x10 results in 100ms. The software multiplies the value entered in this fi eld by 50 i.e. 50x40 results in 2000ms.
This equates to an LED sequence hex value entry of:
010a 0a28 0000 2f e1 This results in LED_1 flashing twice for 100ms every 2 seconds while the device is connectable.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 35 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.14 LED Event Con fi gu rati on Each headset system event can be associated with a unique LED flashing pattern. This is defined in t wo PS Keys:
USR21: specifies the number of LED flashing patterns (entries) defined in PS Key USR22.
USR22: holds the attributes of 1 to n LED flashing patterns.
Pattern flashing attributes are held in PS Key 22 in the following format: Word 1
Word 2
Label
Headset System Event
LED On time (x10ms)
LED off time (x10ms)
LED repeat time (x50ms)
Type
uint16 (D15-8)
(D7-0)
uint16 (D15-8)
(D7-0)
Range/Description
See Appendix Appendix B
0-2550ms (in 10ms steps)
0-2550ms (in 10ms steps)
0-10000ms (in 50ms steps)
Word 3
Word 4
Time out
Number of flashes
LED_A
LED_B
Colour
uint16
uint16 (D15-12)
(D11-8)
(D7-4)
(D3-0)
0-255ms
0-255 ms
0-15
see below
see below
Table A.26: PS Key USR22 – LED Event Config uratio n Bit Fields Description of Bit Fields Headset Syst em Event: System event associated with the LED pattern being defined, see Appendix B Note: This is specified as an offset of 0x6000 i.e. to specify the Power On Event ( 0x6001) the value of this field would be 0x01.
On time, Off time, Number of fl ashes and Repeat tim e values:
Figure 2: LED Pattern
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 36 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
Time out: This field specifies the number of times the sequence, specified by the entry, will repeat (unless superseded by another event) before it times out. When set to 0 the sequence will not tim e out. LED_A: This field is a bitmask that specifies the PIO(s) to which LED are connected. Bit
D15
D14
D13
D12
D11
D10
D9
Mask value
LED_1
LED_0
Tricol_a LEDs *
Tricol_b LEDs *
Tricol_c LEDs *
PIO_10
PIO_9
* See Tricolour LED for further information.
D8
D7
D6
D5
D4
D3
D2
D1
D0
PIO_8
PIO_7
PIO_6
PIO_5
PIO_4
PIO_3
PIO_2
PIO_1
PIO_0
Table A.27: L ED_A Bit mask Colour: This field defines the LED(s) that the sequence will display when a filter is not applied. The options for this field are defined as:
Bit value = 0000: Reserved
Bit value = 0001: LED_A
Bit value = 0010: LED_B
Bit value = 0011: Alternate
Bit value = 0100: LED_BOTH.
Example A typical example of an LED event configuration is the default LED indication for the Power On event in BlueCore4-headsets: Label
Headset Event
LED On time
LED off time
LED repeat time
Type
uint16 (D15-8)
(D7-0)
uint16 (D15-8)
(D7-0)
Binary value
00000001
01100100
00000000
00000000
Hex value
0x0164
Defines
EventPowerOn
1000ms
0 (n/a)
0 (n/a)
Time out
Number of flashes
LED_A
LED_B
Colour
uint16
uint16 (D15-12)
(D11-8)
(D7-4)
(D3-0)
0000000000000000
0001
1111
1110
0001
0x0000
0x1f e1
0
1
LED_1
LED_0
LED_A
0x0000 (1)
(1)
(2)
Table A.28: PS Key USR22 - Example Entry Notes:
(1) (2)
The software multiplies the value entered in this field by 10 i.e. 10x10 results in 100ms. The software multiplies the value entered in this field by 50 i.e. 40x50 results in 2000ms.
This equates to an LED sequence hex value entry of:
0164 0000 0000 1f e1
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 37 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
This results in LED_1 flashing once for 1000ms (1 second) when the Power On event is generated. Specialist u se of PS Key22 PS Key 22 can be used to configure t wo other useful behaviour patterns:
Non-repeating patterns
To configure a PIO as an output pin for the duration of an event
Non-repeating Patterns: Setting the Repeat Time to 0 defines a non-repeating pattern. When a non-repeating pattern has completed the previous state pattern will resume. Configuring a PIO as Output Pin: A PIO can be configured as an output pin, set and unset on individual events. Note: This is generally used to indicate an event.
To configure a PIO as an output pin: 1.
Setting the Number of Flashes to 0.
2.
Set a non-zero On time to set the pin to ON (set high) or set a non-zero Off time to set the pin to Off (set low). Note: Two PS Key entries must be configured, one to set the pin high when the event occurs and one to set the pin low when the event is no longer occurring.
As with normal Event Configuration the LED_A, LED_B and Colour fields can be used to configure the ON and OFF conditions to influence one or two PIOs. For example to set two pins PIO[11] and PIO[12] to high when an Event Char ger Connect ed event is generated, the hex value entered would be:
22f f 0000 00bc 0100
Label
Headset System Event
LED On time
LED off time
LED repeat time
Hex Value
22
ff
00
00
Defines
charger connected event
non-zero
zero
zero
Time out
Number of flashes
LED_A
LED_B
Colour
0x00
00
b
c
0100
zero
zero
PIO[11]
PIO[12]
use both LED_A and LED_B
Table A.29: PS KEY USR22 – Example Ent ry
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 38 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.15 LED Fi lt er Co nf ig ur ati on The BlueCore4-Headset allows each headset state/event to be associated with a unique LED flashing pattern. See Appendix A.13 and Appendix A.14. In addition, the software allows filters to be applied to individual LED patterns to change them in response to some event or change in state. For example, to change the colour and/or frequency of a pattern being displayed when the battery is low. When implementing a filter it is normally necessary to create two filters, one to enable the change when the trigger event or state change occurs and one to disable the change when trigger condition ceases. Two PS Keys hold the configuration details for implementing LED filters:
USR17: specifies the number of filters (entries) defined in PS Key USR18.
USR18: holds the attributes of 1 to n filters.
Filter attributes are held in the following format: Label
Headset Event
Type
uint16 (D15-8)
Filter to cancel
LED to Use
(D7-4)
(D3-0)
Speed Act io n
Speed
Active
Unused
(D7-0)
uint16 (D15)
(D14)
(D13-12)
(D11-8)
Unused
Follower LED Active
Follower LED Delay (x50ms)
Unused
(D14-13)
(D12)
(D11-8)
(D7-0)
Override LED Active uint16 (D15)
Colour
Table A.30: PS Key USR18 - LED Filt er Config uratio n Bit Fields Description of Bit Fields Headset event: System event associated with the LED filter being defined, see Appendix B Note: This is specified as an offset of 0x6000 i.e. to specify the Power On Event (0x6001) the value of this field would be 0x01.
Speed: The multiplier/divider applied to the frequency pattern. Note: To leave the frequency of the original pattern unchanged this bit field should be set to 0.
Act iv e: This bit field enables and disables the filter:
Bit = 1: Enabled.
Bit = 0: Disabled.
Unused: Dummy bit. Speed Action: This field specifies the action to apply to the frequency:
Bit value = 01: SPEED_MULTIPLY, multiply the frequency by the value specified in the Speed field.
Bit value = 00: SPEED_DIVIDE, divide the frequency by the value specified in the Speed field.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 39 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
Colour: This field defines the colour filter to apply:
Bit value = 0000: Reserved
Bit value = 0001: LED_A, force use of LED_A
Bit value = 0010: LED_B, force use of LED_B
Bit value = 0011: Alternative, force use of alternating LEDs
Bit value = 0100: LED_BOTH, force use of both LEDs
Filter to cancel: If the filter is set to not active (i.e. is used to cancel another defined filter when an event is generated), then this field contains the index of the filter that is to be cancel led. For example, if the filter is being specified to cancel the second filter defined in PS Key USR17 then this field must be set to 0x2. LED To Use: This field is used to specify an LED, which will be used for either the Override or LED Follower behaviour, if they are activated. Override LED Active: This field is set to activate or deactivate the Override LED field. When activated the LED specified in the Override LED field will be turned ON during the OFF period of the original pattern.
bit = 1: Activate
bit = 0: Deactivate
Unused: Dummy bits. LED Follower Active: When this bit is set the LED specified in the Override LED field repeats the original pattern with a time offset as specified in the LED Follower delay field. LED Follower delay (x50ms): The value in this field defines the time offset in milliseconds, between the original pattern flashes and follower pattern flashes. Note: The software multiplies the value entered by 50 milliseconds before it is applied.
Unused: Dummy bits.
Example To configure filters to change all indications f rom Blue to Red on the BlueCore4-Headset development board when the low battery event is received the PS Key hex values would be: USR17 = 0003 (indicating 3 filters in PS Key USR18) USR18 = 1a00 8200 0000 1e00 0100 0000 1f 00 0010 0000 Note:
All State and Event Indications that this filter is to affect need LED_A (blue) and LED_B (red) bit fields set in PS Key USR20 (LED State Configuration) and USR22 (LED Event Configuration).
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 40 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
Explanation of USR18 value The following three filters are defined: EventLowBattery – Enable the filter: Label
Headset Event
Type
Speed Act io n
Speed
Active
Unused
Colour
uint16 (D15-8)
(D7-0)
uint16 (D15)
(D14)
(D13-12)
(D11-8)
Binary value
00011010
00000000
1
0
00
0010
Hex value
0x1a00
Description
Event Low Battery
not used
Enabled
not used
not used
LED_B (red)
Filter to cancel
Override LED
Override LED Active
Unused
Follower LED Active
Follower LED Delay (x50ms)
Unused
(D7-4)
(D3-0)
uint16 (D15)
(D14-13)
(D12)
(D11-8)
(D7-0)
0000
0000
0x0
00
0
0000
00000000
not used
not used
not used
not used
8200
0x0000 not used
not used
not used
Table A.31: Example of Enabling Fil ter The first entry, which enables the filter becomes:
1a00 8200 0000
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 41 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
Event TrickleCharge – Disable fi lter Label
Headset Event
Type
Speed Act io n
Speed
Active
Unused
Colour
uint16 (D15-8)
(D7-0)
uint16 (D15)
(D14)
(D13-12)
(D11-8)
Binary value
00011110
00000000
0
0
00
0000
Hex value
0x1e00
Description
Event Trickle Charge
not used
Filter to cancel
Override LED
Override LED Active
(D7-4)
(D3-0)
0001
0000
0010 Disabled
not used
not used
not used
Unused
Follower LED Active
Follower LED Delay (x50ms)
Unused
uint16 (D15)
(D14-13)
(D12)
(D11-8)
(D7-0)
0x0
00
0
0000
00000000
not used
not used
not used
not used
0x0000 st
1 filter defined in PS Key
not used
not used
Table A.32: Example of Disabling Fil ter The second entry to disable the battery lo w filter when the trickle charge event is generated, becomes:
1e00 0010 0000
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 42 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
EventFastCharge – Disable filt er Label
Headset Event
Type
Speed Act io n
Speed
Active
Unused
Colour
uint16 (D15-8)
(D7-0)
uint16 (D15)
(D14)
(D13-12)
(D11-8)
Binary value
00011111
00000000
0
0
00
0000
Hex value
0x1f 00
Description
Event Fast Charge
not used
Filter to cancel
Override LED
Override LED Active
(D7-4)
(D3-0)
0001
0000
0010 Disabled
not used
not used
not used
Unused
Follower LED Active
Follower LED Delay (x50ms)
Unused
uint16 (D15)
(D14-13)
(D12)
(D11-8)
(D7-0)
0x0
00
0
0000
00000000
not used
not used
not used
not used
0x0000 st
1 filter defined in PS Key
not used
not used
Table A.33: Example of Enabling Fil ter The third entry to disable the battery low filter when the fast charge event is generated becomes:
1f 00 0010 0000 The full USR18 hex value entry becomes:
1a00 8200 0000 1e00 0010 0000 1f 00 0010 0000
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 43 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.16 Even t Co nf ig ur ati on Each headset system event is configured to be triggered by a set of system attributes. These i nclude PIO lines, PIO Duration and Headset State. A system event is only be generated when all the specified attribute conditions are satisfied. Two PS Keys USR23 and USR24 are used to configure events. The keys are of fixed length and must be 60 words long. Each key can contain a maximu m of 20 Events = 60 Words. Note: If the key contains less than the full 20 events then the remainder of the key
must
be padded with zero's.
Each event is defined in the following format: Label
System Event
PIO Duration
PIO Mask
Headset State Mask
Type
uint16 (D15-8)
(D7-0)
uint16
uint16
Table A.34: PS Key USR23 and 24 Bit Fields Description of Bit Fields System Events: Event to be triggered, see Appendix B Note: This is specified as an offset of 0x6000 i.e. to specify the Power On Event ( 0x6001) the value of this field would be 0x01.
PIO Duration : This bit field specifies the duration attribute that must be satisfied to generate the system event. The valid durations and their respective hex values are given below: Label
Value
Description
Invalid
0x00
n/a
Short (S)
0x01
Sent immediately on release of the button - sent regardless of whether the short is the first part of a double press
Long (L)
0x02
Sent when the long timer has been reached
Very Long (V)
0x03
Sent when the very long timer has been reached
Double (D)
0x04
Sent when a second identical press is received within the double time timeout
Repeat (R)
0x05
Sent every repeat time if the button is held down
RisingEdge (E)
0x06
Sent immediately on button press
FallingEdge (F)
0x07
Sent immediately on button release
Short SINGLE
0x08
Sent at the double press timeout if a short button press was received, but was not part of a double press.
Long Release
0x09
Sent when the button is released if the time is between the long and very long times.
Very Long Release
0x0a
Sent when the button is released, if the time is after the very long timer.
Very Very Long Press
0x0b
Sent when the very very long timer has been reached.
Very Very Long Release
0x0c
Sent when the button is released if the time is after the very very long timer.
RESERVED
0x0d - 0x0f
n/a
Table A.35: PIO Duratio ns
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 44 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
PIO Mask: The PIO mask is used to specify the PIO or PIOs that must be held high (pressed) to generate the event:
Bit = 1: PIO must be pressed to generate event.
Bit = 0: PIO not involved in generating the event.
For Example: To define a simultaneous press of both PIO[0] and PIO[1] to generate the event, the value for the PIO Mask bit field would be 0x0003. Note: The other attributes specified in the Event System key i.e. PIO Duration and Headset State Mask conditions must also be met for the event to be generated.
Bi t
D15
D14
D13
D12
D11
D10
D9
D8
Feature
Reserved
Reserved
Reserved
Reserved
PIO[11]
PIO[10]
PIO[9]
PIO[8]
Hex Value
0x0003
Binary
0
0
0
0
0
0
0
0
D7
D6
D5
D4
D3
D2
D1
D0
PIO[7]
PIO[6]
PIO[5]
PIO[4]
PIO[3]
PIO[2]
PIO[1]
PIO[0]
0
0
0
0
0
0
1
1
Table A.36: PS Key USR23 and 24 – Example Entry
Headset State Mask For the system event to be generated, the headset must be in the specified state. The Headset State Mask bit field specifies the headset state during which the system event can be generated if the other attribute c onditions are met: Bi t
D15
Feature
Reserved
D7
D6
Test Mode
D14
D13
D11
D10
D9
D8
Incoming Call On Hold
Call Multi Call
Three Way Call - Call On Hold
Three Way Call - Call Waiting
Reserved
Active Call Without SCO
D5
D4
D3
D2
D1
D0
Incoming Call
Outgoing Call
Connected
Connectable/ Discoverable
Connectable
Powering On
Reserved
Active Call with SCO
D12
Table A.37: PS Key USR23 and 24 – Headset State Bitmask
Example of an Event Configu ration entry To configure an Answer Call event to be generated when PIO[0] is pressed for a short duration when the headset is in an Incoming Call state PS Key 24 would include the following hex value entry:
0601 0001 0020
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 45 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.17 Tone Con fig ur ati on Each headset event can be associated with a tone to be played when the event occurs. Two PS Keys are used to configure tones:
USR25: This key defines the number of entries in USR26 i.e. 1 – n.
USR26: This key defines 1 – n event/tone associations in the form:
Label
System Event
Tone
Type
uint8
uint8
Range
0x00 to 0x15 (1) or 0xf f (2)
0x00 to 0x38(3)
(1)
This is the number of the event as an offset of 0x6000, see Appendix B
(2)
The value 0xf f is used to associate the tone used as the headset’s Out of Band Ring Tone, see example below.
(3)
This represents the range of currently available tones, see Appendix C Table A.38: PS Key USR26 – Tone Configu ration Bit Fields
Example: To define an Out of Band Ring Tone (Valkyries): Event = 0xf f , Tone = 0x1d To define toneShort 5 to be played on EventPowerOn: EventPowerOn = 0x6001 = 01, Short 5 = 0x06 Therefore the PS Key hex values required to implement these tones would be: PS Key USR25 = 0002 (indicates that there are two entries in PS Key USR26) PS Key USR26 = f f 1c 0106
A.18 PIO Out pu t Con fi gu rat io n PS Key USR27 provides a method of configuring a PIO as an output pin when certain state/event conditions are met. A specified pin can be configured to high when one of the following events is generated:
Call Active
Incoming Ring
Outgoing Ring
Active SCO
Power On
NiMH Charger Enable
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 46 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
The key value is set in the format:
Label
Call Act iv e PIO
Incoming Ring PIO
Headset Outgoing Act iv e Ring PIO PIO (SCO)
Power On PIO
NiMH Charger Enable PIO
Unused
Unused
Type
uint16 (D15-12)
(D11-8)
(D7-4)
uint16 (D15-12)
(D11-8)
(D7-4)
(D3-0)
(D3-0)
Table A.39: PS Key USR26 – PIO Outp ut Conf igur ation Bit Fields Description of Bit Fields Call Active: If activated, the PIO specified in this field is held high when the headset is in an ongoing call. This is set whenever the headset is in an ongoing c all. If the call is ended, either by the headset or by the AG, this PIO will be set Low. Incoming Ring: If activated, the PIO specified in this field is held high when the headset is in the IncomingCallEstablish state. Outgoing Ring: If activated, the PIO specified in this field is held high when the headset is in the OutgoingCallEstablish state. Headset Active SCO: If activated, the PIO specified in this field is held high when SCO is active and audio is routed to the headset. Power On: If activated, the PIO specified in this field is held high when the headset is in the On state. NiMH Charger Enable: If activated, the PIO specified in this field is held high to s witch on the external NiMH battery fast charging circuit. Example: To configure a Power On PIO[6] and a Ringing PIO[10]. The PS Key value would be configured as follows:
Label
Call Act iv e
Incoming Ring
Outgoing Ring
Act ive SCO
Power On
NiMH Charger Enable
Unused
Unused
Binary Value
1111
1010
1111
1111
0110
1111
1111
1111
Hex value
0xf
0xa
0xf
0xf
0x6
0xf
0xf
0xf
If an entry is set to 0xf the PIO will not be used Table A.40: PS Key USR26 – Example Entry This gives a PS Key hex value of:
f af f 6f f f
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 47 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.19 Tri Col ou r L ED Inf or mat io n PS Key USR28 is used to define the PIO or LED attached to any tricolour LEDs. Once defined, tricolour LEDs can then be passed into LED Filter Configuration (PS Key USR18), LED Configuration (PS Key USR20) or LED Event Configuration (PS Key USR22) to achieve different colours e.g. Red + Blue to give Purple. A bitmask is used to specify the PIO/LED attached to the Tricolour connection pins: Bitmask definition for assigning PIO_x/LED_x Bi t
D15
D14
D13
D12
D11
D10
D9
Mask value
LED_1
LED_0
TriCol_a + TriCol_c
TriCol_b + TriCol_c
TriCol_a + TriCol_b
PIO_10
PIO_9
D8
D7
D6
D5
D4
D3
D2
D1
D0
PIO_8
PIO_7
PIO_6
PIO_5
PIO_4
PIO_3
PIO_2
PIO_1
PIO_0
PS Key USR28 The effect of setting USR28 is best described by considering an example: Label
TriCol_a
TriCol_b
TriColor_c
Unused
Type
uint16 (D15-11)
(D10-7)
(D6-4)
(D3-0)
Description
Define PIO_x/LED_x (to specify the PIO or LED pin connected to TriCol_a LED pins)
Define PIO_x/LED_x (to specify the PIO or LED pin connected to TriCol_b LED pins)
Define PIO_x/LED_x (to specify the PIO or LED pin connected to TriCol_c LED pins)
n/a
Example: to define a Red, Green and Blue connected to PIO[2], LED_0 and LED_1 respectively. (See table Bitmask definition for assigning PIO_x/LED_x for further explanation)
0x2
0xe
0xf
0x0
Binary
0010
1110
1111
0000
Following the example configuration above specifying the LED entries in LED Filter Configuration (PS Key USR18), LED Configuration (PS Key USR20) or LED Event Configuration (PS Key USR22) will have the following results: LED entry used
Resulting LED Colour
2
Red LED only
14
Green LED only
15
Blue LED only
11
Red and Green LEDs
12
Green and Blue LEDs
13
Red and Blue LEDs
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 48 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
A.20 Pow er Tab le Set ti ngs PS Key HFP_POWER_TABLE contains the power table used by the HFP library for any connections made. It allows the link policy and the role switching implemented by the HFP library to be configured. The power table supports entries for two modes:
Normal connected: connected with no active SCO link.
SCO conn ected: connected with an active SCO link.
The first word of the entry defines the number of entries for the Normal and SCO power table with a role for each mode. The bitfields of the first word are defined as: Word 1 Label
Normal Role
Normal number of Entries
SCO Role
SCO Number of Entries
Type
Uint16 (D15-12)
(D11-8)
(D7-4)
(D3-0)
Description
Role Definitions:
Role Definitions:
0x00 = Master
0x00 = Master
0x01 = Slave
0x01 = Slave
0x02 = Passive
0x02 = Passive
Subsequent entries define the power table for each mode. Each entry is in the form: Label
State
min_in terval
max_interval
attempt
timeou t
time
Type
uint16
uint16
uint16
uint16
uint16
uint16
Description
l p_ ac t i ve (0x0000-use
Defines the minimum ??? interval
Defines the maximum ??? interval
Determines how many slots the slave shall listen when not treating the connection as a scatternet link.
Determines how many additional slots the slave shall listen when not treating the connection as a scatternet link.
The period for which the mode will be entered. See example entry below.
active mode)
l p_ sni f f (0x0001-use sniff mode)
l p_passi ve (0x00f f don’t care)
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 49 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Description of PS Keys
Example entry for PS Key HFP_POWER_TABLE This example describes the default settings to describe a typical power table entry: Word 1 Label
Normal Role
Normal number of Entries
SCO Role
SCO Number of Entries
decimal
1
2
1
2
Hex
0x1
0x2
0x1
0x2
Description
Role is slave
Defines two entries for normal connections
Role is slave
defines two entries for SCO connections
Normal Mode power table: Label
state
min interval
max interval
attempt
timeout
time
Entry
lp_passive
0
0
0
0
1
Hex value
0x00f f
0x0000
0x0000
0x0000
0x0000
0x0001
Entry
lp_sniff
800
800
4
1
0
Hex value
0x0001
0x0320
0x0320
0x0004
0x0001
0x0000
SCO Mode power table: Label
state
min interval
max interval
attempt
timeout
time
Entry
lp_passive
0
0
0
0
1
Hex value
0x00f f
0x0000
0x0000
0x0000
0x0000
0x0001
Entry
lp_sniff
160
160
4
1
0
Hex value
0x0001
0x00a0
0x00a0
0x0004
0x0001
0x0000
Thus the hexadecimal entry for the PS key would be:
1212 00f f 0000 0000 0000 0000 0001 0001 0320 0320 0004 0001 0000 00f f 0000 0000 0000 0000 0001 0001 00a0 00a0 0004 0001 0000 This example defines the following behaviour: Word 1defines the device as slave in both modes and indicates that there are two power table entries for each mode.
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 50 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
BlueVOX2 System Events
Appendix B
BlueVOX2 System Events
Table B.1 lists the viable BlueVOX BlueCore4-Headset system events. Note: In the majority of situations, System Events are referenced in PS Keys as an offset of their base 0x6000. i.e. EventPowerOn ( 0x6001) is identified using 0x01. However, in some cases the full Event number is required.
System Event
Event number
Event Type
Description
Power On
0x6001
Action
Power The Headset On
Power Off
0x6002
Action
Shutdown the headset
Enter Pairing Mode
0x6003
Action
Make the headset Connectable / Discoverable
Voice Dial
0x6004
Action
Request a Voice Dial
Last Number Redial
0x6005
Action
Request a Last Number Redial
Answer
0x6006
Action
Answer a single Incoming call
Reject
0x6007
Action
Reject a single Incoming call
Cancel / End
0x6008
Action
Cancel / End a single active call
Transfer Audio
0x6009
Action
Transfer the audio of an active call to or from the AG
Toggle Mute
0x600a
Action
Toggle the Mute state of the headset
Volume Up
0x600b
Action
Increase the local volume and inform the AG of a volume change
Volume Down
0x600c
Action
Decrease the local volume and inform the AG of a volume change
Toggle Volume
0x600d
Action
Swap the orientation of the volume buttons (state does not persist in PS KEY_USR_10)
TWC Release All Held
0x600e
Action
Release all held calls
TWC Accept Waiting Release Active
0x600f
Action
Accept a held or waiting call and release the active call
TWC Accept Waiting Hold Active
0x6010
Action
Accept a held or waiting call and place the active call on hold
TWC Add Held To TWC
0x6011
Action
Create a Multi Party call by adding any held calls to the conversation
TWC Expicit Tx
0x6012
Action
Connect Multi-party calls and remove yourself from the conversation
Enable/Disable Leds
0x6013
Action
Reset Paired Device List
0x6014
Action
Reset the Paired Device List and the Last/Default User
Enter DUT Mode
0x6015
Action
Enter Device Under Test mode
Pairing Fail
0x6016
Indication
A Pairing Attempt has failed
Pairing Successful
0x6017
Indication
A Pairing attempt has succeeded
Audio Link Open
0x6018
Indication
An Audio Link has been Opened (also indicates Tone Playback complete)
Audio Link Close
0x6019
Indication
An Audio link has been Closed
Low Battery
0x601a
Indication
The Battery Voltage is below the minimum threshold
End Of Call
0x601b
Action
CS-110372-UGP1
End Of Call Detected
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 51 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
BlueVOX2 System Events
System Event
Event number
Event Type
Description
Establish SCL
0x601c
Indication
Establish a Service Level Connection as per the Reconnection policy
LED Event Complete
0x601d
Indication
A LED Event indication has finished
Trickle Charge
0x601e
Indication
The Battery Charger has entered Trickle Charge (NiMH Charger Only)
Auto Switch Off
0x601f
Internal
The Automatic Switch off timer has elapsed
Fast Charge
0x6020
Indication
The Battery Charger has entered Fast Charge
Battery OK
0x6021
Indication
The Battery Voltage is above the minimum threshold
Charger Connected
0x6022
Action
The Charger has been connected
Charger Disconnected
0x6023
Action
The Charger has been removed
SLC Disconnected
0x6024
Indication
A Service Level Connection has ben removed
Complete UnMute Mic
0x6025
Internal
Complete the UnMute Action
Link Loss
0x6026
Indication
An abnormal SLC disconnect has been detected
Limbo Timeout
0x6027
Internal
Complete the UnMute Action
Mute On
0x6028
Action
Activate Mute
Mute Off
0x6029
Action
De-Activate Mute
Mute Reminder
0x602a
Internal
Headset is Muted
Reset Complete
0x602b
Internal
A Paired Device Reset is now complete
Enter TXContTestMode
0x602c
Action
Enter TX Continuous Test Mode
Enter DUT State
0x602d
Action
Enter the Device Under Test State
Volume Orientation Normal
0x602e
Action
Restore the default orientation of the Volume buttons
Volume Orientation Invert
0x602f
Action
Invert the Action of the Volume Buttons
Network Not Present
0x6030
Indication
An AG has reported that there is no GSM Network Present
Network Present
0x6031
Indication
An AG has reported that there is a GSM Network Present
Enable LEDS
0x6032
Action
-
Disable LEDS
0x6033
Action
-
SLCConnected
0x6034
Indication
An SLC has been Established
Error
0x6035
Indication
An AT command Error has been received
Long Timer
0x6036
Indication
A button has been held down for the Long Press Duration
tVLong Timer
0x6037
Indication
A button has been held down for the Very Long Press Duration
Enable Power Off
0x6038
Internal
Allow Power Off Events to occur
Charge Error
0x6039
Indication
The Charger is reporting an Error whilst an active call is present
Place Incoming Call On Hold
0x603a
Action
Place an incoming call on hold
Accept Held Incoming Call
0x603b
Action
Accept the held incoming call
Reject Held Incoming Call
0x603c
Action
Reject the held incoming call
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 52 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
BlueVOX2 System Events
System Event
Event number
Event Type
Description
Cancel Led Indication
0x603d
Action
HSP Enter Active Call State
0x603e
Internal
Enters Active call State when in HSP mode
Charge Error In Idle State
0x603f
Indication
The Charger is reporting an Error When no call is present
Reconnect Failed
0x6040
Indication
Indicates headset failed to reconnect following abnormal disconnect
Reset the LED subsystem
Gas Gauge 0
0x6041
Indication
The battery voltage is above gas gauge level 0
Gas Gauge 1
0x6042
Indication
The battery voltage is above gas gauge level 1
Gas Gauge 2
0x6043
Indication
The battery voltage is above gas gauge level 2
Gas Gauge 3
0x6044
Indication
The battery voltage is above gas gauge level 3
Check for Audio Transfer
0x6045
Internal
Establish an audio link if one is not already open.
Table 6.1: BlueVOX2 System Events
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 53 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
BlueVOX2 Tones
Appendix C
BlueVOX2 Tones
Tone Name
Value
Musical Note
Duration
No tone
0x00
Middle 0
0x01
G5
300ms
Short 1
0x02
C6
100ms
Short 2
0x03
E6
100ms
Short 3
0x04
G6
100ms
Short 4
0x05
AS6
100ms
Short 5
0x06
C7
100ms
Short 6
0x07
D7
100ms
Short 7
0x08
E7
100ms
Short 8
0x09
FS7
100ms
Middle 9
0x0a
GS7
300ms
4 Note Rising Scale
0x0b
GS4 DS5 GS5 C6
150 150 150 150
4 Note Falling Scale
0x0c
C6 GS5 DS5 GS4
150 150 150 150
2 Note Rising Scale
0x0d
E6 A6
200 200
2 Note Falling Scale
0x0e
A6 E6
300 300
Long High Short Low
0x0f
G5 G7
400 100
Short Middle
0x10
GS7
100
Long Middle
0x11
GS7
500
Long Low
0x12
G5
500
Short High
0x13
G6
100
V Long High
0x14
G6
800
Long High
0x15
G6
500
Short Double Low
0x16
G5 Ring Tone G5
100 100
Short Double High
0x17
G6 G6
100 100
battery_low_tone
0x18
E6 AS6 E6 AS6 E6
125 125 125 125 125
low_500ms_tone
0x19
G5
500
Long Double Low
0x1a
G5 REST G5
500 500 500
ring_twilight
0x1b
Ring Tone
-
ring tone_g_s_t_q
0x1c
Ring Tone
-
ring tone_valkyries
0x1d
Ring Tone
-
ring tone_greensleeves
0x1e
Ring Tone
-
ring_two_beeps
0x1f
Ring Tone
-
ring _fairground
0x20
Ring Tone
-
ring _counterpoint
0x21
Ring Tone
-
ring_major_arp
0x22
Ring Tone
-
ring_major_scale
0x23
Ring Tone
-
ring_minor_arp
0x24
Ring Tone
-
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
_ ä ì É ` ç ê É
Page 54 of 58
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
BlueVOX2 Tones
Tone Name
Value
Musical Note
Duration
ring_harmonic _minor_scale
0x25
Ring Tone
-
ring_more_than_a_feeling
0x26
Ring Tone
-
ring_eight_beeps
0x27
Ring Tone
-
ring_four_beeps
0x28
Ring Tone
-
ring_bumble_bee
0x29
Ring Tone
-
ring_aug_scale
0x2a
Ring Tone
-
ring_dim_scale
0x2b
Ring Tone
-
CustomRingTone
0x2c
Ring Tone
-
4 Note Low to High
0x2d
G5 D6 G6 B5
37.5 37.5 37.5 37.5
4 Note High to Low
0x2e
B5 G6 D6 G5
37.5 37.5 37.5 37.5
Short High to Low
0x2f
G6 G5
25 25
5 Rapid High Tones
0x30
B6 B6 B6 B6 B6
94 94 94 94 94
Short Low to High
0x31
DS7 G7
100 100
Short High to Low
0x32
G7 DS7
100 100
Short V High
0x33
DS8
50
12 High/Higher beeps
0x34
B6 G8 B6 G8 B6 G8 B6 G8 B6 G8 B6 G8
50 50 50 50 50 50 50 50 50 50 50 50
Short Middle
0x35
DS8
50
5 high beeps
0x36
A6 rest A6 rest A6 rest A6 rest A6 rest
50 50 50 50 50 50 50 50 50 50
Short Low to High
0x37
B6 rest DS8
50 50 50
Short High to Low
0x38
DS8 rest B6
50 50 50
Table 6.2: BlueVOX2 Tones
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 55 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
BlueVOX2 Headset States
Appendix D
BlueVOX2 Headset States
This appendix lists the headset states currently used in BlueVOX 1 BlueCore4 Headsets: State
Value
Description
headsetLimbo
0x00
The headset is physically but not logically on (i.e. the headset application has not received a Power On event) this state is used for NiMH charging
headsetConnectable
0x01
The headset is Connectable but not Discoverable
headsetConnDiscoverable
0x02
The headset is both Connectable and Discoverable
headsetConnected
0x03
The headset is Connected to an AG - No Longer Connectable or Discoverable
headsetOutgoingCallEstablish
0x04
The Connected AG is making an outgoing call
headsetIncomingCallEstablish
0x05
The Connected AG is receiving an Incoming call Indication
headsetActiveCall
0x06
A call is in progress
headsetTestMode
0x07
DUT mode (Device Under Test)
headsetThreeWayCallWaiting
0x08
An active call is in progress and a second incoming call is being indicated
headsetThreeWayCallOnHold
0x09
An active call is in progress and a second call is currently on hold
headsetThreeWay Multi Call
0x0a
Two active calls are in progress - multi-party calling
headsetIncomingCallOnHold
0x0b
A single Incoming Call has been placed on hold
headsetActiveCallNoSco
0x0c
A call is in progress but there is not an active audio connection
Table 6.3: BlueVOX2 Headset States
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
Page 56 of 58
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Terms and Definitions
Terms and Defini tion s BlueCore
™
®
Group term for CSR’s range of Bluetooth wireless technology chips
Bluetooth
Set of technologies providing audio and data transfer over short-range radio connections
Bluetooth SIG
Bluetooth Special Interest Group
CSR
Cambridge Silicon Radio
AG
Audio Gateway
BCSP
BlueCore Serial Protocol
DUT
Device Under Test
EEPROM
Electrically Erasable Programmable Read Only Memory
eSCO
extended Synchronous Connection-Oriented
HFP
Handsfree Profile
HSP
Headset Profile
HMI
Human Machine Interface
2
IC
Inter-Integrated Circuit
LDO
Low Drop Out
LED
Light Emitting Diode
NiMH
Nickel Metal Hydride
PIO
Parallel Input Output
ROM
Read Only Memory
SCO
Synchronous Connection-Oriented
SLC
Service Level Connection
SMPS
Switch Mode Power Supply
SPI
Serial Peripheral Interface
UI
User Interface
USB
Universal Serial Bus
VGS
Volume Gain Setting
CS-110372-UGP1
© CSR plc 2005 This material is subject to CSR’s non-disclosure agreement.
_ ä ì É ` ç ê É
B l u e V O X 2 C o n f i g u r a t o r U s e r G u i d e
Page 57 of 58