BC41B143A-ds-003Pc CSR, BC41B143A-ds-003Pc Datasheet - Page 38

• Manufacturer Part Number: BC41B143A-ds-003Pc
• Description: Blue Core ROM Plug-n-Go
• Manufacturer: CSR

9.1.2
The firmware extends the standard Bluetooth functionality with the following features:
Note:
BC41B143A-ds-003Pc
Always refer to the Firmware Release Note for the specific functionality of a particular build.
Supports BlueCore Serial Protocol (BCSP), a proprietary, reliable alternative to the standard Bluetooth UART
Host Transport
Provides a set of approximately 50 manufacturer-specific HCI extension commands. This command set,
called BlueCore Command (BCCMD), provides:
The firmware can read the voltage on a pair of the chip's external pins. This is normally used to build a battery
monitor, using either VM or host code
A block of BCCMD commands provides access to the chip's Persistent Store configuration database (PS).
The database sets the device's Bluetooth address, Class of Device, radio (transmit class) configuration, SCO
routing, LM, USB and DFU constants, etc.
A UART break condition can be used in three ways:
The DFU standard has been extended with public/private key authentication, allowing manufacturers to
control the firmware that can be loaded onto their Bluetooth modules
A modified version of the DFU protocol allows firmware upgrade via the chip's UART
A block of radio test or BIST commands allows direct control of the chip's radio. This aids the development
of modules' radio designs, and can be used to support Bluetooth qualification.
Virtual Machine (VM). The firmware provides the VM environment in which to run application-specific code.
Although the VM is mainly used with BlueLab and RFCOMM builds (alternative firmware builds providing
L2CAP, SDP and RFCOMM), the VM can be used with this build to perform simple tasks such as flashing
LEDs via the chip's PIO port.
Hardware low power modes: Shallow Sleep and Deep Sleep. The chip drops into modes that significantly
reduce power consumption when the software goes idle.
SCO channels are normally routed via HCI (over BCSP). However, up to three SCO channels can be routed
over the chip's single PCM port (at the same time as routing any remaining SCO channels over HCI).
Key Features of the HCI Stack: Extra Functionality
1.
2.
3.
Access to the chip's general-purpose PIO port
The negotiated effective encryption key length on established Bluetooth links
Access to the firmware's random number generator
Controls to set the default and maximum transmit powers; these can help minimise interference
between overlapping, fixed-location piconets
Dynamic UART configuration
Radio transmitter enable/disable. A simple command connects to a dedicated hardware switch that
determines whether the radio can transmit.
Presenting a UART break condition to the chip can force the chip to perform a hardware reboot
Presenting a break condition at boot time can hold the chip in a low power state, preventing normal
initialisation while the condition exists
With BCSP, the firmware can be configured to send a break to the host before sending data. (This
is normally used to wake the host from a Deep Sleep state.)
© Cambridge Silicon Radio Limited 2005
Advance Information
CSR Bluetooth Software Stacks
Page 38 of 94