Specifications

Introduction
blab-srn-005Pa
© CSR plc 2006
This material is subject to CSR’s non-disclosure agreement.
Page 3 of 48
_äìÉi~Ä»=îPKQ= Software Release Note
1 Introduction
This document describes _äìÉi~Ä»=îPKQ, the most recent release of BlueLab3, CSR's software development
kit for producing embedded applications for CSR’s Bluetooth
®
wireless technology chips. Some additional
documentation is included with BlueLab; see the manual available inside xIDE, the integrated development
environment for BlueLab and the accompanying PDFs.
1.1 BlueLab3
BlueLab3 has the same virtual machine (VM) architecture that has been successfully implemented in the vast
majority of single-chip Bluetooth products, including around 70% of all headset designs. The VM isolates user
code in a ‘sandbox’ where it cannot interfere with the basic Bluetooth operation of the chip. This allows the use of
pre-qualified low-level stack firmware, greatly simplifying Bluetooth qualification process and reducing time to
market. The user does not need to qualify complex low-level firmware. CSR does this.
BlueLab v3.0 introduced true on-chip, real-time debugging for the first time on any Bluetooth chip. There is no
need to stop the chip running to get debug data. It is possible to watch traffic in real-time while the chip runs. The
development environment monitors and records messages between the VM application and the upper layers of
the Bluetooth stack. The resulting record can be as useful as, but much easier to obtain than, an air trace when
debugging complex problems such as interoperability between two Bluetooth devices.
These features make BlueLab3 by far the most flexible and functional set of tools available for any Bluetooth chip
today.
The new tools introduced with BlueLab3 make it easier to take advantage of its much improved and expanded
set of software libraries. These libraries improve performance and consistency for functions such as event
handling. Crucially, they are designed from the ground up to support applications that use multiple simultaneous
connections. This function is essential for cutting edge Bluetooth products like wireless stereo headphones with
call handling.
The library changes mean that applications written for BlueLab2 must be partially rewritten to run under
BlueLab3. Rewriting the code need not be an arduous task because the new libraries automate many common
functions. As a result BlueLab3 applications are considerably simpler than before. It is generally only necessary
to write a user interface to sit above the highly functional libraries provided with the Software Development Kit
(SDK).
The initial releases of BlueLab3 were focussed on wireless headphones with call handling (combined
Headset/Hands-Free and Audiovisual profiles) because the ability to support multipoint connections is essential
for these products.
1.2 BlueLab v3.4
BlueLab v3.4 includes the source code for CSR’s best ever mono headset/handsfree application, designed for
BlueCore3 and BlueCore4. It also includes the configuration tool for that headset, previously supplied as an
update to the BlueLab v3.3 release. Source code for example HID keyboard, mouse and dongle applications are
included for the first time in BlueLab v3.4.
It extends the set of profile libraries to include PBAP (Phone Book Access Profile) and DUN (Dial Up
Networking), adding to the HID, AG, OBEX, SPP, AV and HFP libraries that where shipped with BlueLab v3.3.
BlueLab 3 now includes support for more profiles than BlueLab 2 and (with the exception of PAN applications)
should be the preferred environment for new development of embedded applications on BlueCore.
BlueLab 3 fully supports the latest features of BlueCore4 and has been designed with support for future
development of BlueCore chips.