Low power Bluetooth™ Module with antenna- F2M03GLA
Features
Fully qualified end product with
•
Bluetooth™ v2.0+EDR, CE and FCC
•
Low power consumption
•
Integrated high output antenna
•
Transmit power up to +8dBm
•
Range up to 350m (line of sight)
•
Piconet and Scatternet capability,
•
support for up to 7 slaves
Require only few external components
•
Industrial temperature range -40°C to +85°C
•
USB v2.0 compliant
•
Extensive digital and analog I/O interface
•
PCM interface for up to 3 simultaneous voice channels
•
Large external memory for custom applications
•
Support for 802.11b/g Co-Existence
•
• RoHS compliant
Datasheet
Rev: c
Applications
Industrial and domestic appliances
•
Cable replacement
•
Medical systems
•
Automotive applications
•
Stand-alone sensors
•
Embedded systems
•
Cordless headsets
•
Computer peripherals
•
(Mice, Keyboard, USB dongles, etc.)
Handheld, laptop and desktop computers
•
• Mobile phones
RoHS
COMPLIANT
2002/96/EC
General Description
F2M03GLA is a Low power embedded
Bluetooth™ v2.0+EDR module with built-in high
output antenna. The module is a fully
Bluetooth™ compliant device for data and voice
communication. With a transmit power of up to
+8dBm and receiver sensibility of down to
–83dBm combined with low power consumption
the F2M03GLA is suitable for the most
demanding applications. Developers can easily
implement a wireless solution into their product
even with limited knowledge in Bluetooth™ and
RF. The module is fully Bluetooth™ v2.0+EDR
qualified and it is certified according to CE and
FCC, which give fast and easy Plug-and-Go
implementation and short time to market.
The F2M03GLA comes with an on board highly
efficient omni-directional antenna that simplifies
the integration for a developers Bluetooth™
solution. The high output power combined with
the low power consumption makes this module
ideal for handheld applications and other battery
powered devices.
F2M03GLA can be delivered with the
exceedingly reliable and powerful easy-to-use
Wireless UART firmware implementing the
Bluetooth™ Serial Port Profile (SPP).
BLUETOOTH is a trademark owned by
Bluetooth SIG, Inc., U.S.A. and licensed to Free2move
www.free2move.net
Table of contents
Rev: c
Low power Bluetooth™ Module with antenna- F2M03GLA
Low power Bluetooth™ Module with antenna- F2M03GLA
Datasheet
2 Device terminal functions
Ground Pin Pin type Description
GND 1,16,17,32 VSS Ground connections
Power supplies Pin Pin type Description
+VCC 31 VDD Positive voltage supply (3.0-3.6)
Analog I/O Pin Pin type Description
AIO(0) 18 Bi-directional Programmable input/output line also
AIO(1) 19 Bi-directional Programmable input/output line also
Reset Pin Pin type Description
RESET 30 CMOS input with internal pull-up (10kΩ) Reset if low. Input debounced so must be
Test and debug Pin Pin type Description
SPI MISO 3 CMOS output, tristatable with weak internal
SPI CSB 5 CMOS input with weak internal pull-up Chip select for Synchronous Serial
SPI CLK 2 CMOS input with weak internal pull-down Serial Peripheral Interface clock
SPI MOSI 4 CMOS input with weak internal pull-down Serial Peripheral Interface data input
pull-down
UART Pin Pin type Description
UART CTS 27 CMOS input with weak internal pull-down UART clear to send active low
UART TX 29 CMOS output UART data output active high
UART RTS 26 CMOS output, tristatable with internal pull-up UART request to send active low
UART RX 28 CMOS input with weak internal pull-down UART data input active high
PCM Pin Pin type Description
PCM_OUT 7 CMOS output, tristatable with internal weak
PCM_SYNC 8 Bi-directional with weak internal pull-down Synchronous data SYNC
PCM_IN 9 CMOS input, with weak internal pull-down Synchronous data input
PCM_CLK 6 Bi-directional with weak internal pull-down Synchronous data clock
pull down
USB Pin Pin type Description
USB + 24 Bi-directional USB data plus
USB - 25 Bi-directional USB data minus
PIO Pin Pin type Description
PIO(11) 15 Bi-directional with programmable weak
PIO(10) 14 Bi-directional with programmable weak
PIO(9) 13 Bi-directional with programmable weak
PIO(8) 12 Bi-directional with programmable weak
PIO(7) 11 Bi-directional with programmable weak
PIO(6)/WLAN_Active/
Ch_Data
PIO(5)/BT_Active
PIO(4)/ BT_Priority/Ch_Clk
PIO(3) 21 Bi-directional with programmable weak
PIO(2) 20 Bi-directional with programmable weak
10 Bi-directional with programmable weak
23 Bi-directional with programmable weak
22 Bi-directional with programmable weak
internal pull-up/down
internal pull-up/down
internal pull-up/down
internal pull-up/down
internal pull-up/down
internal pull-up/down
internal pull-up/down
internal pull-up/down
internal pull-up/down
internal pull-up/down
Not connected Pin Pin type Description
NC Not connected Soldering pads for stability
possible to use as digital I/O
possible to use as digital I/O
low for >5ms to cause a reset
Serial Peripheral Interface data output
Interface, active low
Synchronous data output
Programmable input/output line
Programmable input/output line
Programmable input/output line
Programmable input/output line
Programmable input/output line
Programmable input/output line or
Optionally WLAN_Active/Ch_Data input for
co-existence signalling
Programmable input/output line or
Optionally BT_Active output for coexistence signalling
Programmable input/output line or
Optionally BT_Priority/Ch_Clk output for
co-existence signalling
Programmable input/output line
*The ADC is accessed through the VM function. The sample rate given is achieved as a part of this function
Average current consumption
VDD = 3.3V Temperature = 20
o
C
Measured using Wireless UART firmware v4.
Slave:
Mode Average (mA)
No connection (default settings) TBD
No connection (inquiry scan disabled) Connected (Short range), no data transfer Connected (Short range), no data transfer
Sniff mode 200 ms interval
Connected (Short range), no data transfer
Park mode 200 ms interval
Connected, (Short range) 115.2 kbit/s master to slave Connected, (Short range) 115.2 kbit/s slave to master Connected, (Short range) 115.2 kbit/s full duplex Connected, (Short range) 115.2 kbit/s slave to master
Sniff mode 125 ms interval
-
-
-
Master:
Mode Average (mA)
No connection (default settings) TBD
Connected (Short range), no data transfer Connected (Short range), no data transfer
Sniff mode 200 ms interval
Connected (Short range), no data transfer
Park mode 200 ms interval
Connected, (Short range) 115.2 kbit/s master to slave Connected, (Short range) 115.2 kbit/s full duplex Connected, (Long range) 115.2 kbit/s full duplex Connected, (Short range) 115.2 kbit/s slave to master
Sniff mode 125 ms interval
Connected, (Short range) 115.2 kbit/s slave to master
Sniff mode 125 ms interval
Connected, (Short range) 115.2 kbit/s full duplex
Sniff mode 125 ms interval
Low power Bluetooth™ Module with antenna- F2M03GLA
Datasheet
5 Firmware versions
F2M03 is supplied with Bluetooth stack firmware, which runs on the internal RISC micro controller of the
Bluetooth module. This chapter includes an overview of the different options for more in depth information
please use separate firmware datasheets provided by Free2move.
All firmware versions are compliant with the Bluetooth specification v2.0. The F2M03 software architecture
allows Bluetooth processing to be shared between the internal micro controller and a host processor.
Depending on application the upper layers of the Bluetooth stack (above HCI) can execute on-chip or on
the host processor.
Running the upper stack on F2M03 module reduces (or eliminates, in the case of a on module application)
the need for host-side software and processing time.
The integration approach depends on the type of product being developed. For example, performance will
depend on the integration approach adopted. In general Free2move offers four categories of Bluetooth
stack firmware:
• Wireless UART; offers a transparent interface to the Bluetooth channel. There is no need for
additional drivers or Bluetooth software on the host.
• Embedded module solutions offer an application to run on the module. There is no need for an
external host (E.g. a Bluetooth headset).
• Two-processor solution involving a host and host controller, where the higher layers of the
Bluetooth stack has to be implemented on the host.
• Two-processor embedded solution offers a host with limited resources to gain access to a
Bluetooth stack, with the higher layers on-chip, via a special API.
The protocol layer models for the different Bluetooth stack firmware categories can be represented as
shown in the figures below.
Low power Bluetooth™ Module with antenna- F2M03GLA
Datasheet
Application
Port Entity
RFCOMM SDP
L2CAP
HCI
LINK MANAGER
BASEBAND and RF
Device
Manager
Host
F2M03
Application
Bluetooth stack
HCI
HCI
LINK MANAGER
BASEBAND and RF
Host
F2M03
HCI, (Two-Processor
Architecture)
RFCOMM, (Embedded
Two-Processor Architecture)
Wireless UART
Free2move’s Wireless UART (WU) firmware is intended to replace the serial cable(s) connecting portable
and/or fixed electronic devices. Key features are robustness, high configurability, high security, low
complexity and low power. The WU firmware is compliant with the Bluetooth Serial Port Profile (SPP) for
setting up emulated serial cable connections between connected devices. There is no additional need for
drivers or an external host with Bluetooth software when using the WU firmware. When a successful
Bluetooth connection is established the data channel and the voice channel can be used simultaneously or
separately. All information sent/received at the data/voice interface of the WU unit is exchanged
transparently via Bluetooth with the connected remote device.
HCI (Standard Two-Processor Solution)
For the standard two-processor solution, where the split between higher and lower layers of the stack takes
place at the HCI, a complete Bluetooth stack is needed in the external host. It is often preferable to use this
solution when the host is a personal computer of some description. However, in general this category can
include any computing platform with communications capability that is not resource limited.
Free2move can offer a host stack solution on request.
Embedded Solution
This version of the stack firmware requires no host processor. All software layers, including application
software, run on the internal RISC processor in a protected user software execution environment.
The embedded solution can be used for a single chip Bluetooth product. One example is a cordless
headset. However this solution is equally applicable to any small wireless device that would benefit from a
single processor solution.
Free2move can offers among others the following single chip solutions upon a custom request*:
• Headset / Hands Free
• Human Interface Device; Mouse, keyboard etc (HID)
• Dial Up Network (DUN)
• Audio Gateway Profile (AGP)
• OBEX
• Onboard application (development of customer specific applications)
*Please consult your reseller for more information about custom firmwares.
Low power Bluetooth™ Module with antenna- F2M03GLA
Datasheet
5.1 Wireless UART
Free2move’s Wireless UART (WU) firmware is intended to replace the serial cable(s) connecting portable
and/or fixed electronic devices. Key features are robustness, high configurability, high security, low
complexity and low power.
The WU firmware is compliant with the Bluetooth Serial Port Profile (SPP) for setting up emulated serial
cable connections between connected devices. There is no additional need for drivers or an external host
with Bluetooth software when using the WU firmware.
Host
F2M03
Wireless UART application (SPP)
APPLICATION INTERFACE
HardwareBASEBAND and RF
Application
RFCOMMSDP
L2CAP
HCI
LINK MANAGER
Device
Manager
Wireless UART architecture
The WU application runs on top of an embedded Bluetooth v2.0 + EDR compliant stack, including protocols
up to the RFCOMM layer. Point-to-point connections are supported. This means that a unit running WU can
be either a master or slave unit.
The WU firmware offers one asynchronous data channel and one synchronous voice channel, both
channels capable of full duplex transmissions.
When a successful Bluetooth connection is established the data channel and the voice channel can be
used simultaneously or separately. All information sent/received at the data/voice interface of the WU unit is
exchanged transparently via Bluetooth with the connected remote device.
The WU unit is set to operate in a default mode that allows the user to communicate via the asynchronous
data channel over Bluetooth, as soon as a successful connection has been established. This can be
achieved without sending any configuration commands to the WU firmware. However, as long as there is
no Bluetooth connection established, it is possible to configure the WU firmware via hex commands
(described in the document Wireless_UART_protocol) or using a Windows configuration software.
PIOs are used to control/monitor the Bluetooth connectivity of the WU firmware.
PIO
2 Input High
3 Output High
To prevent connections or to close the current Bluetooth connection PIO[2] can be set high.
PIO[3] is held low as long as there is no Bluetooth connection. As soon as a successful Bluetooth
connection has been established with a remote device, PIO[3] goes high.
PIOs can also be used to emulate serial handshaking lines between the connected Bluetooth devices.
Emulation can either be DTE or DCE.
Emulated Signal PIO Signal Direction
While the handshaking lines are transparent to the data channel these I/O may also be used to transfer
digital signals between two Free2move devices running WU
RI 4 Input Output High
DTR 5 Output Input High
DCD 6 Input Output High
DSR 7 Input Output High
Active (TTL) Description
Active (TTL) Description
Request to close the current Bluetooth connection to the remote
device.
Indicates that a successful Bluetooth connection is established with a
remote device.
Low power Bluetooth™ Module with antenna- F2M03GLA
Datasheet
5.1.2 Settings
The default settings allow the user to communicate via Bluetooth, without sending any configuration
commands, as soon as a successful connection has been established. Information sent and received on
the serial interface of the WU unit at 38400 bps is transmitted transparently between the two connected
devices. The default settings are valid as long as the user has made no configuration.
When there is no Bluetooth connection established it is possible to configure the WU firmware via
commands sent on the serial interface. All settings changed by the user are stored in persistent memory.
The following serial settings are used for configuration mode and are not configurable:
Parameter Default Value
Baud rate 38400
Data bits 8
Parity None
Stop bits 1
Hardware flow control On
To be able to send commands to the Wireless UART firmware, it must be set in Host Controlled Mode
(HCM). As previously described the Wireless UART firmware can only enter HCM when no Bluetooth
connection is established.
Once entered HCM there are several commands that can be issued:
• Configuration commands
• Software / Hardware reboot
• Inquiry (search for Bluetooth devices in the neighborhood)
• Pairing (device security - authentication and encryption)
• Advanced configuration commands
• SCO commands
• Information commands
• Control commands
Configuration Commands
There are several settings stored in the Wireless UART firmware that can be read and modified by using
the configuration commands.
Examples of these settings are:
• Local Bluetooth name
• Local SDP-service name
• Operating mode
• Serial port settings
• Bluetooth security settings (authentication, encryption)
There are two normal operating modes:
• Connecting mode – Bluetooth master
• Endpoint mode – Bluetooth slave
In Connecting mode the Wireless UART firmware will continuously try to establish a Bluetooth connection to
a specified remote Bluetooth device in the neighborhood (Bluetooth master).
In Endpoint mode the Wireless UART firmware may accept connections from remote Bluetooth devices. A
connection request will be accepted when the specified rules are fulfilled (Bluetooth slave).
Low power Bluetooth™ Module with antenna- F2M03GLA
Datasheet
Software / Hardware Reboot
This option gives the ability to be able to reboot the module via software commands.
Inquiry
Search for other Bluetooth devices in the neighborhood.
There are three configuration parameters:
• How many seconds the search should be active
• A filter, used when searching for devices of as certain class
• The possibility to include the Bluetooth name of the discovered devices
Pairing
When authentication is enabled, the devices must be paired before a successful connection can be
established.
The Wireless UART firmware can either initiate pairing with a remote device or accept pairing requests.
During a pairing PIN codes are exchanged between the local and remote device. A successful pairing
requires identical PIN codes. The result of the pairing attempt will be returned to the Host. If pairing was
successful, a unique link key has been generated and saved in non-volatile memory. The link key is used in
the connection establishment procedure for secure verification of the relationship between the paired
devices.
The Wireless UART firmware allows the user to be paired with one device at a time. The last pin code
entered and link key generated are saved.
Advanced configuration
Includes among others commands for enabling power save modes, fine tune performance, enabling
modem emulation and changing transmit power.
SCO commands
Makes it possible to establish full duplex audio connections between two WU units.
Low power Bluetooth™ Module with antenna- F2M03GLA
Datasheet
5.1.3 Performance
The WU firmware is a complete on-chip application; limited resources restrict the maximum throughput. The
table below shows the maximum achieved throughput when streaming data between two connected WU
v4.00 devices at close range.
Maximum
Direction Baud Rate
Master to Slave 57600 ~57.6 ~57.6
Slave to Master 57600 ~57.6 ~57.6
Full duplex 57600 ~57.6 ~50.5
Master to Slave 115200 ~115.1 ~93.9
Slave to Master 115200 ~115.1 ~79.6
Full duplex 115200 ~114.5 ~42.0
Master to Slave 230400 ~223.1 ~158.0
Slave to Master 230400 ~221.4 ~117.7
Full duplex 230400 ~172.7 ~86.2
Master to Slave 460800 ~228.6 ~206.7
Slave to Master 460800 ~222.7 ~154.1
Full duplex 460800 ~173.3 ~109.8
Master to Slave 921600 ~240.1 ~235.7
Slave to Master 921600 ~235.4 ~186.0
Full duplex 921600 ~174.7 ~150.5
Throughput (kbit/s
(throughput mode))
Maximum
Throughput (kbit/s)
(latency mode)
5.1.4 Configuration
The F2M03 can either be configured using hex commands described in the document
“Wireless_UART_protocol.pdf” or using the Windows configuration software. The configuration software