DVK-BTM521 Laird Technologies, DVK-BTM521 Datasheet

BT MM DEV KIT

DVK-BTM521

Manufacturer Part Number
DVK-BTM521
Description
BT MM DEV KIT
Manufacturer
Laird Technologies
Type
Transceiver, Bluetoothr
Datasheets

Specifications of DVK-BTM521

Frequency
2.4GHz
Interface Type
RS-232
Processor Series
BTM521
Silicon Manufacturer
Laird Technologies
Kit Application Type
Communication & Networking
Application Sub Type
Bluetooth
Kit Contents
Development Board & Software Tools
Features
Supports CSR
Rohs Compliant
Yes
For Use With/related Products
BTM521
Lead Free Status / RoHS Status
Lead free / RoHS Compliant
Lead Free Status / RoHS Status
Lead free / RoHS Compliant, Lead free / RoHS Compliant
Other names
DVK-BTM521

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
DVK-BTM521-01
Manufacturer:
LAIRD
Quantity:
7
BTM520/521
MULTIMEDIA
MODULE
USER MANUAL
Innovative Technology
for a Connected World

Related parts for DVK-BTM521

DVK-BTM521 Summary of contents

Page 1

BTM520/521 MULTIMEDIA MODULE USER MANUAL Innovative Technology for a Connected World ...

Page 2

... Error Responses ................................ 106 List of UUIDs .................................... 107 References ....................................... 108 FCC Regulatory Statements .......109 BTM520 FCC and IC Statements ...... 109 Declarations of Compliance ......110 EU Declaration of Conformity .......... 110 Mechanical Drawings ................111 Mechanical Drawing ......................... 111 Development Kit Schematic .............. 113 Ordering Information ................116 General Comments .......................... 116 Laird Technologies ...

Page 3

... The BTM520 and BTM521 are the most advanced low power, multimedia Bluetooth modules on the market. They have been designed by Laird Technologies to meet the needs of developers who require the ultimate Bluetooth audio performance and flexibility, along with fast time to market. The modules include everything needed for a fully qualified and functional Bluetooth multimedia application. As well as providing best in class radio performance, range and power consumption, they support all of the functionality to run Cambridge Silicon Radio’ ...

Page 4

... High Quality Stereo Headsets • Mono Voice Headsets • Hands-free devices • Wireless Audio Cable Replacement • MP3 and music players • Medical and Healthcare Devices • Phone Accessories • VoIP products • Cordless Headsets • Aftermarket Automotive Applications Laird Technologies ...

Page 5

... AVRCP – Target and Controller SCO/eSCO FTP Client (future release) DI (future release) GOEP (future release) PBAP (future release) MAP (future release) HDP (future release) Protocols RFCOMM AVCTP AVDTP OBEX (future release) MCAP (future release) Firmware Upgrade Available over UART † † Laird Technologies ...

Page 6

... Storage Temperature -40°C to +85°C Bluetooth Qualified as an END product ® FCC Meets FCC requirements Modular Approval CE & R&TTE Meets CE and R&TTE requirements Lead free Lead-free and RoHS compliant Warranty 12 Months Development Kit Development board and software tools Laird Technologies ...

Page 7

... Microphone bias – Note 4 Microphone, channel B- (right) – Note 4 Microphone, channel B+ (right) – Note 4 Microphone, channel A+ (left) – Note 4 Microphone, channel A- (left) – Note 4 VOLTAGE SPECIFICATION VPADS VPADS VPADS VPADS VPADS VPADS VPADS VPADS Open Drain Open Drain VIO VIO Laird Technologies ...

Page 8

... Clear to Send I/P Transmit data O/P Receive data I/P Module reset I/P (active low) – Note 1 VOLTAGE SPECIFICATION VIO VPADS VIO VIO VPADS VPADS VPADS VPADS VPADS VPADS VPADS VPADS VPADS VPADS VUSB VUSB VIO VUSB VUSB VUSB VUSB VPADS Laird Technologies ...

Page 9

