Rev: 13 September 2005 Class 2 Bluetooth™ Module - F2M03C2 Datasheet Features • Available with complete Bluetooth software stack • Wireless UART functionality without extra protocol. • Headset functionality available. • Serial interface, 8 digital and 2 analog I/O • PCM interface for up to 3 simultaneous voice channels • Nominal 20m range • Transmit power up to +4dBm (Bluetooth Class2) • 4 low power modes • Piconet and Scatternet capability, support for up to seven slaves • Physical size: 25x14 mm • Surface mountable • Bluetooth v1.1 compliant Applications General Description Prototyping and volume production of: This module is a Class 2 surface mountable Bluetooth system (in an automatic mounting line or manually for prototyping). It provides a fully compliant device for data and voice communications. The interfaces to a host (UART and USB) supports full Bluetooth data rate of 723.2kbps. A 13-bit PCM, 8ksamples/s, synchronous bidirectional audio interface is available. Digital and analog I/O and I2C interface are supported by the module. • Industrial and Domestic Appliances • Stand alone sensors • Embedded systems • Cordless Headsets • Computer peripherals (Mice, Keyboards, USB dongles etc) • Handheld, Laptop and Desktop computers • Mobile Phones The module is available with a number of different firmware versions: The Wireless UART firmware is an embedded single processor solution that implements the Serial Port Profile (SPP). All data flows transparent through the serial port to the remote device. Using high level commands the user can configure the Bluetooth connection. Other firmware versions are: Headset, HCI, RFCOMM and the possibility to get customized standalone applications implemented as an on chip solution. BLUETOOTH is a trademark owned by Bluetooth SIG, Inc., U.S.A. and licensed to Free2move © 2004 Free2move AB Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 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 5.2 5.3 5.4 5.5 6 Wireless UART ............................................................................................................................. 11 Onboard application...................................................................................................................... 16 Headset......................................................................................................................................... 17 HCI ................................................................................................................................................ 19 RFCOMM Stack............................................................................................................................ 21 Device terminal description ................................................................................................23 6.1 6.2 6.3 6.4 6.5 6.6 UART Interface ............................................................................................................................. 23 USB Interface................................................................................................................................ 25 Serial Peripheral Interface ............................................................................................................ 29 PCM .............................................................................................................................................. 30 PIO ................................................................................................................................................ 37 Power Supplies ............................................................................................................................. 38 7 Application information.......................................................................................................39 8 Package information............................................................................................................41 9 Tape information..................................................................................................................42 10 Ordering information ...........................................................................................................43 11 Document References .........................................................................................................44 12 Acronyms and definitions...................................................................................................45 © 2003 Free2move AB Page 2(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 1 Device pinout (Top view) 1 GND 34 GND RF NC GND GND AIO(0) PIO(0) AIO(1) PIO(1) RESET PIO(2) SPI_MISO PIO(3) SPI_CSB PIO(4) SPI_CLK PIO(5) SPI_MOSI PIO(6) UART_CTS UART_TX UART_RTS UART_RX 17 PIO(7) USB_DN USB_DP PCM_CLK 1V8 PCM_IN 3V3 PCM_SYNC GND PCM_OUT 18 © 2003 Free2move AB Page 3(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 2 Device terminal functions Ground GND Pin Pin type Description 1,3,17,32,34, VSS Power supplies 1.8 V VDD Pin 15 16 Analog I/O Ground connections Pin type DC 1.8V output (Must not be used) Positive voltage supply (2.7-3.3V) Pin Pin type AIO(0) 4 Bi-directional AIO(1) 5 Bi-directional Reset RESET Pin 6 Test and debug 7 SPI_CSB 8 SPI_CLK SPI_MOSI 9 10 UART UART_CTS UART_TX UART_RTS UART_RX PCM Pin type Pin type Description CMOS input with weak internal pull-down CMOS output CMOS output, tristatable with internal pull-up CMOS input with weak internal pull-down Pin type PCM_SYNC PCM_IN PCM_CLK 19 20 21 CMOS output, tristatable with internal weak pull down Bi-directional with weak internal pull-down CMOS input, with weak internal pull-down Bi-directional with weak internal pull-down Pin PIO 24 PIO(6)/CLK_REQ 25 PIO(5)/USB_DETACH 26 PIO(4)/USB_ON 27 PIO(3)/USB_WAKE_UP/ RAM_CSB 28 PIO(2)/USB_PULL_UP 29 PIO(1) PIO(0) 30 31 Radio RF Not connected NC Synchronous data SYNC Synchronous data input Synchronous data clock Description Pin type programmable Description weak Programmable input/output line weak PIO line or clock request output to enable external clock for external clock line programmable weak PIO line or chip detaches from USB when this input is high programmable weak PIO or USB on (input senses when high, wakes Bluetooth chip) programmable weak PIO or output goes high to wake up PC when in USB mode or external RAM chip select Bi-directional with programmable weak PIO or USB pull-up (via 1.5 kΩ resistor to internal pull-up/down USB_D+) Bi-directional with weak internal pull-up/down Programmable input/output line Bi-directional with weak internal pull-up/down Programmable input/output line programmable Pin type Description Antenna 50 Ω Bi-directional Pin 2 Description Synchronous data output USB data plus USB data minus Bi-directional with internal pull-up/down Bi-directional with internal pull-up/down Bi-directional with internal pull-up/down Bi-directional with internal pull-up/down Bi-directional with internal pull-up/down Pin 33 UART clear to send active low UART data output active high UART request to send active low UART data input active high Pin type Bi-directional Bi-directional Pin PIO(7) also Description 18 22 23 line Reset if high. Input debounced so must be high for >5ms to cause a reset Pin type Pin USB also Description PCM_OUT USB_DP USB_DN line CMOS output, tristatable with weak internal Serial Peripheral Interface data output pull-down CMOS input with weak internal pull-up Chip select for Synchronous Serial Interface, active low CMOS input with weak internal pull-down Serial Peripheral Interface clock CMOS input with weak internal pull-down Serial Peripheral Interface data input Pin 11 12 13 14 Description Programmable input/output possible to use as digital I/O Programmable input/output possible to use as digital I/O CMOS input with internal pull-down (10kΩ) Pin SPI_MISO Description Output VDD Pin type Not connected Description Included for compatibility with F2M03C1 © 2003 Free2move AB Page 4(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 3 Electrical Characteristics Absolute Maximum Ratings Rating Storage Temperature Breakdown supply voltage Min Max -40°C -0.40V +150°C 3.60V Recommended Operating Conditions Rating Min Max Operating temperature range Supply voltage +85°C 3.5V -40°C 2,7 Input/Output Terminal Characteristics Digital Terminals Min Typ Max Unit -0.4 -0.4 0.7VDD - +0.8 +0.4 VDD+0.4 V V V VDD-0.2 - 0.2 - V V -100 +10 -5 0 -1 2,5 -20 +20 -1 +1 0 - -10 +100 0 +5 +1 10 µA µA µA µA µA pF Min Typ Max Unit 0,7VDD - 0,3VDD - V V 2.5 - 10 pF 0 2.8 - 0.2 VDD V V Input Voltage VIL input logic level low (VDD=3.0V) (VDD=3.3V) VIH input logic level high Output Voltage VOL output logic level low, (lO = 4.0mA), VDD=3.0V VOH output logic level high, (lO = 4.0mA), VDD=3.0V Input and tristate current Strong pull-up Strong pull-down Weak pull-up Weak pull-down I/O pad leakage current CI Input Capacitance 2.5 USB Terminals Input threshold VIL input logic level low VIH input logic level high Input leakage current CI Input capacitance Output levels to correctly terminated USB Cable VOL output logic level low VOH output logic level high Notes: Current drawn into a pin is defined as positive; current supplied out of a pin is defined as negative. © 2003 Free2move AB Page 5(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet Input/Output Terminal Characteristics (Continued) Auxiliary DAC, 8-bit resolution Resolution Average output step size (1) Min Typ Max Unit 12.5 14.5 8 17 Bits mV VDD +0.1 0.2 VDD +1 V mA V V µA +120 +2 10 5 mV LSB µS µS Output Voltage Voltage range (IO=0) Current range Minimum output voltage (IO=100µΑ) Maximum output voltage (IO=10mA) High Impedance leakage current GND -10 0 VDD-0.3 -1 Offset (1) Integral non-linearity Starting time (50pF load) Settling time (50pF load) -220 -2 - monotonic - (1) Notes: Current drawn into a pin is defined as positive, current supplied out of a pin is defined as negative. (1) Specified for an output voltage between 0.2V and VDD -0.2V Average current consumption VDD = 3.3V Temperature = 20 oC Measured using Wireless UART firmware. Slave: Mode Average (mA) No connection (default settings) 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 slave to master Sniff mode 125 ms interval Connected, (Short range) 115.2 kbit/s slave to master Sniff mode 125 ms interval 2.6 2,0 30 3,8 1,8 24 22 Master: Mode Average (mA) No connection (default settings) 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 52 5,3 2,8 2,9 23 25 31 17 © 2003 Free2move AB Page 6(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet Peak current consumption VDD = 3.3V Temperature = 20 oC Mode Peak consumption during RF peaks Deep sleep leakage current VDD = 3.3V Temperature = 20 oC Mode Deep sleep Typ Unit 67 mA Typ Unit 68 µA © 2003 Free2move AB Page 7(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 4 Radio Characteristics VDD = 3.0V Temperature = 23 oC Frequency = 2441 MHz All measurements are based on the Bluetooth test specification. Receiver Sensitivity at 0.1% BER Maximum RF transmit power Initial carrier frequency tolerance RF power control range Min Typ Max Bluetooth Specification Unit -10 - -85 3 ±5 24 4 10 - ≤-70 (1) 0 to 4 ±75 ≥16 dBm dBm kHz dB Notes: (1) Class 2 RF transmit power range, Bluetooth specification v1.1 © 2003 Free2move AB Page 8(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 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 v1.1. 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. Application Host Host F2M03 F2M03 Wireless UART application (SPP) APPLICATION INTERFACE RFCOMM APPLICATION INTERFACE SDP RFCOMM Device Manager L2CAP Hardware Application SDP Device Manager L2CAP HCI HCI LINK MANAGER LINK MANAGER BASEBAND and RF Hardware Wireless UART BASEBAND and RF Embedded singleprocessor architecture © 2003 Free2move AB Page 9(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet Application Port Entity Application Host Bluetooth stack Host HCI F2M03 RFCOMM SDP Device Manager L2CAP F2M03 HCI HCI LINK MANAGER LINK MANAGER BASEBAND and RF BASEBAND and RF HCI, (Two-Processor Architecture) RFCOMM, (Embedded Two-Processor Architecture) Wireless UART Free2move’s Wireless UART (WU) firmware is intended to replace the 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 offers the following single chip solutions: • Headset • Human Interface Device (Mouse, keyboard etc) • Onboard application (development of customer specific applications) 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 usable for different versions of Microsoft Windows. RFCOMM (Embedded Two-Processor Solution) The embedded two-processor category is a feature of the F2M03 module. This allows products to be designed that incorporate Bluetooth, where the host is resource limited and cannot support the addition of the Bluetooth functionality. © 2003 Free2move AB Page 10(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 5.1 Wireless UART 5.1.1 General Information Free2move’s Wireless UART (WU) firmware is intended to replace the 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. Application Host F2M03 Wireless UART (SPP) INTERFACE RFCOMM SDP Device Manager L2CAP HCI LINK MANAGER Hardware BASEBAND and RF Wireless UART architecture The WU application runs on top of an embedded Bluetooth v1.1 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 of one unit or participate in a piconet as a slave. The WU firmware offers one asynchronous data channel and one synchronous voice channel, both channels capable of full duplex transmission. 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 commands (described in detail in the separate Wireless UART datasheet) sent on the data interface. © 2003 Free2move AB Page 11(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 5.1.2 General I/O General I/O interfaces are used for different purposes between the WU firmware and the Host: • Asynchronous data interface – configuration of the WU firmware or exchange transparent digital information between the connected Bluetooth devices. • Synchronous voice interface – exchange transparent voice information between the connected Bluetooth devices. • Bluetooth connectivity PIO interfaces – indication and disconnection of the established Bluetooth connection. • Emulate serial handshaking PIO lines interface – DTE or DCE serial handshake emulation between the connected Bluetooth devices. UART interface (Asynchronous data and configuration): Signal Direction Output Input Output Input UART TX RX RTS CTS Active (TTL) High High Low Low Description UART transmit data UART receive data UART request to send UART clear to send Voice interface: CODEC I/O MIC_P MIC_N AUX_DAC SPKR_P SPKR_N Signal Direction Input (analogue) Input (analogue) Output (analogue) Output (analogue) Output (analogue) Description Microphone input positive Microphone input negative Microphone input bias Speaker output positive Speaker output negative PIO are used to control/monitor the Bluetooth connectivity of the WU firmware. PIO Signal Direction Active (TTL) 2 Input High 3 Output High Description Request to close the current Bluetooth connection to the remote device. Indicates that a successful Bluetooth connection is established with a 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. PIO can also be used to emulate serial handshaking lines between the connected Bluetooth devices (F2M03 only). Emulation can either be DTE or DCE Emulated Signal PIO RI DTR DCD DSR 4 5 6 7 Signal Direction Emulate DTE Input Output Input Input Signal Direction Emulate DCE Output Input Output Output Active (TTL) High High High High While the handshaking lines are transparent to the data channel these I/O may also be used to transfer digital signals between to Free2move devices running WU © 2003 Free2move AB Page 12(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 5.1.3 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 Baud rate Data bits Parity Stop bits Hardware flow control Default Value 38400 8 None 1 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). © 2003 Free2move AB Page 13(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 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 (sniff/park), fine tune performance, enabling modem emulation and changing transmit power. SCO commands Makes it possible to establish full duplex voice connections between two WU units. © 2003 Free2move AB Page 14(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 5.1.4 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 v3.00 devices at close range. 57600 57600 57600 Maximum Throughput (kbit/s (throughput mode)) ~57.6 ~57.6 ~57.6 Maximum Throughput (kbit/s) (latency mode) ~57.6 ~57.6 ~50.5 Master to Slave Slave to Master Full duplex 115200 115200 115200 ~115.1 ~115.1 ~114.5 ~93.9 ~79.6 ~42.0 Master to Slave Slave to Master Full duplex 230400 230400 230400 ~223.1 ~221.4 ~172.7 ~158.0 ~117.7 ~86.2 Master to Slave Slave to Master Full duplex 460800 460800 460800 ~228.6 ~222.7 ~173.3 ~206.7 ~154.1 ~109.8 Master to Slave Slave to Master Full duplex 921600 921600 921600 ~240.1 ~235.4 ~174.7 ~235.7 ~186.0 ~150.5 Direction Baud Rate Master to Slave Slave to Master Full duplex 5.1.5 Configuration software When purchasing the Free2move Bluetooth evaluation kit, a Windows application than can be used to configure your Wireless UART modules is included. © 2003 Free2move AB Page 15(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 5.2 Onboard application When using the onboard application firmware option no external host processor is needed. All software layers, including application software, run on the internal RISC processor. The application runs in a protected user software execution environment known as a Virtual Machine (VM). Host F2M03 Application APPLICATION INTERFACE RFCOMM SDP Device Manager L2CAP HCI LINK MANAGER Hardware BASEBAND and RF Embedded SingleProcessor Architecture Free2move provides the service to implement he user specified functionality on the Bluetooth module. The application software will execute together with the Bluetooth stack firmware on-chip. The application is able to make calls to the firmware for various operations. The execution environment is structured so the user application does not adversely affect the stack software routines, thus ensuring that the Bluetooth stack software component does not need re-qualification when the application is changed. Using the VM and the user is able to get specific applications such as a cordless headset or other profiles without the requirement of a host controller. © 2003 Free2move AB Page 16(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 5.3 Headset Headset functionality is one implementation of the onboard application possibility. The Free2move headset firmware is available in a standard version, which is implemented to be adaptable to fit your specific requirements and needs. Adaptations may include the user interface as buttons and LEDs, but also more advanced functionality changes. The headset firmware provides the functionality required as stated in Bluetooth Profiles Specification, volume 2, v1.1, 22 February 2001, Part K6 for a Bluetooth headset. It provides the headset part of that functionality. Host F2M03 Headset application (HP) APPLICATION INTERFACE RFCOMM SDP Device Manager L2CAP HCI LINK MANAGER Hardware BASEBAND and RF Embedded SingleProcessor Architecture Additional Functionality to Headset Profile The firmware extends the standard headset functionality with the following features: • Remote audio volume control (listed as optional in the profile) • Park mode supported (listed as optional in the profile) • Sniff mode supported (not listed in the profile) • Muting of microphone under headset control (not listed in the profile) • Playing of arbitrary tones (not listed in the profile) Headset Buttons Three buttons are used by the standard Headset firmware implementation: PIO 4 5 7 Signal Direction Input Input Input Active (TTL) High High High Description Talk button (Answer and initiate calls) Volume down Volume up © 2003 Free2move AB Page 17(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet LED PIO 2 3 Signal Direction Output Output Active (TTL) High High Description Used for indicate connection state Used for indicate paring mode Other I/O PIO 6 TBD Signal Direction Input Output Active (TTL) High High Description ON/OFF (The headset to goes into deep sleep) CODEC, Is driven high to enable the codec and low to power it down (Not needed in F2M03AC2, may instead be used to bias the microphone) © 2003 Free2move AB Page 18(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 5.4 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. Application Bluetooth stack HCI Host HCI F2M03 LINK MANAGER BASEBAND and RF Standard Two-Processor Architecture 5.4.1 Standard Bluetooth Functionality The firmware has been written against the Bluetooth Core Specification v1.1. • 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, up to 723.2 kb/s asymmetric(1) • Operation with up to seven active slaves(1) • Operation with up to three SCO links, routed to one or more slaves • 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 codings, 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 specification v1.1. F2M03 supports all combinations of active ACL and SCO channels for both Master and Slave operation, as specified by the Bluetooth specification v1.1. (2) © 2003 Free2move AB Page 19(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 5.4.2 Extra Functionality The firmware extends the standard Bluetooth functionality with the following features: • Supports BlueCore Serial Protocol (BCSP) - a proprietary, reliable alternative to the standard Bluetooth (H4) UART Host Transport. • Provides a set of approximately 50 manufacturer-specific HCI extension commands. This command set (called BCCMD – “BlueCore Command”) provides: o Access to the module’s general-purpose PIO port o Access to the module’s Bluetooth clock - this can help transfer connections to other Bluetooth devices. o The negotiated effective encryption key length on established Bluetooth links o Access to the firmware’s random number generator o Controls to set the default and maximum transmit powers - these can help to reduce interference between overlapping, fixed-location piconets o Dynamic UART configuration o Radio transmitter enable/disable - a simple command connects to a dedicated hardware switch that determines whether the radio can transmit. • The firmware can read the voltage on a pair of the module’s external pins (normally used to build a battery monitor, using either VM or host code). • A block of BCCMD commands provides access to the module’s Persistent Store (PS) configuration database. 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: o Presenting a UART break condition to the module can force the module to perform a hardware reboot. o Presenting a break condition at boot time can hold the module in a low power state, preventing normal initialisation while the condition exists. o With BCSP, the firmware can be configured to send a break to the host before sending data - normally used to wake the host from a Deep Sleep state. • 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 module’s UART. • A block of “radio test” or Built-In Self-Test (BIST) commands allows direct control of the module’s radio. This aids the development of modules’ radio designs and can be used to support Bluetooth qualification. • Virtual Machine (VM). The VM allow development of customer applications on the module. Although the VM is mainly used with “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 module’s PIO port. • Hardware low power modes: Shallow Sleep and Deep Sleep. The module drops into modes that significantly reduce power consumption when the software goes idle. • 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). © 2003 Free2move AB Page 20(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 5.5 RFCOMM Stack In this firmware version the upper layers of the Bluetooth stack up to RFCOMM are run onboard the module. This reduces host-side software and hardware requirements at the expense of some of the power and flexibility of the HCI only stack. Application Port Entity Host F2M03 RFCOMM SDP Device Manager L2CAP HCI LINK MANAGER BASEBAND and RF Embedded Two-Processor Architecture The RFCOMM firmware exposes APIs (application programming interface) to L2CAP, Service Discovery Protocol (SDP), RFCOMM and Device Manager (DM) functionality. Background information on Bluetooth and its upper layers can be found in the Bluetooth specification v1.1. The firmware also contains a Virtual Machine (VM), which may be used to develop customer applications on the module. Two variants of this firmware are provided; one supports the BlueCore Serial Protocol (BCSP) transport protocol and the other supports the Bluetooth UART (Universal Asynchronous Receiver Transmitter) H4 protocol. Note: RFCOMM firmware does not expose the Host Controller Interface (HCI) and is, therefore, not suitable for use with third party stacks. 5.5.1 Key Features of the RFCOMM Stack Interfaces to Host • RFCOMM, an RS-232 serial cable emulation protocol • SDP, a service database look-up protocol Connectivity • Maximum number of active slaves: 3 • Maximum number of simultaneous active ACL connections: 3 • Maximum number of simultaneous active SCO connections: 3 • Data Rate: up to 350 Kb/s Security • Full support for all Bluetooth security features up to and including strong (128-bit) encryption. Power Saving • Full support for all Bluetooth power saving modes (Park, Sniff and Hold). © 2003 Free2move AB Page 21(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet Data Integrity • Channel quality driven data rate (CQDDR) increases the effective data rate in noisy environments. • Received signal strength indication (RSSI) used to minimise interference to other radio devices using the ISM band. © 2003 Free2move AB Page 22(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 6 Device terminal description 6.1 UART Interface The F2M03 Bluetooth module’s Universal Asynchronous Receiver Transmitter (UART) interface provides a simple mechanism for communicating with other serial devices using the RS232 standard(1). Universal Asynchronous Receiver 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) Parameter Baud Rate Minimum Maximum Possible Values 1200 Baud (≤2%Error) 9600 Baud (≤1%Error) 1.5MBaud (≤1%Error) Flow Control RTS/CTS or None Parity None, Odd or Even Number of Stop Bits 1 or 2 Bits per channel 8 Possible UART Settings © 2003 Free2move AB Page 23(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 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. This is subject to firmware support, contact Free2move for more information. Break signal © 2003 Free2move AB Page 24(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 6.2 USB Interface F2M03 USB devices contain a full-speed (12Mbits/s) USB interface, capable of driving a USB cable directly. No external USB transceiver is required. The device operates as a USB peripheral, responding to requests from a master host controller such as a PC. Both the OHCI and the UHCI standards are supported. The set of USB endpoints implemented behave as specified in the USB section of the Bluetooth specification v1.1, part H2. As USB is a master-slave orientated system, F2M03 only supports USB slave operation. 6.2.1 USB Data Connections The USB data lines emerge as pins USB_DP (USB_D+) and USB_DN (USB_D-) on the package. To match the connection to the characteristic impedance of the USB cable series resistors are connected internally of the F2M03C2. No external resistors are needed for either USB_D+ or USB_D- (valid for F2M03C2 only). 6.2.2 USB Pull-up Resistor F2M03 features an internal USB pull-up resistor. This pulls the USB_DP pin weakly high when F2M03 is ready to enumerate. It signals to the PC that it is a full-speed (12Mbit/s) USB device. 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 thevenin resistance to the host of at least 900 ohms. Alternatively, an external 1.5kO pull-up resistor can be placed between a PIO line and DP on the USB cable. The firmware must be alerted to which mode is used (contact Free2move). The default setting uses the internal pull-up resistor. 6.2.3 Power Supply The minimum output high voltage for USB data lines is 2.8V. To safely meet the USB specification, the voltage on terminals must be an absolute minimum of 3.1V. Free2move recommends 3.3V for optimal USB signal quality. 6.2.4 Self-Powered Mode In self-powered mode, the circuit is powered from its own power supply and not from the VBUS (5V) line of the USB cable. It draws only a small leakage current (below 0.5mA) from VBUS on the USB cable. This is the easier mode for which to design for, as the design is not limited by the power that can be drawn from the USB hub or root port. However, it requires that VBUS be connected to F2M03 via a resistor network (Rvb1 and Rvb2), so F2M03 can detect when VBUS is powered up. F2M03 will not pull USB_D+ high when VBUS is off. Connections to F2M03 for Self-Powered Mode © 2003 Free2move AB Page 25(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet The terminal marked USB_ON can be any free PIO pin. The PIO pin selected must be registered by settings in firmware (contact Free2move) to the corresponding pin number. 6.2.5 Bus-Powered Mode In bus-powered mode the application circuit draws its current from the 5V VBUS supply on the USB cable. F2M03 negotiates with the PC during the USB enumeration stage about power consumption. 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. As well as regulation down to 3.3V and 1.8V, applications should include careful filtering of the 5V line to attenuate noise that is above the voltage regulator’s bandwidth. Excessive noise on the 1.8V supply to the supply pins of F2M03 may result in reduced receive sensitivity and a distorted transmit signal. Connections to F2M03 for Bus-Powered Mode USB Interface Component Values Identifier Value Function Rvb1 47kΩ -5% VBUS ON sense divider Rvb2 22kΩ - 5% VBUS ON sense divider Note: USB_ON is shared with F2M03’s PIO terminals. © 2003 Free2move AB Page 26(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 6.2.6 Suspend Current USB devices that run off VBUS must be able to enter a suspended state, whereby they consume less that 0.5mA from VBUS. The voltage regulator circuit itself should draw only a small quiescent current (typically less than 100µA) to ensure adherence to the suspend-current requirement of the USB specification. This is not normally a problem with modern regulators. Ensure that external LEDs can be turned off by F2M03. The entire circuit must be able to enter the suspend mode. 6.2.7 Detach and Wake_Up Signalling F2M03 can provide out-of-band signalling to a host controller by using the dedicated control lines called ‘USB_DETACH’ and ‘USB_WAKE_UP’. These are outside the USB specification (no wires exist for them inside the USB cable), but can be useful when embedding F2M03 into a circuit where no external USB is visible to the user. Both control lines are shared with PIO pins and can be assigned to any PIO pin by firmware settings (contact Free2move) USB_DETACH, is an input which, when asserted high, causes F2M03 to put USB_D- and USB_D+ in a high-impedance state and to 1.5kO pull-up resistor on USB_D+. 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. USB_DETACH and USB_WAKE_UP Signal 6.2.8 USB Driver A USB Bluetooth device driver is required to provide a software interface between F2M03 and Bluetooth applications running on the host. © 2003 Free2move AB Page 27(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 6.2.9 USB 1.1 Compliance The Bluetooth chip on the F2M03 is qualified to the USB specification v1.1, details of which are available from http://www.usb.org. The specification contains valuable information on aspects such as PCB track impedance, supply inrush current and product labelling. Although F2M03’s Bluetooth chip 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, with particular attention being given to Chapter 7. 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_DP and USB_DN adhere to the USB specification 1.1 (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. 6.2.10 2.0 Compatibility F2M03 is compatable with USB specification 2.0 masters; under these circumstances the two ends agree the mutually acceptable rate of 12Mbits/s according to the USB 2.0 specification. © 2003 Free2move AB Page 28(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 6.3 Serial Peripheral Interface F2M03 is a slave device that uses terminals SPI_MOSI, SPI_MISO, SPI_CLK and SPI_CSB. This interface is used for program emulation/debug and IC test. It is also the means by which the F2M03 flash may be programmed, before any 'boot' program is loaded. 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 by Free2move. © 2003 Free2move AB Page 29(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 6.4 PCM Pulse Code Modulation (PCM) is the standard method used to digitise human voice patterns 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 p-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). F2M03 interfaces directly to PCM audio devices includes the following: Qualcomm MSM 3000 series and MSM 5000 series CDMA baseband devices OKI MSM7705 four channel A-law and p-law CODEC Motorola MC145481 8-bit A-law and µ-law CODEC Motorola MC145483 13-bit linear CODEC F2M03 is also compatible with the Motorola SSITM interface Note: (1) Subject to firmware support, contact Free2move for current status. © 2003 Free2move AB Page 30(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 6.4.1 PCM Interface Master/Slave When configured as the Master of the PCM interface, F2M03 generates PCM_CLK and PCM_SYNC. F2M03 as PCM Interface Master When configured as the Slave of the PCM interface, F2M03 accepts PCM_CLK rates up to 2048kHz F2M03 as PCM Interface Master © 2003 Free2move AB Page 31(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 6.4.2 Long Frame Sync Long Frame Sync is the name given to a clocking format that controls the transfer of PCM data words or samples. In Long Frame Sync, the rising edge of PCM_SYNC indicates the start of the PCM word. When F2M03 is configured as PCM Master, generating PCM_SYNC and PCM_CLK, then PCM_SYNC is 8-bits long. When F2M03 is configured as PCM Slave, PCM_SYNC may be from two consecutive falling edges of PCM_CLK to half the PCM_SYNC rate (i.e., 62.5µs) long. Long Frame Sync (Shown with 8-bit Companded Sample) 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. 6.4.3 Short Frame Sync In Short Frame Sync the falling edge of PCM_SYNC indicates the start of the PCM word. PCM_SYNC is always one clock cycle long. Short Frame Sync (Shown with 16-bit Sample) 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 © 2003 Free2move AB Page 32(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 6.4.4 Multi-Slot Operation More than one SCO connection over the PCM interface is supported using multiple slots. Up to three SCO connections can be carried over any of the first four slots. Multi-slot Operation with Two Slots and 8-bit Companded Samples 6.4.5 GCI Interface F2M03 is compatible with the General Circuit Interface, a standard synchronous 2B+D ISDN timing interface. The two 64Kbps B channels can be accessed when this mode is configured. In the GCI interface two clock cycles are required for each bit of the voice sample. The voice sample format is 8-bit companded. As for the standard PCM interface up to 3 SCO connections can be carried over the first four slots. 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) © 2003 Free2move AB Page 33(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 6.4.6 Slots and Sample Formats F2M03 can receive and transmit on any selection of the first four slots following each sync pulse. Slot durations can be either 8 or 16 clock cycles. Durations of 8 clock cycles may only be used with 8-bit sample formats. Durations of 16 clocks may be used with 8, 13 or 16-bit sample formats. F2M03 supports 13-bit linear, 16-bit linear and 8-bit p-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. 6.4.7 Additional Features F2M03 has a mute facility that forces PCM_OUT to be 0. In Master mode, PCM_SYNC may also be forced to 0 while keeping PCM_CLK running (which some CODECS use to control power-down) © 2003 Free2move AB Page 34(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 6.4.8 PCM Timing Information PCM Master Timing Symbol fmclk - Parameter PCMCLK frequency M in ( 1 ) Typ M a x (2) Unit - 128 256 512 - kHz 980 730 - 8 - - kHz ns ns 20 ns - - 20 ns - - 20 ns - - 20 ns tdmclksynch PCM_SYNC frequency PCM_CLK high PCM_CLK low Delay time from PCM_CLK high to PCM_SYNC high tdmclkpout Delay time from PCM_CLK high to valid PCM_OUT tdmclklsyncl Delay time from PCM_CLK low to PCM_SYNC low (Long Frame Sync only) tdmclkhsyncl Delay time from PCM_CLK high to PCM_SYNC low tdmclklpoutz Delay time from PCM_CLK low to PCMOUT high impedance - - 20 ns tdmclkhpoutz Delay time from PCM_CLK high to PCMOUT high impedance - - 20 ns tsupinclkl Set-up time for PCM_IN valid to PCM_CLK low 30 - - ns 30 - - ns - - 15 15 ns ns (1) tmclkh (1) tmclkl thpinclkl tr tf Hold time for PCM_CLK low to PCM_IN invalid Edge rise time (Cl = 50 pf, 10-90 %) Edge fall time (Cl = 50 pf, 10-90 %) 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 +105°C PCM Master Timing © 2003 Free2move AB Page 35(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet PCM Slave Timing Symbol Parameter Min (1) Typ Max ( 1 ) Unit fsclk PCM clock frequency (Slave mode: input) 64 - 2048 kHz fsclk PCM clock frequency (GCI mode) 128 - 4096 kHz tsclkl PCM_CLK low time 200 - - ns tsclkh PCM_CLK high time 200 - - ns thsclksynch Hold time from PCM_CLK low to PCM_SYNC high 30 - - ns tsusclksynch Set-up time for PCM_SYNC high to PCM_CLK low 30 - - ns tdpout Delay time from PCM_SYNC or PCM_CLK whichever is later, to valid PCM_OUT data (Long Frame Sync only) - - 20 ns tdsclkhpout Delay time from CLK high to PCM_OUT valid data - - 20 ns tdpoutz Delay time from PCM_SYNC or PCM_CLK low, whichever is later, to PCM_OUT data line high impedance - - 20 ns tsupinsclkl Set-up time for PCM_IN valid to CLK low 30 - - ns thpinsclkl Hold time for PCM_CLK low to PCM_IN invalid 30 - tr Edge rise time (Cl = 50 pF, 10-90 %) Tf Edge fall time (Cl = 50 pF, 10-90 %) - - ns 15 15 ns ns Note: (1) Valid for temperatures between -40°C and +105°C PCM slave timing © 2003 Free2move AB Page 36(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 6.5 PIO The Parallel Input Output (PIO) Port is a general-purpose I/O interface to F2M03. The port consists of eight programmable, bi-directional I/O lines, PIO[7:0]. Programmable I/O lines can be accessed either via an embedded application running on F2M03 or via private channel or manufacturer-specific HCI commands. PIO[0] Programmable I/O terminal (Not available for use at F2M03C1) PIO[1] Programmable I/O terminal (Not available for use at F2M03C1) PIO[2]/USB_PULL_UP (1) This is a multifunction terminal. The function depends on whether F2M03 is a USB or UART capable version. On UART versions, this terminal is a programmable I/O. On USB versions, it can drive a pull-up resistor on USB_D+. PIO[3]/USB_WAKE_UP (1) This is a multifunction terminal. On UART versions of F2M03 this terminal is a programmable I/O. On USB versions, its function is selected by firmware settings, either as a programmable I/O or as a USB_WAKE_UP function. PIO[4]/USB_ON (1) This is a multifunction terminal. On UART versions of F2M03 this terminal is a programmable I/O. On USB versions, the USB_ON function is also selectable (see USB Interface section 9.6). PIO[5]/USB_DETACH (1) This is a multifunction terminal. On UART versions of F2M03 this terminal is a programmable I/O. On USB versions, the USB_DETACH function is also selectable (see USB Interface section 9.6). PIO[6] Programmable I/O terminal. PIO[7] Programmable I/O terminal. Note: (1) USB functions can be software mapped to any PIO terminal (contact Free2move). © 2003 Free2move AB Page 37(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 6.6 Power Supplies VDD Power for the F2M03 GND Ground for F2M03 NC To guarantee correct operation, NC must not be connected externally. Free2move recommends that unconnected terminals be placed on unconnected pads to ensure mechanical robustness. RESET Free2move recommend the RESET to be connected to an external micro controller or reset circuit. It is recommended that RESET is applied for a period greater than 5ms. 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. © 2003 Free2move AB Page 38(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 7 Application information The module uses edge pads for soldering. This makes it possible to solder the module both on an automatic solder line as well as manually. Recommended pad layout is shown in figure below. (Top view) 2.4 25.0 1.27 1.0 2.28 1.0 14.5 Recommended pad layout © 2003 Free2move AB Page 39(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet A typical application schematic is shown in the figure below. The module must be provided with a clean power from a LDO with fast transient response. The XC6209B332 from TOREX is a good choice. All capacitors in the schematic are ceramic and must be mounted as close as possible to its respectively IC. The module must be start up with a reset. This can be done either with a reset-circuit such as the DS1817 from Dallas-semiconductor or using an I/O from a microcontroller. Reset cannot be done with a R-C network. Layout tips: 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. VDD should be connected to the LDO using a wide trace. The PCM signals should be routed with close proximity to a ground plane. For more details it is highly recommended to read the MC145483-datasheet from Motorola. The RF pin has an impedance of 50Ω. It is of most importance that the wire or stripe line (wave guide) to the antenna is correctly matched to 50Ω, for more details see application notes about antenna design from Free2move For more application information consult available application notes or contact Free2move. © 2003 Free2move AB Page 40(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 8 Package information (Top and side view) 25 1.92 17 14.5 13.7 34 18 1.27 0.8 1 2.1 2.28 1.27 0.75 Package information © 2003 Free2move AB Page 41(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 9 Tape information TAPE DETAILS All units in mm 3.2 24.0 4.0 1.5 37.5 26.0 44.0 15.0 Pulling direction Cover tape © 2003 Free2move AB Page 42(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 10 Ordering information The F2M03C2 is available for delivery in volumes. Part nr: Description F2M03C2 Class 2 module (Always use t three postfix with three signs for correct software) F2M03C2 001 Class 2 Bluetooth module with Wireless UART firmware (followed by three letters indicating version number e.g. F2M03C2-001-R1D) When not indicating version number e.g. R1D the latest available version will be delivered. For correct part numbers for your firmware contact Free2move. Please use our website: www.free2move.se for more information about local distributors and dealers. © 2003 Free2move AB Page 43(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 11 Document References Document References Version Specification of the Bluetooth system v1.1, 22 February 2001 Universal Serial Bus Specification v1.1, 23 September 1998 © 2003 Free2move AB Page 44(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 12 Acronyms and definitions Term: Bluetooth ACL AC A-law API BCSP BER C/I CMOS CODEC CPU CQDDR CTS CVSD DAC dBm DC DFU GCI HCI Host Host Controller HV ISDN ISM ksamples/s L2CAP LC LSB p-law MISO OHCI PA PCB PCM PIO RAM RF RFCOMM RISC RSSI RTS RX SCO SDP SIG SPI SPP TBD TX UART USB VM www Definition: A set of technologies providing audio and data transfer over short-range radio Asynchronous Connection-Less. A Bluetooth data packet. Alternating Current Audio encoding standard Application Programming Interface BlueCore™ Serial Protocol Bit Error Rate. Used to measure the quality of a link Carrier Over Interferer Complementary Metal Oxide Semiconductor Coder Decoder Central Processing Unit Channel Quality Driven Data Rate Clear to Send Continuous Variable Slope Delta Modulation Digital to Analogue Converter Decibels relative to 1mW Direct Current Device Firmware Upgrade General Circuit Interface. Standard synchronous 2B+D ISDN timing interface Host Controller Interface Application’s microcontroller Bluetooth integrated chip Header Value Integrated Services Digital Network Industrial, Scientific and Medical kilosamples per second Logical Link Control and Adaptation Protocol (protocol layer) Link Controller Least-Significant Bit Encoding standard Master In Serial Out Open Host Controller Interface Power Amplifier Printed Circuit Board Pulse Code Modulation. Refers to digital voice data Parallel Input Output Random Access Memory Radio Frequency Protocol layer providing serial port emulation over L2CAP Reduced Instruction Set Computer Receive Signal Strength Indication Ready To Send Receive or Receiver Synchronous Connection-Oriented. Voice oriented Bluetooth packet Service Discovery Protocol Special Interest Group Serial Peripheral Interface Serial Port Profile To Be Defined Transmit or Transmitter Universal Asynchronous Receiver Transmitter Universal Serial Bus or Upper Side Band (depending on context) Virtual Machine world wide web © 2003 Free2move AB Page 45(46) Rev: 13 September 2005 Class 2 Bluetooth module - F2M03C2 Datasheet 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. Trademarks, Patents and Licenses TM BlueCore , is a trademark of CSR Ltd. TM Bluetooth and the Bluetooth logos are trademarks owned by Bluetooth SIG Inc, USA and licensed to Free2move. Windows is a registered trademark of the Microsoft Corporation. TM I2C is a trademark of Philips Corporation. All other product, service and company names are trademarks, registered trademarks or service marks of their respective owners. © 2003 Free2move AB Page 46(46)