F2M03GLA
F2M03GLA
F2M03GLA
Datasheet R ev: e 200 9
Features
• Fully qualified product with Bluetooth® v2.0+EDR, CE,
FCC, and IC
• Low power consumption
• Integrated high output antenna
• Transmit power up to +6.3dBm
• Class1/ 2/ 3 Configurable
• Range: up to 250m (line of sight)
• Piconet and Scatternet capability, supports 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
• REACH compliant
Table of contents
1
Device pinout ........................................................................................................................... 3
2
Device terminal functions ....................................................................................................... 4
3
Electrical Characteristics ....................................................................................................... 5
4
Radio Characteristics ............................................................................................................. 8
5
Firmware versions ................................................................................................................... 9
5.1
Wireless UART ........................................................................................................................ 11
5.2
HCI .......................................................................................................................................... 16
6
Device terminal description ................................................................................................. 19
6.1
UART Interface ........................................................................................................................ 19
6.2
USB Interface .......................................................................................................................... 20
6.3
Serial Peripheral Interface ....................................................................................................... 24
6.4
I C Interface ............................................................................................................................. 25
2
1 Device pinout
Pinout of the F2M03GLA seen from the component side [TOP VIEW]
3 Electrical Characteristics
*F2M03GLA meet the Bluetooth® v2.0+EDR specification when used in the recommended operating
condition.
Output Voltage
VOL output logic level low, (lO = 4.0mA), 2.7V ≤ VDD ≤ 3.0V - - 0.2 V
VOH output logic level high, (lO = 4.0mA), 2.7V ≤ VDD ≤ 3.0V VDD-0.2 - - V
Input threshold
VIL input logic level low - - 0.3VDD V
VIH input logic level high 0.7VDD - - V
Notes:
Current drawn into a pin is defined as positive; current supplied out of a pin is defined as negative.
*The ADC is accessed through the VM function. The sample rate given is achieved as a part of this function
Slave:
Mode Average (mA)
No connection (default settings) 1,6
Connected, no data transfer 26
Connected, no data transfer 3,2
Sniff mode 125 ms interval
Connected, 115.2 kbit/s master to slave 33
Connected, 115.2 kbit/s slave to master 35
Connected, 115.2 kbit/s full duplex 35
Connected, 115.2 kbit/s master to slave 23
Sniff mode 125 ms interval
Connected, 115.2 kbit/s slave to master 18
Sniff mode 125 ms interval
Connected, 115.2 kbit/s full duplex 30
Sniff mode 125 ms interval
SCO connection HV1, no data transfer 50
SCO connection HV3, no data transfer 36
SCO connection HV3, no data transfer 29
Sniff mode 30 ms interval
SCO connection HV3, 115.2 kbit/s master to slave 42
Master:
Mode Average (mA)
No connection (default settings) 44
Connected, no data transfer 7
Connected, no data transfer 3,5
Sniff mode 200 ms interval
Connected, 115.2 kbit/s master to slave 35
Connected, 115.2 kbit/s slave to master 31
Connected, 115.2 kbit/s full duplex 35
Connected, 115.2 kbit/s master to slave 26
Sniff mode 125 ms interval
Connected, 115.2 kbit/s slave to master 13
Sniff mode 125 ms interval
Connected, 115.2 kbit/s full duplex 29
Sniff mode 125 ms interval
SCO connection HV1, no data transfer 50
SCO connection HV3, no data transfer 31
SCO connection HV3, no data transfer 31
Sniff mode 30 ms interval
SCO connection HV3, 115.2 kbit/s master to slave 49
Leakage current
VDD = 3.3V Temperature = 20 oC
Mode Typ Unit
Reset LOW 200 mA
Deep sleep 275 mA
4 Radio Characteristics
Note:
The F2M03GLA has a maximum transmit power of +6.3dBm and is certified according to the Bluetooth®
v2.0+EDR specification as a Class1 device. It is though possible to restrict the maximum transmit power to
comply with either a Class2 or Class3 device upon configuration.
Bluetooth® Specification
Class of device Maximum transmit power
Class1 +20dBm
Class2 +4dBm
Class3 0dBm
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 UART 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.
Application
Host Host
F2M03
F2M03 Wireless UART application (SPP) Application
Device Device
L2CAP L2CAP
Manager Manager
HCI HCI
Application
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.
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.
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.
Application
Host Host
F2M03
F2M03 Wireless UART application (SPP) Application
Device D
L2CAP L2CAP
Manager M
HCI HCI
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.
Signal
UART Active (TTL) Description
Direction
TX Output High UART transmit data
RX Input High UART receive data
RTS Output Low UART request to send
CTS Input Low UART clear to send
Voice interface:
CODEC I/O Signal Direction Description
MIC_P Input (analogue) Microphone input positive
MIC_N Input (analogue) Microphone input negative
AUX_DAC Output (analogue) Microphone input bias
SPKR_P Output (analogue) Speaker output positive
SPKR_N Output (analogue) Speaker output negative
Signal
PIO Active (TTL) Description
Direction
Request to close the current Bluetooth® connection to the remote
2 Input High
device.
Indicates that a successful Bluetooth® connection is established with a
3 Output High
remote device.
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.
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
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.
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).
Inquiry
Search for other Bluetooth® devices in the neighborhood.
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.
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 Maximum
Direction Baud Rate Throughput (kbit/s Throughput (kbit/s)
(throughput mode)) (latency mode)
Master to Slave 57600 ~57.6 ~57.6
Slave to Master 57600 ~57.6 ~57.6
Full duplex 57600 ~57.6 ~50.5
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 can
be downloaded from www.free2move.se
5.2 HCI
In this implementation the internal processor of the module runs the Bluetooth® stack up to the Host
Controller Interface (HCI) as specified in the Bluetooth® specification V1.1. The external host processor must
provide all upper Bluetooth® stack layers. Free2move do not offer a host stack solution for an external Host.
Application
Bluetooth stack
HCI
Host
HCI
BASEBAND and RF
Standard Two-Processor
Architecture
The firmware has been written against the Bluetooth® v2.0 + EDR specification.
• Bluetooth® components: Baseband (including LC), LM and HCI
• Standard USB (v1.1) and UART (H4) HCI Transport Layers
• All standard radio packet types
• Full Bluetooth® data rate, enhanced data rates of 2 and 3Mbps(1)
• Operation with up to seven active slaves(1)
• Operation with up to three SCO links, routed to one or more slaves
• Scatternet v2.5 operation
• Maximum number of simultaneous active ACL connections: 7(2)
• Maximum number of simultaneous active SCO connections: 3(2)
• Role switch: can reverse Master/Slave relationship
• All standard SCO voice coding, plus “transparent SCO”
• Standard operating modes: Page, Inquiry, Page-Scan and Inquiry-Scan
• All standard pairing, authentication, link key and encryption operations
• Standard Bluetooth® power saving mechanisms: Hold, Sniff and Park modes, including “Forced
Hold”
• Dynamic control of peers’ transmit power via LMP
• Master/Slave switch
• Broadcast
• Channel quality driven data rate (CQDDR)
• All standard Bluetooth® Test Modes
• Standard firmware upgrade via USB (DFU)
Note:
(1)
Maximum allowed by Bluetooth® v2.0 + EDR specification.
(2)
F2M03 supports all combinations of active ACL and SCO channels for both Master and Slave operation, as specified by
the Bluetooth® v2.0 + EDR specification.
SCO channels are normally routed over HCI (over BCSP). However, up to three SCO channels can be routed
over the module’s single PCM port (at the same time as routing any other SCO channels over HCI).
Four signals are used to implement the UART function, as shown in the figure above. When F2M03 is
connected to another digital device, UART_RX and UART_TX transfer data between the two devices. The
remaining two signals, UART_CTS and UART_RTS, can be used to implement RS232 hardware flow control
where both are active low indicators. All UART connections are implemented using CMOS technology and
have signalling levels of 0V and VDD. UART configuration parameters, such as Baud rate and packet format,
are set by Free2move firmware.
Note:
In order to communicate with the UART at its maximum data rate using a standard PC, an accelerated serial
port adapter card is required for the PC.
(1)
Uses RS232 protocol but voltage levels are 0V to VDD, (requires external RS232 transceiver IC)
The UART interface is capable of resetting the Free2move module upon reception of a break signal. A Break
is identified by a continuous logic low on the UART_RX terminal, as shown in figure below. If tBRK is longer
than a special value, defined by the Free2move firmware a reset will occur. This feature allows a host to
initialise the system to a known state. Also, the F2M03 can emit a Break character that may be used to wake
the Host. The above capabilities are not supported in the standard firmware, please contact Free2move for
more information.
Break signal
Note: The USB interface can only be used with the HCI firmware
The USB internal pull-up is implemented as a current source, and is compliant with 7.1.5 of the USB
specification v1.1. The internal pull-up pulls USB DP high to at least 2.8V when loaded with a 15kΩ-5% pull-
down resistor (in the hub/host) (when VDD=3.1V). This presents a the venin resistance to the host of at least
900Ω. Alternatively, an external 1.5kΩ pull-up resistor can be placed between a PIO line and D+ on the USB
cable. The default setting for the HCI-firmware uses the internal pull-up resistor.
PIO
USB +
USB –
When selecting a regulator, be aware that VBUS may go as low as 4.4V. The inrush current (when charging
reservoir and supply decoupling capacitors) is limited by the USB specification (see USB 1.1 specification,
section 7.2.4.1). Some applications may require soft-start circuitry to limit inrush current if more than 10µF is
present between VBUS and GND.
The 5V VBUS line emerging from a PC is often electrically noisy. Regulation down to e.g. VDD=3.3V should
include careful filtering of the 5V line to attenuate noise that is above the voltage regulator’s bandwidth.
Excessive noise on the VDD supply pins of F2M03 may result in reduced receive sensitivity and a distorted
transmit signal. Recommended voltage regulator for the F2M03 is presented in section 6.7.
USB +
USB –
USB ON
Note:
USB ON is shared with F2M03’s PIO terminals.
USB_DETACH, is an input which, when asserted high, causes F2M03 to put USB- and USB+ in a high-
impedance state and turns off the pull-up resistor on USB+. This detaches the device from the bus and is
logically equivalent to unplugging the device. When USB_DETACH is taken low, F2M03 will connect back to
USB and await enumeration by the USB host.
USB_WAKE_UP, is an active high output (used only when USB_DETACH is active) to wake up the host and
allow USB communication to recommence. It replaces the function of the software USB WAKE_UP message
(which runs over the USB cable proper), and cannot be sent while F2M03 is effectively disconnected from the
bus.
Although F2M03’s Bluetooth® module meets the USB specification, Free2move cannot guarantee that an
application circuit designed around the chip is USB compliant. The choice of application circuit, component
choice and PCB layout all affect USB signal quality and electrical characteristics. The information in this
document is intended as a guide and should be read in association with the USB specification. Independent
USB qualification must be sought before an application is deemed USB compliant and can bear the USB
logo. Such qualification can be obtained from a USB plugfest or from an independent USB test house.
Terminals USB+ and USB- adhere to the USB specification v2.0 (Chapter 7) electrical requirements.
For ac and dc specifications for terminals USB_DETACH, USB_WAKE_UP, USB_PULL_UP and USB_ON, refer
to section PIO specification.
Note:
The SPI signals should be routed out from the module if you need to upgrade the firmware on the module in
the future when the module is already soldered. It is highly recommended to route out the SPI-signals of the
module for software upgrade of the firmware!
Note:
The designer should be aware that no security protection is built into the hardware or firmware associated with this port,
so the terminals should not be permanently connected in a PC application. This interface is not a user interface and only
used for initial download and configuration of the firmware for the module.
6.4 I 2 C Interface
PIO[8:6] can be used to form a master I2C interface. The interface is formed using software to drive these
lines. Therefore, it is suited only to relatively slow functions such as driving a dot matrix liquid crystal display
(LCD), keyboard scanner or EEPROM.
Notes:
The I2C interface is controlled by firmware specific settings. Please see specific firmware datasheet for information
PIO lines need to be pulled-up through 2.2k: resistors.
PIO[7:6] dual functions, UART bypass and EEPROM support, therefore, devices using an EEPROM cannot
support UART bypass mode.
For connection to EEPROMs, contact Free2move for information about devices that are currently supported.
6.5 PCM
Pulse Code Modulation (PCM) is the standard method used to digitise audio (particulary voice) for
transmission over digital communication channels. Through its PCM interface, F2M03 has hardware support
for continual transmission and reception of PCM data, thus reducing processor overhead for wireless
headset and other audio applications. F2M03 offers a bi-directional digital audio interface that routes
directly into the baseband layer of the on-chip firmware. It does not pass through the HCI protocol layer.
Hardware on F2M03 allows the data to be sent to and received from a SCO connection. Up to three SCO
connections can be supported by the PCM interface at any one time(1)
F2M03 can operate as the PCM interface Master generating an output clock of 128, 256 or 512kHz. When
configured as PCM interface slave it can operate with an input clock up to 2048kHz. F2M03 is compatible
with a variety of clock formats, including Long Frame Sync, Short Frame Sync and GCI timing environments.
It supports 13 or 16-bit linear, 8-bit µ-law or A-law companded sample formats at 8ksamples/s and can
receive and transmit on any selection of three of the first four slots following PCM_SYNC. The PCM
configuration options are enabled by firmware settings (contact Free2move).
Qualcomm MSM 3000 series and MSM 5000 series CDMA baseband devices
• OKI MSM7705 four channel A-law and µ-law CODEC
• Motorola MC145481 8-bit A-law and µ-law CODEC
• Motorola MC145483 13-bit linear CODEC
• Winbond W681360R 13-bit linear CODEC
• STW 5093 and 5094 14-bit linear CODECs
• F2M03 is also compatible with the Motorola SSITM interface
When configured as the Slave of the PCM interface, F2M03 accepts PCM_CLK rates up to 2048kHz
F2M03 samples PCM_IN on the falling edge of PCM_CLK and transmits PCM_OUT on the rising edge.
PCM_OUT may be configured to be high impedance on the falling edge of PCM_CLK in the LSB position or on
the rising edge.
As with Long Frame Sync, F2M03 samples PCM_IN on the falling edge of PCM_CLK and transmits PCM_OUT
on the rising edge. PCM_OUT may be configured to be high impedance on the falling edge of PCM_CLK in the
LSB position or on the rising edge
GCI Interface
The start of frame is indicated by PCM SYNC and runs at 8kHz. With F2M03 in Slave mode, the frequency of
PCMCLK can be up to PCM_SYNC In order to configure the PCM interface to work in GCI mode it is necessary
to have the correct firmware support (contact Free2move)
F2M03 supports 13-bit linear, 16-bit linear and 8-bit µ-law or A-law sample formats. The sample rate is
8ksamples/s. The bit order may be little or big endian. When 16-bit slots are used, the 3 or 8 unused bits in
each slot may be filled with sign extension, padded with zeros or a programmable 3-bit audio attenuation
compatible with some Motorola CODECs.
Note:
(1)
Assumes normal system clock operation. Figures will vary during low power modes, when system clock speeds are reduced.
(2)
Valid for temperatures between -40°C and +85°C
Note:
(1)
Valid for temperatures between -40°C and +105°C
6.6 PIOs
The F2M03GLA have 10 programmable general-purpose I/O ports PIO[11:2] and two analog I/O ports
AIO[1:0]. PIO lines can be configured through software to have either weak or strong pull-ups or pull-downs.
All PIO lines are configured as inputs with weak pull-downs at reset.
AIO[1:0] functions available via these pins include an 8-bit ADC but can also be used as general-purpose I/O
lines. Typically the AIO[0] is used for battery voltage measurement. The voltage range for AIO[1:0] is
constrained by the internal analogue supply voltage which is 1.8V.
Note:
The PIO and AIO lines are controlled by firmware specific settings. Please see specific firmware
datasheet for information about the PIOs used!
PIO[2]
Programmable I/O terminal.
PIO[3]
Programmable I/O terminal.
PIO[4]/ BT_Priority/Ch_Clk
Programmable input/output line or Optionally BT_Priority/Ch_Clk output for co-existence signaling
PIO[5]/BT_Active
Programmable input/output line or Optionally BT_Active output for co-existence signalling
PIO[6]/WLAN_Active/Ch_Data
Programmable input/output line or Optionally WLAN_Active/Ch_Data input for co-existence signalling
PIO[7]
Programmable I/O terminal.
PIO[8]
Programmable I/O terminal.
PIO[9]
Programmable I/O terminal.
PIO[10]
Programmable I/O terminal.
PIO[11]
Programmable I/O terminal.
AIO[0]
Programmable input/output line also possible to use as digital I/O
AIO[1]
Programmable input/output line also possible to use as digital I/O
The voltage supplied should have low noise, less than 10mV rms between 0 and 10MHz. The transient
response of the regulator is also important. At the start of a Bluetooth® packet, power consumption will
jump to high levels. The regulator should have a response time of 20µs or less; it is essential that the power
rail recovers quickly.
6.7.2 Reset
The F2M03GLA has an active low reset (pin nr: 30). The reset pin MUST be connected to either a reset-circuit
(voltage monitor) such as the TC1270ASVRCTR, MAX811S, DS1818 or using an I/O from a microcontroller.
Reset cannot be done with a R-C network. It is recommended to used one of the reset circuits mentioned
above. Special considerations must be taken when using an I/O from a microcontroller; a pull-down resistor
(1.8kΩ) must be placed on the I/O-line.
At reset the digital I/O pins are set to inputs for bi-directional pins and outputs are tristated. The PIOs have
weak pull-downs.
7 Application information
F2M03GLA
All dimensions are in [mm]
17 16
[TOP VIEW]
28.5
20.42
1.27
0.8
0.8
32 1
1.37
1.2
15.2
Solder pad
Recommended extended pad for manual soldering
Restricted area for ground planes or other components
The module uses bottom pads for soldering optimized for an automatic solder line. It is also possible to
solder the module manually by using hot air soldering. For manual soldering solder pads may in some
situation be made slightly larger to allow easier heating process.
To achieve good RF performance it is recommended to place ground plane(s) beneath the module but not
under the antenna. The ground planes should be connected with vias surrounding the module. Except from
the ground plane it is preferable that there are as few components and other material as possible nearby the
antenna. Free air is the best surrounding for the antenna.
All GND pads must be connected directly to a flooded ground-plane. If more then one ground layer is used
then make a good connection between them using many via holes. +VCC should be connected to the voltage
regulator using a wide trace.
Antenna
Vias
Ground layers
F2M03GLA
Typical application schematic for F2M03GLA when using the Wireless UART firmware
8 Package information
F2M03GLA
Weight: 1.2g
9 Certifications
9.1 Bluetooth®
F2M03GLA has passed the Bluetooth® Qualification/Certification process as specified within the Bluetooth®
Specifications and as required within the PRD 2.0.
QDID: B012541
9.2 CE
F2M03GLA complies with the requirements of R&TTE Directive 1999/5/CE, the European Community
Directive 73/23/EEC and 93/68/EEC.
• EN 300 328
• EN 301 489-1/-17
• EN 60950
9.3 FCC
FCC-B Radio Frequency Interference Statement
This deceive 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 when the equipment is operated in commercial environment. This equipment generates, uses
and can radiate radio frequency energy and, if not installed and used according with the instruction manual,
may cause harmful interference to radio communication. Operation of this equipment in a residential area is
likely to cause harmful interference, in which case the user will be required to correct the interference at his
own expense.
Notice1
The changes or modifications not expressly approved by the party responsible for the compliance could void
the user’s authority to operate the equipment.
Notice 2
Shielded interface cables an A.C. power cord, if any, must be used in order to comply with the emission
limits.
Notice 3
This modular transmitter uses an electronic display of the FCC identification number, the information must
be readily accessible on the device in which it is installed.
The FCC ID can be read from the UART of the device.
FCC ID R47F2M03GL
If the module is installed inside another device, then the outside of the device into which
the module is installed must display a label referring to the enclosed module. This exterior
label can use wording such as the following: “Contains FCC certified transmitter
module(s).”
Any similar wording that expresses the same meaning may be used.
9.4 IC
This device complies with RSS-210 of the Industry Canada Rules. 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.
IMPORTANT NOTE:
Radiation Exposure Statement:
This equipment complies with IC radiation exposure limits set forth for an uncontrolled environment.
End users must follow the specific operating instructions for satisfying RF exposure compliance.
To maintain compliance with IC RF exposure compliance requirements, please follow operation instruction
as documented in this manual.
This device has been designed to operate with an antenna having a maximum gain of 2 dBi.
Antenna having a higher gain is strictly prohibited per regulations of Industry Canada. The required antenna
impedance is 50 ohms.
10 RoHS Statement
F2M03GLA meet the requirements of Directive 2002/95/EC of the European Parliament and of the Council on
the Restriction of Hazardous Substance (RoHS). The module is assembled solely using RoHS compliant
components.
11 REACH Statement
F2M03GLA meets the requirements of Substances of Very Hiqh Concern (SVHC) in accordance with list
published by European Chemicals Agency (ECHA) on 2008 October 28, regarding Regulation (EC) No
1907/2006, by showing a concentration of all SVHC compounds < 0.1%.
Pulling direction
A 330.0 max
B 1.5 min
C 13.0±0.2
W2
D 20.2 min
N 100.0
W1 44.4 +2.0 –0.0 W1
W2 50.4 max
D C
A N
13 Ordering information
Please use our website: www.free2move.se for more information about local distributors and dealers.
TTT
14 Document history
F2M03GLA
Datasheet
Datasheet_F2M03GLA_rev_e.pdf
Contact information
For support questions please contact your local dealer
For other purposes use: [email protected]
Website: www.free2move.se
Local dealer/distributor
The information given herein includes text, drawings, illustrations and schematics that are believed to be reliable. However, Free2move
makes no warranties as to its accuracy or completeness and disclaims any liability in connection with its use. Free2move will in no case
be liable for any incidental, indirect or consequential damages arising out of sale, resale, use or misuse of the product. Users of
Free2move products should make their own evaluation to determine the suitability of each such product for the specific application.