... Min Typ Max 0.625VDD_USB VDD_USB+0.3 -0.3 0.25VDD_USB 0.75VDD_USB VDD_USB 0 0.125 Min Typ Max 0.625VDD_IO VDD_IO+0.3 -0.3 0.25VDD_IO 0.75VDD_IO VDD_IO 0 0.125 Min Typ Max 0.625VDD_PADS VDD_PADS+0.3 -0.3 0.25VDD_PADS 0.75VDD_PADS VDD_PADS 0 0.125 Min Typ Max 0.7VDD_USB 0.3VDD_USB 2.8 VDD_USB 0 0.2 Laird Technologies ...

Page 10

... When operating in line input mode, the input can be connected directly to the module input pins in either single or double ended configuration as follows: AC Single ended Module MIC_BIAS 15nH MIC_AP 15pF 15nH MIC_AN 15pF Module External Circuit AC Double ended Laird Technologies VDD R External Circuit ...

Page 11

... 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 12

... 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 13

... Bluetooth version Features Profiles BTM520 / BTM521 Chipset Bluetooth version Features Profiles 13 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 14

... A string delimited by double quotes, e.g., “Hello World”. The “ character MUST be supplied as delimiters. A four character UUID number consisting of ASCII characters ‘0’ to ‘9’, ‘A’ to ‘F’ and ‘a’ to ‘f’. {Enable/Disable Echo} AT-Command Prefix AT+SP… AT+AP… AT+AV… AT+HS… AT+HF… AT+DU… Laird Technologies ...

Page 15

... 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 16

... 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> 16 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 17

... AT+BTX may put the device into the correct idle mode. 15. ATIn 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. For recognized values of n: Response: < ...

Page 18

... 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 19

... An optimal solution would be a first inquiry scan without friendly name and <dev_class> filter second run, the friendly name is queried by AT+BTF<BdAddr> for each device found. 19 www.lairdtech.com Bit Reserved for future usage EIRD Default Figure 3.1: S Register 330 controlling inquiry response format RSSI FN COD ADR Laird Technologies ...

Page 20

... 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 1. the Bluetooth device address 2. device class code { Inquire } 1. the Bluetooth device address 2. device class code 3. friendly name Laird Technologies ...

Page 21

... Outgoing EIR Data} Characteristics • MITM protection (MITM = “Man in the Middle” attack) • Encryption • User interaction • No MITM protection • Encryption Comment High security Medium Security Laird Technologies ...

Page 22

... The device does not have the ability to indicate ‘yes’ or ‘no’, and the device does not have the ability to display or communicate a 6 digit decimal number. Reject IO-Cap requests IO-capability requests prior to SSP are rejected. Table 3.4: IO capabilities Comment Low Security Permitted only for service discovery Laird Technologies ...

Page 23

... 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) Comment Representing ‘yes’ input Representing ‘no’ input Laird Technologies ...

Page 24

... Please refer to section 2.3, page 89. 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 25

... S Register 325..328 is set automatically save the link key (see Section 2.3, page 89). 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. 25 www.lairdtech.com {Initiate Pairing} {Set Passkey} Laird Technologies ...

Page 26

... 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. 26 www.lairdtech.com {List Trusted Device} {Add Trusted Device} Laird Technologies ...

Page 27

... S Register 12 and is the same as per the ^^^ escape sequence. By default the guard time is set to 100 milliseconds. 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> 27 www.lairdtech.com (e.g. <string> too long) (e.g. <string> too long) Laird Technologies ...

Page 28

... 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 29

... 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 30

... 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. 30 www.lairdtech.com {Set Incoming Peer Address} {Delete Incoming Peer Address} Laird Technologies ...

Page 31

... Outgoing Peer Address} This section gives an example on how an SPP connection between two Laird Technologies BTM devices can be established assumed that two devices A and B are connected to a terminal program e.g. Ezurio Terminal on a PC. The example sequence of AT commands is listed in Table 3.9. ...

Page 32

... 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 33

... 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 34

... For backward compatibility, the following command fulfils the same purpose: ATH Response: <cr,lf>NO CARRIER<cr,lf> 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 35

