User's Manual
Table Of Contents
- 2035-UM1xx.book
- Table of Contents
- List of Figures
- List of Tables
- Section 1: Introduction
- Section 2: Hardware System Overview
- Section 3: BCM2035 Usage Models
- Section 4: Hardware Configuration
- Section 5: Software Configuration
- Introduction
- Hardware Power-Up Sequence
- Boot ROM Power-Up Sequence
- Firmware Power-Up Sequence
- BCM2035 Mini-Drivers
- Loading Mini-Drivers from USB
- Load Mini-Drivers From UART
- SCO Configuration
- Frequency Trimming
- UART Sleep Mode Operation
- Section 6: Configuration Data File System
- Section 7: Vendor-Specific HCI Command Reference
- Section 8: ASCII Hex File Download Protocol
- Section 9: ASCII HEX File Format
- Section 10: Configuration Data Download Protocol
- Section 11: Configuration Data Image Format
- Section 12: UART Start-up Sequence
- Section 13: USB Start-up Sequence
9/29/2004 OV4F2
C
O
N
F
I
D
E
N
T
I
A
L
F
O
R
W
I
S
T
R
O
N
C
O
R
P
O
R
A
T
I
O
N
User Manual BCM2035
04/23/03
Broadcom Corporation
Document 2035-UM100-R SCO Configuration Page 49
SCO CONFIGURATION
INTRODUCTION
The
BCM2035 supports Bluetooth SCO connections for phone quality voice applications. HV1, HV2, and HV3
packet types are supported, as are CVSD, a-law, and m-law air coding.
Voice data may be input and output to or from the PCM interface, the UART, or the USB interface using linear
PCM, a-law, or m-law audio formats.
The section describe the software requirements needed to support SCO, and any associated Vendor Specific
HCI Commands that must be issued to set the correct configuration.
IMPLEMENTING SCO OVER PCM
The two basic requirements to successfully implement SCO connections while using the PCM interface on the
BCM2035 are proper hardware connections between the PCM interface and the audio CODEC, and proper
configuration of the PCM interface through Vendor Specific HCI commands. The hardware connections
between the PCM interface and audio CODEC are described in Section 4.5.1.
Once the configuration is correct, an SCO connection that is added through the use of the standard
Add_SCO_Connection HCI command will automatically route audio data to and from the PCM interface.
PCM Data Format
The data formats supported by the PCM Interface are Linear PCM, a-law, and m-law. Linear PCM is a signed
2's complement 16-bit format, and a-law and m-law are 8-bit formats defined in ITU recommendation G.711.
When using a-law or m-law, the 8-bit data may be right or left justified within a 16-bit PCM time slot, and may
be shifted Least Significant Bit first or Most Significant Bit first.
When using Linear PCM audio coding with the PCM interface, the data format may be adjusted to allow
flexibility interfacing with various CODECs. Each PCM time slot is 16-bits long, but the meaningful PCM data
supported by the
BCM2035 is always 13-bits. The data may have fill bits inserted to format it as 14, 15, or 16-
bits, and the right/left justification may be modified. The fill bits are programmable and may each be set to 1,
0, or a copy of the sign bit. The position of the fill bits depends on the number of fill bits enabled, and the
justification selected.
The Linear PCM data may be shifted out of the PCM interface Least Significant Bit first, or Most Significant Bit
first. These settings are controlled through Vendor Specific HCI commands discussed throughout this
document, and in Appendix 1.