DVK-BTM411 Laird Technologies, DVK-BTM411 Datasheet
DVK-BTM411
Specifications of DVK-BTM411
Available stocks
Related parts for DVK-BTM411
DVK-BTM411 Summary of contents
Page 1
BTM410/411 DATA MODULE USER MANUAL Version 1.0 Innovative Technology for a Connected World ...
Page 2
... BTM410/411 Bluetooth AT Data Module ® REVISION REVISION HISTORY HISTORY Revision Version 1.0 www.lairdtech.com 2 Description 06/22/10 - Initial Release Version Laird Technologies ...
Page 3
... FCC Regulatory Statements .........55 BTM410 FCC and Industry Canada Statements ............................ 55 BTM411 FCC and Industry Canada Statements ............................ 55 Declarations of Compliance ........56 BTM410 EU Declaration of Conformity .................................... 56 BTM411 EU Declaration of Conformity .................................... 57 Mechanical Drawings ..................58 BTM410 Mechanical Details ............... 58 BTM411 Mechanical Details ............... 60 Development Kit Schematic ............... 63 Ordering Information ..................65 Product Part Numbers ........................ 65 General Comments ............................ 65 Laird Technologies ...
Page 4
... Future releases include support for the Bluetooth Health Device Profile, making this module the ideal choice for manufacturers who are developing Continua Health Alliance compliant devices. A comprehensive AT command interface is included, which simplifies firmware integration. Combined with a low cost developers kit, this ensures that the choice of Laird Technologies Bluetooth modules guarantees the fastest route to market. FEATURES AND BENEFITS • ...
Page 5
... PCM Clock available when in slave mode Bluetooth Stack V2.1 compliant. Fully integrated. GAP (Generic Access Profile) SDP (Service Discovery Profile) Profiles SPP (Serial Port Profile) HDP (Health Device Profile) – future release Firmware Upgrade Available over UART Connection Modes Point to point (cable replacement) Laird Technologies ...
Page 6
... Full Modular Approval (BTM411) CE & R&TTE Meets CE and R&TTE requirements Lead free Lead-free and RoHS compliant Warranty 12 Months Development board and software tools Development Kit DVK-BTM410 Dev Kit with BTM410 module fitted DVK-BTM411 Dev Kit with BTM411 module fitted Laird Technologies ...
Page 7
... VIO See note 2 VIO VIO See note 3 See note 3 See note 3 See note 3 See note 3 See note 3 See note 3 See note 3 See note 3 See note 3 See note 3 See note 3 See note 3 VIO VIO VIO VUSB VUSB VIO VIO VIO Laird Technologies ...
Page 8
... MIN TYP MAX 0.7VDD_USB -0.4 +0.8 -0.4 +0.4 VDD_USB – 0.4 0.4 VDD_USB – 0.2 0.2 MIN TYP MAX 0.7VDD_IO -0.4 +0.8 -0.4 +0.4 VDD_IO – 0.4 0.4 VDD_IO – 0.2 0.2 Laird Technologies ...
Page 9
... Just like telephony modems, Laird Technologies’ devices power unconnected state and will only respond via the serial interface. In this state the device will not even respond to Bluetooth Inquiries. Then, just like controlling a modem, the host can issue AT commands which map to various Bluetooth activities ...
Page 10
... Pulse Width Modulation : Sub Band Codec : Synchronous Connection Oriented Link (used for Audio) : Service Level Connection : Serial Port Profile : Serial Stream Oriented : Secure Simple Pairing : SUBUNIT INFO Command : S-Register No. xxx : Trusted Device List : Universal Asynchronous Receiver / Transmitter : UNIT INFO Command Laird Technologies ...
Page 11
... Bluetooth version Features Profiles BTM520 / BTM521 Chipset Bluetooth version Features Profiles 11 www.lairdtech.com CSR BC4-Ext 2.1 SSP, EIR, SCO (1), eSCO (1) SPP CSR BC5MM-Ext 2.1 SSP, EIR, SCO, eSCO SPP, A2DP, AVRCP,HSP,HFP,DUN(DT) CSR BC5MM-Ext 2.1 SSP, EIR, SCO, eSCO SPP, A2DP, AVRCP,HSP,HFP,DUN(DT) Laird Technologies ...
Page 12
... E.g. the value 1234 can also be entered as $4D2 A string delimited by double quotes. E.g. “Hello World”. The “ character MUST be supplied as delimiters character UUID number consisting of ASCII characters ‘0’ to ‘9’, ‘A’ to ‘F’ and ‘a’ to ‘f’. Laird Technologies ...
Page 13
... Bits 2-7: Bits 8-12: Bits 13-23: Laird Technologies devices do not map to any predefined Major Service Class or Major Device Class and so the default devclass as shipped is 001F00, which means no Major Service Class and “Unclassified” Major Device class. Other examples of device class codes are follows: ...
Page 14
... The setting remains valid until next reset or power cycle (unless not changed by any other AT command subsequently). For permanent discoverable/connectable settings, please refer to S Register 512. Response: <cr,lf>OK<cr,lf> 14 www.lairdtech.com {Set Friendly Name Temporarily} {Set Friendly Name Permanently} {Make Device Discoverable and Connectable } {Make Device Discoverable} {Make Device Connectable} Laird Technologies ...
Page 15
... AT+BTX may put the device into the correct idle mode. 15. ATIn {Information} This will return the information about the Laird Technologies device and its status. Please refer to Table 4.2 (Appendix) for a complete list of supported ATIn parameters. ...
Page 16
... Minimum power consumption, UART baud rate set to 38400 Minimum power consumption, UART baud rate set to 115200 Medium power consumption, UART baud rate set to 115200 Maximum power consumption, UART baud rate set to 115200 {Clear Non-volatile Memory} {Clear Non-volatile Memory} {Write S Registers to Non-volatile Memory} Laird Technologies ...
Page 17
... RSSI value on inquiry result 0 – do not display RSSI value on inquiry result; if any further bit is set, a comma is inserted as separator 1 – display eird on inquiry result 0 – do not display eird on inquiry result Table 3.2: Field Descriptions for S Register 330 RSSI FN COD ADR Laird Technologies ...
Page 18
... Bluetooth device address 2. device class code 3. friendly name 1. the Bluetooth device address 2. device class code 3. friendly name 4. rssi (receiver signal strength indicator) 1. the Bluetooth device address 2. device class code 3. friendly name 4. rssi (receiver signal strength indicator) 5. extended inquiry data Laird Technologies ...
Page 19
... No MITM protection • Encryption • No MITM protection • (No) Encryption (1) • Minimal user interaction • No MITM protection • No Encryption • Minimal user interaction Table 3.3: Security Levels Comment High security Medium Security Low Security Permitted only for service discovery Laird Technologies ...
Page 20
... Reject IO-Cap requests IO-capability requests prior to SSP are rejected. Table 3.4: IO capabilities Operation Accept pairing request Reject pairing request Table 3.5: SSP Input commands Comment Representing ‘yes’ input Representing ‘no’ input Laird Technologies ...
Page 21
... Disable legacy (pre-BT2.1) Pairing: 0 – legacy pairing enabled 1 – legacy pairing disabled 90 1..255 Secure Simple Pairing timeout in s This value must be at least 60 in order to meet the recom- mendation of BT2.1 specification Table 3.6: S-Registers for Secure Simple Pairing (SSP) Laird Technologies ...
Page 22
... Please refer to section 2.3, page 37 Pairing timeout Pairing failed Pairing failed (too many repeat attempts) Pairing rejected by remote device Pairing failed (unit keys not supported) Pairing failed (SSP not supported) Pairing failed (already busy with pairing) Table 3.7: Asynchronous messages for SSP Laird Technologies ...
Page 23
... S Register 325..328 is set automatically save the link key (see Section 2, pg 37) The value MM indicates the result of the save operation and a value of 00 implies success, otherwise the value corresponds to an error code. 23 www.lairdtech.com {Initiate Pairing} {Set Passkey} Laird Technologies ...
Page 24
... SSO connection (SSP or DUN). An attempt to connect a second SSO profile while already one SSO connected will result in Error 65. Any incoming connection request to an SSO profile will be rejected if one SSO is already connected. The following section describes AT- commands related to SSO-profiles 24 www.lairdtech.com {Add Trusted Device} Laird Technologies ...
Page 25
... The remote device issues ATO as normal to return to data mode (Refer to 5). For this command to be effective S Register 536 must be set to 1. Response: <cr,lf>OK<cr,lf> 25 www.lairdtech.com {Send Data in Local Command and Connected Mode} (e.g. <string> too long) {Send Data in Local Command and Connected Mode} (e.g. <string> too long) Laird Technologies ...
Page 26
... ATH command. Laird Technologies BTM devices provide a variety of ways of dropping a connection. One method is similar to the above, but instead a ^^^ character sequence is used. This is to eliminate ambiguity when a data call is in progress via a mobile phone which was established using the mobile phone’ ...
Page 27
... When set remote device can ‘capture’ the AT parser of this unit by it sending this module an escape “!!!” sequence. The inter character timing is set via S Register 12 Register 507 is >= 2, then reading this register will always return 0 and writing 1 will result in ERROR 33. Table 3.8: S Registers for SSO profiles Laird Technologies ...
Page 28
... No “OK” is sent in response. Hence the host to send a character regularly (e.g. one per second) until the BTM device echoes all buffered characters to the host (provided echo is enabled). Once the BTM device echoes characters command mode. 28 www.lairdtech.com {Set Incoming Peer Address} Laird Technologies ...
Page 29
... Reset B AT&F* Restore factory default settings ATS102=1 Enable Serial Port Profile (SPP) ATS0=1 Automatic response after one “RING” AT&W Store settings ATZ Reset AT+BTP Make device temporary connectable and discoverable ATI4 Query Bluetooth device address of local device <BdAddr_DevB> Laird Technologies ...
Page 30
... UART; UART data from host is not sent across to remote device AT+SPH Response “NO CARRIER…” (A and B): disconnection confirmed Table 3.9: SPP Example Command Sequence Figure 3.2: SPP example - Preparation of Device A Figure 3.3 SPP example – Preparation of Device B (pairing successful, A and B) (B only) Laird Technologies ...
Page 31
... Therefore if that number is exceeded, then the connection attempt will fail with the following response:- Response: <cr,lf>CALL LIMIT Or <cr,lf>NO CARRIER<cr,lf> In that case, issuing an ATZ to reset the device will reset the count to 0 and more connections are possible. Laird Technologies ...
Page 32
... For backward compatibility, the following command fulfils the same purpose: ATH Response: <cr,lf>NO CARRIER<cr,lf> SPP – Incoming Connections The Laird Technologies BTM device can be configured using the AT+BTP or AT+BTG command so that it will scan for incoming connections from other Bluetooth devices. It can also be configured via S Register 512 this mode by default on power up. ...
Page 33
... If S0 <> 0 and S100 <> 0 then S0 must be < S100 value is entered which violates this rule, then ERROR 29 is sent in response. Table 3.10: S Registers for SPP Register Default Range Description S589 8 0..8 External codec output gain Table 3.11: S Registers for Hardware Units Laird Technologies ...
Page 34
... GPIO Pin (BTM410/411) Handshaking GPIO1 RI GPIO2 DCD GPIO3 - GPIO4 - GPIO5 - GPIO6 - GPIO7 DTR GPIO8 DSR GPIO - Alternative Functions BTM410/411 Reserved Figure 3.6: GPIO configuration register Alternative Function Wi-Fi Coexistence - - BT_Priority / Ch_Clk BT_Active / BT_ State Wlan_Active Rf_Active - - FME INV DIR Laird Technologies ...
Page 35
... GPIO6 GPIO7 GPIO8 GPIO1..8 0x0000 0..0xFF Read/Write all GPIOs in one atomic step (Write operation only affects GPIOs configured as outputs) 0x0001: GPIO1 0x0002: GPIO2 0x0004: GPIO3 0x0008: GPIO4 0x0010: GPIO5 0x0020: GPIO6 0x0040: GPIO7 0x0080: GPIO8 Table 3.13: GPIO S Registers Laird Technologies ...
Page 36
... The recommended value to enable this feature is 7. Value = bitmask for packet type. The link type (SCO/ eSCO) is defined by S584 Feature disabled 1 : HV1 (S584=0) or EV3 (S584= HV2 (S584=0) or EV4 (S584= HV3 (S584=0) or EV5 (S584=1) Table 3.14: SCO/eSCO AT-commands and S-Registers Laird Technologies ...
Page 37
... S328 [0..1] Table 3.15: Automatic storage of link keys Comment not store (cache only store automatically (default) identical with S538 not store (cache only store automatically (default not store (cache only store automatically (default not store (cache only store automatically (default) Laird Technologies ...
Page 38
... ATI64 0 = not connected 1 = ACL connected 2 = audio connected ATI65 0 = not connected 1 = SLC connected 2 = audio connected call, SLC call, audio ATI66 0 = not connected 1 = SLC connected 2 = Audio connected call - SLC call – audio ATI67 0 = not connected 1 = connected Table 3.16: Profile connection status Laird Technologies ...
Page 39
... If AVRCP was not connected, response = “NO CARRIER” instance was connected, response = “NO CARRIER 110E” instance was not connected, response = “NO CARRIER” If HSG instance was connected, response = “NO CARRIER 1112” If HSG instance was not connected, response = “NO CARRIER” Laird Technologies ...
Page 40
... If HFG instance was not connected, response = “NO CARRIER” Response = “NO CARRIER” If DUN was connected, response = “NO CARRIER 1103” If DUN was not connected, response = “NO CARRIER” Table 3.19: Implications of S329 Figure 3.7: Page and Inquiry Scan Intervals and Windows Laird Technologies ...
Page 41
... General bonding does not work if initiated by the legacy device. Instead, the legacy device must initiate dedicated bonding first (=pairing, BISM2: “AT+BTW<BdAddr>”). After successful pairing, the connection can be initiated by the legacy device (BISM2: “ATD<BdAddr>”). 41 www.lairdtech.com Figure 3.8: Sniff Mode Example Laird Technologies ...
Page 42
... Append Bluetooth Address to Friendly name If S Reg 593 is set to 1, then the last 6 hex digits of the Bluetooth address are automatically appended to the friendly name. This allows multiple devices with the same name in a neighbourhood to be differentiated. 42 www.lairdtech.com Figure 3.9: BREAK capability in Ezurio Terminal Laird Technologies ...
Page 43
... CONNECT message, separated by a comma 2 – symbol style: append ‘<’ to incoming and ‘>’ to outgoing CONNECT message, separated by a comma applies only to role indicating UUID (e.g.HSP/HFP) and if S329=0 Laird Technologies ...
Page 44
... Page Scan Window in milliseconds. Minimum is 11.25ms so 10/11ms will give 11.25ms, refer to Section 6, pg. 40. 640 11..2550 Inquiry Scan Interval in milliseconds. Minimum is 11.25ms so 10/11ms will give 11.25ms, refer to Section 6, pg. 40. 160 11..2550 Inquiry Scan Window in milliseconds. Minimum is 11.25ms so 10/11ms will give 11.25ms, refer to Section 6, pg. 40. Laird Technologies ...
Page 45
... When S507>0, and in a connection, DSR can be used to change from data to command state by de-asserting the DSR line for less than the time specified in this register. This value is rounded down to the nearest 100ms >), save the set- hex Laird Technologies ...
Page 46
... Must be set before the baud rate change. 1000 100..15000 Reconnect delay when configured as master in pure-cable-replace- ment mode. This value is rounded down to the nearest 100ms. See S Register 505 also. Laird Technologies ...
Page 47
... S Register 507 is anything other than 0, a de-as- sertion of DSR will cause the Bluetooth connection to be dropped. If bits 0..3 and 4..7 are set to 0, then some Bluetooth devices will use that as a signal to stop sending any data back. Laird Technologies ...
Page 48
... This specifies a mask. When Bit the response word “ERROR“ is replaced by “BTERR” and “OK” is replaced by “ok”. When Bit then error responses do not include the error number and instead the error number can be retrieved using ATI12. Laird Technologies ...
Page 49
... S reg 538 0 0..1 Automatically append last 6 digits of local Bluetooth address to the Friendly name which was set via AT+BTN or AT+BTF 0 0..2^32 10 General Purpose 32 bit Registers for use by host. These are stored in non-volatile memory. Table 4.1: BTM - General S Registers Laird Technologies ...
Page 50
... Codec Input Maximum Gain Range Bluetooth version Audio connection status off Returns the number of bytes pending to be sent in the rf buffer when a connection is up. Version number of Multipoint application (Note: ATI is provided for compatibility in multipoint mode, other AT commands are not available). Laird Technologies ...
Page 51
... As the value approaches 1000 (BER = 0.1 indication that the link is very bad and a large number of Bluetooth packets are being lost. Manufacturing data (e.g. module serial number, manufacturing date) Full AT firmware version number Table 4.2: BTM ATI Commands Laird Technologies ...
Page 52
... E.g. new Attempt value greater than MinInterval. Solution is to first increase MinInterval and re-enter the Attempt value. 38 Get Remote Friendly name Failed 39 Failed to change mode to Multipoint 40 7 Bit mode requires parity to be even or odd 41 Stream Error 42 Stream Pending Error 52 www.lairdtech.com Laird Technologies ...
Page 53
... OBEX File Transfer Headset Profile (HSP) A2DP A2DP AVRCP A2DP AVRCP AVRCP Headset Profile Hands-free Profile (HFP) Hands-free Profile (HFP) Table 4.4: Selected UUIDs Role - - - - - Headset Audio Source Audio Sink Remote Target - - Remote Controller Audio Gateway Hands-free unit Audio Gateway Laird Technologies ...
Page 54
... Caution: this tool allows selection of more than one minor device classes, so make sure that only one minor device class is select and verify the result with [3] anyway. [5] “Bluecore 4 External” Data Sheet, Cambridge Silicon Radio (CSR) http://www.csrsupport.com (log in or new account required) [6] “Winbond 681360 Codec Board User Guide”, Ezurio Application Note 54 www.lairdtech.com Laird Technologies ...
Page 55
BTM410/411 Bluetooth AT Data Module ® FCC REgULATORY BTM410 FCC and Industry Canada Statements STATEMENTS The Final Equipment user manual must show the following statements: This device complies with part 15 of the FCC Rules. Operation is subject to the ...
Page 56
... EN55022:2006/A1:2000/A2:2006(ClassB) Immunity: EN61000-4-2:1995/A1:1998/A2:2001 EN61000-4-3:2002/A1:2002 Means of the efficient use of EN 300 328 V1.7.1 (2006-10) the radio frequency spectrum Ezurio Ltd dba Laird Technologies Saturn House, Mercury Park Wooburn Green HP100HH, United Kingdom tel: +44 (0)1628 858 940 fax: +44 (0)1628 528 382 October 2009 ...
Page 57
... EN55022:2006/A1:2000/A2:2006(ClassB) Immunity: EN61000-4-2:1995/A1:1998/A2:2001 EN61000-4-3:2002/A1:2002 Means of the efficient use of EN 300 328 V1.7.1 (2006-10) the radio frequency spectrum Ezurio Ltd dba Laird Technologies Saturn House, Mercury Park Wooburn Green HP100HH, United Kingdom tel: +44 (0)1628 858 940 fax: +44 (0)1628 528 382 November 2009 ...
Page 58
BTM410/411 Bluetooth AT Data Module ® MECHANICAL DRAWINgS BTM410 Mechanical Details 58 ...
Page 59
BTM410/411 Bluetooth AT Data Module ® MECHANICAL DRAWINgS BTM410 Mechanical Details 59 ...
Page 60
BTM410/411 Bluetooth AT Data Module ® MECHANICAL DRAWINgS BTM411 Mechanical Details 60 ...
Page 61
BTM410/411 Bluetooth AT Data Module ® MECHANICAL DRAWINgS BTM411 Mechanical Details 61 ...
Page 62
BTM410/411 Bluetooth AT Data Module ® MECHANICAL DRAWINgS BTM411 Mechanical Details 62 ...
Page 63
BTM410/411 Bluetooth AT Data Module ® MECHANICAL DRAWINgS Development Kit Schematic N/C 37 N/C 38 N/C 39 N/C 40 GND 41 GPIO_1/RI GPIO1/UART_RI 42 GPIO7/UART_DTR GPIO_7/DTR 43 GPIO8/UART_DSR GPIO_8/DSR 44 GND 45 USB_D- USB_MOD_D- 46 USB_D+ USB_MOD_D+ 47 GPIO6/RF_ACTIVE 48 ...
Page 64
BTM410/411 Bluetooth AT Data Module ® MECHANICAL DRAWINgS Development Kit Schematic GPIO_2/DCD GPIO_4/BT_ACTIVE/BT_STATE RESET_ PCM_OUT PCM_CLK PCM_SYNC PCM_IN ...
Page 65
... PART NUMBeR BTM410 BTM411 DVK – BTM410 DVK – BTM411 gENERAL COMMENTS This is a preliminary datasheet. Please check with Laird Technologies for the latest information before commencing a design doubt, ask. Refer to the schematic BTDMD-R-001.pdf for the Development Kit on the following two pages for examples of typical pin connections ...
Page 66
... Laird Technologies will not be liable for, any damage or failure caused by misuse, abuse, acts of God, accidents, electrical irregularity, or other causes beyond Laird Technologies’ control, or claim by other than the original purchaser event shall Laird Technologies be responsible or liable for any damages arising: From the use of product; From the loss of use, revenue or profit of the product result of any event, circumstance, action, or abuse beyond the control of Laird Technologies, whether such damages be direct, indirect, consequential, special or otherwise and whether such damages are incurred by the person to whom this warranty extends or third party. If, after inspection, Laird Technologies’ ...