Users are not permitted to make changes or modify the device in any way.
With the Development Kit for the Bluetooth Platform Solution from Motorola, the company is launching a
unique demonstration and development tool for its platform.
The Development Kit contains all of the hardware, software, and documentation needed to evaluate the
functionality of the ICs making up Motorola’s Bluetooth platform solution chipset:
•MC71000 Bluetooth Baseband Controller IC
•MC13180 Bluetooth Low Power Wireless Data Transceiver IC
•MC13181 Wireless Power Management IC
Also, you can develop software and hardware solutions around the platform chipset. The Development Kit
makes it possible to easily and quickly set up and start demonstrating a Class 2 Bluetooth solution, and it
provides an efficient layout for the baseband and RF on an FR4 PCB substrate.
The primary applications of the Development Kit are:
•Evaluation of the platform chipset and its features
•Porting of a user Bluetooth stack to the Motorola Bluetooth hardware
•Prototyping of a Bluetooth-enabled host device
•Reference design for quick layout of a Bluetooth solution based on the MC71000 and MC13180
chipset
The Development Kit is Bluetooth 1.1 qualified and type approved in a great number of countries. See the
section “Regulatory”.
For detailed information on the ICs making up the platform chipset, please see the technical brief
accompanying each of the ICs: MC71000, MC13180, and MC13181. These technical briefs are all
included on the CD.
1.1About This Guide
This user’s guide will help you get started with the Bluetooth Development Kit. The guide covers a large
number of aspects of using the Development Kit, including:
•Overview of the Development Kit and accompanying documentation
•Instructions on setting up the hardware and software
•Descriptions of the various elements that make up the Development Kit
The following is an overview of the various sections of this user’s guide and a brief description of each
section:
•Chapter 1, “Introduction” contains an overview of the user’s guide and additional documents
available from the CD. The introduction is also where to find information on support, unpacking,
system requirements, and a list of the acronyms used in this guide.
•Chapter 2, “Product Overview” provides an overview of the Development Kit where the various
elements of the product are described briefly.
•Chapter 3, “Setup” explains how to set up the hardware and software to get the Development Kit
running.
•Chapter 4, “Hardware” describes the various aspects of the Development Kit hardware
•Chapter 5, “Limitations” describes the limitations of the current Development Kit version.
Currently this chapter deals with HCI Limitations only.
•Chapter 6, “Regulatory” contains regulatory statements, a list of the countries where the
Development Kit will be type approved, and information on what is needed to obtain type approvals
for new products.
•Appendix A, “Board Diagram“, contains a diagram of the Development Kit board.
1.2Additional Documents
In addition to this user’s guide, the documentation for the Development Kit includes the following
documents. These are all accessible from the document overview on the CD.
•User’s Guides for various elements of the Development Kit:
— Bluetooth HCI Terminal Guide
— Configuration Manager User’s Guide
— DemoBench User’s Guide
— Bluetooth Platform Solution Embedded System User’s Guide
— Bluetooth Headset Guide
•Reference designs: Bluetooth Platform Solution Reference Designs including descriptions and
schematics
•A platform document providing a system overview of the Bluetooth Platform Solution from
Motorola
•Technical briefs for the various Bluetooth platform elements:
— MRFIC2408 External Power Amplifier IC
— MC13180 Bluetooth Low Power Wireless Data Transceiver IC
— MC13181 Wireless Power Management IC
— MC71000 Bluetooth Baseband Controller IC
— Bluetooth Development Kit
•Application notes for the following:
— Using the Bluetooth Audio Signal Processor (BTASP) for High-Quality Audio Performance
— Motorola’s Bluetooth Solution to Interference Rejection and Coexistence with 802.11
This section contains a brief overview of the Development Kit. More detailed information on the various
elements of the Development Kit is included in later sections and in the separate user’s guides included on
the CD.
2.1Block Diagram
The following figure shows the Development Kit block diagram:
Figure 2-1. Block Diagram
USB
RS232
UART
Modular Jack
DC
Power
Input
USB
RS232
Level
Shifter
CODEC
MC13181
MC71000MC13180
EEPROM
7 Status
LEDs
Reset Switch
2.2Interfaces
The development kit features RS232, UART, and USB interfaces:
Antenna
Diversity
Switch
Class ½
Antenna Jumper
Antenna
Connector
F Antenna
•RS232 interface: Programmable baud rate from 1200 to 921 Kbit.
•UART interface: 5-pin header with RxD, CTS, RTS, and GND, 3.3 V signaling, programmable
baud rate from 1200 to 921 Kbit, HCI UART transport layer.
With the Bluetooth HCI Terminal you can interact with your Bluetooth hardware. The interface is similar
to that of an AT Terminal application when communicating with a modem. The Bluetooth HCI Terminal
makes it easy to send HCI commands from a computer to a Bluetooth device. Likewise, it is easy to
receive HCI responses from a Bluetooth device. Consequently, you can get hands-on experience with the
HCI. Or you can test your own Bluetooth hardware.
The Bluetooth HCI Terminal is accompanied by the Bluetooth HCI Terminal Guide, accessible from the
document overview on the CD:
2.5.2Configuration Manager
The Configuration Manager is an application that allows you to handle the Development Kit file system.
With this tool, you can download firmware patches and set up a number of baseband and radio parameters
to exercise the board. All parameters are restorable and default settings are stored automatically.
The Configuration Manager is accompanied by a user’s guide, accessible from the document overview on
the CD.
2.5.3DemoBench
The DemoBench is a demonstration tool that can be used for a number of purposes. You can send a file to
another Bluetooth device, “chat” with another Bluetooth device, and view link and packet statistics in a
real-time application.
The DemoBench is accompanied by a user’s guide, accessible from the document overview on the CD.
This section provides information on various aspects of the Development Kit hardware. In addition,
Appendix A, “Board Diagram“, contains a diagram of the Development Kit board.
4.1Signal and Connection Descriptions
The development kit contains the following connections, switches, and indicators:
•Power supply input
•Modular jack 4/4 connector for mono-audio speaker and microphone (headset application)
•RS232 interface
•UART interface
•USB interface
•Antenna connector
•JTAG allowing interface to MC71000 production test
•Reset switch
•Four control buttons for the headset application
•On/off switch
•Seven status LEDs
The power supplied for the development kit is DC with the ratings stated in the specifications.
An analog audio signal to be transmitted over the Bluetooth connection can be fed into the development kit
via the modular jack or as streaming audio through the host interface. It will be converted to digital data and
transmitted through the Bluetooth link. A digital audio signal received from a connected Bluetooth device
will be converted to an analog audio signal and available at the modular jack or as streaming audio through
the host interface (UART, SSI, SPI). The MC71000 has a Bluetooth Audio Signal Processor (BTASP) for
superior audio performance.
The RS232/UART interfaces can be used to transfer data and audio between a host and the Bluetooth device.
The firmware of the development kit can be upgraded through the RS232/UART interface.
The USB interface is a standard HCI USB interface. This interface can be used to connect the development
kit to a PC or other devices with PC-compatible USB connections.
The CODEC is attached to the MC71000 via the SPI (data) and SSI (streaming audio) interfaces.
The antenna connector is an SMA 50 ohm connection.
•Audio output: 1.6 Vpp, modular jack 4/4 connector
The following table shows the current consumption measurements of the circuits of the MC71000
Bluetooth Baseband Controller and MC13180 Bluetooth Low Power Wireless Data Transceiver ICs.
Table 1: Current Consumption Measurements of MC71000 and MC13180 Circuits
DH5 asymmetric RX50.4 mATX rate 57.6 kbits
RX rate 723.2 kbits
DH5 asymmetric TX48.5 mATX rate 723.2 kbits
RX rate 57.6 kbits
DH5 symmetric45.8 mATX rate 433.9 kbits
RX rate 433.9 kbits
HV145.8 mA
HV327.8 mA
Total system in
low-power mode
0.130 mA
Note that the table contains typical values.
4.4.1Power Supply
The board is fed with power from on-board standard regulators.
The on-board power supply regulators should be fed with the supply provided, which generates the
following voltages for the board:
•1.85 V
•2.65 V
•3.3V
4.4.2Reset Circuit
The board includes a push button for full system reset of the MC71000 and all peripherals.
4.4.3Clocks
The clocks in the system are as follows:
•Sleep mode clock: 32.768 kHz.
•Active mode clock: 24 MHz from MC13180 radio module
The MC71000 includes an internal oscillator circuit for the 32.768 kHz sleep mode clock. Only an external
crystal and a few other components are needed.
The MC71000 has embedded memory of 256 Kbytes of ROM and 64 K of RAM. An image can be
uploaded from a host system, or a low-cost serial EEPROM (four-wire connection). For more information
on the contents and structure of the MC71000 memory, please refer to the Bluetooth Platform Solution Embedded System User’s Guide. This is accessible from the document overview on the Development Kit
CD.
4.4.5UART Interface
The UART interface is embedded in the MC71000. However, an external level converter is needed. For
this purpose, the MAX3237 1.0 Mbit level converter is used. The level converter is connected to the
MC71000 and a female 9-pin D-sub. The connection between the level converter and the MC71000 is
passed through a jumper block in order to aid debugging, and, if ever needed, to use a different type of
level converter.
4.4.6USB Interface
The USB interface consists of the National USBN9604 USB device controller. A 3.3 V power supply is
used for the USBN 9604.
For information on the USB limitations of the Development Kit, see the section “USB Limitations”
4.4.7CODEC Interface
The audio interface consists of the Xemics XE3006 CODEC, a 4-pin header and a 4/4p amp connector. As
to the power supply for the CODEC, both 1.8 V and 3.3 V are selectable by a “+” formation jumper.
Sampling rate is configured at 7.8125 kHz.
4.4.8Antenna
The Development Kit contains an F entenna and an SMA 50 Ohm antenna connector.
4.5Reference Designs
The Bluetooth Platform Solution reference designs include the following: Host optimized, host
non-optimized, and standalone (headset). Descriptions and schematics are included in the Bluetooth Platform Solution Reference Designs document. This is accessible from the document overview on the
Development Kit CD.
This device is intended for evaluation and development purposes by professionals only and is NOT
for re-sale.
Regulatory
This section contains regulatory statements, a list of the countries where the Development Kit will be type
approved, and information on what is needed by developers to obtain type approvals for their products.
6.1 Regulatory Statements
NOTE:
Users are not permitted to make changes or modify the system in any way.
Changes or modifications not expressly approved by the party responsible
for compliance could void the user’s authority to operate the equipment.
6.1.1General
This product complies with any mandatory product specification in any country where the product is sold.
6.1.2European Union (EU) and EFTA
This equipment complies with the R&TTE directive 1999/5/EC and has been provided with the CE mark
accordingly.
6.1.3France
This equipment may only be used as a Class 2 device, not as a Class 1 device. Note also that only indoor
use is allowed.
6.1.4Nederland
(Applies to 20dBm products only)
Niet voor gebruik in de buitenlucht.
Deze apparatuur is uitsluitend bedoeld voor gebruik binnenshuis.
Tested to comply with FCC Standards FOR HOME OR OFFICE USE. See FCC 47CFR part 15.19(b)(2)
This device complies with part 15 of the FCC rules and with RSS-210 / RSS-139 of the Industry Canada.
Operation is subject to the following two conditions: (1) This device may not cause harmful interference,
and (2) this device must accept any interference received, including interference that may cause undesired
operation. See FCC regulation CFR47 sec. 15.19(3).
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant
to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful
interference in a residential installation. This equipment generates, uses and can radiate radio frequency
energy and, if not installed and used in accordance with the instructions, may cause harmful interference to
radio communications. However, there is no guarantee that interference will not occur in a particular
installation. If this equipment does cause harmful interference to radio or television reception, which can
be determined by turning the equipment off and on, the user is encouraged to try to correct the interference
by one or more of the following measures:
•Reorient or relocate the receiving antenna
•Increase the separation between the equipment and receiver
•Connect the equipment into an outlet on a circuit different from that to which the receiver is
connected
•Consult the dealer or an experienced radio/TV technician for help
In order to comply with FCC RF Exposure requirements, a minimum separation distance of 20 cm must
always be maintained between the transmitter antenna and all persons during normal operation.
Note that any changes or modifications to this equipment not expressly approved by the manufacturer may
void the FCC authorization to operate this equipment.See FCC regulation CFR47 sec. 15.21.
6.1.6 Canada Compliance (Industry Canada)
To prevent radio interference to the licensed service, this device is intended to be operated indoors and
away from windows to provide maximum shielding. Equipment that is installed outdoors is subject to
licensing.
In French: Pour empêcher un brouillage radioélectrique au service faisant l'objet d'une licence, cet appareil
doit être utilisé à l'interieur et loin des fenêtres afin de founir un écran de blindage maximal. Au cas aù un
installation en plain air, le materiel doit faire l'objet d'une licence.
6.1.7Singapore
This product complies with the standard Infocomm Development Authority of Singapore (IDA) TS SSS
amended by the Guidance notes on Bluetooth Type Approval Framework and has been approved by the
IDA under the Type Approval Certificate (TAC) number: Motorola TAC number TBD
The supplier of this equipment is responsible that the equipment can be used as described in the
accompanying documentation. Furthermore, the supplier is responsible for providing proper installation
and after-sales maintance of the equipment to meet the user's needs.
Under no circumstances is the IDA liable for the use, installation, or after-sales maintenance of the
Este equipamento opera em caráter secundário, isto é, não tem direito a proteção contra interferência
prejudicial, mesmo de estações do mesmo tipo, e não pode causar interferência a sistemas operando em
caráter primário.
Customers of Motorola Bluetooth chipsets will face some Bluetooth qualification and regulatory
requirements for their products. The following lists the requirements for the major markets as defined by
Digianswer/Motorola as tier 1 countries: Australia, Canada, Europe (15 + 4 EFTA countries), Japan, New
Zealand and US. A number of other countries worldwide will accept the test reports made for Europe
and/or US approvals.
Motorola chipsets (radio/baseband) are pre-qualified as Bluetooth components. Also any variants of
Motorola software stacks will be pre-qualified. The assumption of pre-qualification provides that
customers will implement the radio module (radio chip including surrounding components and print
layout) without any changes.
6.2.1Requirements for Bluetooth Qualification
Baseband chipset will be used as a pre-qualified component and do not require re-testing.
Any incorporated variant of Motorola software stack will be used as a pre-qualified component and do not
require re-testing.
Radio will need to be re-tested in the product layout for the following 8 (of 16) test cases:
Table 6-1.
TRM/CA/04/ETX Output Spectrum-Frequency range
TRM/CA/08/EInitial Carrier Frequency Tolerance
TRM/CA/09/ECarrier Frequency Drift
TTRC/CA/01/EOut-of-Band Spurious Emissions-radiated
RCV/CA/02/ESensitivity-multi-slot packets
RCV/CA/03/EC/I performance
RCV/CA/04EBlocking performance
TP/PHYS/TRX/BV-05-CSymbol rate
If changes are made to the Development Kit radio module BOM or layout, all 16 Bluetooth test cases will
be required to be re-tested. Depending on the nature of changes to the radio, re-testing might only be
necessary in normal temperature. This has to be decided by the BQB in each case.
6.2.2Requirements for regulatory type approvals:
The following regulatory testing needs to be made:
•For CE-marking: EN 300 328-2 (emission), EN 301 489-17 (EMC), EN 60950 (safety)
•For Japan approval: ARIB T-66.
•For FCC grant: CFR47 part 15.205, 15.209 and 15.247 (except 15.247e: processing gain)
NOTE:
As Motorola radios will be approved by FCC as radio modules and the
FCC testing can be avoided for regulatory purposes for radio modules,
provided no changes are made to the radio module BOM or layout, it will
still be necessary to perform the Out-of-Band Spurious
Emissions-radiated-test of part 15.209.
The product might be subject to additional product specific regulations, such as PSTN regulations and
other.
Type approval applications have to be filed to the national authorities for each product.
Documentation submitted for type approvals can vary from country to country, but will in general include:
test reports, pictures, BOM, schematics, PCB layouts, product descriptions (block diagrams), antenna
information, SAR statements (see below), label/manual information (legal text) and manufacturer
information.
Both in Europe and US regulators are currently working on new sets of rules for combined radio
equipment as well as rules for SAR. Test requirements for SAR (including combined radio) will most
likely be topical within the next year.