... Support in SRC (Audio Source) Support in SNK (Audio Sink) Spec. 1. SBC M 2. MPEG-1,2 Audio O 3. MPEG-2,4 AAC O 4. ATRAC family O M: mandatory O: optional Table 3.12: A2DP Supported Codec Types on BTM5xx Support in SNK (Audio Sink) BTM5xx Spec. BTM5xx Yes M BTM5xx Spec. BTM5xx Yes M Yes Yes Laird Technologies ...

Page 36

... Volume Disconnect 36 www.lairdtech.com This section gives an example of an A2DP connection between a Laird Technologies BTM device as Audio Sink (wireless speaker/ wireless headphones) and a PC with a built in Bluetooth device and Toshiba Bluetooth Stack 2.1 as Audio Source. The PC must support A2DP different stack the procedure should be similar and follow the steps of: 1 ...

Page 37

... BTM520/521 Bluetooth Multimedia Plus Module ® AT COMMAND SET REFERENCE 37 www.lairdtech.com Figure 3.6: A2DP example 1 – PC Bluetooth settings Figure 3.7: A2DP example 1 – Start discovery of Bluetooth devices Laird Technologies ...

Page 38

... AT COMMAND SET REFERENCE Figure 3.8: A2DP example 1 – Select Bluetooth device (Click “Refresh” if Laird BTMM is not listed) 38 www.lairdtech.com Figure 3.9: A2DP example 1 – Confirm pairing (here: Secure Simple Pairing, no PIN required) Figure 3.10: A2DP example 1: Connection established Laird Technologies ...

Page 39

... Preparation 39 www.lairdtech.com Figure 3.11: A2DP example 1: New Bluetooth Audio Device in the Device Manager This section gives an example of an A2DP connection between a Laird Technologies BTM5xx device (A) as Audio Sink (wireless speaker/ wireless headphones) and another Laird Technologies BTM5xx device (B) as Audio source. ...

Page 40

... A/B AT+APH Response “NO CARRIER 110D”: disconnection confirmed Table 3.14: A2DP Example 2 Command Sequence and Instructions Figure 3.12: A2DP Example 2 – Preparation of Device A (Sink) Figure 3.13: A2DP Example 2 – Preparation of Device B (Source) (pairing successful, A and B) Laird Technologies ...

Page 41

... A2DP Source The setting must be saved by AT&W and becomes effective on next power cycle (ATZ). CAUTION 300=0 at boot time (no role selected) and the A2DP flag (0x80) is set in S102, the A2DP flag will be cleared automatically because A2DP cannot be enabled without a role selected. Laird Technologies ...

Page 42

... Portable Audio Sink Audio/Video Car audio Sink Audio/Video n/a Source Audio/Video Microphone Source Audio/Video HiFi Audio Device Source > where <device_class hex >. The remote device must support the hex (first time only, auto pairing without MITM authent.) (not successful) > hex >. hex Laird Technologies ...

Page 43

