The STA2500D is a single chip Bluetooth solution that is fully optimized for automotive
applications such as telematics, navigation and portable navigation. Power consumption
levels are targeted at battery powered devices and single chip solution brings cost
advantages. Manufacturers can easily and quickly integrate the STA2500D on their product
to enable a rapid time to market.
STA2500D supports the Bluetooth specification V2.1 + EDR (“Lisbon“) and is optimized in
terms of RF performance and cost.
The STA2500D is a ROM-based solution targeted at applications requiring integration up to
HCI level. Patch RAM is available, enabling multiple patches/upgrades and fast time to
volume. The STA2500D’s main interfaces are UART or SPI for HCI transport, PCM for voice
and GPIOs for control purposes.
The radio has been designed specifically for single chip requirements, for low power
consumption and minimum BOM count.
6/58Doc ID 16067 Rev 2
STA2500DQuick reference data
2 Quick reference data
BT_VIO_x means BT_VIO_A, BT_VIO_B.
BT_HVx means BT_HVA, BT_HVD.
(See also Ta bl e 1 2.)
2.1 Absolute maximum ratings
The absolute maximum rating (AMR) corresponds to the maximum value that can be
applied without leading to instantaneous or very short-term unrecoverable hard failure
(destructive breakdown).
Table 1.Absolute maximum ratings
SymbolParameterMin.Max.Unit
BT_HVxCore supply voltages-0.34.0V
BT_VIO_A Supply voltage I/O-0.34.0V
BT_VIO_B Supply voltage I/O (for the low power clock)-0.34.0V
BT_V
V
ssdiff
T
stg
Input voltage of any digital pin-0.34.0V
in
Maximum voltage difference between different types of
V
pins.
ss
Storage temperature- 65+ 150°C
2.2 Operating ranges
Operating ranges define the limits for functional operation and parametric characteristics of
the device. Functionality outside these limits is not implied.
Table 2.Operating ranges
SymbolParameterMin.Typ.Max.Unit
BT_T
BT_HVxCore supply voltages2.652.752.85V
BT_VIO_AI/O supply voltage1.65-2.85V
BT_VIO_BI/O supply voltage (for the low power clock)1.17-2.85V
Operating ambient temperature-4025+85
amb
-0.30.3V
°
C
Doc ID 16067 Rev 27/58
Quick reference dataSTA2500D
2.3 I/O specifications
The I/Os comply with the EIA/JEDEC standard JESD8-B.
1. X is the source/sink current under worst-case conditions according to the drive capabilities (see Section 3)
Low level output voltageId = X
High level output voltageId = X
(1)
(1)
mA
mA
--0.15V
BT_VIO_x
- 0.25
--V
V
V
2.4 Clock specifications
The STA2500D supports, on the BT_REF_CLK_IN pin, the system clock both as a sine
wave clock and as a digital clock. For configuration, see Tab le 1 2 : pin BT_VDD_CLD (E6).
Table 5.System clock supported frequencies
SymbolParameterValuesUnit
F
Table 6.System clock overall specifications
SymbolParameterMin.Typ.Max.Unit
F
INTOL
8/58Doc ID 16067 Rev 2
Clock input frequency list
IN
Tolerance on input frequency-20-20ppm
9.6, 10, 13, 16, 16.8, 19.2,
26, 33.6, 38.4
MHz
STA2500DQuick reference data
Table 7.System clock, sine wave specifications
SymbolParameterMin.Typ.Max.Unit
V
PP
N
Z
INRe
Z
INIm
Z
IDRe
Z
IDim
1. Equivalent to max 10 ps time jitter (rms).
Table 8.System clock, digital clock DC specifications
Peak to peak voltage range0.270.51.8V
Total harmonic content of input signal---25dBc
H
Real part of parallel input impedance at pin306090kΩ
Imaginary part of parallel input impedance at pin-58pF
Real impedance discrepancy between active and nonactive mode of clock input
Imaginary impedance discrepancy between active and
non-active mode of clock input
Phase noise @ 10 kHz
(1)
-- 7kΩ
--500fF
---126dBc/Hz
SymbolParameterMin.Typ.Max.Unit
V
IL
V
IH
C
IN
Table 9.System clock, digital clock AC specifications
Low level input voltage-0.2-
High level input voltage
BT_VDD_CLD
Input capacitance-58pF
0.65 *
-
0.35 *
BT_VDD_CLD
(BT_VDD_CLD
+ 0.2) and
(≤ 2.85)
V
V
SymbolParameterMin.Typ.Max.Unit
T
RISE
T
FAL L
D
CYCLE
-Phase noise @ 10 kHz
1. Equivalent to max 15 ps time jitter (rms).
Table 10.Low power clock specifications
10% - 90% rise time-1.56ns
90% - 10% fall time-1.56ns
Duty cycle455055%
(1)
---121dBc/Hz
The low power clock pin is powered by connecting BT_VIO_B to the wanted supply.
Table 10.Low power clock specifications (continued)
The low power clock pin is powered by connecting BT_VIO_B to the wanted supply.
SymbolParameterMin.Typ.Max.Unit
V
hyst
C
IN
T
RISE
T
FAL L
-Total jitter
1. The rise and fall time are not the most important parameters for the low power clock input due to the Schmitt trigger logic. It
is more important that the noise on the Low power clock line remains substantially below the hysteresis in amplitude.
2. The total jitter is defined as the error that can appear on the actual frequency between two clock edges compared to the
perfect frequency. Due to this, the total jitter value must contain the jitter itself and the error due to the accuracy on the
clock frequency. The lower the accuracy, the smaller the jitter is allowed to be.
Active: audio eSCO (2-EV5), (64 kbps symmetrical T
Active: audio eSCO (3-EV5), (64 kbps symmetrical T
1. The power consumption (except for power safe modes i.e. complete power down and deep sleep mode)
will rise (with approx. 200 µA) if an analog system clock is used instead of a digital clock.
2. In functional sleep mode, the baseband clock is still running.
= 6)
eSCO
12
15
= 12)
eSCO
7.8
11.7
= 18)
eSCO
6.5
10.5
= 36), Master mode8mA
eSCO
= 36), Slave mode11.9mA
eSCO
= 36), Master mode6.3mA
eSCO
= 36), Master mode5.75mA
eSCO
mA
mA
mA
mA
mA
mA
mA
mA
Doc ID 16067 Rev 211/58
Block diagram and electrical schematicSTA2500D
/
3 Block diagram and electrical schematic
Figure 1.Block diagram and electrical schematic
BT_RFP
Filter
BT_RFN
BT_REF_CLK_IN
BT_VDD[4:0]
INTERNAL SUPPLY MANAGEMENT
RECEIVER
RF PLL
Fracti onal N
TRANSMI TTER
AUTOCALIBRATION
BT_TEST[1:0]BT_VDD_CLD
BT_HV[1:0]BT_VIO_ABT_VIO_B
DEMO-
DULATOR
CONTROL
AND
REGISTER
BASEBAND
CORE
MODULATOR
PLL
EBC
AMBA
PERIPH.
BUS
BT_AF_PRG BT_VSS[5:0]
ARM7TDMI
CPU Wrapper
RAM
ROM
INTERRUPT
UART/
SPI
TIMER
PCM
WLAN
I2C
JTAG
BT_GPIO_0
BT_GPIO/JTAG
[4: 0]
BT_LP_CLK
BT_HOST_WAKEUP
BT_SPI_INT
BT_WAKEUP
BT_RESETN
BT_UART/BT_SPI
[3: 0]
BT_PCM
[3: 0]
BT_CONFIG
[2: 0]
BT_CLK_REQ_IN
[1: 0]
BT_CLK_REQ_OUT
[1:0]
12/58Doc ID 16067 Rev 2
STA2500DPinout
4 Pinout
Figure 2.Pinout (bottom view)
7654321
A
B
C
D
E
F
G
BT_VDD_DSM
BT_VDD_N
BT_VDD_CL
BT_VDD_CLD
BT_HOST_WAKEUP
/BT_SPI_I NT
GPIO_3
BT_CLK_REQ_OUT_2
BT_TEST2
BT_VSSANA
BT_CLK_REQ_IN _1
BT_UART_T XD
/ BT_SPI_DO
BT_CLK_REQ_IN_2
BT_VSSRF
BT_WAKEUP
BT_GPIO_0
GPIO_0
BT_UART_RXD
/ BT_SPI_D I
BT_VSSANABT_VSSANABT_TEST1
BT_CLK_REQ_OUT_1
BT_UART_R TS
/ BT_SPI_C S
BT_UART_C TS
/ BT_SPI_C LK
BT_RFPBT_RFNBT_HVA
BT_GPIO_16
BT_GPIO_8
JTAG_TCK
BT_RESETNBT_REF_CLK_ IN
BT_VSSDIGBT_VSSDIGBT_AF_PRG
BT_VIO_B
BT_LP_CL K
BT_VSSRF
BT_GPIO_11
BT_PCM_SYNC
BT_CONFIG_1
BT_CONFIG_3
BT_VDD_RF
BT_GPIO_9
BT_GPIO_10
BT_PCM_CLKBT_PCM_A
BT_PCM_B
BT_CONFIG_2
BT_HVDBT_VDD_DBT_VIO_A
4.1 Pin description and assignment
Ta bl e 1 2 shows the pin list of the STA2500D.
In columns “Reset” and “Default after reset”, the “PD/PU” shows the pads implementing an
internal pull-down/up.
The column “Reset” shows the state of the pins during hardware reset; the column “Default
after reset” shows the state of the pins after the hardware reset state is left, but before any
software parameter download.
The column “Type” describes the pin directions:
–I for Input (All inputs have a Schmitt trigger function.)
–O for Output
–I/O for Input/Output
–O/t for tri-state output
Doc ID 16067 Rev 213/58
PinoutSTA2500D
For the output pin the default drive capability is 2 mA, except for pin K3 (BT_GPIO_11) and
pin L3 (BT_GPIO_8) where it is 8 mA such that when used for Class 1, these 2 pins can be
used for a switch control in a cheaper way.
Name
Pin
#
DescriptionTypeReset
(3)
IInputInput
(1)
Default
after reset
(2)
Table 12.The STA2500D pin list (functional and supply)
Clock and reset pins
BT_RESETND3Global reset - active low--
BT_REF_CLK_IND6Reference clock input
BT_LP_CLKG3 Low power clock input--
SW initiated low power mode
BT_CLK_REQ_OUT_1 C4
BT_CLK_REQ_OUT_2 G7
Wake-up signal to Host (Active high or Active
low, depending on configuration pins)
Wake-up signal to Host. Active low
(SPI mode only)
BT_CLK_REQ_IN_2G6 Clock request input (Active low)Input PUInput PU
BT_HOST_WAKEUP/
BT_SPI_INT
BT_WAKEUPC5 Wake-up signal to Bluetooth (Active high)I/OInput
F7Wake-up signal to Host or SPI interruptInput PDOutput
(5)
Input
UART interface
BT_UART_RXD/
BT_SPI_DI
UART receive data
F5
SPI data in Input PD
Input PD
Input PD
BT_UART_TXD/
BT_SPI_DO
BT_UART_CTS/
BT_SPI_CLK
UART transmit data Output high
F6
SPI data out Input PD
I/O
(4)
UART clear to send
G4
SPI clock Input PD
Input PU
Input PU
BT_UART_RTS/
BT_SPI_CSN
UART request to send Output low
F4
SPI chip select Input PU
PCM interface
BT_PCM_SYNCC2 PCM frame signal
BT_PCM_CLKD1PCM clock signal
I/O
BT_PCM_AD2PCM data
BT_PCM_BE1PCM data
JTAG interface
BT_GPIO_9B1JTAG_TDI or GPIO-Input PU
14/58Doc ID 16067 Rev 2
(4)
Input PDInput PD
(6)
Input PU
(6)
STA2500DPinout
Table 12.The STA2500D pin list (functional and supply) (continued)
(6)
(6)
(6)
(6)
(2)
Name
Pin
#
DescriptionTypeReset
BT_GPIO_11B2JTAG_TDO or GPIO-Input PD
BT_GPIO_10C1JTAG_TMS or GPIOI/O
BT_GPIO_16B3
JTAG_NTRST (Active low) or Alternate
function.
(4)
Input PD
-Input PD
BT_GPIO_8C3JTAG_TCK or GPIO-Input PD
(1)
(6)
(6)
(6)
(6)
General purpose input/output pins
(4)
BT_GPIO_0D5General purpose I/OI/O
Input PDInput PD
Configuration pins
BT_CONFIG_1E2---
BT_CONFIG_2F1Configuration signalIInputInput
BT_CONFIG_3F2---
RF signals
Default
after reset
Input PD
Input PD
Input PD
Input PD
BT_RFPA3
Differential RF portI/O
BT_RFNA4--
Power supply
BT_HVAA7
Power supply (Connect to 2.75 V)---
BT_HVDG1
BT_VIO_AG5 1.65 V to 2.85 V I/Os supply
BT_VIO_BF31.17 V to 2.85 V I/Os supply
(7)
(7)
---
---
System clock supply
1.65 V to 2.85 V
BT_VDD_CLDE7
(Connect to BT_VIO_A in case of a digital
---
reference clock input, to BT_VSSANA in case
of an analog reference clock input.)
E3
BT_VSSDIG
Digital ground---
E4
B4
BT_VSSANA
Analog ground---B6
C6
A2
BT_VSSRF
RF ground---
A5
--
BT_VDD_CLD7
Internal supply decoupling/Regulator output.
Need 220nF decoupling capacitor to
BT_VSSANA.
Doc ID 16067 Rev 215/58
---
PinoutSTA2500D
Table 12.The STA2500D pin list (functional and supply) (continued)
Name
BT_VDD_DG2
BT_VDD_DSMB7
BT_VDD_NC7
BT_VDD_RFA1
Other pins
Pin
#
DescriptionTypeReset
Internal supply decoupling/Regulator output.
Need 220nF decoupling capacitor to
BT_VSSDIG.
Internal supply decoupling/Regulator output.
Need 220nF decoupling capacitor to
BT_VSSANA.
Internal supply decoupling/Regulator output.
Need 220nF decoupling capacitor to
BT_VSSANA.
Internal supply decoupling/Regulator output.
Need 220nF decoupling capacitor to
BT_VSSRF.
(1)
Default
after reset
---
---
---
---
(2)
BT_TEST1B5
Test pinI/OInput
(8)
Input
(8)
BT_TEST2A6
BT_AF_PRGE5Test pin (Leave unconnected)
1. Pin behaviour during HW reset (BT_RESETN low).
2. Pin behaviour immediately after HW reset and internal chip initialization, but before SW parameter download.
3. See also pin BT_VDD_CLD in Table 12.
4. Reconfigurable I/O pin.The functionality of these I/Os can be configured through software parameter download (see
Section 7.5).
5. Should be strapped to BT_VSSDIG if not used.
6. JTAG mode.
7. Described in Section 4.3.
8. To be strapped to BT_VSSANA.
9. Pin is ST - reserved for test function and it must be soldered to an isolated pad (not connected to anything, just floating).
(9)
I/OOpenOpen
4.2 HW configuration of the STA2500D
By means of the three configuration pins, one can select the Host interface (UART or SPI)
and clock request signal polarity to be used at startup.
The available combinations of Host interface and protocol are illustrated in Tab l e 1 3 (where
‘1’ = BT_VIO_A and ‘0’ = BT_VSSDIG). Additionally, the polarity of the BT_CLK_REQ
signals can be programmed through the same pins. The polarity of the BT_CLK_REQ_IN
and BT_CLK_REQ_OUT signals is further described in Section 6.8.
16/58Doc ID 16067 Rev 2
STA2500DPinout
Table 13.Configuration programming
BT_CONFIG_1 BT_CONFIG_2 BT_CONFIG_3
Communication
Protocol
BT_CLK_REQ_OUT_1 BT_CLK_REQ_OUT_2
010H4 UARTActive high
011H4 UARTActive low
Depending on SW
config
Depending on SW
config
110ReservedReservedReserved
111ReservedReservedReserved
100ReservedReservedReserved
101Enhanced H4 SPI
(1)
Active highActive low
001ReservedReservedReserved
000ReservedReservedReserved
1. In order to get other SPI modes, the Host must send a specific configuration at start-up in addition of these configuration
pins.
4.3 I/O Supply
The device STA2500D has two different I/O supplies: BT_VIO_A and BT_VIO_B.
The two different pins may be potentially connected to separate dedicated voltage supplies
in order to harmonize the digital levels to the platform.
They are linked to different interfaces as described in Ta bl e 1 4 .
The transmitter uses the serial transmit data from the Bluetooth Controller. The transmitter
modulator converts this data into GFSK, π/4-DQPSK or 8-DPSK modulated I and Q digital
signals for respectively 1, 2 and 3 Mbps transmission speed. These signals are then
converted to analog signals that are low pass filtered before up-conversion. The carrier
frequency drift is limited by a closed loop PLL.
5.2 Receiver
The STA2500D implements a low-IF receiver for Bluetooth modulated input signals. The
radio signal is taken from a balanced RF input and amplified by an LNA. The mixers are
driven by two quadrature LO signals, which are locally generated from a VCO signal running
at twice the frequency. The I and Q mixer output signals are band pass filtered by a polyphase filter for channel filtering and image rejection. The output of the band pass filter is
amplified by a VGA to the optimal input range for the A/D converter. Further channel filtering
is done in the digital part. The digital part demodulates the GFSK,
coded bit stream by evaluating the phase information. RSSI data is extracted. Overall
automatic gain amplification in the receive path is controlled digitally. The RC time constants
for the analog filters are automatically calibrated on chip.
π/4-DQPSK or 8-DPSK
5.3 PLL
The on chip VCO is part of a PLL. The tank resonator circuitry for the VCO is completely
integrated without need of external components. Variations in the VCO centre frequency are
calibrated out automatically.
18/58Doc ID 16067 Rev 2
STA2500DFunctional description
5.4 Bluetooth controller V1.2 and V2.0 + EDR features
The Bluetooth controller is backward compatible with the Bluetooth specification V1.2 [] and
V2.0 + EDR []. Here below is a list with the main features of those specifications:
●Adaptive Frequency Hopping (AFH): hopping kernel, channel assessment as Master
and as Slave
●Fast Connection: Interlaced scan for Page and Inquiry scan, answer FHS at first
reception, RSSI used to limit range
●Extended SCO (eSCO) links: supports EV3, EV4 and EV5 packets
●Channel Quality Driven Data Rate change (CQDDR)
●QoS Flush
●Synchronization: BT clocks are available at HCI level for synchronization of parallel
applications on different Slaves
●L2CAP Flow & Error control
●LMP SCO handling
●2 Mbps packet types
–ACL: 2-DH1, 2-DH3, 2-DH5
–eSCO: 2-EV3, 2-EV5
●3 Mbps packet types
–ACL: 3-DH1, 3-DH3, 3-DH5
–eSCO: 3-EV3, 3-EV5
5.5 Bluetooth controller V2.1 + EDR (“Lisbon”)
●Encryption Pause/Resume (EPR)
●Extended Inquiry Response (EIR)
●Link Supervision Time Out (LSTO)
●Secure Simple Pairing
●Sniff Subrating
●Quality of Service (Qos)
–Packet Boundary Flag
–Erroneous Data Delivery
5.6 Processor and memory
●ARM7TDMI
●On chip RAM, including provision for patches
●On chip ROM, preloaded with SW up to HCI
Doc ID 16067 Rev 219/58
Functional descriptionSTA2500D
5.7 TX output power control
The STA2500D supports output power control with advanced features:
●Basic feature:
–With the standard TX power control algorithm enabled, the STA2500D will adapt
its output power when a remote BT device supports the RSSI feature; this allows
the remote device to measure the link strength and to request the STA2500D to
decrease/increase its output power. In case the remote device does not support
the RSSI feature, the STA2500D will use its ‘default’ output power level.
●Advanced features, available via specific HCI commands:
–Enhanced power control feature: allows the STA2500D to decrease autonomously
its output power until the remote BT device, supporting the RSSI feature, requests
to increase the output power.
20/58Doc ID 16067 Rev 2
STA2500DGeneral specification
6 General specification
All the values are provided according to the Bluetooth specification V2.1 + EDR (“Lisbon”)
unless otherwise specified. The below values are preliminary and will be updated in the next
version of this datasheet.
6.1 Receiver
All specifications below are given at device pin level and with the conditions as specified.
Parameters are given for each of the 3 modulation types supported.
Typical is defined at T
= 25 °C, BT_HV = 2.75 V. Minimum and Maximum are worst cases
amb
over corner lots and temperature. Parameters are given at device pin, except for receiver
interferers measured at antenna with a filter having a typical attenuation of 2.3 dB.
Table 15.Mbps receiver parameters - GFSK
SymbolParameterTest conditionMin.Typ.Max.Unit
RFinInput frequency range-2402-2480MHz
RXsensC
RXsensD
RXmax
Receiver blocking performance @ BER 0.1% on Channel 58 (without Filter)
Receiver sensitivity
(Clean transmitter)
Receiver sensitivity
(Dirty transmitter)
Maximum useable input signal
level
-
-
-
signal in GSM band 900 MHz
(824 MHz to 960 MHz)
signal in GSM band 1800 MHz
(1805 MHz to 1990 MHz)
= 25 °C, BT_HV = 2.75 V. Minimum and Maximum are worst cases
amb
Measured as defined in BT
test specification [].
-39-32=dBm
over corner lots and temperature. Parameters are given at device pin, except for receiver
interferers measured at antenna with a filter having a typical attenuation of 2.3 dB.
Table 16.Mbps receiver parameters - π/4-DQPSK
SymbolParameterTest conditionMin.Typ.Max.Unit
RFinInput frequency range=24022480MHz
RXsensC
RXsensD
RXmax
Receiver sensitivity
(Clean transmitter)
Receiver sensitivity
(Dirty transmitter)
Maximum useable input signal
level
@ BER 0.01%--87-85dBm
@ BER 0.01%--86.5-84.5dBm
@ BER 0.1%-15-9-dBm
Receiver blocking performance @ BER 0.1% on channel 58 (without Filter)
-
-
-
signal in GSM band 900 MHz
(824 MHz to 960 MHz)
signal in GSM band 1800 MHz
(1805 MHz to 1990 MHz)
= 25 °C, BT_HV = 2.75 V. Minimum and Maximum are worst cases
amb
@ Input signal
strength = -67 dBm
@ Input signal
strength = -67 dBm
--47-20dB
--48-40dB
over corner lots and temperature. Parameters are given at device pin, except for receiver
interferers measured at antenna with a filter having a typical attenuation of 2.3 dB.
Table 17.Mbps receiver parameters - 8-DPSK
SymbolParameterTest conditionMin.Typ.Max.Unit
RFinInput frequency range-2402-2480MHz
RXsensC
RXsensD
RXmax
Receiver blocking performance @ BER 0.1% on channel 58 (without Filter)
Receiver sensitivity
(Clean transmitter)
Receiver sensitivity
(Dirty transmitter)
Maximum useable input signal
level
-
Signal in GSM band 900 MHz
(824 MHz to 960 MHz)
@ BER 0.01%--79.5-77.5dBm
@ BER 0.01%--77-74.5dBm
@ BER 0.1%-20-15-dBm
@ Input signal
strength = -67 dBm
--20-dBm
-
-
Signal in GSM band 1800 MHz
(1805 MHz to 1990 MHz)
Signal in WCDMA band
(2010 MHz to 2170 MHz)
Receiver interferer performance @ BER 0.1%
C/I
co-channel
C/I
C/I
C/I
C/I
C/I
C/I
1MHz
+2MHz
-2MHz
+3MHz
-3MHz
≥
4MHz
Co-channel interference
Adjacent (±1 MHz) interference
Adjacent (+2 MHz) interference
Adjacent (-2 MHz) interference
Adjacent (+3 MHz) interference
Adjacent (-3 MHz) interference
Adjacent (≥ ±4 MHz)
interference
@ Input signal
strength = -67 dBm
@ Input signal
strength = -67 dBm
@ Input signal
strength = -60 dBm
@ Input signal
strength = -60 dBm
@ Input signal
strength = -60 dBm
@ Input signal
strength = -67 dBm
@ Input signal
strength = -67 dBm
@ Input signal
strength = -67 dBm
@ Input signal
strength = -67 dBm
--14.5-dBm
--14-dBm
-1921dB
--45dB
--37-25dB
--120dB
--46-33dB
--40-13dB
--43-33dB
Doc ID 16067 Rev 223/58
General specificationSTA2500D
6.2 Transmitter
Unless otherwise stated, typical is defined at T
= 25 °C, BT_HV = 2.75 V. Minimum and
amb
Maximum are worst cases over corner lots and temperature. Parameters are given at device
pin, except for in-band spurious measured at antenna.
Initial carrier frequency tolerance (for an exact reference)
ΔF|f_TX-f0|--0-kHz
Carrier frequency stability
(6)
|Δf_s|Carrier frequency stability--3.210kHz
Carrier frequency drift
(7)
|Δf_p1|One slot packet--1225kHz
|Δf_p3|Three slots packet--1440kHz
|Δf_p5|Five slots packet--1440kHz
Carrier frequency drift rate
(7)
|Δf/50us|Frequency drift rate--8/5020/50kHz/µs
(6) (7)
Modulation accuracy
(8)
Δf1avgMaximum modulation-140163175kHz
Δf2maxMinimum modulation-115135-kHz
Δ
f1avg/Δf2avg
-0.80.9-
-2-DH5 RMS DEVM--820%
-2-DH5 99% DEVM---30%
-2-DH5 Peak DEVM--2135%
-3-DH5 RMS DEVM--813%
-3-DH5 99% DEVM---20%
-3-DH5 Peak DEVM--2125%
(5)
TX out of band emission
E850Emission in GSM band 850 MHz BW = 200 kHz
E900Emission in GSM band 900 MHz BW = 200 kHz
E1500Emission in GPS bandBW = 200 kHz
E1800
E1900
Emission in GSM band 1800 MHz
Emission in GSM band 1900 MHz
BW = 200 kHz
BW = 200 kHz
EwcdmaEmission in WCDMA bandBW = 3.8 MHz
1. Lower transmit power (i.e. Class 2) can be obtained by programming the radio init power table via software parameter
download or an HCI command.
2. Power of GFSK part.
3. Relative power of EDR part compared to the GFSK part.
4. At antenna with maximum output power, filter attenuation of 2.3 dB.
5. Phase noise will add maximum [-10 kHz;10 kHz] for worst case clock 270 mVpp at 13 MHz.
6. Worst case clock 270 mVpp at 13 MHz. Measurement according to EDR RF test spec V2.0.E.3 [].
7. With maximum output power (BR or EDR).
8. Measured on reference design STLC2555_rev1.1 following eBOM and layout recommendations.
9. Measurement bandwidth.
10. Transmitting DH5 packets.
(7) (9) (10)
(7) (9) (10)
(7) (9) (10)
(7) (9) (10)
(7) (9) (10)
(7) (9) (10)
--79-76dBm
--79-76dBm
--85-84dBm
--87-84dBm
--87-84dBm
--78-75dBm
Doc ID 16067 Rev 225/58
General specificationSTA2500D
6.3 Class 1 operation
The STA2500D supports operation at Class 1 output power levels with the use of an
external PA. The operation of the external PA and antenna switch are controlled by the
following signals:
Table 19.Output power: class 1 control signals
Control signal nameFunction
PAENPA enable (active during TX slot)
PA_VAL0Bit 0 of the power level delivered by the PA
PA_VAL1Bit 1 of the power level delivered by the PA
RXENLNA enable (if present)
AntSwControl of the antenna switch
edr_modeIndication to PA whether TX is EDR or BR
If Class 1 functionality is enabled through SW parameter download, then these 6 control
signals are available on the pins as indicated in Ta bl e 2 0 and Tab le 2 1 .
Table 20.Output power: class 1 device pin configuration (depending on SW
parameter download)
FunctionSW configuration 1SW configuration 2
PA_VAL0BT_GPIO_0BT_GPIO_10
PA_VAL1BT_CLK_REQ_IN_1BT_GPIO_9
RXENBT_CLK_REQ_IN_2BT_GPIO_8
AntSw(BT_GPIO_11)BT_GPIO_11
Table 21.Output power: class 1 device pin configuration (depending on SW
FunctionSW configuration aSW configuration bSW configuration c
edr_modeBT_CLK_REQ_OUT_1BT_CLK_REQ_OUT_2not available on a pin
Configuration 2 allows to deploy the STA2500D in Class 1 mode, still maintaining the
necessary control signals to coexist and cooperate with a WLAN transceiver. The
handshake between the STA2500D and a WLAN device happens in this case through other
BT_GPIO pins.
6.4 Power-up
The BT_RESETN pin should be active while powering up BT_VDD_HV and should stay
active at least two cycles of the low power clock (BT_LP_CLK) after power-up is completed.
PAENBT_HOST_WAKEUPBT_GPIO_16
parameter download)
The time between the STA2500D making BT_CLK_REQ_OUT_x active and the platform
providing a stable clock should maximally be 15 ms.
26/58Doc ID 16067 Rev 2
STA2500DGeneral specification
6.5 System clock
The STA2500D works with a sine wave or digital clock provided on the BT_REF_CLK_IN
pin. Detailed specifications are found in Section 2.4.
6.6 Low power clock
The low power clock is used by the Bluetooth Controller as reference clock during the low
power modes. It requires an accuracy of +
to be provided on the BT_LP_CLK pin, with frequencies of 3.2 kHz, 32 kHz and 32.768 kHz.
After power-up, the low power clock must be available before the reset is released. It must
remain active all the time until the STA2500D is powered off.
250 ppm. The STA2500D requires a digital clock
6.7 Clock detection
An integrated automatic detection algorithm detects the system and low power clock
frequencies after a hardware reset. The steps in the clock detection routine are:
●Identification of the system clock frequency (9.6 MHz, 10 MHz, 13 MHz, 16 MHz,
16.8MHz, 19.2 MHz, 26 MHz, 33.6 MHz or 38.4 MHz)
●Identification of the low power clock (3.2 kHz, 32.768 kHz or 32 kHz).
6.8 Clock request signals
To allow minimum power consumption, a clock request feature is available so that the
system clock (BT_REF_CLK_IN) can be stopped when not needed by the Bluetooth
system. The clock request signal can be active high or active low, and the STA2500D
supports internal propagation of clock request signal coming from another device in the
system.
Different configurations as described below are supported immediately after reset and in all
Bluetooth operation modes, provided that BT_VIO_A is available.
The clock request functionality is based on four different signals: BT_CLK_REQ_OUT_1,
BT_CLK_REQ_OUT_2, BT_CLK_REQ_IN_1, BT_CLK_REQ_IN_2, with the following
function:
●BT_CLK_REQ_OUT_1: active low or high clock request, depending on HW
configuration pins (Table ). Support for either push-pull or open drain output.
●BT_CLK_REQ_OUT_2: active low clock request, only used in combination with SPI
mode. Support for either push-pull or open drain output.
●BT_CLK_REQ_IN_1: active high clock request input from an other device, depending
on HW configuration pin.
●BT_CLK_REQ_IN_2: active low clock request input from an other device.
The following modes are supported:
●Active high clock request input and output combined with UART or SPI:
Doc ID 16067 Rev 227/58
General specificationSTA2500D
Figure 3.Active high clock request input and output combined with UART or SPI
Internal BT CLK Request
BT_CLK_REQ_IN_1
BT_CLK_REQ_IN_2
(*) BT_CLK_REQ_IN_1 and BT_CLK_REQ_IN_2 are used UNLESS one or both are re-programmed as alternate function(s) via Parameter File
NOT
(*)
OR
(*)
BT_CLK_REQ_OUT_1
●Active low clock request input and output combined with UART:
Figure 4.Active low clock request input and output combined with UART
Internal BT CLK Request
BT_CLK_REQ_IN_1
BT_CLK_REQ_IN_2
(*) BT_CLK_REQ_IN_1 and BT_CLK_REQ_IN_2 are used UNLESS one or both are re-programmed as alternate function(s) via Parameter File
NOT
(*)
AND
(*)
BT_CLK_REQ_OUT_1
●Active low clock request input and output combined with SPI:
Figure 5.Active low clock request input and output combined with SPI
Internal BT CLK Request
BT_CLK_REQ_IN_1
BT_CLK_REQ_IN_2
(*) BT_CLK_REQ_IN_1 and BT_CLK_REQ_IN_2 are used UNLESS one or both are re-programmed as alternate function(s) via Parameter File
Table 22.Use of the BT_CLK_REQ_IN and BT_CLK_REQ_OUT signals in different modes
NOT
BT_CONFIG_1 BT_CONFIG_2 BT_CONFIG_3 Protocol
010H4 UART
011H4 UART
101
1. BT_CLK_REQ_IN_1 and BT_CLK_REQ_IN_2 are used in the configuration logic, UNLESS one or both I/Os reprogrammed as alternate function(s) via the Parameter File.
Enhanced
H4 SPI
(*)
AND
(*)
BT_CLK_
REQ_IN_1
Active
(1)
high
Active
(1)
low
BT_CLK_REQ_OUT_2
BT_CLK_
REQ_IN_2
Active
(1)
low
Active
(1)
low
BT_CLK_R
EQ_OUT_1
BT_CLK_R
EQ_OUT_2
Active highnot used
Active lownot used
Active high Active low Active highActive low
The pins which are “not used” are available for alternate functions as described in
Section 7.5.
28/58Doc ID 16067 Rev 2
STA2500DGeneral specification
6.9 Interrupts
The user can program the BT_GPIOs as external interrupt sources.
6.10 Low power modes
6.10.1 Overview
To save power, three low power modes are supported as described in Ta b le 2 3.
Depending of the Bluetooth and of the Host's activity, the STA2500D decides to use Sleep
mode or Deep Sleep mode. Note however that the Deep Sleep mode must first be activated
via SW parameter download or an HCI command prior to any possibility to use it as the
default configuration is only Sleep mode. Complete Power Down is entered only after an
explicit command from the Host.
Table 23.Low power modes
Low power modeDescription
Deep Sleep mode
Sleep mode
The STA2500D:
– Accepts HCI commands from the Host.
– Supports all types of Bluetooth links.
– Can transfer data over Bluetooth links.
– Dynamically switches between sleep and active mode when needed.
– The system clock is still active in part of the design.
– Parts of the chip are dynamically powered off depending on the Bluetooth activity.
The STA2500D:
– Does not accept HCI commands from the Host.
– Supports Page and Inquiry scans.
– Supports Bluetooth links that are in Sniff or Sniff Subrating.
– Dynamically switches between Deep Sleep and active mode during Bluetooth
activity. The Deep Sleep mode entry is initiated by the Host, the STA2500D
acknowledges or not. The wake-up mechanism must be enabled by a SW
parameter download before it can be used. More details in section 6.10.3.
– The system clock is not active in any part of the design.
– Parts of the chip are dynamically powered off depending on the Bluetooth activity.
Complete Power Down
The STA2500D is effectively powered down:
– No Bluetooth activity is supported.
– The HCI interface is shut down.
– The system clock is not active in any part of the design.
– Most parts of the chip are completely powered off.
– RAM content is not maintained (initialisation is required at wake-up).
– Some pins (UART/SPI I/Os and the 4 clock request signals and BT_GPIO_16)
keep their previous configuration (input or output, pull behaviour) during
Completed Power Down.
– The Complete Power Down entry is initiated by an HCI command followed by a
Deep Sleep command, this in order to ensure a smooth transition from active to
Complete Power Down state. In order to go out of this mode, either a HW reset or
BT_WAKEUP = ‘1’ is needed.
Doc ID 16067 Rev 229/58
General specificationSTA2500D
6.10.2 Some examples for the usage of the low power modes
Sniff or sniff subrating
The STA2500D is in active mode with a Bluetooth connection. Once the transmission is
concluded, Sniff or Sniff Subrating is programmed. When one of these two states is entered,
the STA2500D goes into Sleep mode. After that, the Host may decide to place the
STA2500D in Deep Sleep mode as described in Section 6.10.3. The Deep Sleep mode
allows for lower power consumption. When the STA2500D needs to send or receive a
packet (e.g. at T
enters active mode for the needed transmission/reception. Immediately afterwards, the
STA2500D will go back to Deep Sleep mode. If some HCI transmission is needed, the
UART/SPI link will be reactivated, using one of the four ways explained in Section 6.10.3
and the STA2500D will move from Deep Sleep mode to Sleep mode.
Inquiry/page scan
When only Inquiry scan or Page scan is enabled, the STA2500D will go in Sleep mode or
Deep Sleep mode outside the receiver activity. The selection between Sleep mode and
Deep Sleep mode depends on the UART/SPI activity as in Sniff or Sniff Subrating.
No connection
or at the beacon instant), the STA2500D requests the system clock and
sniff
If the Host allows Deep Sleep mode (as described in Section 6.10.3) and there is no activity,
then the STA2500D puts itself in Deep Sleep mode. It is possible to exit the Deep Sleep
mode by using one of the four methods explained in Section 6.10.3. In this Deep Sleep
mode (no connection), the Host can also decide to put the STA2500D in Complete Power
Down to further reduce the power consumption. In this case some part of the STA2500D will
be completely powered off. The request to quit the Complete Power Down is done either by
putting the BT_WAKEUP signal to ‘1’ or with an HW reset.
Active link
When there is an active link ((e)SCO or ACL), the Bluetooth Controller will not go in Deep
Sleep mode and not in Complete Power Down. But the Bluetooth Controller is made in such
a way that whenever it is possible, depending on the scheduled activity (number of link, type
of link, amount of data exchanged), it goes in Sleep mode.
6.10.3 Deep sleep mode entry and wake-up
During periods of no activity on the Bluetooth and on the Host side, the chip can be placed
in Deep Sleep mode. Four ways to initiate Deep Sleep mode and to wake up are supported
(selection is done through software parameter download): they are respectively based on a
UART interface in the first case, an SPI interface in the second case and third case, while
either UART or SPI interfaces can be used in the fourth case that is based on an handshake
mechanism.
Deep sleep mode entry and wake up through H4 UART
It requires BT_CLK_REQ_OUT_1, BT_UART_RXD and BT_UART_RTS. The
BT_UART_RXD is used as wake-up signal from the Host, the BT_CLK_REQ_OUT_1
requires the clock from the Host and the BT_UART_RTS indicates when the STA2500D is
30/58Doc ID 16067 Rev 2
STA2500DGeneral specification
available. In this mode, the break function (BT_UART_RXD is low for more than 1 word) is
used to distinguish between normal operation and low power mode usage.
●Deep sleep mode entry
The Host tells the STA2500D that it can go in Deep Sleep mode power by forcing the
BT_UART_RXD of the STA2500D to '0' for more than 1 word. The STA2500D decides
to go in Deep Sleep mode, or not, depending on its scheduled activity and on the
number of events or data packets to be sent to the Host. In case it decides to go in
Deep Sleep mode, it signals it by forcing BT_UART_RTS high; then it asserts
BT_CLK_REQ_OUT_1 low to tell the Host that it does not need the clock anymore. The
STA2500D cannot go in Deep Sleep mode by itself. This is a logical consequence of
the fact that the system clock is needed to receive characters on the UART.
Note that when the system is in Deep Sleep mode, the UART is closed.
●Deep sleep mode wake-up
The wake-up procedure can be initiated by the Host or by the STA2500D. In the latter
case, it can be with or without communication, depending if there are data to be
transmitted to the Host.
1.Wake-up initiated by the Host
The Host sets the BT_UART_RXD pin of the STA2500D to '1'. Then the STA2500D
asks the Host to restart the system clock by setting BT_CLK_REQ_OUT_1 to '1'. When
the clock is available, the STA2500D confirms it is awake by releasing BT_UART_RTS
to '0'.
2. Autonomous wake-up with UART communication (i.e. initiated by the STA2500D)
The STA2500D first asks the Host to restart the system clock by setting
BT_CLK_REQ_OUT_1 to '1'.
When the clock is available, the STA2500D sets BT_UART_RTS low, and then the Host
can give confirmation by releasing the BT_UART_RXD of the STA2500D.
Another possibility is that the STA2500D sets BT_HOST_WAKEUP to ‘1’ to request the
Host attention. Then the Host can give confirmation by releasing the BT_UART_RXD of
the STA2500D and the STA2500D sets BT_UART_RTS low.
The choice between the two possibilities is selected by a software parameter.
3. Autonomous wake-up without UART communication (i.e. initiated by the STA2500D)
The STA2500D asks the Host to restart the system clock by setting
BT_CLK_REQ_OUT_1 to '1'.
Doc ID 16067 Rev 231/58
General specificationSTA2500D
Figure 6.Deep sleep mode entry and wake-up through H4 UART
UART on
UART on
Active
Active
HOST_WAKEUP=‘1’or ‘0’
HOST_WAKEUP=‘ 1’ or ‘ 0’
Host:UART_RXD=‘1’
Hos t:BT _UA RT_R XD =‘ 1’
BT Controller:
BT Co nt ro l ler :
BB
BB
Sleep Mode
Sleep Mode
UART_RTS=‘0’
BT_ UA RT_RT S =‘0’
Or
Or
HOST_WAKEUP=‘1’
BT_H OST_WA KEUP =‘1’
Host:UART_RXD=‘0’
Hos t:BT _UA RT_ RXD =‘ 0’
BT Controller:
BT Co nt ro l ler :
Host:UART_RXD=‘1’
Hos t:BT _UA RT_ RXD =‘ 1’
AND
AND
BT Controller:
BT Controller: BT_CLK_REQ_OUT_1=‘ A’
UART_RTS=‘1’
BT_ UART _RT S=‘ 1’
CLK_REQ_OUT_1=‘A’
and
and
UART_RTS=‘0’
BT_ UART _RT S=‘ 0 ’
UART off
UART off
Active
Active
HOST_WAKEUP=‘0’
HOST_WAKEUP=‘ 0’
BB
BB
Sleep Mode
Sleep Mode
=‘ A’
BT_CLK_REQ_OUT_1
BT Controller:CLK_REQ_OUT_1=‘A’
BT Co n trol le r :
Deep Sleep
BT Controller:CLK_REQ_OUT_1=‘P’
BT Co n trol le r : BT_CLK_REQ_OUT_1=‘P’
UART off
UART off
Mode
BT_CLK_REQ_OUT_1 =
‘A’: Active
‘P’ : Passive
high/low
low/high
Deep sleep mode entry and wake-up through enhanced H4 SPI
In this case no additional signals are needed to control the Deep Sleep mode and the wakeup mechanism except for BT_CLK_REQ_OUT_x (BT_CLK_REQ_OUT_1 for active high
polarity and BT_ CLK_REQ_OUT_2 for active low polarity).
The enhanced H4 protocol makes use of three messages: SLEEP, WAKEUP and WOKEN.
More details on the enhanced H4 protocol can be found in Section 8.2.
●Deep sleep mode entry
Entering Deep Sleep mode can only be initiated by the Host sending a SLEEP
message to the Bluetooth Controller.
If that one accepts it, the device enters Deep Sleep mode: consequently the Bluetooth
Controller de-asserts BT_CLK_REQ_OUT_x and internally gates the system clock.
This is illustrated in Figure 7.
If there is still pending activity at the Bluetooth side on the air, the Bluetooth Controller
does not immediately enter Deep Sleep mode and therefore BT_CLK_REQ_OUT_x
stays 'active' during this period: however the Bluetooth Controller will go in Deep Sleep
mode at the end of the air activity.
If there is pending data to be transferred to the Host, the Bluetooth Controller will
request a data transfer: however the Bluetooth Controller will go in Deep Sleep mode at
the end of the data transfer.
●Deep sleep mode wake-up
Wake-up can be requested by the Host or autonomously by the Bluetooth Controller. In
the latter case, it can be with or without communication on the interface (i.e. during
Page scan, there is no data to transfer to the Host).
1.Wake-up initiated by the Host
In the case of a wake-up by the Host, it sends a WAKEUP command and waits for a
WOKEN response before starting the data exchange. Of course the Bluetooth
Controller must first request the system clock through BT_CLK_REQ_OUT_x.
It should be noted that the WAKEUP message is decoded in the Bluetooth Controller's
32/58Doc ID 16067 Rev 2
STA2500DGeneral specification
SPI HW block even before the system clock is available. This block will generate an
interrupt, allowing the Bluetooth Controller to reply with a WOKEN message. This is
illustrated in Figure 8.
2. Autonomous wake-up with communication (i.e. initiated by the STA2500D)
In the case of an autonomous wake-up with data transmission, the Bluetooth Controller
sets BT_SPI_INT high to request the SPI interface and waits for BT_SPI_CSN going
low, indicating the SPI transaction starts. Of course the Bluetooth Controller must first
request the system clock through BT_CLK_REQ_OUT_x before being able to start the
process. This is illustrated in Figure 9. Note that the Bluetooth Controller goes back to
Deep Sleep mode at the end of the data transfer.
3. Autonomous wake-up without communication (i.e. initiated by the STA2500D)
For autonomous wake-up without SPI communication, the STA2500D only asserts
BT_CLK_REQ_OUT_x to get the system clock.
Figure 7.Entering deep sleep mode through enhanced H4 SPI
SPI_CSN
SPI_CLK
1
SPI_DO
SPI_DI
SPI_INT
CLK _REQ _OUT _1
REF_CLK _IN
2
SLEEP
3
Figure 8.Wake-up by the host through enhanced H4 SPI
SPI_CSN
SPI_CLK
SPI_DO
SPI_DI
SPI_INT
CLK _REQ _OUT _1
REF_CLK _IN
1
2
WAKEUP
3
WOKEN
5
4
4
Doc ID 16067 Rev 233/58
General specificationSTA2500D
Figure 9.Wake-up by the Bluetooth controller with data transmission to the host,
through enhanced H4 SPI
SPI_CSN
SPI_CLK
SPI_DO
SPI_DI
SPI_INT
CLK _REQ_OUT_1
4
3
5
DATA
2
1
REF_CLK _IN
Deep sleep mode entry and wake-up through H4 SPI
It requires BT_CLK_REQ_OUT_x (BT_CLK_REQ_OUT_1 for active high polarity and
BT_CLK_REQ_OUT_2 for active low polarity), BT_WAKEUP and BT_SPI_INT. The
BT_WAKEUP is used as wake-up signal from the Host, the BT_CLK_REQ_OUT_x requires
the clock from the Host and BT_SPI_INT is used as a wake-up signal from the Bluetooth
Controller.
●Deep sleep mode entry
The Host tells the STA2500D that it can go in Deep Sleep mode by forcing the
BT_WAKEUP of the STA2500D to ‘0’. The STA2500D decides to go in Deep Sleep
mode, or not, depending on its scheduled activity and on the number of events or data
packets to be sent to the Host. In case it decides to go in Deep Sleep mode, it asserts
BT_CLK_REQ_OUT_x ‘inactive’ to tell the Host that it does not need the clock
anymore. The STA2500D cannot go in Deep Sleep mode by itself. Note that the Host
cannot force BT_WAKEUP to ‘0’ before the end of a write operation from the Host, this
in order to allow correct decoding of the message by the Bluetooth Controller.
●Deep sleep mode wake-up
The wake-up procedure can be initiated by the Host or by the STA2500D. In the latter
case, it can be with or without communication, depending if there are data to be
transmitted to the Host.
1.Wake-up initiated by the Host
The Host sets the BT_WAKEUP pin of the STA2500D to ‘1’. Then the STA2500D asks
the Host to restart the system clock by setting BT_CLK_REQ_OUT_x to ‘active’. When
the clock is available and stable, the Host can use BT_SPI_CSN to start an SPI
transaction if needed (there is a programmable minimum delay between the assertion
of BT_CLK_REQ_OUT_x and the moment the Host can assert BT_SPI_CSN).
2. Autonomous wake-up with SPI communication (i.e. initiated by the STA2500D)
The STA2500D first asks the Host to restart the system clock by setting
BT_CLK_REQ_OUT_x to ‘active’.
When the clock is available, the STA2500D sets BT_SPI_INT high to request the SPI
interface to the Host and waits for BT_SPI_CSN going low, indicating the SPI
transaction starts.
3. Autonomous wake-up without SPI communication (i.e. initiated by the STA2500D)
The STA2500D asks the Host to restart the system clock by setting
BT_CLK_REQ_OUT_x to ‘active’.
34/58Doc ID 16067 Rev 2
STA2500DGeneral specification
Figure 10. Deep sleep mode entry and wake-up through H4 SPI
SPI on
SPI on
Active
Active
HOST_WAKEUP=‘1’or ‘0’
HOST_WAKEUP =‘1’ or ‘0’
Host:BT_WAKEUP=‘1’
Hos t:BT_WAKEUP=‘1’
OR
OR
BT Co nt ro ll er :
BT Controller:
BB
BB
Sleep Mode
Sleep Mode
SPI_INT=‘1’
BT_SPI_INT =‘1 ’
Host:BT_WAKEUP=‘0’
Host:BT_WAKEUP=‘0’
Host:BT_WAKEUP=‘1’
Host:BT_WAKEUP=‘1’
AND
AND
BT Controller:
BT Co nt ro ll er :
BT_CLK_REQ_OUT_1=‘ A’
SPIoff
SPI off
Active
Active
CLK_REQ_OUT_1=‘A’
HOST_WAKEUP=‘0’
HOST_WAKEUP=‘ 0’
BB
BB
Sleep Mode
Sleep Mode
BT Controller:CLK_REQ_OUT_1=‘A’
BT Co nt ro l ler :BT_CLK_REQ_OUT_1 =‘A’
Mode
Deep Sleep
BT Controller:CLK_REQ_OUT_1=‘P’
BT Co nt ro l ler :BT _C LK _ R EQ_ O UT_ 1=‘ P’
SPIoff
SPI off
Mode
CLK_REQ_OUT_1 = ‘ A’ : Active high/low
CLK_REQ_OUT_1 = ‘ A’ : Active high/low
‘P’:
‘P’:
Passive
Passive
low/high
low/high
Deep sleep mode entry and wake-up through H4 UART or H4 SPI with
handshake
This method is supported by both H4 UART and H4 SPI. The description below is for H4
UART.
It requires BT_CLK_REQ_OUT_1, BT_WAKEUP and BT_HOST_WAKEUP. The
BT_WAKEUP is used as wake-up signal from the Host, the BT_CLK_REQ_OUT_1 requires
the clock from the Host and BT_HOST_WAKEUP is used as a wake-up signal from the
Bluetooth Controller.
●Deep sleep mode entry
The Host tells the STA2500D that it can go in Deep Sleep mode by forcing the
BT_WAKEUP of the STA2500D to ‘0’. The STA2500D decides to go in Deep Sleep
mode, or not, depending on its scheduled activity and on the number of events or data
packets to be sent to the Host. In case it decides to go in Deep Sleep mode, it asserts
BT_CLK_REQ_OUT_1 low to tell the Host that it does not need the clock anymore. On
the contrary, if it still wants the interface active for up-transmission, it keeps
BT_HOST_WAKEUP to ‘1’ as long as needed before de-asserting
BT_CLK_REQ_OUT_1. This is illustrated in Figure 11.
●Deep sleep mode wake-up
The wake-up procedure can be initiated by the Host or by the STA2500D. In the latter
case, it can be with or without communication, depending if there are data to be
transmitted to the Host.
1.Wake-up initiated by the Host
The Host sets the BT_WAKEUP pin of the STA2500D to ‘1’. Then the STA2500D asks
the Host to restart the system clock by setting BT_CLK_REQ_OUT_1 to ‘1’. When the
clock is available and stable, the STA2500D puts BT_UART_RTS low to allow
communication. In case the STA2500D wants to send events to the Host, it then puts
Doc ID 16067 Rev 235/58
General specificationSTA2500D
BT_HOST_WAKEUP to ‘1’ in order to warm the Host and traffic starts when the Host
puts BT_UART_CTS to low. This is illustrated in Figure 12.
2. Autonomous wake-up with communication (i.e. initiated by the STA2500D)
The STA2500D first asks the Host to restart the system clock by setting
BT_CLK_REQ_OUT_1 to ‘1’.
When the clock is available, the STA2500D requests traffic by asserting
HOST_WAKEUP high. Then either it puts BT_UART_RTS low to start traffic exchange
directly or it waits for the Host to first assert BT_WAKEUP high. The selection in
between the two behaviours is done by a SW parameter in the Parameter File.
3. An autonomous wake-up without communication (i.e. initiated by the STA2500D)
The STA2500D asks the Host to restart the system clock by setting
BT_CLK_REQ_OUT_1 to ‘1’. The UART signals are not changing.
Figure 11. Entering deep sleep mode, pending data on UART interface, through
UART with handshake
BT_WAKEUP
BT_WAKEUP
UART_RTS
UART_RTS
UART_RTS
UART_RTS
12
12
3
HOST_WAKEUP
HOST_WAKEUP
CLK_REQ_OUT_1
CLK_REQ_OUT_1
REF_CLK_IN
REF_CLK_IN
3
4
4
1.Host puts BT_WAKEUP low. BT Controller notices it. But as there is pending traffic to
be send to Host, it keeps HOST_WAKEUP high as long as needed for up-transmission
and then de-asserts HOST_WAKEUP, telling the Host there is nothing more to
transmit.
2. BT Controller puts UART_RTS high to set “flow off”. This is done in fixed number of
instructions.
3. Then BT Controller puts CLK_REQ_OUT_1 to ‘0’, telling the Host it can cut the clock.
This is done in fixed number of instructions.
4. There is no clock, BT is in Deep Sleep mode.
36/58Doc ID 16067 Rev 2
STA2500DGeneral specification
Figure 12. Wakeup by host through UART with handshake
BT_WAKEUP
UART_RTS
UART_RTS
UART_RTS
UART_CTS
HOST_WAKEUP
CLK_REQ_OUT_1
REF_CLK_IN
5. Host pulls BT_WAKEUP high to wake-up BT Controller. HW starts driving
CLK_REQ_OUT_1 high (after 2*LP_CLK).
6. Host starts 13 MHz clock and distribute it when stable. Delay between
CLQ_REQ_OUT_1 and usage of stable clock is programmable in between 3 and 39
ms.
7. When BT Controller starts with clock, it sets “flow on” by putting UART_RTS low. There
is a fixed SW latency. Host can send commands.
8. BT Controller sets HOST_WAKEUP high telling to the Host it has events to send to the
Host.
9. When the Host is ready for data transmission, it asserts UART_CTS low.
6.11 Patch RAM
8
5
7
9
6
The STA2500D includes a HW block that allows patching of the ROM code.
Additionally, a SW patch mechanism allows replacing complete SW functions without
changing the ROM image.
A part of the RAM memory is used for HW and SW patches.
6.12 Download of SW parameter file
To change the device configuration a set of customizable parameters have been defined
and put together in one file, the parameter file. This Parameter File is downloaded at startup into the STA2500D.
Examples of parameters are: radio configuration, PCM settings etc.
The same HCI command is used to download the file containing the patches (both those for
the SW and HW mechanism).
A more detailed description of the SW parameter file is available upon request.
Doc ID 16067 Rev 237/58
General specificationSTA2500D
6.13 Bluetooth - WLAN coexistence in collocated scenario
The coexistence interface uses up to 4 WLAN control signal pins, which can be mapped via
software parameter download on different pins of the STA2500D (see Section 7.5).
The functionality of the 4 WLAN control signal pins depends on the selected algorithm, as
explained
below and summarized in Ta bl e 2 4.
Bluetooth and WLAN 802.11 b/g [] [] technologies occupy the same 2.4 GHz ISM band. The
STA2500D implements a set of mechanisms to avoid interference in a collocated scenario.
The STA2500D supports 5 different algorithms in order to provide efficient and flexible
simultaneous functionality between the two technologies in collocated scenarios:
●Algorithm 1: PTA (Packet Traffic Arbitration) based coexistence algorithm defined in
accordance with the IEEE 802.15.2 recommended practice [].
●Algorithm 2: the WLAN is the Master and it indicates to the STA2500D when not to
operate in case of simultaneous use of the air interface.
●Algorithm 3: the STA2500D is the Master and it indicates to the WLAN chip when not
to operate in case of simultaneous use of the air interface.
●Algorithm 4: Two-wire mechanism
●Algorithm 5: Alternating Wireless Medium Access (AWMA), defined in accordance
with the WLAN 802.11 b/g [] [] technologies.
The algorithm is selected via an HCI command. The default algorithm is algorithm 1.
The algorithm is based on a bus connection between the STA2500D and the WLAN chip:
Figure 13. PTA diagram
RF_REQUEST
STATUS
STLC2500 D
By using this coexistence interface it is possible to dynamically allocate bandwidth to the two
devices when simultaneous operations are required while the full bandwidth can be
allocated to one of them in case the other one does not require activity.
The algorithm involves
●a priority mechanism, which allows preserving the quality of certain types of link.
●a mechanism to indicate that a periodic communication is ongoing.
A typical application would be to guarantee optimal quality to the Bluetooth voice
communication while an intensive WLAN communication is ongoing.
FREQ
RF_CONFIRM
WLAN
Several algorithms have been implemented in order to provide a maximum of flexibility and
efficiency for the priority handling. ST specific HCI commands are implemented to select the
algorithm and to tune the priority handling.
38/58Doc ID 16067 Rev 2
STA2500DGeneral specification
The combination of time division multiplexing and the priority mechanism avoids the
interference due to packet collision. It also allows the maximization of the 2.4 GHz ISM
bandwidth usage for both devices while preserving the quality of some critical types of link.
6.13.2 Algorithm 2: WLAN master
In case the STA2500D has to cooperate, in a collocated scenario, with a WLAN chip not
supporting a PTA based algorithm, it is possible to put in place a simpler mechanism.
The interface is reduced to 1 line:
Figure 14. WLAN master
STLC2500 D
BT_RF_NOT_ALLOWED
When the WLAN has to operate, it alerts high the BT_RF_NOT_ALLOWED signal and the
STA2500D will not operate while this signal stays high.
This mechanism permits to avoid packet collision in order to make an efficient use of the
bandwidth but cannot provide guaranteed quality over the Bluetooth links.
6.13.3 Algorithm 3: Bluetooth master
This algorithm represents the symmetrical case of algorithm 2. Also in this case the
interface is reduced to 1 line:
Figure 15. Bluetooth master
STLC2500 DWLAN
WLAN_RF_NOT_ALLOWED
WLAN
When the STA2500D has to operate it alerts high the WLAN_RF_NOT_ALLOWED signal
and the WLAN will not operate while this signal stays high.
This mechanism permits to avoid packet collision in order to make an efficient use of the
bandwidth, it provides high quality for all Bluetooth links but cannot provide guaranteed
quality over the WLAN links.
6.13.4 Algorithm 4: two-wire mechanism
Based on algorithm 2 and 3, the Host decides, on a case-by-case basis, whether WLAN or
Bluetooth is master.The Master role can be checked and changed at run-time by the Host
via an HCI command.
Doc ID 16067 Rev 239/58
General specificationSTA2500D
6.13.5 Algorithm 5: Alternating wireless medium access (AWMA)
AWMA utilizes a portion of the WLAN beacon interval for Bluetooth operations. From a
timing perspective, the medium assignment alternates between usage following WLAN
procedures and usage following Bluetooth procedures.
The timing synchronization between the WLAN and the STA2500D is done by the HW signal
MEDIUM_FREE.
Table 24.WLAN HW signal assignment
WLAN control
signal
(see also
Tabl e 2 8)
Scenario 1:
PTA
Scenario 2:
WLAN master
Scenario 3:
BT master
Scenario 4:2-wire
Scenario 5:
AWM A
WLAN 1RF_CONFIRM
WLAN 2RF_REQUESTNot used
WLAN 3STATUSNot usedNot usedNot usedNot used
WLAN 4
FREQ
(optional)
BT_RF_NOT_
ALLOWED
Not usedNot usedNot usedNot used
Not used
WLAN_RF_NOT_
ALLOWED
BT_RF_NOT_
ALLOWED
WLAN_RF_NOT_
ALLOWED
MEDIUM_F
REE
Not used
40/58Doc ID 16067 Rev 2
STA2500DDigital interfaces
7 Digital interfaces
7.1 The UART interface
The STA2500D contains a 4-pin (BT_UART_RXD, BT_UART_TXD, BT_UART_RTS, and
BT_UART_CTS) UART compatible with 16450, 16550 and 16750 standards. It is running up
to 4000 kbps (+1.5% / -1%).
The configuration is 8 data bits, 1 start bit, 1 stop bit, and no parity bit. The transmit and
receive paths contain a DMA function for low CPU load and high throughput. Auto RTS/CTS
is implemented in HW, controllable by SW.
The UART accepts all HCI commands as described in the Bluetooth specification, it
supports H4 proprietary commands and the Deep Sleep mode entry and wake-up through
H4 UART (see Section : Deep sleep mode entry and wake up through H4 UART). The
complete list of supported proprietary HCI commands is available upon request.
At startup, the UART baud rate is fixed at 115200 bps independently of the
BT_REF_CLK_IN frequency. A specific HCI command is provided to change the UART
baud rate when necessary within the range 9600 bps to 4000 kbps. All standard baud rates
and many other ones are supported.
7.2 The SPI interface
The physical SPI interface is made up of 5 signals: clock, chip select, data in, data out and
interrupt. When the SPI mode is selected, these signals are available through the
BT_UART/BT_SPI and BT_HOST_WAKEUP pins.
Figure 16. SPI interface
Host
SPI_CLK
SPI_CSN
SPI_MISO
SPI_MOSI
SPI_INT
●SPI_CSN (on pin BT_UART_RTS/BT_SPI_CSN): chip select allows the use of multiple
Slaves (1 chip select per Slave). This signal is active low. This signal is mandatory,
even with only 1 Slave, because the Host must drive this signal to indicate SPI frames.
●SPI_CLK (on pin BT_UART_CTS/BT_SPI_CLK): clock signal, active for a multiple of
data length cycles during an SPI transfer (SPI_CSN active). The clock is allowed to be
active when SPI_CSN is not active, in order to serve other Slaves.
●SPI_DO (on pin BT_UART_TXD/BT_SPI_DO): data transfer from Slave to Master.
Data is generated on the negative edge of SPI_CLK by the Slave and sampled on the
BT Controller
SPI_CLK
SPI_CSN
SPI_DO
SPI_DI
SPI_INT
Doc ID 16067 Rev 241/58
Digital interfacesSTA2500D
positive edge of SPI_CLK. When SPI_CSN is inactive, this BT Controller output is in
tristate mode.
●SPI_DI (on pin BT_UART_RXD/BT_SPI_DI): data transfer from Master to Slave. Data
is generated on the negative edge of SPI_CLK by the Master and sampled on the
positive edge of SPI_CLK.
●SPI_INT (on pin BT_HOST_WAKEUP/BT_SPI_INT): interrupt from the Slave, used to
request an SPI transfer by the Slave to the Master. The signal is active high (Host input
must be level sensitive).
The SPI interface is Master at the Host side, and Slave at Bluetooth Controller side. It is
designed to work with the H4 and enhanced H4 protocol. Also synchronous data packet
transfer (eSCO) over HCI is supported.
The SPI data length and endianness are configurable.
The SPI interface can only operate in half duplex mode.
Also the use of flow control is configurable. The flow control consists of an indication from
the Bluetooth Controller whether its receive buffers are ready to receive data. This indication
is available in three ways:
●On the SPI_DO during T
(time between SPI_CSN becoming active and SPI_CLK
SCS
becoming high), see FC in Figure 17 and Tscs in Figure 18
●In a register that can be read by the Host
●Optionally on one of the programmable GPIOs: GPIO_16. This is enabled by a SW
parameter download, see Section 7.5
The default SPI configuration is:
●Half duplex mode
●16 bit data length
●Most significant byte first
●Most significant bit first
●Flow control on SPI_DO and in a register
More detailed information on the SPI interface is available upon request.
Figure 17. SPI data transfer timing for data length of 8 bits and lsb first, full duplex
SPI_CSN
SPI_CLK
SPI_DO
SPI_DI
SPI_INT
Z FCb0b1b2b3b4b5b6b7Z
b0b1b2b3b4b5b6b7
42/58Doc ID 16067 Rev 2
STA2500DDigital interfaces
Figure 18. SPI setup and hold timing
SPI_CSN
SPI_CLK
SPI_DI
T
CSL
P
CL
T
SCS
T
CLL
T
CLH
T
T
SDC
HCD
T
CSH
T
SCL
SPI_DO
T
SCLD
Table 25.SPI timing parameters
SymbolDescriptionMin.Typ.Max.Unit
T
T
T
T
T
T
T
T
T
P
SCLD
SPI_CLK full period7000ns
CL
High period of SPI_CLK16.6ns
CLH
Low period of SPI_CLK26.4ns
CLL
High period of SPI_CSN1 * P
CSH
Low period of SPI_CSN9 * P
CSL
Setup time, SPI_CSN Low to SPI_CLK high1 * P
SCS
Setup time, SPI_CLK Low to SPI_CSN high1/2 * P
SCL
Setup time, SPI_MOSI valid to SPI_CLK high9.75ns
SDC
Hold time, SPI_MOSI valid after SPI_CLK
HCD
high
CL
CL
CL
CL
0ns
Setup time, SPI_CLK Low to SPI_MISO valid26.5ns
ns
ns
ns
ns
7.3 The PCM interface
The chip contains a 4-pin direct voice interface to connect to standard CODEC.
The interface supports multiport PCM operations for voice transfer. It can be programmed to
act as a Master or a Slave via a SW parameter download or via specific HCI commands.
The four signals of the multiport PCM interface are:
●PCM_CLK: PCM clock
●PCM_SYNC : PCM 8 kHz sync (every 125 μs)
●PCM_A: PCM data (TX or RX)
●PCM_B: PCM data (RX or TX)
As a Master the interface by default generates a PCM clock rate of 2048 kHz, but it can be
configured to rates from 8 kHz up to 2048 kHz. As a Slave, it can automatically handle
external PCM clock rates from 128 kHz up to 4000 kHz. The default PCM_SYNC rate is 8
kHz.
The following external PCM data format are supported: linear (13 - 16 bit), µ−law (8 bit) or Alaw (8 bit).
Doc ID 16067 Rev 243/58
Digital interfacesSTA2500D
In Slave mode, all possible PCM_SYNC lengths are supported (including “short frame” (= 1
PCM_CLK period) and “long frame” (> 1 PCM_CLK period)). In Master mode, the length is
configurable (1 (“short frame”), 8 or 16 (“long frame”) PCM_CLK periods).
The start of the PCM data is configurable. One possible configuration is e.g. for a short
frame, the falling edge of the PCM_SYNC indicating the start of the PCM word. Another
possible configuration is e.g. for a long frame, the rising edge of the PCM_SYNC indicating
the start of the PCM word.
TX data are by default generated on the positive edge of PCM_CLK and expected to be
latched by the external device on the negative edge while RX data are latched on the
negative edge of PCM_CLK. But the inverted clock mode is also supported, whereby the
generation of TX data is on the negative edge and the latching of TX and RX data is on the
positive edge.
One additional PCM_SYNC signal can be provided via the GPIOs. See section 7.5 for more
details.
Figure 19. PCM (A-law, µ-law) standard mode
PCM_CLK
PCM_SYNC
PCM_ABB
012345678910 11 1213 14 15
PCM_B
B
Figure 20. Linear mode
PCM_CLK
PCM_SYNC
PCM_A
PCM_B
012345678910 11 1213 14 15
Figure 21. Multislot operation
125µs
125μs
B
D02TL558
D02TL559
The PCM implementation supports from 1 up to 3 slots per frame with the following
parameters:
44/58Doc ID 16067 Rev 2
STA2500DDigital interfaces
Table 26.PCM interface parameters
SymbolDescriptionMin.Typ.Max.Unit
PCM Interface
F
PCM_CLK
F
PCM_SYNC
P
sync_delay
S
s
Frequency of PCM_CLK (Slave)128
(1)
20484000
Frequency of PCM_SYNC-8-kHz
Delay of the starting of the first slot0-255cycles
Slot start (programmable for every slot)0-255cycles
(2)
DData size8-16bits
NNumber of slots per frame1-3-
1. Note that it is not possible to use 16 bits in Slave case if pcm_clk is 128kHz. This is the only exception.
2. In Master case, the maximum of PCM_CLK is 2048 kHz.
Setup time, PCM_A/B input valid to PCM_CLK low100--ns
Hold time, PCM_CLK low to PCM_A/B input valid100--ns
Delay time, PCM_CLK high to PCM_A/B output valid--150ns
kHz
Figure 22. PCM interface timing
PCM_CLK
t
WCH
PCM_SYNC
t
WSH
PCM_A/B in
PCM_B/A out
t
WCL
t
SSC
t
SDC
MSBMSB-1 MSB-2 MSB-3 MSB-4
t
DCD
MSBMSB-1 MSB-2 MSB-3 MSB-4
t
HCD
D02TL557
Doc ID 16067 Rev 245/58
Digital interfacesSTA2500D
7.4 The JTAG interface
The JTAG interface is compliant with the JTAG IEEE Standard 1149.1. It allows both the
boundary scan of the digital pins and the debug of the ARM7TDMI application when
connected with the standard ARM7 developments tools. It is also used for the industrial test
of the device. The JTAG interface is available through the following 5 pins: BT_GPIO_8,
BT_GPIO_9, BT_GPIO_10, BT_GPIO_11 and BT_GPIO_16.
7.5 Alternate I/O functions
The STA2500D has 10 additional general purpose pins on top of the 4 PCM pins, the 4
UART pins and BT_CLK_REQ_OUT_1 that can also be reconfigured. They are fully
programmable via specific HCI commands. They can be configured as input, output,
interrupt with asynchronous or synchronous edge or level detection and/or wake-up.
The alternative functions are:
●Wake-up by the Host in Deep Sleep mode through UART or SPI with handshake (see
Section : Deep sleep mode entry and wake-up through H4 UART or H4 SPI with
handshake)
●WLAN coexistence control
●I2C interface
●PCM synchronization
●GPIOs
●UART / SPI interface
●external driver/LNA control for Class 1 operation.
19 pins can be redefined by SW to perform other functions. Pin BT_HOST_WAKEUP e.g.
can be redefined to perform up to 7 functions, depending on SW settings.
4 exemplary combinations of pin programmings are given in Tab l e 28 . The available
functions are
●ex. 1: UART + I2C + Class 1 control
●ex. 2: UART + WLAN + Class 1 control
●ex. 3: SPI + WLAN + Class 1 control
●ex. 4: SPI + WLAN + I
2
C + Class 1 control
(The complete list of alternate functions is available upon request).
The I2C interface is used to access I2C peripherals.
The interface is a fast Master I
functionality is not supported.
2
C; it has full control of the interface at all times. I2C Slave
Doc ID 16067 Rev 247/58
HCI transport layerSTA2500D
8 HCI transport layer
The STA2500D supports the HCI transport layer as defined by the SIG: H4 []. It is supported
in combination with UART and SPI mode. The STA2500D also supports an enhanced
version of the H4 protocol in combination with SPI mode.
8.1 H4 UART transport layer
The objective of HCI UART transport layer is to make it possible to use Bluetooth HCI over a
serial interface between two UARTs on the same PCB. The HCI UART transport layer
assumes that the UART communication is free from line errors.
UART settings
The HCI UART transport layer uses the following settings for RS232:
The flow-off response time defines the maximum time that the STA2500D can still receive
data after setting RTS high.
RTS/CTS flow control is used to prevent temporary UART buffer overrun between the
Bluetooth Controller and the Host.
The RS232 signals should be connected in a null-modem fashion, i.e. the Bluetooth
Controller TXD output should be connected to the Host RXD input and the Bluetooth
Controller RTS output should be connected to the Host CTS input and vice versa.
If the Bluetooth Controller RTS output (connected to the Host CTS input) is low, then the
Host is allowed to send.
If the Bluetooth Controller RTS output (connected to the Host CTS input) is high, then the
Host is not allowed to send.
If the Bluetooth Controller CTS input (connected to the Host RTS output) is low, then the
Bluetooth Controller is allowed to send.
If the Bluetooth Controller CTS input (connected to the Host RTS output) is high, then the
Bluetooth Controller is not allowed to send.
Figure 23. UART transport layer
BLUETOOTH
HOST
BLUETOOTH HCI
BLUETOOTH
HOST
CONTROLLER
HCI UART TRANSPORT LAYER
48/58Doc ID 16067 Rev 2
STA2500DHCI transport layer
8.2 Enhanced H4 SPI transport layer
This is the default SPI mode.
The enhanced H4 protocol is based on the H4 protocol as defined by the SIG []. In addition
a messaging protocol is defined for controlling the Deep Sleep mode entry and wake-up,
see Section : Deep sleep mode entry and wake-up through enhanced H4 SPI.
Three messages are defined: SLEEP, WAKEUP and WOKEN. More details on the
messages are available upon request.
At SPI level, the default configuration is used:
●The SPI interface works in half duplex mode
●The data are exchanged in multiple of 16 bits
●The most significant byte first
●The most significant bit first
●There is a read and write command from the Host to access the Bluetooth device
●The Bluetooth device requests a transfer by the activation of the interrupt line
●Flow control on SPI_DO and in a register
8.3 H4 SPI transport layer
As stated in the previous section, the SPI interface is configurable. One possible
configuration is the following, implementing a simple H4 SPI transport layer.
●The SPI interface works in half duplex mode
●The data are exchanged in multiples of 8 bits
●The least significant bit first
●There is a read and write command from the Host to access the Bluetooth device
●The Bluetooth device requests a transfer by the activation of the interrupt line
●Flow control on BT_SPI_DO and in a register
8.4 eSCO over HCI
The STA2500D supports synchronous data packet transfer (eSCO) over HCI.
Doc ID 16067 Rev 249/58
Package informationSTA2500D
9 Package information
In order to meet environmental requirements, ST offers these devices in different grades of
ECOPACK
®
packages, depending on their level of environmental compliance. ECOPACK
®
specifications, grade definitions and product status are available at: www.st.com.
ECOPACK
®
is an ST trademark.
Figure 24. LFBGA48 (6x6x1.4mm) mechanical data and package dimensions
DIM.
A1.2500.0492
A10.2100.0083
A20.8900.0350
A30.3000.0118
A40.6000.0236
b0.350 0.400 0.450 0.0138 0.0157 0.0177
D5.850 6.000 6.150 0.2303 0.2362 0.2421
D14.8000.1890
E5.850 6.000 6.150 0.2303 0.2362 0.2421
E14.8000.1890
e0.8000.0315
F0.6000.0236
ddd0.1000.0039
eee0.1500.0059
fff0.0800.0031
mminch
MIN. TYP. MAX. MIN. TYP. MAX.
OUTLINE AND
MECHANICAL DATA
Body: 6 x 6 x 1.4mm
LFBGA48
Low profile Fine Pitch Ball Grid Array
50/58Doc ID 16067 Rev 2
8092328 B
STA2500DPackage information
Figure 25. Package markings
A
BD
G
H
Table 29.Package markings legend
C
E
F
ItemDescriptionFormatValue
AType + versionXXXXXX2500D7
BAssembly PlantP-
CBE sequence (LL)LL-
DAssembly Year (Y)Y-
EAssembly Week (WW)WW-
FSecond_lvl_intct--
GStandard ST Logo--
HDot (pin A1)--
Note:The ECO level is reflected in the “Order code” (see Ta b le 3 2)
Doc ID 16067 Rev 251/58
ReferencesSTA2500D
10 References
Short
name
NameDateOwner
Specification of the Bluetooth System - Host Controller
Interface [Transport Layer] Volume 04 Revision 1.2 or later,
2006, part A: UART v1.1
Radio Frequency Test Suite Structure (TSS) and Test
Purposes (TP) System Specification 1.2/2.0/2.0 + EDR,
document number RF.TS/2.0.E.3
IEEE 802.15.2, IEEE Recommended Practice for
Telecommunications and Information exchange between
systems – Local and metropolitan area networks Specific
Requirements - Part 15.2: Coexistence of Wireless Personal
Area Networks with Other Wireless Devices Operating in
Unlicensed Frequency Band
IEEE 802.11, IEEE Standards for Information Technology -Telecommunications and Information Exchange between
Systems -- Local and Metropolitan Area Network -- Specific
Requirements -- Part 11: Wireless LAN Medium Access
Control (MAC) and Physical Layer (PHY) Specifications
Table 30.References
ID
[1]-Specification of the Bluetooth System V2.1 + EDR (“Lisbon”)
[2]-Specification of the Bluetooth System V2.0 + EDR
[3]-Specification of the Bluetooth System V1.2
[4]-
[5]-
[6]-
[7]WLAN
Not yet
released
November
2004
November
2003
January
2006
March
2005
August
2003
1999IEEE
Bluetooth SIG
Bluetooth SIG
Bluetooth SIG
Bluetooth SIG
Bluetooth SIG
IEEE
IEEE 802.11b, Supplement to 802.11-1999, Wireless LAN
[8]802.11b
[9]802.11g
[10]-
52/58Doc ID 16067 Rev 2
MAC and PHY specifications: Higher speed Physical Layer
(PHY) extension in the 2.4 GHz band
IEEE 802.11g, IEEE Standard for Information technology—
Telecommunications and information exchange between
systems—Local and metropolitan area networks—Specific
requirements—Part 11: Wireless LAN Medium Access
Control (MAC) and Physical Layer (PHY) specifications—
Amendment 4: Further Higher-Speed Physical Layer
Extension in the 2.4 GHz Band
ANSI/EIA/TIA-232-F, September 1997, Interface Between Data Terminal Equipment
and Data Circuit-Terminating Equipment Employing Serial Binary Data Interchange
RSSIReceive Signal Strength Indication
RXReceive
SCOSynchronous Connection Oriented
SIGBluetooth Special Interest Group
SPISerial Peripheral Interface
STSTMicroelectronics
SWSoftWare
TBDTo Be Defined
T
eSCO
T
T
SCO
sniff
eSCO interval
SCO interval
Sniff interval
TXTransmit
UARTUniversal Asynchronous Receiver/Transmitter
VCOVoltage Controlled Oscillator
VGAVariable Gain Amplifier
WCDMAWideband Code Division Multiple Access
WFBGAVery Very Thin Profile Fine Pitch Ball Grid Array
WLANWireless Local Area Network
WLCSPWafer-Level Chip Scale Package
Description
Doc ID 16067 Rev 255/58
Order codesSTA2500D
12 Order codes
Table 32.Ordering information
Order codePackagePackingProduction
STA2500DCLFBGA48TraySimplified production flow
STA2500DCTRLFBGA48Tape and reelSimplified production flow
STA2500DLFBGA48TrayAutomotive version
STA2500DTRLFBGA48Tape and reelAutomotive version
56/58Doc ID 16067 Rev 2
STA2500DRevision history
13 Revision history
Table 33.Document revision history
DateRevisionChanges
24-Jul-20091Initial release.
18-Jan-20102
Removed device summary table in cover page.
Added Section 12: Order codes on page 56.
Doc ID 16067 Rev 257/58
STA2500D
Please Read Carefully:
Information in this document is provided solely in connection with ST products. STMicroelectronics NV and its subsidiaries (“ST”) reserve the
right to make changes, corrections, modifications or improvements, to this document, and the products and services described herein at any
time, without notice.
All ST products are sold pursuant to ST’s terms and conditions of sale.
Purchasers are solely responsible for the choice, selection and use of the ST products and services described herein, and ST assumes no
liability whatsoever relating to the choice, selection or use of the ST products and services described herein.
No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted under this document. If any part of this
document refers to any third party products or services it shall not be deemed a license grant by ST for the use of such third party products
or services, or any intellectual property contained therein or considered as a warranty covering the use in any manner whatsoever of such
third party products or services or any intellectual property contained therein.
UNLESS OTHERWISE SET FORTH IN ST’S TERMS AND CONDITIONS OF SALE ST DISCLAIMS ANY EXPRESS OR IMPLIED
WARRANTY WITH RESPECT TO THE USE AND/OR SALE OF ST PRODUCTS INCLUDING WITHOUT LIMITATION IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE (AND THEIR EQUIVALENTS UNDER THE LAWS
OF ANY JURISDICTION), OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
UNLESS EXPRESSLY APPROVED IN WRITING BY AN AUTHORIZED ST REPRESENTATIVE, ST PRODUCTS ARE NOT
RECOMMENDED, AUTHORIZED OR WARRANTED FOR USE IN MILITARY, AIR CRAFT, SPACE, LIFE SAVING, OR LIFE SUSTAINING
APPLICATIONS, NOR IN PRODUCTS OR SYSTEMS WHERE FAILURE OR MALFUNCTION MAY RESULT IN PERSONAL INJURY,
DEATH, OR SEVERE PROPERTY OR ENVIRONMENTAL DAMAGE. ST PRODUCTS WHICH ARE NOT SPECIFIED AS "AUTOMOTIVE
GRADE" MAY ONLY BE USED IN AUTOMOTIVE APPLICATIONS AT USER’S OWN RISK.
Resale of ST products with provisions different from the statements and/or technical features set forth in this document shall immediately void
any warranty granted by ST for the ST product or service described herein and shall not create or extend in any manner whatsoever, any
liability of ST.
ST and the ST logo are trademarks or registered trademarks of ST in various countries.
Information in this document supersedes and replaces all information previously supplied.
The ST logo is a registered trademark of STMicroelectronics. All other names are the property of their respective owners.