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
BCM2035 User Manual
04/23/03
Broadcom Corporation
Page 42 Load Mini-Drivers From UART Document 2035-UM100-R
Figure 22: Host and Bluetooth Device Handshaking Prologue: Mode is 0 and Configuration Data is
Missing or Invalid. Negotiate Baud Rate and Download Mini-Driver Over UART
Figure 23: Host and Bluetooth Device Handshaking Prologue: Following Bluetooth Firmware Start-up
Host
Host Controller
0x55 (UART
RX)
Negotiation
character 0x55
should not be
sent earlier then
~1ms
Host Controller's
UART-CTS
should be TRUE
within ~1ms of
Reset
"41"
(at negotiated
baud-rate over UART
TX)
CTS
Host
Host Controller
For systems
without non-
volatile-memory
and 15.36Mhz
crystals (default)
Host should not
transmit CTS for
~5Ms after Host
controller reset.
CTS
RTS
Host Controller
will sense CTS ,
Iniatialize
Bluetooth
subsystems and
transmit RTS
within 100ms
Download mini-driver
vendor specific command
Download mini driver
successful
command
complete event
~100ms after
transmitting
command
complete event
the boot-rom will
transmit "41"
upon receiving
CTS
"41"