... AT-Command / SRegister Comment S102 S300 [0..2] 128 = A2DP, Error 46 if A2DP role has not been set (see S300) Needs subsequent AT&W and ATZ to become effective 0 = feature not set 1 = A2DP Sink (default A2DP Source Needs subsequent AT&W and ATZ to become effective Laird Technologies ...

Page 44

... Subsequent AT&W plus ATZ required for a new value to become effective S313 [1..15] Bitmask - source supported features: Bit 0 = Player (default) Bit 1 = Microphone Bit 2 = Tuner Bit 3 = Mixer Subsequent AT&W plus ATZ required for a new value to become effective Table 3.16: A2DP – S Registers and AT-Commands Laird Technologies ...

Page 45

... AVRCP Example 1 45 www.lairdtech.com Table 3.17: AVRCP Supported Features on BTM5xx This section gives an example of an AVRCP connection between a Laird Technologies BTM5xx device as AVRCP Controller and a PC with a built in Bluetooth device and Toshiba Bluetooth Stack 2.1 as AVRCP Target. For any other Bluetooth Stack with AVRCP (target role) support, the setup should follow the steps of: 1 ...

Page 46

... Send “Stop” (Figure 3.21) Response: “OK” - command accepted “AVPTC 0,45,0” -confirmation received from PC “AVPTC 0,45,1” -confirmation received from PC BTM5xx AT+AVH Response: (Figure 3.20) “NO CARRIER 110E” (disconnection confirmed) Table 3.18: AVRCP Example 1 Command Sequence Laird Technologies ...

Page 47

... BTM520/521 Bluetooth Multimedia Plus Module ® AT COMMAND SET REFERENCE 47 www.lairdtech.com Figure 3.16: AVRCP Example 1 – Bluetooth Address of PC and AV Remote Control Service Figure 3.17: AVRCP Example 1 – Player Selection and Receiving Commands Display Setup Laird Technologies ...

Page 48

... Figure 3.18: AVRCP Example 1 – Secure simple pairing dialogue Figure 3.19: AVRCP Example 1 – BTM5xx Preparation and Connection Setup Figure 3.20: AVRCP Example 1 – BTM5xx Sending Commands and Connection Release Figure 3.21: AVRCP Example 1 – Incoming AVRCP commands (top-right corner of screen) Laird Technologies ...

Page 49

... The module must hex >,<company_id ><cr,lf> hex hex > and <company_id hex >,<pagedata > <cr,lf> (after command completion) dec hex > hex Laird Technologies ...

Page 50

... The IEEE Company bit integer which can be set via S Register 303. The response is sent automatically with the company ID as per S303 and a fixed unit type of 0x09 (“Panel”). > and <pagedata > will not dec hex >,<button_state><cr,lf> hex > and <button_state> are omitted. hex Laird Technologies ...

Page 51

... Tuner 4 = Menu Needs subsequent AT&W and ATZ to become effective Response if accepted: “CONNECT 0123456789012,110E,>” Response if rejected: “NO CARRIER 110E” Response: “NO CARRIER 110E” if connection has existed and S329=0 “NO CARRIER” if connection has not existed and S329=0 Laird Technologies ...

Page 52

... If S 310 == 1, response from host is not required. Table 3.19: AVRCP – S Registers and AT Commands >: see Table 3.20 hex ‘1’ Button released >,<state>” hex >,<unit_type >,<company_ hex hex >” >,<pagedata > dec hex >: see Table 3.22 hex Laird Technologies ...

Page 53

... Pause 0x46 Record 0x47 Rewind 0x48 Fast forward 0x49 Eject 0x4A Forward 0x4B Backward 0x4C Angle 0x50 Sub picture 0x51 F1 0x71 F2 0x72 F3 0x73 F4 0x74 F5 0x75 Vendor unique 0x7e Table 3.20: AVRCP – Operation IDs for Remote Control Commands Laird Technologies ...

Page 54

... Table 3.21 <company_id>: IEEE Company ID (n>0) Unsuccessful response to AT+AVU (UNIT INFO Request), indicates completion of command <n> = status Read-Value (S311, Write-Value (S311) or sent in response) AT+AVR<parameter> ‘110E’ – UUID indicating AVRCP >: Unit ID hex : 1 – fail dec 4 – timeout Laird Technologies ...

Page 55

... Confirmation of AT+AVC (Control Command Request) <n> = statusdec : 0 – success 1 – fail 4 – timeout 7 – operation not supported any value in range [1..9] - not successful <operation_id >: see Table 3.20 hex <state>: ‘0’ – Button pushed ‘1’ – Button released Laird Technologies ...

Page 56

... Depending on the current audio connection state, the audio gateway will establish or release the audio connection subsequently. Please refer to Table 3.25. Support in AG BTM5xx Specification Yes M Yes O Yes M (1) O Host AT command interface BTM5xx [HS] BTM5xx Yes Yes Yes (1) >. hex Laird Technologies ...

Page 57

... HS”AU1” Audio connection (SCO) has been established (= “audio on”). HS”AU0” Audio connection (SCO) has been released (= “audio off”). NO CARRIER 1108 ACL connection to local HS-instance has been released. Please note section 6, page 92. <cr,lf>NO CARRIER 1108<cr,lf> >[,<dir>] hex Laird Technologies ...

Page 58

... Enable HS disconnection “ATH1108” and “ATH*” disabled (default enable Should only be enabled for test purpos- es, because disconnection initiated by HS other than sending “AT+CKPD=200” to gateway is not defined in HSP speci- fication not connected 1 = ACL connected 2 = Audio connected Mobile Termination Network Laird Technologies ...

Page 59

... Connection Release from AG AT+HSGH Release existing connection to a HS. If the HS is alerted, alerting will be cancelled audio connection exists it will be released first. ACL will be released in either case. Response: On audio disconnection (optional): <cr,lf>HSG”AU0”<cr,lf> On SLC disconnection: <cr,lf>NO CARRIER 1112<cr,lf> Laird Technologies >. hex ...

Page 60

... HS (speaker gain setting). The valid range for n is 0..15. HSG”VGMn” “AT+VGM=n” with was received from HS (microphone gain setting). The valid range for n is 0..15. NO CARRIER 1112 ACL connection to local AG-instance has been released. Please note section 6, page 92, too. >[,<dir>] hex Laird Technologies ...

Page 61

... ACL established 3 = auto alerting on outgoing and incoming ACL established 0 = disable in-band ringing 1 = enable in-band ringing 0 =disable 1 = ACL will be released automatically when audio was released by the HS not connected 1 = ACL connected 2 = Audio connected 5 = Ringing (ACL connected In-band ringing (Audio connected) Laird Technologies ...

Page 62

... M M Yes M M Yes O M Yes M M Yes M O Yes M O Yes M O Yes M O Yes Yes Yes (2) O Laird Technologies Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes (2) Yes (5) (5) (5) (4) (1) (2) Yes Yes (2) ...

Page 63

... AT+HFH Release connection from local Hands-free instance. Audio connection will be released if existing, SLC will be released anyway. Response: On audio disconnection: <cr,lf>HF”AU0”<cr,lf> On SLC disconnection: <cr,lf>NO CARRIER 111E<cr,lf> Host Controller AT command interface Audio Echo BTM5xx [HF] (only if audio connection exists) Laird Technologies ...

Page 64

... The according flag is set in the HF service record. 2. The according flag is set in the BRSF-message on Service Level Connection establishment 3. The SLC message “AT+CCWA=1” is sent automatically once the SLC is established Response to action no. 3 will be indicated by either HF”CCWA,OK” or HF”CCWA,ERROR” after the “CONNECT…” message. Laird Technologies ...

Page 65

... BTM accepting command) And one of the following: <cr><lf>HF”CMEE,OK”<cr><lf> or: <cr><lf>HF”CMEE,ERROR”<cr><lf> (error, e.g. not supported by HFG) (refer to section 3.2.7.1.17) (original SLC response from HF gateway, (feature not supported by HF-gateway) (confirmation from HFG) Laird Technologies ...

Page 66

... HF”AU0” Audio connection (SCO) has been released (= “audio off”). HF”CLIP,OK” HFG has replied with OK to reception of “AT+CLIP=1” or “AT+CLIP=0”. (S333=1, default) HFI indicator_id Section in HFP spec. [5] (S333=0) 1 4.4 2 All call related sections 4.5 6 4.6 7 4.7 >[,<dir>] Laird Technologies ...

Page 67

... Operator – the name of the network operator in alphanumeric format HF”COPS,OK” HFG has replied with OK to reception of “AT+COPS?”. Laird Technologies ...

Page 68

... HFI… asynchronous message (refer to Section 7.1.15 on page 66) Bitmask Bit 1 – call waiting notification capability Bit 2 – CLIP presentation capability Other options are not supported by the current firmware 0 = not connected 1 = SLC connected 2 = Audio connected call - SLC call - audio Laird Technologies ...

Page 69

... Release audio connection only. The service level connection will be retained. Response: Audio off: <cr,lf>HFG”AU0”<cr,lf> This command is not permitted to be issued in a call setup state (incoming / dialling / alerting, ATI66 = and will return with ERROR 63 in that case. Laird Technologies ...

Page 70

... HFG”L” (redial last number) “OK” is sent as successful response to the HF’s request. Signal an outgoing call status by sending “+CIEV:3,2” (callsetup=2) indicator to HF audio connection is not present yet, it will be initiated. (only if audio connected) > dec >] dec Laird Technologies >” dec ...

Page 71

... AT+HFGI should only be used with indicator IDs 1 (service), 5 (network signal strength), 6 (roam) and 7 (battery charge level). For call management purposes the appropriate AT+HFGCx command should be used. They will send call related indicators (call, call setup, call held) automatically. > dec Laird Technologies ...

Page 72

... Subscriber number records are stored in volatile memory. Hence they are lost on reset or power cycle. At maximum 4 subscriber number records are allowed. Range of value Section in HFP spec. [5] 0..1 4.4 0..1 All call related sections 0..3 All call related sections 0..2 All call related sections 0..5 4.5 0..1 4.6 0..5 4.7 Laird Technologies ...

Page 73

... If there are higher numbered indexes than the one deleted, the remaining records will get a new index assigned dynamically on HFGS?. Response: <cr><lf>OK<cr><lf> Or: <cr><lf>ERROR 66<cr><lf> record with requested index <n> not available Or: <cr><lf>ERROR 05<cr><lf> syntax error command finished Laird Technologies ...

Page 74

... CLIP, refer to section 7.2.5. Laird Technologies ...

Page 75

... HFG”R” Incoming call was rejected by HF. HFG”OP?” Request for network operator string (“AT+COPS?”) received from HF expected to reply with “+COPS:0,0,<operator_string>” on SLC. Use AT+HFGO”<operator_string>”. HFG status, no SLC (ATI66 >[,<dir>] hex Laird Technologies ...

Page 76

... ERROR 63 is returned in that case Sends “RING” and “+CLIP: <number_string>, <type>” <type> must be in range 128..175 Refer to section 7.2.5 on page 70 Sends “+CIEV:2,1” (call=1) and “+CIEV:3,0” (callset- up=0) over SLC. Refer to section 7.2.6 on page 70 Laird Technologies ...

Page 77

... Otherwise a simple “ERROR” is sent to HF. AT+HFGB0/1 “+BSIR:0” or “+BSIR:1” is sent to HF. SLC must exist and Bit 3 of S596 (HFG supported features) must have been set at boot time. Ringtone signal must be provided by external circuit. or (1) or (2) (2) Laird Technologies ...

Page 78

... HFP1.5 – AG not connected 1 = SLC connected 2 = Audio connected call – SLC call – audio 5 = call setup: ringing (incoming call) / dialling or alerting (outgoing call) – SLC 6 = call setup: ringing (incoming call) / dialling or alerting (outgoing call) – audio call but no SLC Laird Technologies ...

Page 79

... Accordingly, DSR de-asserted means a voltage level of logic 1 (3 the module pin. Response: On Bluetooth disconnection: Support in DT Support in GW BTM Specification Yes N/A No N/A No N/A >. The remote device must support the hex <cr,lf>NO CARRIER 1103<cr,lf> BTM Laird Technologies ...

Page 80

... Responses: successful: “NO CARRIER 1103” profile disabled: “ERROR 59” incorrect state: “ERROR 63” Comment Mode off 1 = on, ADC -> DAC 2 = on, ADC -> DSP -> DAC kHz 1 = 11.025 kHz kHz 3 = 22.050 kHz kHz kHz 6 = 44.1 kHz Laird Technologies ...

Page 81

... Overall Gain (dBr) Input Gain Level S689 or S690 S589 or S590 22 +21.5 21 +18.0 20 +15.5 19 +12.0 18 +9.5 17 +6 -3.0 13 -6.0 12 -9.0 11 -12.0 10 -15.0 9 -18.0 8 -21.0 7 -23.5 6 -27.0 5 -29.5 4 -33.0 3 -35.5 2 -39.0 1 -41.5 0 -45.0 Table 3.40: Gain Table Digital Analogue Component Component Laird Technologies ...

Page 82

... Error 58 shall appear if minimum gain level reached AT+GO? AT+GOR AT+GOS AT+GIU Error 57 shall appear if maximum gain level reached AT+GID Error 58 shall appear if minimum gain level reached AT+GI? AT+GIR AT+GIS Table 3.41: Gain Settings AT commands and S-Registers Figure 3.26: ADC Analogue Amplifier Block Diagram Laird Technologies ...

Page 83

... Table 3.38: Mic Bias Voltage Output – S418 Laird Technologies ...

Page 84

... Set codec input gain in dBr * 10 (applies to source), default = 0 0 0..3 Set LED0 mode 0 = LED_OFF 1 = LED_ON 2 = LED_PWM 3 = LED_PULSE Comment Mode LED_OFF 1 = LED_ON 2 = LED_PWM 3 = LED_PULSE referenced if LED mode = LED_PWM or LED_PULSE referenced if LED mode = LED_PWM referenced if LED mode = LED_PULSE Laird Technologies ...

Page 85

... Set Auxiliary DAC Level Table 3.40: S Registers for Hardware Units GPIO Pin Handshaking GPIO1 - GPIO2 - GPIO3 - GPIO4 - GPIO5 - GPIO6 - GPIO7 - GPIO8 - GPIO9 DTR GPIO10 - GPIO11 - GPIO12 - GPIO13 - Table 3.41: GPIO - Alternative Functions Alternative Function Wi-Fi Coexistence RxEnable TxEnable - - - BT_State/BT_Priority Wlan_Active - - - - - - Laird Technologies ...

Page 86

... Valid only if FME=1. FMS selects function mapping code or av_operation_id. See also section 8.1 on pg.84 “Profile specific GPIO function mapping” And section 5.5 on pg. 55 “AVRCP GPIO Mapping” Table 3.42: GPIO Configuration Register Field Descriptions Reserved FMS FME INV Laird Technologies 1 0 DIR ...

Page 87

... GPIO1 0x0002: GPIO2 0x0004: GPIO3 0x0008: GPIO4 0x0010: GPIO5 0x0020: GPIO6 0x0040: GPIO7 0x0080: GPIO8 0x0100: GPIO9 0x0200: GPIO10 0x0400: GPIO11 0x0800: GPIO12 0x1000: GPIO13 Comment A2DP,HFP: adjust volume locally A2DP,HFP: adjust volume locally A2DP,HFP HFP HFP HFP HFP Laird Technologies ...

Page 88

... S532 [0..7] 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.45: SCO/eSCO AT-commands and S-Registers Laird Technologies ...

Page 89

... Table 3.46: Automatic storage of link keys S-Register Comment S325 [0.. not store (cache only store automatically (default) identical with S538 S326 [0.. not store (cache only store automatically (default) S327 [0.. not store (cache only store automatically (default) S328 [0.. not store (cache only store automatically (default) Laird Technologies ...

Page 90

... CARRIER” ATH110E or AT+AVH If AVRCP connection released: response = “NO CARRIER 110E” AVRCP connection has ex- isted: response = “NO CARRIER” ATH1112 or AT+HSGH If AG(HSP) connection released: response = “NO CARRIER 1112” HSP connection has existed: response = “NO CARRIER” Laird Technologies ...

Page 91

... 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, re- sponse = “NO CARRIER” Laird Technologies ...

Page 92

... Headset role (Headset profile) Common UUID for source and sink role Common UUID for controller and target role Audio gateway role (Headset profile) Hands-free role (Hands-free profile) Audio gateway role (Hands-free profile) Example Outgoing connection CONNECT 0123456789AB,1108 CONNECT 0123456789AB,1108,O CONNECT 0123456789AB,1108,> Laird Technologies ...

Page 93

... Table 3.55: Selected items of HSP - audio gateway role service record to query UUIDs of a remote device in order to determine hex Profile [Ref #5] See Headset Profile, Bluetooth SIG See Headset Profile, Bluetooth SIG Bluetooth Headset Profile, Bluetooth SIG UUID 0x1131 0x1108 UUID 0x1112 0x1108 Laird Technologies ...

Page 94

... Although the specification defines these parameters in terms of timeslots, the S register values have to be specified in units of milliseconds and the firmware does the necessary translation to timeslots. 94 www.lairdtech.com Figure 3.28: Page and Inquiry Scan Intervals and Windows Laird Technologies ...

Page 95

... If connected using Ezurio Terminal, the module can be reset to the factory default baud rate as follows: Right click in the Ezurio Terminal window  Factory Default  Via BREAK/CMD @ 9600 (Tested with version 6.7.2 of Ezurio Terminal) 95 www.lairdtech.com Figure 3.29: Sniff Mode Example Laird Technologies ...

Page 96

... If S Reg 593 is set to 1, then the last six 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. 96 www.lairdtech.com Figure 3.30: BREAK capability in Ezurio Terminal Laird Technologies ...

Page 97

... 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 98

... Page Scan Window in milliseconds. Minimum is 11.25ms so 10/11ms will give 11.25ms, refer to Section 7, page. 93. 640 11..2550 Inquiry Scan Interval in milliseconds. Minimum is 11.25ms so 10/11ms will give 11.25ms, refer to Section 7, page. 93. 160 11..2550 Inquiry Scan Window in milliseconds. Minimum is 11.25ms so 10/11ms will give 11.25ms, refer to Section 7, page. 93. Laird Technologies ...

Page 99

... 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 hex Laird Technologies ...

Page 100

... 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 101

... S Register 507 is anything other than 0, a de-assertion 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 102

... 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 103

... S reg 538. 0 0..1 Automatically append last six 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 104

... 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 105

... 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 106

... Bit mode requires parity to be even or odd 41 Stream Error 42 Stream Pending Error 43 Unknown Audio Gateway Command 44 Busy, try later 45 Command or operation not allowed 46 No A2DP role has been set (see S register 300 AVRCP role has been set (see S register 301) 106 www.lairdtech.com Laird Technologies ...

Page 107

... 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 108

... External” Data Sheet, Cambridge Silicon Radio (CSR) http://www.csrsupport.com (log in or new account required) [11] “Bluecore 4 External” Data Sheet, Cambridge Silicon Radio (CSR) http://www.csrsupport.com (log in or new account required) 108 www.lairdtech.com Laird Technologies ...

Page 109

... This exterior label can use wording such as the following: “Contains Transmitter Module FCC ID: PI4520B” or “Contains FCC ID: PI4520B.” Any similar wording that expresses the same meaning may be used. 109 www.lairdtech.com Laird Technologies ...

Page 110

... 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 111

... BTM520/521 Bluetooth Multimedia Plus Module ® MEChANICAL DRAWINGS BTM520/521 Mechanical Diagrams 111 www.lairdtech.com Laird Technologies ...

Page 112

... BTM520/521 Bluetooth Multimedia Plus Module ® MEChANICAL DRAWINGS BTM520/521 Mechanical Diagrams 112 www.lairdtech.com Laird Technologies ...

Page 113

... BTM520/521 Bluetooth Multimedia Plus Module ® MEChANICAL DRAWINGS BTM520/521 Development Kit Schematic 113 www.lairdtech.com AUDIO_GND 19 GND 81 GND 75 GND 66 GND 18 GND 14 GND AGND GND 2 2 Laird Technologies 1 1 ...

Page 114

... BTM520/521 Bluetooth Multimedia Plus Module ® MEChANICAL DRAWINGS BTM520/521 Development Kit Schematic 114 www.lairdtech.com Laird Technologies ...

Page 115

... BTM520/521 Bluetooth Multimedia Plus Module ® MEChANICAL DRAWINGS BTM520/521 Development Kit Schematic 115 www.lairdtech.com Laird Technologies ...

Page 116

... ORDERING INFORMATION INFORMATION BTM520 BTM521 DVK-BTM520 DVK-BTM521 GENERAL COMMENTS This is a preliminary user manual. Please check with Laird Technologies for the latest information before commencing a design doubt, ask. Refer to the schematic BTV-R-003.pdf for the Development Kit for examples of typical pin connections. ...

Page 117

... 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’ ...

Related keywords