Ezurio 510B Bluetooth Multimedia Module User Manual 1

Ezurio Ltd Bluetooth Multimedia Module 1

Contents

User manual 1

BTM510/511MULTIMEDIA MODULEUSER MANUALInnovative Technology for a Connected Worldwww.lairdtech.com
2 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONTENTSBTM510/511 Bluetooth® Module ..3Overview .............................................. 3BTM510/511 Key Features ................... 3Specications ................................4Detailed Specications ......................... 4Pin Denitions ...................................... 6Operating Parameters ...................8Voltage Specications .......................... 8Notes for PCB Layout ........................... 8Conguring the BTM510/511 ........9References ........................................... 9Glossary of Terms ............................... 10AT Command Set .............................. 11Assumptions ...................................... 11Commands ........................................ 11General AT Commands ..................... 11General Bluetooth® Control ............... 22Hardware Unit Control ....................... 28Bluetooth® Proles ............................. 30Secure Simple Pairing ......................... 37Link Key Management ....................... 37Miscellaneous...................................... 38Appendix ........................................... 39BT-MM Unsolicited Messages ............ 39BT-MM Error Responses ..................... 39Mechanical Drawings ..................41Mechanical Details ............................. 41Recommended PCB Footprint ............ 41Diagrams ............................................ 42Ordering Information ..................45Product Part Numbers ........................ 45General Comments ............................ 45TABLE OF CONTENTS
3 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleThe BTM510 and BTM511 are low-power Bluetooth® modules designed for adding robust audio and voice capabilities. Based on the market-leading Cambridge Silicon Radio BC05 chipset, these modules provide exceptionally low power consumption with outstanding range. Supporting the latest Bluetooth® Version 2.1+EDR speci cation, these modules provide the important advantage of secure simple pairing that improves security and enhances easy use.At only 14mm x 20mm, the compact size of the BTM510 makes it ideal for battery-powered or headset form factor audio and voice devices. With a 16-bit stereo codec and microphone inputs to support both stereo and mono applications, these modules also contain a full, integrated Bluetooth®-quali ed stack along with SPP, HFP 1.5, HSP, AVRCP, and A2DP pro les. Customers using these modules may list and promote their products free of charge on the Bluetooth® website.The BTM510/511 modules include an embedded 32-bit, 64-MIPS DSP core within the BC05. This is integrated with the Bluetooth® functionality which allows designers to add signi cant product enhancements including features such as echo cancellation, noise reduction, and audio enhancement using additional soft codecs. The availability of the 16MB of  ash memory in the module allows complex functionality to be included. DSP routines can be licensed through a number of specialist partners. Typical applications for these modules include Bluetooth® stereo headsets, VoIP phones, and wireless audio links. To speed product development and integration, Laird Technologies has developed a comprehensive AT command interface that simpli es application development, including support for audio and headset functionality. Access to GPIO pins allows mapping for direct connection to actuator buttons on headsets. Combined with a low-cost development kit, Laird Technologies’ Bluetooth® modules provide faster time to market.FEATURES• Fully featured Bluetooth® multimedia module• Bluetooth® v2.1+EDR• Supports mono and stereo headset applications• Adaptive Frequency Hopping to cope with interference from other wireless devices• 32bit Kalimba DSP for enhanced audio applications• Support for Secure Simple Pairing• External or internal antenna options• HSP, HFP, A2DP, and AVRCP audio pro les• 16-bit stereo codec and microphone input• Integrated audio ampli ers for driving stereo speaker• Comprehensive AT interface for simple programming• Bluetooth® END product quali ed• Compact size• Class 2 output – 4dBm• Low power operation• Wi-Fi co-existence hardware supportAPPLICATION AREAS• High-quality stereo headsets• Mono voice headsets• Hands-free devices• Wireless audio cable replacement• MP3 and music players• Phone accessories• VoIP products• Cordless headsets• Automotive OVERVIEW AND KEY FEATURES
4 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCATEGORIES FEATURE IMPLEMENTATIONWireless Specication Standards Supported Bluetooth® v2.1 + EDRTransmit Class Class 2Frequency 2.402 – 2.480 GHzChannels 79 channels Frequency Hopping Adaptive Frequency HoppingMax Transmit Power +4 dBm @ antenna pad – BTM510 +4 dBmi from integrated antenna – BTM511 (provisional)Min Transmit Power -27 dBm @ antenna pad – BTM510 -27 dBmi from integrated antenna – BTM511 (provisional)Receive Sensitivity Better than -86 dBmData Transfer rate Up to 300kbps Range Up to 50 meters free space (Data)Antenna Modes External Antenna 50 Ohm matched SMT pad – BTM510Integrated Antenna +0dB (provisional) multilayer ceramic – BTM511UART Interface Serial Interface RS-232 bi-directional for commands and data 16550 compat-ibleBaud Rate Congurable from 1,200 to 921,600bps Non-standard baud rates supportedBits 8Parity Odd, even, noneStop bits 1 or 2Default Serial parameters 9,600,n,8,1Levels Set by VDD_USB pinModem Control DTR, DSR, DCD, RI, RTS, CTSGeneral Purpose Interface I/O 8 general purpose I/O pinsI2S Stereo Audio Digital Interface BusLED TwoAudio Codec Integrated stereo codec with -95dB SNR for DACAmpliers Direct drive for 22Ω Mono Speaker / 44Ω Stereo SpeakersMicrophone Input with bias for low noise microphoneSample Rates (DAC & ADC) 8, 11.025, 16, 22.05, 32 & 44.1kHzProtocols & Firmware Bluetooth® Stack V2.1 compliant. Fully integrated.Proles GAP (Generic Access Prole) SDP (Service Discovery Prole) SPP (Serial Port Prole) HSP HFP – Audio Gateway and Handsfree A2DP – Source and Sink AVRCP – Target and ControllerProtocols RFCOMM AVCTP AVDTPFirmware Upgrade Available over UARTSPECIFICATIONS
5 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCATEGORIES FEATURE IMPLEMENTATIONCommand Interface AT Instruction set Comprehensive control of connection and module operation, including extensions for Audio control. Direct mapping of GPIO to audio functions, e.g. Play, Volume, etc. S Registers for non-volatile storage of parametersDSP Kalimba DSP Integrated in BC05 32bit, 64MIPS, 16Mbps Flash Memory (shared)Applications Available from partnersCurrent Consumption Data Transfer Typically < 35mA Stereo Music Typically < 70mA (including speaker drive)Low Power Sniff Mode Less than 1.5mASupply Voltage Supply 3.0V – 3.6V DCI/O 1.7V – 3.6V DCUSB 1.7V – 3.6V DCCoexistence / Compatibility WLAN (802.11) 2-wire and 3-wire hardware coexistence schemes supportedConnections External Antenna (option) Pad for 50 Ohm antenna – BTM510Interface Surface Mount Pads Physical Dimensions 14.0mm x 20.0 x 1.6mm - BTM510 14.0mm x 26.0mm x 1.6mm - BTM511 (provisional)Weight 3 gramsEnvironmental Operating Temperature -30°C to +70°C Storage Temperature -40°C to +85°CApprovals Bluetooth®Qualied as an END product FCC Meets FCC requirements Modular Approval (Integrated Antenna option – BTM511)CE & R&TTE Meets CE and R&TTE requirementsMiscellaneous Lead free Lead-free within EU requirements and RoHS compliantWarranty 12 MonthsDevelopment Tools Development Kit Development board and software toolsSPECIFICATIONSCATEGORIES FEATURE IMPLEMENTATIONWireless Specication Standards Supported Bluetooth® v2.1 + EDRTransmit Class Class 2Frequency 2.402 – 2.480 GHzChannels 79 channels Frequency Hopping Adaptive Frequency HoppingMax Transmit Power +4 dBm @ antenna pad – BTM510 +4 dBmi from integrated antenna – BTM511 (provisional)Min Transmit Power -27 dBm @ antenna pad – BTM510 -27 dBmi from integrated antenna – BTM511 (provisional)Receive Sensitivity Better than -86 dBmData Transfer rate Up to 300kbps Range Up to 50 meters free space (Data)Antenna Modes External Antenna 50 Ohm matched SMT pad – BTM510Integrated Antenna +0dB (provisional) multilayer ceramic – BTM511UART Interface Serial Interface RS-232 bi-directional for commands and data 16550 compat-ibleBaud Rate Congurable from 1,200 to 921,600bps Non-standard baud rates supportedBits 8Parity Odd, even, noneStop bits 1 or 2Default Serial parameters 9,600,n,8,1Levels Set by VDD_USB pinModem Control DTR, DSR, DCD, RI, RTS, CTSGeneral Purpose Interface I/O 8 general purpose I/O pinsI2S Stereo Audio Digital Interface BusLED TwoAudio Codec Integrated stereo codec with -95dB SNR for DACAmpliers Direct drive for 22Ω Mono Speaker / 44Ω Stereo SpeakersMicrophone Input with bias for low noise microphoneSample Rates (DAC & ADC) 8, 11.025, 16, 22.05, 32 & 44.1kHzProtocols & Firmware Bluetooth® Stack V2.1 compliant. Fully integrated.Proles GAP (Generic Access Prole) SDP (Service Discovery Prole) SPP (Serial Port Prole) HSP HFP – Audio Gateway and Handsfree A2DP – Source and Sink AVRCP – Target and ControllerProtocols RFCOMM AVCTP AVDTPFirmware Upgrade Available over UART
6 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModulePIN SIGNAL DESCRIPTION VOLTAGE SPECIFICATION1 PIO15 / DTR Host I/O VIO2 PIO5/BT_STATE/BT_PRIORITY Host I/O, BT Co-existence VIO3 PCM_IN PCM Data I/P VIO4 PCM_OUT PCM Data O/P VIO5 PCM_SYNC PCM Sync I/P VIO6 PCM_CLK PCM CLK I/P VIO7 LED_EXT1 Host I/O See Note 28 LED_EXT0 Host I/O See Note 29 GND10 VDD_USB USB supply voltage11 VDD_IO I/O supply voltage12 VDD_IN Main supply voltage13 GND14 SPI_CSB SPI bus chip select I/P VIO15 SPI_MISO SPI bus serial O/P VIO16 SPI_CLK SPI bus clock I/P VIO17 SPI_MOSI SPI bus serial I/P VIO18 PIO2/DSR Host I/O VIO19 PIO3/RI Host I/O VIO20 PIO1/DCD Host I/O VIO21 PIO0/BT_ACTIVE Host I/O, BT Co-existence VIO22 GND23 AUDIO_GND Audio ground24 SPKR_A_N Speaker, channel A- (left) See note 325 SPKR_A_P Speaker, channel A+ (left) See note 326 SPKR_B_N Speaker, channel B- (right) See note 327 SPKR_B_P Speaker, channel B+ (right) See note 328 MIC_BIAS Microphone bias See note 429 MIC_BP_C Microphone, channel A- (left) See note 430 MIC_BN_C Microphone, channel A+ (left) See note 431 MIC_AP_C Microphone, channel B- (right) See note 432 MIC_AN_C Microphone, channel B+ (right) See note 433 Unused34 ANT Antenna connection – BTM510 (50 ohm matched)35 Unused36 Unused37 Unused38 Unused39 Unused40 Unused41 Unused42 Unused43 Unused44 Unused45 USB_D- VUSB46 USB_D+ VUSB47 GND48 UART_RTS Request to Send O/P VUSB49 UART_CTS Clear to Send I/P VUSB50 UART_TX Transmit data O/P VUSB51 UART_RX Receive data I/P VUSB52 PIO7/RF_ACTIVE Host I/O, BT Co-existence VIO53 PIO6/WLAN_ACTIVE Host I/O, BT Co-existence VIO54 Reset Module reset I/P See Note 1SPECIFICATIONS
7 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleSPECIFICATIONS The voltage on the module pad should be maintained below 0.5V in which case the Ron of the FET is around 20Ω. Provided that this condition is met, then the current owing through the diode is: 3. The speaker output is capable of driving loads with a minimum impedance of 16Ω directly. 4. The audio inputs can operate in either line input mode or microphone mode. The input circuit has a two stage amplier – the rst stage provides a xed 24dB gain and the second a variable gain of between -3dB and 18dB. If an input gain of less than 24dB is selected, then the rst stage is switched out and the module is operating in line input mode. Iled =VDD - VFWhere VF is the forward bias voltage of the LED.R + 20When operating in microphone mode the microphone should be biased as follows:MIC_APMIC_ANModuleExternal CircuitExternal CircuitMIC_BIAS15 nH15 pF15 nH15 pFThe input impedance on the microphone inputs (in microphone mode) is typically 6kΩ. In order to maintain the regulation on the MIC_BIAS pin, the current drawn must be in the range 0.2 – 1.23mA. If the microphone draws less current than this then an additional resistor to ground must be added to pre-load the microphone output. The audio input is designed for use with inputs of between 1μA and 10μA at 94dB SPL. If the biasing resistors are set to 1kΩ this implies a microphone with a sensitivity in the range -40dBV to -60dBV. The low pass lter elements formed by the inductor and capacitor are required to eliminate RF pick up on the microphone inputs and should be placed as close to the module as possible. When operating in line input mode, the input can be connected directly to the module input pins in either single or double ended conguration as follows:AC ACSingle ended Double endedNote: 1. Reset input is active low. Input is pulled up to VDD_IN via 22k. Minimum reset pulse width is 5ms. 2. LED drive pins are open drain outputs and hence the external circuit to the right should be used.VDDModule External CircuitR
8 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleNOTES FOR PCB LAYOUT:1. The RF output pin must be matched to a 50Ω strip-line or coplanar waveguide on the antenna-less version (BTM510).2. Ensure that there are no exposed conductors under the module to avoid shorts to the test points on the module underside.3.  ThePCBfootprintisprovidedforguidanceonly.UsersmaywishtomodifythePCBlanddimensionstosuittheirspecic manufacturing or process.OPERATING PARAMETERSRECOMMENDED OPERATING CONDITIONSOperating Condition Min MaxVDD_USB (USB compatibility not required) 1.7 3.6VDD_USB (USB compatibility required) 3.1 3.6VDD_IO 1.7 3.3VDD_IN 3.0 3.6VOLTAGE SPECIFICATIONSLOGIC LEVELS (VUSB)Input Voltage Levels Min Typ MaxVih 0.625VDD_USB VDD_USB+0.3Vil -0.3 0.25VDD_USBOutput Voltage Levels Voh (Iout = -4mA) 0.75VDD_USB VDD_USBVol (Iout = 4mA) 0 0.125LOGIC LEVELS (VIO)Input Voltage Levels Min Typ MaxVih 0.625VDD_IO VDD_IO+0.3Vil -0.3 0.25VDD_IOOutput Voltage Levels Voh (Iout = -4mA) 0.75VDD_IO VDD_IOVol (Iout = 4mA) 0 0.125LOGIC LEVELS (VUSB – USB TERMINALS D+, D-)Input Voltage Levels Min Typ MaxVih 0.7VDD_USBVil 0.3VDD_USBOutput Voltage Levels (to correctly terminated USB cable) Voh 2.8 VDD_USBVol 0 0.2OPERATING PARAMETERS
9 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511INTRODUCTIONThis document describes the protocol used to control and congure the BT-MM Bluetooth device. The AT commands described in the document apply to rmware releases from V14.0.9 onwards.The protocol is similar to the industry standard Hayes AT protocol used in telephony modems which is appropriate for cable replacement scenarios, as both types of devices are connection oriented. Just like telephony modems, Laird Technologies’ devices powers up in an 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. Conguration can be saved, so that on a subsequent power up the device is discoverable or automatically connects. The device has a serial interface and an RF communications end point. The latter has a concept of connected and unconnected modes and the former will have a concept of command and data modes. This leads to the matrix of states shown below.RF UNCONNECTED RF CONNECTEDLocal Command Mode OK OKRemote Command Mode ILLEGAL OKData Mode ILLEGAL OKThe combinations, ‘Data and RF Unconnected Mode’ and ‘Remote Command and RF Unconnected Mode’ do not make sense and will be ignored.Navigation between these states is done using the AT commands which are described in detail in subsequent sections.REFERENCES [1] “AT Command Set” [2] “BlueLab_v4.0_Release_Note.pdf” [3] “Audio/Video Distribution Transport Protocol Specication” Rev.V12, 16/04/2007 [4] “Advanced Audio Distribution Prole Specication” Rev. V12, 16/04/2007 [5] “Audio/Video Remote Control Prole” Revision V14r00, 26/06/2008 [6] “Software Release Note Stereo Headset SDK Q3 2007 RC3.1” CS-117522-RNP1, CSR [7] “Stereo Headset SDK Q3 2007 User Guide” CSR, CS-116451-UGP1, CSR, December2007 [8] “Bluetooth Specication Version 2.1 + EDR [vol3]”, 26 July 2007
10 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511Glossary of TermsDESCRIPTIONA2DP : Advanced Audio Distribution ProleADC :Analogue to Digital ConverterAGHFP : Audio Gateway Hands-Free ProleAT : Command prex, ‘Attention’AVRCP : Audio/Video Remote Control ProleBISM :Bluetooth Intelligent Serial ModuleCodec :Device capable of encoding / decoding an analogue / digital signalDAC :Digital to Analogue ConverterDSP :Digital Signal ProcessorDUN : Dial-Up Network ProleFTP : File Transfer ProleGOEP : Generic Object Access Exchange ProleGPIO :General Purpose Input OutputHFP : Hands Free ProleHID : Human Interface Device ProleI/O (IO) : Input/OutputMic :MicrophoneOPP : Object Push ProlePBAP : Phone Book Access ProlePWM :Pulse Width ModulationSxxx :S-Register No. xxxSBC : Sub Band CodecSPP : Serial Port ProleTBD :To Be DeterminedUART :Universal Asynchronous Receiver / TransmitterPT :PASSS THROUGH CommandUI :UNIT INFO CommandSUI :SUBUNIT INFO Command
11 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511AT Command SetAssumptions 1. All commands are terminated by the carriage return character 0x0D, which is represented by the string <cr> in descriptions below this cannot be changed. 2. All responses from the device have carriage return and linefeed characters preceding and appending the response. These dual character sequences have the values 0x0D and 0x0A respectively and shall be represented by the string <cr,lf>. 3. All Bluetooth addresses are represented by a xed 12 digit hexadecimal string, case insensitive. 4. All Bluetooth Device Class codes are represented by a xed 6 digit hexadecimal string, case insensitive.CommandsThe following syntax is employed throughput this document to describe optional or mandatory parameters for AT commands. <bd_addr> A 12 character Bluetooth address consisting of ASCII characters ‘0’ to ‘9’, ‘A’ to ‘F’ and ‘a’ to ‘f’.<devclass> A 6 character Bluetooth device class consisting of ASCII characters ‘0’ to ‘9’, ‘A’ to ‘F’ and ‘a’ to ‘f’.N A positive integer value.M An integer value which could be positive or negative, which can be entered as a decimal value or in hexadecimal if preceded by the ‘$’ character. E.g. the value 1234 can also be entered as $4D2<string> A string delimited by double quotes. E.g. “Hello World”. The “ character MUST be supplied as delimiters.<uuid> A 4 character UUID number consisting of ASCII characters ‘0’ to ‘9’, ‘A’ to ‘F’ and ‘a’ to ‘f’.General AT Commands 1. AT Used to check the module is available. Response: <cr,lf>OK<cr,lf> 2. ATA {Answer Call} Accept an incoming connection, which is indicated by the unsolicited string <cr,lf>RING 123456789012<cr,lf> every second. 123456789012 is the Bluetooth address of the connecting device. Response: <cr,lf>CONNECT 123456789012<cr,lf> 3. ATD<bd_addr>,<uuid> {Make Outgoing Connection} Make a connection to device with Bluetooth address <bd_addr> and SPP prole <uuid>. The <uuid> is an optional parameter which species the UUID of the prole server to attach to, and if not supplied then the default UUID from S Register 101 is used. As this is a device which utilises the RFCOMM layer as described in the Bluetooth specication, it necessarily implies that only proles based on RFCOMM can be accessed. The timeout is specied by S register 505. Response: <cr,lf>CONNECT 123456789012<cr,lf> Or <cr,lf>NO CARRIER<cr,lf> Due to a known issue in the Bluetooth RFCOMM stack, it is not possible to make more than 65525 outgoing connections in a single power up session. 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.
12 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 The following RFCOMM based UUIDs are dened in the Bluetooth Specication:- 4. ATDL {Remake Connection} Make a connection with the same device and service as that specied in the most recent ATD command. An error will be returned if the ‘L’ modier is specied AND a Bluetooth address. If both ‘L’ and ‘R’ modiers are specied then an error will be returned. Response: <cr,lf>CONNECT 123456789012 AE<cr,lf> Or <cr,lf>NO CARRIER<cr,lf> 5.ATDR{MakeConnectiontopeerspeciedinAT+BTR} Make a SPP connection with the device address specied in the most recent AT+BTR command. The service is as specied in S Register 101. An error will be returned if the ‘R’ modier is specied AND a Bluetooth address. If both ‘R’ and ‘L’ modiers are specied then an error will be returned. Response: <cr,lf>CONNECT 123456789012 AE<cr,lf> Or <cr,lf>NO CARRIER<cr,lf> 6. ATEn {Enable/Disable Echo} This command enables or disables the echo of characters to the screen. A valid parameter value will be written to S Register 506. All other values of n will generate an error. Response: <cr,lf>OK<cr,lf> Or Response: <cr,lf>ERROR nn<cr,lf> 7. ATH {Drop Connection} Drop an existing connection or reject an incoming connection indicated by unsolicited RING messages. Response: <cr,lf>NO CARRIER<cr,lf>PROFILE NAME UUIDSerial Port 0x1101LAN Access Using PPP 0x1102Dialup Networking 0x1103IrMC Sync 0x1104OBEX Object Push 0x1105OBEX File Transfer 0x1106IrMC Sync Command 0x1107Headset 0x1108Cordless Telephony 0x1109E0 Disable echo.E1 Enable echo.PROFILE NAME UUIDIntercom 0x1110Fax 0x1111Audio Gateway (HSP) 0x1112WAP 0x1113WAP_CLIENT 0x1114Advanced Audio Distribution0x110DA/V Remote Control 0x110EHandsfree 0x111EAudio Gateway (HFP) 0x111F
13 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511Table 3-1: S-Register ListREGISTER DEFAULT RANGE COMMENTS0 1 -1..15 Number of RING indication before automatically answering an incoming connection. A value of 0 disables autoanswer. If -1, then autoanswer on one RING and do NOT send RING/CONNECT response to the host. This emulates a serial cable replacement situation Setting values >= 0, resets S Register 504 to 0 and <0 forces 504 to 1.If S0 <> 0 and S100 <> 0 then S0 must be < S100. If a value is entered which violates this rule, then ERROR 29 is sent in response.If S504 =1 then this register will return -1, regardless of the actual value stored in non-volatile memory.S2 0x5E 0x20..0x7E Escape sequence character. It is not ‘+’ by default as a Bluetooth® serial link can be used to connect to a mobile phone which exposes an AT command set, which will in turn use ‘+’ as default. So if both used ‘+’ there will be confusion. 0x5e is the character ‘^’.S12 100 40..5000 Escape sequence guard time in milliseconds, with a granularity of 20ms. New values are rounded down to the nearest 20ms multipleS100 15 0..15 Number of RING indications before an auto disconnection is initiated. A value of 0 disables this feature.If S0 <> 0 and S100 <> 0 then S0 must be < S100. If a value is entered which violates this rule, then ERROR 29 is sent in response.S101 $1101 0..$ffff UUID of default SPP based prole when not specied explicitly in the ATD command.S102 1 1..0x7FF Denes a set of bits masks for enabling prole servers. Values can be ORed.0x001 is Serial Port Prole0x080 is A2DP0x100 is AVRCPS103 1 1..7 Boot Mode on cold boot.S126 ? 0 .. 0xFFFF Primer for changing to Multipoint modeS300 1 0..2 Set A2DP role:0 is feature not set1 is A2DP Sink (default)2 is A2DP SourceS301 1 0..2 Set AVRCP role:0 is feature disabled1 is Control (CT) (default)2 is Target (TG)S302 0 0..4 Set AVRCP category:0 is Feature disabled (default)1 is Player/Recorder2 is Monitor/Amplier3 is Tuner4 is Menu 8. ATSn=m {Set S Register} As with modems, the Bluetooth module employs a concept of registers which are used to store parameters, such as escape sequence character, inquiry delay time etc, as listed in detail below. The value part ‘m’ can be entered as decimal or hexadecimal. A hexadecimal value is specied via a ‘$’ leading character. For example $1234 is a hexadecimal number. When S register values are changed, the changes are not stored in non-volatile memory UNTIL the AT&W command is used. Note that AT&W does not affect S registers 520 to 525 or 1000 to 1010 as they are updated in non-volatile memory when the command is received.
14 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 REGISTER DEFAULT RANGE COMMENTS303 0 0..0xFFFFFF Set Company ID:IEEE Company ID, 24bit hexadecimal,Required for UNIT INFO Response in AVRCP target mode, default value is 0.S305 1 0..1 Accept UNIT INFO request:0 – reject1 – acceptS306 1 0..1 Accept SUBUNIT INFO request:0 – reject1 – acceptS310 1 0..1 Congure PASS THROUGH (PT) Response:1 = Enable automatic PT-response, response type is read from S311, (default)0 = Host is required to respond to PT-Indication, see ‘AT+AVR’S311 1 w9 r0..7 (Write) Set automatic PT response:This value is queried for automatic PT-Response, see Table 3-10. The written value is mapped internal, that is why the Read-value is different from the written value. The Read-value is actually sent out as responseS312 1 0..15 A2DP sink supported features (Bitmask) :Bit 0 = Headphone (default)Bit 1 = SpeakerBit 2 = RecorderBit 3 = AmplierS313 1 0..15 A2DP source supported features (Bitmask) :Bit 0 = Player (default)Bit 1 = MicrophoneBit 2 = TunerBit 3 = MixerS320 2 1..3 Security Level: see [12], Generic Access Prole - Table 5.7needs subsequent ‘AT&W’ and power cycle to take effectS321 1 0..4 Set IO capability:0 – display only1 – display yes no2 – keyboard only3 – no input no output4 – reject IO-cap requestsS322 0 0..1 Force man-in-the-middle-protection (MITM):0 – disabled1 – enabledS323 0 0..1 Disable legacy (pre-BT2.1) Pairing:0 – legacy pairing enabled1 – legacy pairing disabledS324 90 1..255 Secure Simple Pairing timeout in sThis value must be at least 90 in order to meet the recommendation of BT2.1 specicationS325 1 0..1 Store link key automatically on dedicated bonding outgoing (DBO), identical with S538S326 1 0..1 Store link key automatically on general bonding outgoing (GBO)S327 1 0..1 Store link key automatically on dedicated bonding incoming (DBI)S328 1 0..1 Store link key automatically on general bonding incoming (GBI)S329 0 0..1 Enable legacy (BISM2) response format
15 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 REGISTER DEFAULT RANGE COMMENTS330 1 1..15 Congure inquiry response of AT+BTI (Bitmask):1 – show device address2 – show class of device4 – show friendly name8 – show extended inquiry dataValues can be ORedS415 0 0..1 Enable Microphone Input Gain, adds extra 24dB to input gainS416 0 0..1 Enable MicBiasS417 0 0..15 Set MicBiasCurrentS418 0 0..15 Set MicBiasVoltageS419 6 0..6 Set sampling rate for Audio Loopback Mode0 = 8 kHz1 = 11.025 kHz2 = 16 kHz3 = 22.050 kHz4 = 24 kHz5 = 32 kHz6 = 44.1 kHzS504 0 0..1 Setting to 1 will force S0 to -1 and will suppress messages arising from connections or pairing. E.g. CONNECT, NO CARRIER, RING, PAIR etc.Suppressing connection based messaged allows the device to be congured in cable replacement mode.S505 10 2..120 Minimum delay before abandoning connection attempt as a master. Referenced by ATD. In units of seconds. See S Registers 530 and 543 also.Please note that as disconnection time can vary, this register only guarantees the minimum delay. Note that for invalid addresses specied in the ATD command, the “NO CARRIER” response will be immediate. See S register 560 for specifying disconnect max timeout.S506 1 0..1 Enable/Disable echoes. The ATEn command also affects this.S507 0 0..2 When set to 0, a connection can be dropped using ^^^ escape sequence only and the state of DSR line is ignored. When set to 1 a connection can be dropped using EITHER the ^^^ escape sequence OR the DSR handshaking line. When set to 2, a connection can only dropped using a deassertion of DSR. Mode 2 provides for the highest data transfer rate.If the status of the DSR line is to be conveyed to the remote device as a low bandwidth signal then this register MUST be set to 0, otherwise a deassertion of DSR will be seen as a request to drop the Bluetooth® connection.This register affects S Register 536 – see details of 536
16 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 REGISTER DEFAULT RANGE COMMENTS512 1 0..7 Specify power up state. When set to 0, AT+BTO is required to open the device for Bluetooth® activity.When set to 1, it proceeds to a state as if AT+BTO was entered. When set to 2, it will be discoverable only, similar to issuing AT+BTQ.When set to 3, it will be connectable but not discoverable e.g. AT+BTGWhen set to 4, it will be connectable and discoverable e.g. AT+BTP. When set to 5, it will be like 2, but all UART RX trafc is discarded in absence of a connection while DSR is asserted. If DSR is not asserted, then it behaves exactly as per mode 2.When set to 6, it will be like 3, but all UART RX trafc is discarded in absence of a connection while DSR is asserted. If DSR is not asserted, then it behaves exactly as per mode 3.When set to 7, it will be like 4, but all UART RX trafc is discarded in absence of a connection while DSR is asserted. If DSR is not asserted, then it behaves exactly as per mode 4.Note that by implication, a change to this can only be seen after a power cycle AND if AT&W is actioned prior to the power cycle.If S Reg 554 is non-zero and this register is between 2 and 7 inclusive, then the value of S554 species the time in seconds that the device will remain in the specied mode after power up. On timeout, the device will fall back to the mode specied in S Register 555.In some rmware builds, S Registers 565 to 569 inclusive are visible, which allows the start-up mode to depend on the state of RI line (Setting S Reg 565 forces the RI pin to be congured as an input). For this feature to be active, SReg 565 should be set to 1. In that case, on start-up, if RI is asserted, then the start-up mode is dened by S Reg 566 and if deasserted then S Reg 567.S514 10 1..60 Pairing Timeout in seconds. This includes the time a host takes to supply the PIN number when PIN? messages are indicated.S515 0x001F00 0.. 0xFFFFFF Default Device Class Code on power up. When queried, the value is always printed as a hexadecimal number.To change the device class of the module permanently, use this S register plus subsequent AT&W and ATZ. To change the device class temporarily (until next power cycle), use the command AT+BTC.S516 0x000000 0..0x2FFFFFF Default Device Class lter to be used with AT+BTI when it is not explicitly specied. When queried the value is always printed as a hex number.The seventh most signicant digit, can be 0,1 or 2, and is used to specify the type of device class lter.When 0, it species no ltering.When 1, it species an AND mask and all 24 bits are relevantWhen 2, it species a lter to look for devices with matching major device class which occupies a 5 bit eld from bits 8 to 12 inclusive (assuming numbering starts at bit 0). All other 19 bits MUST be set to 0.S517 20 2..61 Inquiry Length in units of seconds. This parameter is referenced by the AT+BTI command.S518 8 0..255 Maximum number of responses from an inquiry request. This parameter is reference by the AT+BTI command. If this number is set too high, then AT+BTI will return ERROR 27. For a particular rmware revision, determine the effective maximum value by trial and error. That is, set to a high value, send AT+BTI and if ERROR 27 is returned, then retry with a smaller value. This effective max value will remain unchanged for that particular rmware build.S519 500 100..6000 When S507>0, and in a connection, DSR can be used to change from data to command state by deasserting the DSR line for less than the time specied in this register. This value is rounded down to the nearest 100msS530 1000 100..15000 Reconnect delay when congured as master in pure-cable-replacement mode. This value is rounded down to the nearest 100ms. See S Register 505 and 543 also.
17 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 REGISTER DEFAULT RANGE COMMENTS531 0 0..5 Species the mode on connection establishment.0 = Normal, that data is exchanged between UART and RF1 = LOCAL_COMMAND. UART input is parsed by the AT interpreter and RF data is discarded2 = REMOTE_COMMAND. RF input is parsed by the AT interpreter and UART data is discarded. If S Reg 536 is not 1 then this register cannot be set to 2 and an ERROR will be returned3 = LOCAL_COMMAND. UART input is parsed by the AT interpreter and incoming RF data is sent to the host using the RX<string> asynchronous response.4 = LOCAL_COMMAND and on the rf side, the gpio is automatically sent when there is a change in input. See section 9.5 for more details.5 = DEAMON modeS532 0 0..7 If non zero then on every connection, a SCO channel (audio) will be initiated. Bit 0 for HV1, Bit1 for HV2 and Bit2 for HV3. When the connection is lost, the SCO channel disappears along with it.S533 1 0..2 If set to 1 then GPIO5 follows RI state, if set to 2 then it follows the state of DSR and if 0 it is not driven and GPIO5 is available as a user I/O.This register will not necessarily be effective immediately after changing the value. It must be saved to non-volatile memory using AT&W and will operate as expected after an ATZ or a power cycle.S534 1 0..2 When set to 0, GPIO4 is available as user i/oIf set to 1 then GPIO4 follows DCD state. If set to 2 then GPIO4 behaves as per setting 1, but in addition, when not in a connection, if the device is connectable or discoverable, then GPIO4 will blink.This register will not necessarily be effective immediately after changing the value. It must be saved to non-volatile store using AT&W and will operate as expected after an ATZ or a power cycle.S535 20 0..41 Link Supervision Timeout. If units go out of range, then a NO CARRIER message will be sent to the host after the time specied hereS536 0 0..1 When set to 1, a 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.If S Register 507 is >= 2, then reading this register will always return 0 and writing 1 will result in ERROR 33.S538 0 0..1 If 1, then when a successful pairing occurs, it is automatically saved in the trusted device database – if it has room to store it.S539 0 0..1 When set to 1, in idle mode (S512=1), UART Rx characters are discarded if DSR is deasserted.S541 6 -50..6 This sets the power level in dBm when inquiring or paging. Reading this register returns the value stored in non-volatile memory.S542 6 -50..6 As per S541, however reading this register returns the current power level as set in the base band. The read can be different from S541because the actual power is set using a lookup table and the base band rounds down to the nearest value in the table.S543 0 0..1 If this is set to 1, then incoming pairing attempts will be accepted (if a pin code has been pre-entered using AT+BTK) while in the wait phase of auto connect cycle initiated by the AT+BTR command. In addition to accepting pairing attempts, if the pairing is successful, then the new device is automatically set as the peer address for automatic connections (as if an explicit AT+BTR command was entered).See S Register 505 and 530 also
18 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 REGISTER DEFAULT RANGE COMMENTS551 0x3211 0xFFFF This register species in each 4 bit nibble, how the outgoing modem status bits to the remote peer gets its value. Bluetooth® allows for RTR, RTC, DV and IC bits to be exchanged over an RFCOMM connection.Nibble 0..3 species the source for RTC 4..7 species the source for RTR 8..11 species the source for DV (i.e. DCD) 12..15 species the source for IC (i.e. RI)Each nibble can take the following value:- 0 Always set to 0 1 Always set to 1 2 If DCD (pin 8 on module connector) is output then always 1 If DCD is input then 1 if DCD is asserted otherwise 0 3 If RI (pin 6) is output then always 0 If RI is input then 1 if RI is asserted otherwise 0 4 If DSR (pin 10) is asserted then 1 otherwise 0In the event that a nibble species DSR as the source of its state, be aware that if, 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. For example, Nokia 6310 stops responding.If this register is changed while in command and connected mode, then on going back online using the ATO command, a fresh signal will be sent to the peer to update the bits.S552 0x0122 0x0FFF This register species in each 4 bit nibble, how the DTR, DCD, RI output pins are controlled when in a Bluetooth connectionNibble 0..3 species the source for DTR 4..7 species the source for DCD 8..11 species the source for RIEach nibble can take the following value:- 0 Do NOT touch the I/O 1 Always deassert 2 Always assert 3 If RTC bit in CONTROL_IND is 1 then assert otherwise deassert 4 If RTR bit in CONTROL_IND is 1 then assert otherwise deassert 5 If DV bit in CONTROL_IND is 1 then assert otherwise deassert 6 If IC bit in CONTROL_IND is 1 then assert otherwise deassertIf this register is changed while in command and connected mode, then on going back online using the ATO command, the modem output lines will get refreshed.S553 0x0201 0x0FFF This register species in each 4 bit nibble, how the DTR,DCD,RI output pins are controlled when NOT in a Bluetooth connectionNibble 0..3 species the source for DTR 4..7 species the source for DCD 8..11 species the source for RIIn addition it also refers to S Register 552 to see if the relevant pin is an input or not to be touched. If the nibble in 552 is 0, then the relevant pin is an input.Each nibble can take the following value:- 0 Always deassert 1 Always assert 2 Assert if RING is being sent to the host
19 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 REGISTER DEFAULT RANGE COMMENTS554 0 0..900 If S Register 512>=2 and <=7 then this register species a time in seconds for which the device will stay in the S512 mode after power up or reset. On timeout, it will abort the discoverable and/or connectable and fall back into S512=1 mode, when it is deaf and dumb.Note that if AT+BTR has been used to specify a peer device, then on reverting to mode 1, it will attempt to make a connection to that peer device.A power cycle, reset via BREAK or ATZ is required to see the effects of change.S555 1 1..7 If S Register 554 is nonzero, then after the post reset window expires, the mode will revert to the mode specied in this register. This allows, for example, the device to be discoverable and connectable on power up (mode 4 or 7) and on window timer expiry to revert to connectable only (mode 3 or 6).A power cycle, reset via BREAK or ATZ is required to see effects of a change.In some rmware builds, S Registers 565 to 569 inclusive are visible, which allows the start-up mode to depend on the state of RI line (Setting S Reg 565 forces the RI pin to be congured as an input). For this feature to be active, SReg 565 should be set to 1. In that case, on start-up, if RI is asserted, then the start-up mode is dened by S Reg 568 and if deasserted then S Reg 569.S558 0 0..1 When 1, the following responses; “RING”, “NO CARRIER” and “CONNECT” are replaced by “BTIN”, “BTDOWN” and “BTUP” respectively. This will eliminate ambiguity when the module has a Bluetooth connection to an AT modem which also gives these responses.S559 0 0..3 This species a mask.When Bit 0 is 1, the response word “ERROR“ is replaced by “BTERR” and “OK” is replaced by “ok”. When Bit 1 is 1, then error responses do not include the error number and instead the error number can be retrieved using ATI12.S560 15 15..120 Disconnect timeout in seconds. This timer species how long to wait for conrmation from the peer device and/or the underlying stack that the connection has been successfully torn down. There can be instances where a conrmation does not arrive and so in this case this timer is used to ‘close off’ the procedure and put the state machine back into a proper mode for new operations.Time is specied with 15 seconds intervals.S565 0 1 If set to 1, RI (Ring Indicate) line is congured as an input and forces the start-up mode (SReg512) and post-timeout on Start-up mode (SReg555) to be dependent on the state of RI. The RI conditional modes are dened by SRegs 566 to 569 inclusive.S566 1 7 If S565=1, and RI is asserted then this is the mode the device will start up in.S567 1 7 If S565=1, and RI is deasserted then this is the mode the device will start up in.S568 1 7 If S565=1, and RI is asserted then this is the mode the device will assume after the post-start-up timeout dened in SReg 554 instead of mode dened in SReg555S569 1 7 If S565=1, and RI is deasserted then this is the mode the device will assume after the post-start-up timeout dened in SReg 554 instead of mode dened in SReg555S584 0 0..1 Enable/Disable eSCOWhen changing the unit returns ERROR 14 it implies the device is either in a connection or waiting for a connection and so the new value cannot be accepted. For the former, drop the connection, then issue the command AT+BTX and then set the new value and for the latter issue the command AT+BTX prior to setting the register.S588 0 0..1 After a disconnection, there will be a cold resetS589 15 0..22 Codec output gainS590 15 0..22 Codec input gainS591 0 0..1FF Default GPIO output states when not in a connection. This is used when virtual digital i/o cable replacement mode is in operation
20 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 REGISTER DEFAULT RANGE COMMENTS592 0 0..1 Set this to 1 to reduce the trusted device database to just 1 record when autosaving of pairing is enabled via S reg 538S593 0 0..1 Automatically append last 6 digits of local bluetooth address to the friendlyname which was set via AT+BTN or AT+BTFS689 0 -450..+215 Set codec output gain in dBr * 10(applies to sink), default = 0S690 0 -450..+215 Set codec input gain in dBr * 10(applies to source), default = 0S730 0 0..1 Enable Auxiliary DACS731 0 0..225 Set Auxiliary DAC Level 9. ATSn? {Read S Register Value} This will return the current value of register n. For recognised values of n Response: <cr,lf>As Appropriate<cr,lf>OK<cr,lf> For unrecognised values of n Response: <cr,lf>ERROR nn<cr,lf> 10. ATSn=? {Read S Register – Valid Range} This will return the valid range of values for register n. For recognised values of n Response: <cr,lf>Sn:(nnnn..mmmm)<cr,lf>OK<cr,lf> For unrecognised values of n Response: <cr,lf>ERROR nn<cr,lf> 11. ATZ<n> {Hardware Reset and emerge into mode ‘n’} Forces the device through a hardware reset which means it will eventually come alive in the local command and unconnected mode. This allows changes to the PS store to take effect. The module will issue an OK response after the reset is complete and it is ready to receive commands once again. ATZ and ATZ0 signify reset and emerge into the current mode (see command ATI14). ATZ1 to ATZ4 instructs the module to reset and then emerge into the appropriate boot mode. Note that S Reg 103 species the boot mode from cold. Response: <cr,lf>OK<cr,lf> and OK is returned after the RESET 12. AT&W {Write S Registers to Non-volatile Memory} Writes current S Register values to non-volatile memory so that they are retained over a power cycle. Response: <cr,lf>OK<cr,lf> Or Response: <cr,lf>ERROR nn<cr,lf>
21 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 13. ATIn {Information} This will return the following information about the Laird Technologies device. For recognised values of n. All other values of n will will return the manufacturer details. Response: <cr,lf>As Appropriate<cr,lf>OK<cr,lf> Or Response: <cr,lf>ERROR nn<cr,lf>I0 The product name/variant.I1 The CSR rmware build number.I2 The Laird Technologies rmware build number. For internal use only.I3 The Laird Technologies rmware revision.I4 A 12 digit hexadecimal number corresponding to the Bluetooth address of the device.I5 The manufacturer of this device.I6 The maximum size of trusted device database.I7 The manufacturer of the Bluetooth chipset.I8 The chipset format.I9 0 if not in a connect state and 1 if in a connect state.I11 The reason why a “NO CARRIER” resulted in the most recent attempt at making an outgoing connection. Where the response values are as follows: 0 = No prior connection 1 = Connection timeout 2 = Connection attempt cancelled 3 = Normal disconnection 4 = Peer device has refused connection 5 = Service prole <uuid> requested not available on remote device 6 = Connection has failed 32 = ATH was entered 33 = Incoming connection aborted because too many rings 34 = Unexpected incoming connection 35 = Invalid address 36 = DSR is not asserted 37 = Call limit of 65531 connections has been reached 38 = Pairing in progress 39 = No link key 40 = Invalid link key 255 = Unknown ReasonI12 The last ERROR response number.I60 Connection status of SPP 0 = not connected 1 = connected identical with ATI9I61 Connection status of A2DP 0 = not connected 1 = connectedI62 Connection status of AVRCP 0 = not connected 1 = connected
22 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia Module 14. ATO {Enter Data Mode} (letter ‘o’) Return to data mode. Assume that the module is in data mode after OK is received. Responds with an error if there is no Bluetooth connection. Response: <cr,lf> CONNECT 123456789012<cr,lf> Or Response: <cr,lf>ERROR nn<cr,lf> 15. AT&Fn {Set S Register Defaults} This command will only work when the device is in local command and unconnected mode. Depending on the value of ‘n’ it installs S Register values appropriate for various power modes, ranging from minimum power consumption to maximum. Legal values of ‘n’ are as per the following table. All other values of n will generate a syntax error response. If ‘n’ is not specied then a default value of 0 is assumed where the baud rate is NOT changed. The new values are NOT updated in non-volatile memory until the AT&W command is sent to the device. Response: <cr,lf>OK<cr,lf> Or Response: <cr,lf>ERROR nn<cr,lf>General Bluetooth Control 1.AT+BTAn{ControlAudioChannel} Once a Bluetooth connection is active, and assuming the peer device is also a Laird Technologies device, this command is used to start/stop a SCO channel to transfer audio between the two peer devices. The value N is a bit mask indicating the packet type to be used on the SCO link If n is set to 0 the SCO channel is disabled. On receipt of the command, the following response immediately follows. Response: <cr,lf>OK<cr,lf> The lower layers then go through the process of setting up the SCO channel, and as soon as a SCO link is established, the following response is asynchronously sent to the host. Response: <cr,lf>AUDIO ON<cr,lf> Or if the SCO failed to be established. Response: <cr,lf>AUDIO FAIL<cr,lf> On the peer device, the host will asynchronously get …. Response: <cr,lf>AUDIO ON<cr,lf>CONFIGURING THE BTM510/511&F0 (Default) Medium power consumption, UART baud rate unchanged.&F1 Minimum power consumption, UART baud rate set to 9600.&F2 Minimum power consumption, UART baud rate set to 38400. &F3 Minimum power consumption, UART baud rate set to 115200. &F4 Medium power consumption, UART baud rate set to 115200. &F5 Maximum power consumption, UART baud rate set to 115200. &F6 Maximum power consumption, UART baud rate set to 115200.Bit 0 HV1Bit 1 HV2Bit 2 HV3Bit 3 - 14 Unused, set to zeroBit 15 ESCO
23 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 2.AT+BTC<devclass>{SetDeviceClassCode} This command is used to set the device class code which will be sent in subsequent inquiry responses. It can be read back using the AT+BTC? Command, as described below. The device class setting is valid until the module is reset or power cycled. <devclass> is a 6 digit hexadecimal number derived as per section “1.2 The Class of Device/Service Field” of the Bluetooth specication “Bluetooth Assigned Numbers”. The 24 bits are made of 4 elds briey described as follows (bit 0 corresponds to the least signicant bit):- Laird Technologies devices do not map to any predened Major Service Class or Major Device Class and so the default devclass as shipped is 001F00, which means no Major Service Class and “Unclassied” Major Device class. Other examples of device class codes are follows:- Response: <cr,lf>OK<cr,lf> Or for an invalid <devclass> value (usually a value which is not 6 hexadecimal characters long). Response: <cr,lf>ERROR 08<cr,lf> 3.AT+BTC?{ReadDeviceClassCode} This command is used to read the current device class code. Response: <cr,lf>123456 <cr,lf>OK<cr,lf> 4.AT+BTD<bd_addr>{RemoveTrustedDevice} This command is used to remove the specied device from the list of trusted devices in the non-volatile database. If the device is not in the database then the response will still be an OK. Response: <cr,lf>OK<cr,lf> 5.AT+BTD*{RemoveAllTrustedDevices} This command is used to remove all devices from the list of trusted devices in the non-volatile database. No conrmation will be asked for. So beware!!! WARNING: If you make an authenticated connection, the link key gets cached in the underlying stack. So if you subsequently delete the key using AT+BTD* and immediately request an authenticated connection to the same device, then the connection will be established. To ensure this does not happen, either send ATZ after the AT+BTD* OR send AT+BTD<bd_addr> for each item in the trusted device database. Response: <cr,lf>OK<cr,lf> 6.AT+BTF=<string>{SetFriendlyName} This sets the friendly name of this device as seen by other devices. The friendly name specied in this way is valid until the next reset or power cycle. To set a permanent friendly name use AT+BTN. Response: <cr,lf>OK<cr,lf>Bits 0-1 Format Type. This eld currently only has a value of 00 (i.e. format type 1)Bits 2-7 These 6 bits dene the Minor Device Class and the value is interpreted differently based on the Major Device class stored in the next 5 bits.Bits 8-12 These 5 bits dene the Major Device Class as per Table 1.3 in “Bluetooth Assigned Numbers”Bits 13-23 This is an 11 bit eld used as a mask to dene the Major Service Class, as per Table 1.2 in “Bluetooth Assigned Number”CODE (HEXADECIMAL) NAME MAJOR SERVICE MAJOR DEVICE MINOR DEVICE001F00 Unclassied None Unclassied n/a200404 Headset Audio Audio Headset
24 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 7.AT+BTF<bd_addr>{GetRemoteFriendlyName} This command gets the remote friendly name of the peer specied. Response: <cr,lf><bd_addr>,”Friendly Name” <cr,lf>OK<cr,lf> 8.AT+BTG<bd_addr>{EnableCautiousPageScanningONLY} Make device connectable and wait for a connection from device with Bluetooth address <bd_addr>. If the specied address is 000000000000 then incoming connections are accepted from any device, is as per AT+BTP without an address. Inquiry Scans are disabled. Response: <cr,lf>OK<cr,lf> 9.AT+BTG{EnablePromiscuousPageScanningONLY} Enable page scanning only and wait for a connection from any device. Inquiry scans are disabled. Response: <cr,lf>OK<cr,lf> 10.AT+BTI<devclass>{Inquire} This will make the device perform an inquiry for device class code for delay seconds and max number of unique responses, where delay is specied by S register 517 and max is specied by S register 518. The <devclass> is an optional parameter where the value species either a 6 digit device class code or a 2 digit major device class. If it is not specied, then the value is taken from S register 516. When <devclass> is 6 hexadecimal characters long, it species an AND mask which is used to lter inquiry responses. When <devclass> is 2 hexadecimal characters long, it forces the inquiry to lter responses to devices that match their major device class code to this value – which can only be in the range 00 to 1F. Response: <cr,lf>12346789012 <cr,lf>12345678914 <cr,lf>OK<cr,lf> If the module is waiting for an incoming connection, (entered via AT+BTP, AT+BTG, AT+BTQ), then it will respond with ERROR 14. To perform the inquiry, send AT+BTX to put the module back into idle mode. Response: <cr,lf>ERROR 14<cr,lf> ERROR RESPONSE A Bluetooth inquiry process is such that for a single inquiry request a device could respond many times. To ensure that an address is sent to the host only once for a particular AT+BTI, an array of addresses is created at the start of each AT+BTI and is lled as responses come in. This array of addresses is stored in dynamic memory and as such if the memory allocation fails then the inquiry procedure is aborted and in that case an error response is sent to the host. To clarify, a single AT+BTI will never return the same Bluetooth address more than once, but as long as the responding device is active, all AT+BTI commands will always return it. Response: <cr,lf>ERROR 27<cr,lf> 11.AT+BTIV<devclass>{Inquire} As per AT+BTI but the response includes the device class code for all inquiry responses. Please refer to the ‘ERROR RESPONSE’ note in the description for AT+BTI<devclass>. Response: <cr,lf>12346789012,123456 <cr,lf>12345678914,123456 <cr,lf>OK<cr,lf>
25 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 12.AT+BTIN<devclass>{Inquire} As per AT+BTI but the response includes the device class code and friendly name for all inquiry responses. Please refer to the ‘ERROR ESPONSE’ note in the description for AT+BTI<devclass>. The friendly name strings are in UTF-8 format as per the Bluetooth specication. Response: <cr,lf>12346789012,123456,”TDK SYSTEMS AT DONGLE 1” <cr,lf>12345678914,123456, “TDK SYSTEMS RS232” <cr,lf>OK<cr,lf> Note: Many releases of rmware will return the product name as LAIRD, e.g. Response: <cr,lf>12346789012,123456,”Laird BTMM 789012” <cr,lf>12345678914,123456, “TDK SYSTEMS RS232” <cr,lf>OK<cr,lf> We strongly recommend that any software implementation that uses this command should check for LAIRD, EZURIO and TDK SYSTEMS to ensure backwards and forwards compatibility. 13.AT+BTK=<string>{SetPasskey} This command is used to provide a passkey when PIN? 12345678 indications are received asynchronously. If a pairing is not in progress then the pin is written to non-volatile memory for future use. Specifying an empty string deletes the key from the non-volatile memory. The string length must be in the range 0 to 8, otherwise an error will be returned. Response: <cr,lf>OK<cr,lf> 14.AT+BTM<bd_addr>{SetIncomingPeerAddress} This command is used to set the peer address. Response: <cr,lf>OK<cr,lf> 15.AT+BTM{DeleteIncomingPeerAddress} This command is used to delete the peer address previously stored using AT+BTM<bd_addr>. Response: <cr,lf>OK<cr,lf> 16.AT+BTM?{ReadIncomingPeerAddress} This command is used to display the peer address stored in non-volatile memory, used to put the module in pure cable replacement mode. Response: <cr,lf>12346789012 <cr,lf>OK<cr,lf> If the location is empty the response is as follows. Response: <cr,lf>00000000000 <cr,lf>OK<cr,lf> 17.AT+BTN=<string>{SetFriendlyNameinNon-volatileMemory} This sets the default friendly name of this device as seen by other devices. It will be stored in non-volatile memory. Use AT+BTF to make the name visible to other devices. Use AT+BTN? To read it back. The friendly name programmed in this way will only be used AFTER the device has been reset (ATZ) or power cycled. To set a temporary friendly name for immediate use, use the AT+BTF command. An empty string (“”) will delete the string from non-volatile memory which will force the default name to be used. Response: <cr,lf>OK<cr,lf>
26 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 18.AT+BTN?{ReadFriendlyNamefromNon-volatileMemory} Read the default friendly name from non-volatile memory. Response: <cr,lf>”My FriendlyName”<cr,lf> <cr,lf>OK<cr,lf> 19.AT+BTP<bd_addr>{EnableCautiousPage/InquiryScanning} Enable page scanning and wait for a connection from device with Bluetooth address <bd_addr>. If the specied address is 000000000000 then incoming connections are accepted from any device, is as per AT+BTP without an address. Inquiry scanning is also enabled. Response: <cr,lf>OK<cr,lf> 20.AT+BTP{EnablePromiscuousPage/InquiryScanning} Enable page scanning and wait for a connection from any device. Inquiry scanning is also enabled. Response: <cr,lf>OK<cr,lf> 21.AT+BTQ{EnableInquiryScansONLY} When inquiry scan is enabled, it implies that this device will respond to inquiries from other devices. Use AT+BTX to disable inquiries. Response: <cr,lf>OK<cr,lf> 22.AT+BTR<bd_addr>{SetOutgoingPeerAddress} This command is used to store a peer address for outbound connections in non-volatile memory. A value of 000000000000 has the special meaning of invalid peer address. This command is used to set up a module in pure cable replacement mode. If S register 512 = 1 and the peer address is NOT 000000000000, then it will periodically (time specied via S register 505) attempt to connect to the peer address specied. In this circumstance all commands from the host are buffered in the receive buffer, until a Bluetooth connection is established with the peer device and it then sends the buffer across. This means that if the peer device is not in the vicinity and will never be there, the device effectively becomes useless, as in this circumstance a host would want to get attention of the AT parser to send it new commands – probably one to delete the peer device. In this circumstance, a recovery is possible by one of two methods. The rst method assumes that the DTR from the host is connected to the DSR line of the module and the second method assumes that this connection is absent. In the rst method it is enough to deassert the DTR line from the host and that will abort the autoconnect cycle. The second method is initiated by resetting the device and then ensuring that the text string “AT+BT&BISM&<cr>” is sent (where <cr> is the carriage return character). There is special code which looks out for this magic command and terminates the autoconnect cycle if it sees it and conrms to the host of that fact by sending an “OK” response. Response: <cr,lf>OK<cr,lf> 23.AT+BTR{DeleteOutgoingPeerAddress} This command is used to delete the peer address previously stored using AT+BTR<bd_addr>. Response: <cr,lf>OK<cr,lf> 24.AT+BTR?{ReadOutgoingPeerAddress} This command is used to display the peer address stored in non-volatile memory, used to put the device in pure cable replacement mode. Response: <cr,lf>123456789012 <cr,lf>OK<cr,lf> If the location is empty the response is as follows. Response: <cr,lf>00000000000 <cr,lf>OK<cr,lf>
27 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 25.AT+BTT{AddTrustedDevice} This command is used to store the cached link key in the non-volatile database. If the database is full it will respond with an ERROR. If the device is already in the database, then the key is replaced. If the link key cache is empty, that is, a pairing has not been performed since the device was powered, then the response will be an ERROR. Response: <cr,lf>OK<cr,lf> Or Response: <cr,lf>ERROR<cr,lf> 26.AT+BTT?{ListTrustedDevice} This command is used to list the contents of the trusted device database. The link key is NOT displayed so the response is as shown below. If the list is empty then just the OK response is sent otherwise an OK is used to terminate the list. Use the command ATI6 to read the maximum size of the trusted device database. Response: <cr,lf>12346789012 <cr,lf>123456789013 <cr,lf>123456789014 <cr,lf>OK<cr,lf> 27.AT+BTW<bd_addr>{InitiatePairing} This initiates pairing with a device whose Bluetooth address is <bd_addr>. An OK response is sent and when the PIN is required, asynchronous indications will be sent to the host in the form PIN? <bd_addr> where the address conrms the device with which the pairing is to be performed. To supply a PIN, use the AT+BTK command. For a successful pairing, the link key is stored in a volatile cache which is overwritten every time a new pairing is initiated using this command. The link key can be stored in a non-volatile database within the device. The list of trusted devices is managed using commands AT+BTT?, AT+BTT and AT+BTD. The AT+BTT? command produces a list of trusted Bluetooth addresses (link key is NEVER displayed) and AT+BTT is used to store the cached link key. The command AT+BTD123456789012 is used to remove the specied device from the database. The “OK” response is sent immediately on receipt of the AT+BTW command. On pairing completion, an unsolicited message will be sent to the host which will be in the form PAIR n <bd_addr>. See section 3.7 for more details. If AT+BTI or AT+BTP or AT+BTG or AT+BTQ or ATD is issued between the AT+BTW command and the subsequence PAIR asynchronous response, then an ERROR response will be sent to those commands as the device is not in a mode from where such commands can be actioned. Response: <cr,lf>OK<cr,lf> 28.AT+BTW?{ListCachedTrustedDevice} This command is used to list the cached trusted device. Response: <cr,lf>12346789012 <cr,lf>OK<cr,lf> If the cache is empty the response is as follows. Response: <cr,lf>OK<cr,lf> 29.AT+BTX{DisablePage/InquiryScanning} Disable page/inquiry scanning. This means it will not accept incoming connections or inquiry requests. In fact this negates the effect of AT+BTQ, AT+BTG and AT+BTP commands. Response: <cr,lf>OK<cr,lf>
28 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511Hardware Unit ControlThis section covers S-Registers and AT-Commands that are related to hardware units within the module. 1. Audio Loopback Mode For testing purposes, an audio loopback mode will be introduced. The stereo audio input signal is fed through the Kalimba DSP with running SBC codec, and is directed back to the audio stereo output. Audio Loopback Mode is controlled with the new AT Command “AT+BTL”. 2.CodecGain On BC05-MM, analogue input and output gains can be set to one of 23 steps called “Gain Level”. To each gain level, an overall gain (dBr) is assigned, according to Table 3 3: Gain Table. Gain values can be specied either as gain level or as overall gain by separate S Registers. Please note that a pair of such S-Registers always updates the other corresponding S-Register (e.g. S589 – S689 and S590 – S690). For S689 and S690 the overall gain (dBr) must be entered multiplied by 10. If the input value doesn’t match a gain table entry, the nearest possible value is set. The actually set value can be checked by reading back S689/S690. The value of S689/S690 is printed out multiplied by 10 in order to avoid non integer numbers. The command class “AT+G….” allows incremental / decremental control of codec gain settings. The increment/decrement command corresponds to one row up/down in the gain table (Table 3 3). The Gain level registers S589/S689 and S590/S690 are not affected by increment/decrement commands. Instead, the current gain level is cached and can be retrieved by “AT+G(I|O)?”. There are 2 further commands to restore the cached gain level from S589/S590 (“AT+G(I|O)R”) and to save the currently cached gain level to S589/S590 (“AT+G(I|O)S”).Table 3-2: Audio Loopback AT-Commands and S-RegistersTASK AT-COMMAND / SREGISTER COMMENTSet audio loopback mode AT+BTL<Mode> Mode: 0 = off 1 = on, via PCM 2 = on, via SBC encoder/decoderSet sampling rate for Audio Loopback ModeS419 [0..6], default=6 0 = 8 kHz 1 = 11.025 kHz 2 = 16 kHz 3 = 22.050 kHz 4 = 24 kHz 5 = 32 kHz 6 = 44.1 kHz
29 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511Table3-3:GainTableOUTPUT GAIN LEVEL OR INPUT GAIN LEVEL S589 OR S590OVERALL GAIN (DBR) S689 OR S69022 +21.5 21 +18.0 20 +15.5 19 +12.0 18 +9.5 17 +6.0 16 +3.5 15 0 14 -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 TASK AT-COMMAND / SREGISTER COMMENTSet output gain level S589 [0..22], default=15 See Gain Table; S689 is affected, tooSet output overall gain (dBr) S689 [-450..+215], default=0 See GainTable; value must be entered (and is returned) multiplied by 10; S589 is affected, tooSet input gain level S590 [0..22], default=15 See Gain Table; S690 is affected, tooSet input overall gain (dBr) S690 [-450..+215], default=0 See GainTable; value must be entered (and is returned) multiplied by 10; S590 is affected, tooIncrement current output gain levelAT+GOU Error 57 may appear if maximum gain level reachedDecrement current output gain levelAT+GOD Error 58 may appear if minimum gain level reachedQuery current output gain level AT+GO?Restore current output gain level from S589AT+GORSave current output gain level to S589AT+GOSIncrement current input gain levelAT+GIU Error 57 may appear if maximum gain level reachedDecrement current input gain levelAT+GID Error 58 may appear if minimum gain level reachedQuery current input gain level AT+GI?Restore current input gain level from S590AT+GIRSave current input gain level to S590AT+GISTable3-4:GainSettingsATCommandsandS-Registers
30 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 3.MicInputGain A microphone preamplier which adds extra 20dB to input gain, is controlled by S-Register 415. 4.MicBias Mic Bias will be enabled with S-Register 416. Mic Bias Current is controlled by S-Register 417. Mic Bias Voltage is controlled by S-Register 418. 5. Auxiliary DAC The auxiliary DAC is enabled with S-Register 730. The DAC output level is set by S-Register 731. 6. LED The BT-MM module provides two dedicated output pins for LEDs (LED_EXT0, LED_EXT1). Following modes are supported: LED_OFF, LED_ON, LED_PWM and LED_PULSE. In LED_PWM mode, the parameters “Duty Cycle” an “PWM Period” can be specied via S-Registers. This enables the user to either dim the brightness of an LED (PWM Period=0) or to specify blinking with dened on-time in a dened period (PWM Period > blinking visible for the eye) In LED_PULSE mode, the brightness of an LED is modulated. Modulation speed is dened by parameter “Pulse Rate” and maximum brightness is dened by parameter “Duty Cycle”.Bluetooth ProlesThis section covers S-Registers and AT-Commands that are related to the supported Bluetooth Proles on the BT-MM module. 1.ProleServerActivation In order to advertise available services to potential client devices, S-Register 102 is used. Supported proles can be activated by setting the appropriate Flag in S-Register 102 (see Table 3 1). After S-Register 102 has been written, all S-Registers must be saved to non-volatile memory (“AT&W”) and subsequently a reset has to be carried out (“ATZ”). 2.A2DP The “Advanced Audio Distribution Prole” is used to transmit high quality audio streams between two Bluetooth devices. An A2DP role must be assigned to a BT-MM module, either source or sink. After this has been done, the appropriate service can be advertised. An attempt to advertise A2DP-service without prior set up of a role will result in a (new) response error code 46. An incoming A2DP connection request is accepted automatically if a valid link key for the paging device exists. If no link key is available, Secure Simple Pairing (SSP, BT2.1) or legacy pairing (BT2.0 or earlier) is carried out, depending on the Bluetooth Version of the paging device. After an A2DP connection has been established, the module remains in AT Command mode. S Register 531 is ignored for A2DP connections.Table 3-5: LED S-RegistersTASK AT-COMMAND / SREGISTER COMMENTSet LED_EXT0 mode S335 [0..3], default=0 Mode: 0 = LED_OFF 1 = LED_ON 2 = LED_PWM 3 = LED_PULSESet LED_EXT1 mode S340 [0..3], default=0Set LED_EXT0 Duty Cycle S336 [0..4095], default = 2048 referenced if LED mode = LED_PWM or LED_PULSESet LED_EXT1 Duty Cycle S341 [0..4095], default = 2048Set LED_EXT0 PWM Period S337 [0..15], default = 0 referenced if LED mode = LED_PWMSet LED_EXT1 PWM Period S342 [0..15], default = 0Set LED_EXT0 Pulse Rate S338 [0..15], default = 0 referenced if LED mode = LED_PULSESet LED_EXT1 Pulse Rate S343 [0..15], default = 0
31 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511Table3-6:A2DP-S-RegistersandAT-CommandsTASK AT-COMMAND / SREGISTER COMMENTSet A2DP role S300 [0..2] 0 = feature not set 1 = A2DP Sink (default) 2 = A2DP SourceAdvertise service S102 128 = A2DP, Error 46 if A2DP role has not been set (see S300)Initiate outgoing A2DP connectionAT+APD<bd_addr> Response if accepted: “CONNECT 0123456789012,110D” Response if rejected: “NO CARRIER 110D”close only A2DP connection “AT+APH” or “ATH110D” Response: “NO CARRIER 110D” if connection has existed and S329=0 “NO CARRIER” if connection has not existed and S329=0close all connections ATH* Response: “NO CARRIER <proleUUID>” for each prole that was previously connected (see section 3.7.2)Set gain level S589 [0..22], default = 15 Set codec output gain level (applies to sink)S590 [0..22], default = 15 Set codec input gain level (applies to source)Set overall gain (dBr * 10) S689 [-450..215] Set codec output gain in dBr * 10 (applies to sink), default = 0S690 [-450..215] Set codec input gain in dBr * 10 (applies to source), default = 0Set A2DP sink supported features bit maskS312 [0..15] Bitmask - sink supported features: Bit 0 = Headphone (default) Bit 1 = Speaker Bit 2 = Recorder Bit 3 = AmplierSet A2DP source supported features bit maskS313 [0..15] Bitmask - source supported features: Bit 0 = Player (default) Bit 1 = Microphone Bit 2 = Tuner Bit 3 = Mixer 3.AVRCP The “Audio/Video Remote Control Prole” is used to remotely control audio or video streaming devices. A device must be dened as either control or target. Furthermore, one of four categories (Player/Recorder, Monitor/Amplier, Tuner, Menu) has to be assigned to a device. The AVRCP specication [5] adopts the AV/C Digital Interface Command Set (AV/C command set, dened by the 1394 Trade Association) device model and control message format. In this device model a remote control target consists of one or more subunits. At least the subunit ”PANEL” must exist. Remote control commands are passed to a subunit with the “PASS THROUGH” command. A BT-MM Module, congured as target will support one PANEL subunit. 3.1 AVRCP-Control(CT) This section describes AT Commands and S registers used when BT-MM is congured as an AVRCP Controller (S301=1).
32 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511    3.1.1 InitiateAVRCPcontrolconnection AT+AVD<bd_addrhex> Initiate AVRCP control connection to Bluetooth address <bd_addrhex>. The module must be congured as AVRCP Control by S register 301 = 1. Furthermore a category must be selected in S register 302. Response: <cr,lf>CONNECT 123456789012,110E<cr,lf> Or: <cr,lf>NO CARRIER 110E<cr,lf> Or: <cr,lf>ERROR 47<cr,lf> Or: <cr,lf>ERROR 48<cr,lf> After an AVRCP connection has been established, the module remains in AT command mode. S Register 531 is ignored for AVRCP connections. 3.1.2 ReleaseAVRCPcontrolconnection      AT+AVH Release AVRCP control connection. Response: <cr,lf >NO CARRIER 110E<cr,lf> 3.1.3 SendUNITINFORequest      AT+AVU Send a Unit Info request to a connected AVRCP target. Response immediately: <cr,lf>OK<cr,lf> On command completion: <cr,lf>AVUR <n> <unit_idhex> <unit_typehex> <company_idhex><cr,lf> n = statusdec : 0 – success 1 – fail 4 – timeout For unit_type see Table 3 9: AV/C Unit/Subunit Types. 3.1.4 SendSUBUNITINFORequest(incomplete)      AT+AVS<pagedec> Send a Subunit Info request to a connected AVRCP target. Response: <cr,lf>OK<cr,lf> (immediately) And: <cr,lf>AVSR <pagedec> <pagedatahex> <cr,lf> (after command completion) <pagedec> : requested page [0..31] <pagedatahex> : 1st word of requested page
33 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 3.1.5 Send remote control command      AT+AVC<operation_idhex>,<button_state> Send a remote control command to a connected AVRCP target. Internally, a PASS THROUGH command is created and sent to the PANEL subunit of the AVRCP target. <operation_idhex> is the value for the actual remote control command. Valid values are specied in Table 3 8. Some Operation IDs can be replaced by mnemonics, see Table 3 8. <button_state> represents “Button pushed” (=0) or “Button released” (=1) If <button_state> is not specied, two PASS THROUGH commands, each with button_state=0 and button_state=1 will be created and sent consecutively. The “OK” response is sent immediately on receipt of AT+AVC command. On command completion, an unsolicited message will be sent to the host in the form “AVPTC n <bd_addr> <button_state>”. AVPTC means “AVrcp Pass Through Conrmation”. Parameter n indicates the command status: ‘n’=0: successful, command conrmation received from target ‘n’=1: timeout, target has not sent conrmation within the specied maximum time ‘n’=2: all other unsuccessful outcomes Parameters: <operation_idhex> (mandatory): see Table 3 8 <button_state> (optional) : ‘0’ - Button pushed ‘1’ - Button released Response: <cr,lf>OK<cr,lf> (immediately) And: <cr,lf>AVPTC n <operation_idhex> <button_state><cr,lf> (after command completion) If status n indicates an unsuccessful outcome,<operation_idhex> and <button_state> are omitted. 3.2 AVRCP–Target(TG) This section describes AT Commands and S registers when BT-MM is congured as an AVRCP Target (S301=2). In this mode, BT-MM supports one subunit PANEL (see [5]).    3.2.1 IncomingAVRCPConnectionRequest An incoming AVRCP connection request is accepted automatically if a valid link key for the paging device exists. If no link key is available, Secure Simple Pairing (SSP, BT2.1) or legacy pairing (BT2.0 or earlier) is carried out, depending on the Bluetooth Version of the paging device. After an AVRCP connection has been established, the module remains in AT command mode. S Register 531 is ignored for AVRCP connections. 3.2.2 UNIT INFO Response It is mandatory to respond to a UNIT INFO command if congured as AVRCP target. Required response parameters are IEEE Company ID and a Unit Type. The IEEE Company ID is a 24 bit integer which can be set via new S register 303. In the current revision of BT-MM rmware, subunit “Panel” (=0x09) will be returned always. Values of unit/subunit types are outlined in Table 3 9.    3.2.3 SUBUNITINFOResponse It is mandatory to respond to a SUBUNIT INFO command if congured as AVRCP target. Required response parameters are Subunit type and MaxSubUnitId. Subunit type will always be returned as 0x09 (Panel). MaxSubUnitId will always be returned as 0x00 (only one subunit exists, which is panel)
34 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511    3.2.4 PASSTHROUGHIndication An incoming PASS THROUGH command will be indicated by an unsolicited message AVPTI <subunit_idhex> <operation_idhex> <button_state> For subunit_idhex see Table 3 9. For operation_idhex see Table 3 8. <button_state>: ‘0’ is Button pushed ‘1’ is Button released    3.2.5 PASSTHROUGHResponse AT+AVR<avrc_response_typehex> If S register 310 = 0, a Pass Through (PT) response is required from the host. The response is sent with: AT+AVR<avrc_response_typedec> Parameter: <avrc_response_typedec>: see Table 3 10, write-value. If S register 310 == 1, a Pass Through response is sent automatically with an <avrc_response_type> congured by S register 311. In this case, the host is not required to respond.Table3-7:AVRCP-S-RegistersandAT-CommandsTASK AT-COMMAND / SREGISTER COMMENTSet AVRCP role S301 [0..2] 0 = disabled 1 = Control “CT” (default) 2 = Target “TG”Set AVRCP category S302 [0..4] 0 = Feature disabled (default) 1 = Player/Recorder 2 = Monitor/Amplier 3 = Tuner 4 = MenuSet Company Id S303 [0..0xFFFFFF] IEEE Company ID, 24bit hexadecimal,Required for UNIT INFO Response in AVRCP target mode, default value is 0.Enable Unit Info Response S305 [0..1] default = 1Enable Subunit Info Response S306 [0..1] default = 1Congure PASS THROUGH (PT) ResponseS310 [0..1] 1 = Enable automatic PT-response, response type is read from S311, (default) 0 = Host is required to respond to PT-Indication, see ‘AT+PTR’Set automatic response typeS311 [0.. 7] This value is queried for automatic PT-Response, see Table 3 10 Default value is “accepted” 1w/ 9rAdvertise service S102 256 = AVRCP, Error 47 if AVRCP role has not been set (see S301); Error 48 if S301== 2 and Category has not been set (see S302)Initiate outgoing AVRCP control connectionAT+AVD<bd_addr> Response if accepted: “CONNECT 0123456789012,110E” Response if rejected: “NO CARRIER 110E”Close only AVRCP con-nection“AT+AVH“ or “ATH110E” Response: “NO CARRIER 110E” if connection has existed and S329=0 “NO CARRIER” if connection has not existed and S329=0Close all connections ATH* Response: “NO CARRIER <proleUUID>” for each prole that was previously connected (see Miscellaneous section 2)Send a Unit Info request AT+AVUSend a Subunit Info requestAT+AVS (incomplete!)Send remote control com-mandAT+AVC<operation_idhex>,<state><operation_id>: see Table 3 8, mnemonics possible instead of hexval <state> (optional): ‘0’ Button pushed ‘1’ Button released Response on command completion: “AVPTC n <operation_idhex> <state>”Respond to incoming Pass Through commandAT+AVR<avrc_response_typehex> <avrc_response_typehex>: see Table 3 10 If S 310 == 1, response from host is not required.
35 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511Table3-8:AVRCP-OperationIDandMnemonicforRemoteControlCommandsCOMMAND OPERATION ID MNEMONICSelect 0x00Up 0x01Down 0x02Left 0x03Right 0x04Right up 0x05Right down 0x06Left up 0x07Left down 0x08Root menu 0x09Setup menu 0x0AContents menu 0x0BFavourite menu 0x0CExit 0x0D0 0x201 0x212 0x223 0x234 0x245 0x256 0x267 0x278 0x289 0x29Dot 0x2AEnter 0x2BClear 0x2CChannel up 0x30Channel down 0x31Sound select 0x32Input select 0x33Display information 0x34Help 0x35Page up 0x36Page down 0x37Power 0x40Volume up 0x41Volume down 0x42Mute 0x43Play 0x44 PLAYStop 0x45 STOPPause 0x46 PAUSERecord 0x47Rewind 0x48 REWINDFast forward 0x49 FFORWARDEject 0x4AForward 0x4B FORWARDBackward 0x4C BACKWARDAngle 0x50Sub picture 0x51F1 0x71F2 0x72F3 0x73F4 0x74F5 0x75Vendor unique 0x7e
36 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511Table 3-9: AV/C Unit/Subunit TypesUNIT / SUBUNIT TYPE VALUEMonitor 0x00Audio 0x01Printer 0x02Disc 0x03Tape recorder player 0x04Tuner 0x05CA 0x06Camera 0x07Reserved 0x08Panel 0x09Bulletin board 0x0ACamera storage 0x0BVendor unique 0x1CReserved for all 0x1DExtended 0x1EUnit 0x1FTable 3-10: AVRC Response TypesAVRC RESPONSE TYPE READ-VALUE (S311, SENT IN RESPONSE)WRITE-VALUE (S311)Not implemented 8 0Accepted 9 1Rejected 10 2In transition 11 3Stable 12 4Changed 13 5Interim 15 6Bad prole 16 7Table3-11:AVRCPUnsolicitedMessagesMESSAGE COMMENTCONNECT 123456789012 110E’ AVRCP control connection established‘123456789012’ – bd_addr of peer device ‘110E’ – UUID indicating AVRCPNO CARRIER 110E AVRCP connection rejected or closedNO CARRIER All Connections closedAVUR <n><unit_idhex><unit_typehex> <company_idhex> AV Unit Info Response, sent in response to AT+AVU (UNIT INFO Request),<n>: statusdec 0 - success 1 - Fail 2 - Timeout <unit_idhex>: Unit ID <unit_type>: see Table 3 9 <company_id>: IEEE Company IDAVSR AV Subunit Info Response, sent in response to AT+AVS (SUBUNIT INFO Request), incompleteAVPTI <subunit_idhex> <operation_idhex> <state> Indication of incoming Pass Through command <subunit_idhex>: subunit id <operation_idhex>: see Table 3 8 <state>: ‘0’ – Button pushed ‘1’ – Button releasedAVPTC n <operation_idhex> <state> Conrmation of AT+AVC (Control Command Request) n: ‘0’ – successful ‘1’ – timeout ‘2’ – not successful, other than timeout
37 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511SECURE SIMPLE PAIRING (SSP)Secure Simple Pairing is supported on the BT-MM module. A set of S Registers provides conguration capabili-ties for SPP: • Security Level – S320 • IO-Capability – S321 • Force man-in-the-middle-protection (MITM) – S322 • Disable legacy pairing – S323 For details see Table 3 1.LINK KEY MANAGEMENTOn BT-MM link keys are managed by the AT rmware. 1.DedicatedBonding In BT2.1 specication, “dedicated bonding” is dened as the exchange of link keys between two devices without the intention of establishing a connection immediately. Dedicated bonding is initiated by “AT+BTW<BdAddr>” (initiation of pairing). 2.GeneralBonding In BT2.1 specication, “general bonding” is dened as the exchange of link keys between two devices with the intention of establishing a connection immediately. This is the case if a device wants to connection to another device without existing link key. Hence, pairing (authentication and exchange of link keys) is initiated automatically prior to the connection. General bonding is initiated by “ATD<BdAddr>”, “AT+APD<BdAddr>”, “AT+AVD<BdAddr>” if there are no link keys for the peer device existing. 3.LegacyIssues(BT2.0) There are some special cases if a legacy device (BT2.0 or earlier, e.g.BISM2) requests a connection to a BT-MM (BT2.1) module. General bonding does not work if initiated by the legacy device. Instead, the legacy device must initiate dedicated bonding rst (for example on BISM2 the command “AT+BTW<BdAddr>” would be used). After successful pairing, the connection can be initiated by the legacy device (for example on BISM2 the “ATD<BdAddr>” command would be used).
38 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511MISCELLANEOUS 1.ProleConnectionStatus The connection status of a prole can be queried by an ATI-Command. This might be helpful in order to decide whether to disconnect all connected proles (via ATH*) or a certain one. For details please see Table 3 12. 2.DisconnectingProles A connection to a prole can be released by “ATH<Prole-UUID>” or by using the prole specic disconnect command. The response on a disconnect command is “NO CARRIER <proleUUID>”. If no connection existed then the proleUUID is omitted. If all connections are to be released, ATH* may be used. Please see Table 3 13. 3.ProductionInfoString A string with production information can be retrieved by “ATI200”.Table3-13:ProleReleaseCommandsTASK AT-COMMAND COMMENTDisconnect A2DP ATH110D orAT+APH If A2DP connection released: response = “NO CARRIER 110D”; If no A2DP connection has existed: response = “NO CARRIER”Disconnect AVRCP ATH110E or AT+AVH If AVRCP connection released: response = “NO CARRIER 110D”; If no AVRCP connection has existed: response = “NO CARRIER”Disconnect all proles ATH* Response = “NO CARRIER <ProleUUID>” for each previously connected proleTable3-12:ProleConnectionStatusTASK AT-COMMAND COMMENTGet connection status of SPP ATI60 0 = not connected 1 = connected identical with ATI9Get connection status of A2DP ATI61 0 = not connected 1 = connectedGet connection status of AVRCP ATI62 0 = not connected 1 = connected
39 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511APPENDIXBT-MM Unsolicited MessagesBT-MM Error ResponsesMESSAGE COMMENTCONNECT 123456789012,110D A2DP control connection established ‘123456789012’ – bd_addr of peer device ‘110D’ – Prole UUID indicating A2DPNO CARRIER 110D A2DP connection rejected or closed (if S329==0)CONNECT 123456789012,110E AVRCP control connection established ‘123456789012’ – bd_addr of peer device ‘110E’ – Prole UUID indicating AVRCPNO CARRIER 110E AVRCP connection rejected or closed (if S329==0)AVUR n <unit_idhex> <unit_typehex> <company_idhex>AV Unit Info Response, sent in response to AT+AVU (UNIT INFO Request), <unit_idhex>: unit id <unit_typehex>: see Table 3 9 <company_id>: IEEE Company IDAVSR <pagedec> <pagedatahex> AV Subunit Info Response, sent in response to AT+AVS (SUBUNIT INFO Request), Page data: 1st word of requested page, incompleteAVPTI <operation_idhex> <button_state> <subunit_idhex> <subunit_typehex>Indication of incoming Pass Through command <operation_idhex>: see Table 3 8 <button_state>: ‘0’ – pushed ‘1’ – released <subunit_idhex>: subunit id <subunit_typehex>: subunit type, see Table 3 9AVPTC n <operation_idhex> <state> Conrmation of AT+AVC (Control Command Request) n: ‘0’ – successful ‘1’ – timeout ‘2’ – not successful, other than timeoutPAIR ? <BdAddr> Incoming pairing request from device with BdAddrPAIR 0 <BdAddr> Succesfully paired with device with BdAddrPAIR 1 <BdAddr> Pairing errorPASSKEY ? <BdAddr> Incoming passkey request (respond with at+btb012345)PASSKEY N <BdAddr> 012345 Passkey notication (if MITM protection is enabled)ERROR DESCRIPTION01 Register not recognised02 Value for register is out of range03 Incoming call NOT pending04 No call to connect to. This error code has meaning for ATO only05 Syntax Error06 Empty String06 Device Class could not be stored08 Invalid Device Class Code09 Invalid Bluetooth Address10 Could not set Service or Friendly name11 PS Store Write12 PS Store Read13 Not Idle14 Incorrect Mode15 Already Scanning16 Pairing is already in progress17 Not USED
40 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleCONFIGURING THE BTM510/511 ERROR DESCRIPTION18 Not USED19 Not USED20 Not safe to write to Non-volatile Store - Ongoing Bluetooth Connection21 Link Key Cache is Empty22 Link Key Database is Full23 Malloc returned NULL - Resource Issue24 Remote Address same as Local Address25 Connection Setup Fail, DSR Not asserted26 Unauthenticated licence27 Max Responses (See S Register 518) too high. Memory allocation error28 The length of Pin in AT+BTK is too long29 Invalid Ring count specied for S Register 0 or 100. If S0<>0 and S100<>0 then S0 must be < S10030 ADC Error31 Analogue Value cannot be read as it is set for output32 Analogue Value cannot be written as it is set for input33 S Register Value is invalid34 Both L and R modier cannot be specied in ATD command35 Invalid Major Device Class – valid value in range 0x00 to 0x1F inclusive36 Pairing in progress – Command cannot be actioned – try again later37 Invalid Sniff parameter specied. E.g. new Attempt value greater than MinInterval. Solution is to rst increase MinInterval and re-enter the Attempt value.38 Get Remote Friendly name Failed39 Failed to change mode to Multipoint40 7 Bit mode requires parity to be even or odd41 Unused42 Unused43 Unused44 Unused45 Unused46 No A2DP role has been set (see S register 300)47 No AVRCP role has been set (see S register 301)48 No AVRCP category has been set (see S register 302)49 No AVRCP control connection50 No A2DP or AVRCP connection currently incoming50 No A2DP or AVRCP connection currently incoming51 Invalid operation ID (AVRCP)52 Wrong AVRCP role53 Command disabled by S-Register 31054 Production info string does not exist55 Audio resource error56 Invalid UUID57 Maximum gain level reached58 Minimum gain level reached
41 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia ModuleMECHANICAL DETAILSRECOMMENDED PCB FOOTPRINT(all dimensions in mm)11213 272854 403934 RF OUT (See Note 1)15.221.21x111x14pin pitchpin pitchPad Width 0.7 Typ Pad Length 1.65 Typ5.5710.67.6MODULE OUTLINE(See note 2)11213 272854 403911213 272854 4039TOP VIEW BOTTOM VIEW(COMPONENT SIDE)(SMT PADS)ED3434 RF OUTRF OUTSIDE VIEWDescription 54 pin BT Voice Module (8X6 Flash)Size20.0 x 14.0 x 2.4mmPitch 1.0mmDimension Minimum Typical Maximum NotesD1E1eGHA1A2AbA2.42.7A1 0.80.91.0A2 1.51.7b 0.60D13.87 14.0 14.13E 19.87 20.0 20.13e1.0D1 11.0E1 14.0F1.50G3.00PCB ThicknessRF Shield HeightGlobal pad widthGlobal pitch2.3H0.85 Global length of pad to edge of boardUnits mmPin OutsRF ShieldU1U3 Orientation markon PCB and RF Shielddenotes pin 1FH1.30.650.55Pad Centre to Board edgePad Centre to Board edge11213 272854 403911213 272854 4039TOP VIEW BOTTOM VIEW(COMPONENT SIDE)(SMT PADS)ED3434 RF OUTRF OUTSIDE VIEWDescription 54 pin BT Voice Module (8X6 Flash)Size20.0 x 14.0 x 2.4mmPitch 1.0mmDimension Minimum Typical Maximum NotesD1E1eGHA1A2AbA2.42.7A1 0.80.91.0A2 1.51.7b 0.60D13.87 14.0 14.13E 19.87 20.0 20.13e1.0D1 11.0E1 14.0F1.50G3.00PCB ThicknessRF Shield HeightGlobal pad widthGlobal pitch2.3H0.85 Global length of pad to edge of boardUnits mmPin OutsRF ShieldU1U3 Orientation markon PCB and RF Shielddenotes pin 1FH1.30.650.55Pad Centre to Board edgePad Centre to Board edge11213 272854 403911213 272854 4039TOP VIEW BOTTOM VIEW(COMPONENT SIDE)(SMT PADS)ED3434 RF OUTRF OUTSIDE VIEWDescription 54 pin BT Voice Module (8X6 Flash)Size20.0 x 14.0 x 2.4mmPitch 1.0mmDimension Minimum Typical Maximum NotesD1E1eGHA1A2AbA2.42.7A1 0.80.91.0A2 1.51.7b 0.60D13.87 14.0 14.13E 19.87 20.0 20.13e1.0D1 11.0E1 14.0F1.50G3.00PCB ThicknessRF Shield HeightGlobal pad widthGlobal pitch2.3H0.85 Global length of pad to edge of boardUnits mmPin OutsRF ShieldU1U3 Orientation markon PCB and RF Shielddenotes pin 1FH1.30.650.55Pad Centre to Board edgePad Centre to Board edge11213 272854 403911213 272854 4039TOP VIEW BOTTOM VIEW(COMPONENT SIDE)(SMT PADS)ED3434 RF OUTRF OUTSIDE VIEWDescription 54 pin BT Voice Module (8X6 Flash)Size20.0 x 14.0 x 2.4mmPitch 1.0mmDimension Minimum Typical Maximum NotesD1E1eGHA1A2AbA2.42.7A1 0.80.91.0A2 1.51.7b 0.60D13.87 14.0 14.13E 19.87 20.0 20.13e1.0D1 11.0E1 14.0F1.50G3.00PCB ThicknessRF Shield HeightGlobal pad widthGlobal pitch2.3H0.85 Global length of pad to edge of boardUnits mmPin OutsRF ShieldU1U3 Orientation markon PCB and RF Shielddenotes pin 1FH1.30.650.55Pad Centre to Board edgePad Centre to Board edgeMECHANICAL DRAWINGS
42 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia Module5544332211D DC CBBAAAGNDAGNDAGNDAGNDAGNDAGNDAGNDAGNDAGNDAGNDAGNDVCC_IOVCC_IOVCC_IOVCC_IOSPKR_A_PSPKR_A_NSPKR_B_NSPKR_B_PMIC_BIASMIC_A_PMIC_A_NMIC_B_NMIC_B_PPIO_5/BT_STATE_BT_PRIORITYPIO_7/RF_ACTIVEPIO_6/WLAN_ACTPIO_0/BT_ACTIVEMIC_A_N_DIFFAGNDMIC_A_N_DIFFTitleSize Document Number RevDate: Sheet ofBTVMD-R-001-04 04Mini Dev Board - CommsC1 3Friday, October 31, 2008TitleSize Document Number RevDate: Sheet ofBTVMD-R-001-04 04Mini Dev Board - CommsC1 3Friday, October 31, 2008TitleSize Document Number RevDate: Sheet ofBTVMD-R-001-04 04Mini Dev Board - CommsC1 3Friday, October 31, 2008Single ended StereoHeadphone OutputSingle-ended stereo inputJ3NF 3 way 2.5mm audio jackJ3NF 3 way 2.5mm audio jack1243J13 way 2.5mm audio jackJ13 way 2.5mm audio jack1243R38NF 0RR38NF 0R1 2+C35NF 100u+C35NF 100u+C32NF 100u+C32NF 100uR439RR439R12R302K2R302K212SW1NFSW1NF1324C7NF 15pFC7NF 15pF12SW2NFSW2NF1 32 4R160RR160R12R25NF 0RR25NF 0R1 2R2 0RR2 0R12+C33NF 100u+C33NF 100uR22NF 0RR22NF 0R12J23 way 2.5mm audio jackJ23 way 2.5mm audio jack1243C3100uC3100u1 2SW3NFSW3NF1324R170RR170R12C1415pFC1415pF12R101MRR101MR1 2R150RR150R12R60RR60R1 2SW4NFSW4NF1324TP3TP31C1215pFC1215pF12R939RR939R12R290RR290R12R362K2R362K212R1810KR1810K12R24NF 0RR24NF 0R12C9NF 15pFC9NF 15pF12L315nL315nR377K5R377K512C5100uC5100u1 2R23NF 0RR23NF 0R1 2R140RR140R12R51MRR51MR1 2TP4TP41R310KR310K12R10RR10R12R34NF 0RR34NF 0R1 2C1115pFC1115pF12J43 way 2.5mm audio jackJ43 way 2.5mm audio jack1243C4100nC4100n12R26NF 0RR26NF 0R12R21NF 0RR21NF 0R12C2100nC2100n12R200RR200R12R7 0RR7 0R12R320RR320R12L115nL115nR39NF 0RR39NF 0R12TP1TP11R28NF 0RR28NF 0R12C1315pFC1315pF12R357K5R357K512C6100uC6100u1 2+C34NF 100u+C34NF 100uR33NF 0RR33NF 0R1 2TP2TP21R810KR810K12R1310KR1310K12C1100uC1100u12L415nL415nR19NF 0RR19NF 0R12R270RR270R12L215nL215nR31NF 0RR31NF 0R1 2C10NF 15pFC10NF 15pF12C8NF 15pFC8NF 15pF12MECHANICAL DRAWINGS
43 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia Module5544332211D DC CBBAAAGNDAGNDVCC_IOVCC_3V3VCC_IOVCC_3V3 VCC_3V3VCC_3V3VCC_3V3VCC_IO VCC_IOVCC_3V3VCC_IOVCC_3V3VCC_3V3VCC_IOVCC_IO VCC_IOVCC_3V3VCC_3V3VCC_3V3VCC_3V3VCC_3V3VCC_3V3VCC_3V3VCC_3V3VCC_3V3VDD_CONNVCC_3V3VCC_IOUSB_DSRUSB_DCDUSB_CTSPIO_1/DCDModule_TX USB_RXSPI_CLK_PCSPI_CS_PCSPI_MISO_PCSPI_MOSI_PCPCM_INPCM_CLKPCM_SYNCModule_RTSModule_TXRESET_ Module_RXModule_CTSPIO_3/RIPIO_1/DCDPIO_3/RI USB_PIO_3/RIPIO_2/DSRPIO_5/DTRModule_RTSPCM_CLKPCM_OUTModule_CTSPCM_SYNCModule_RTSSPKR_A_NSPI_MOSILED EXT1LED EXT0SPKR_A_PSPKR_B_PPIO_0/BT_ACTIVESPKR_B_NMIC_BIASANTMIC_B_PMIC_A_NMIC_A_PMIC_B_NPIO_7/RF_ACTIVEUSB_MOD_D+PIO_6/WLAN_ACTUSB_MOD_D-RESET_SPI_MISOSPI_CSPIO_5/BT_STATE_BT_PRIORITYPIO_5/DTRPIO_2/DSRPIO_3/RIPIO_1/DCDSPI_CLKPCM_INModule_RXModule_TXSPI_CLK_PCSPI_CS_PCSPI_CSSPI_CLKSPI_MOSI_PCSPI_MOSISPI_MISO_PCSPI_MISOAGNDLED EXT1USB_MOD_D+LED EXT0USB_MOD_D-USB_TX Module_RXModule_CTSUSB_RTSUSB_DTRFTDI_ENFTDI_ENFTDI_ENFTDI_ENUSB_PWRENMIC_BIASSPKR_B_PMIC_B_NSPKR_A_PMIC_B_PMIC_A_N MIC_A_PSPKR_A_NSPKR_B_NPCM_OUTAGNDPIO_2/DSRPIO_5/DTRPIO_2/DSRPIO_3/RIPIO_1/DCDPIO_5/DTRTitleSize Document Number RevDate: Sheet ofBTVMD-R-001-04 04Mini Dev Board - CommsC2 3Friday, October 31, 2008TitleSize Document Number RevDate: Sheet ofBTVMD-R-001-04 04Mini Dev Board - CommsC2 3Friday, October 31, 2008TitleSize Document Number RevDate: Sheet ofBTVMD-R-001-04 04Mini Dev Board - CommsC2 3Friday, October 31, 2008R5110KR5110K12D1HSMC-A100-Q00J1D1HSMC-A100-Q00J121R4110KR4110K12U1NC7SZ125U1NC7SZ125OE_1IN2GND3OUT 4VCC 5U4CONN_SM_54U4CONN_SM_54PIO_15/DTR1PIO_5/BT_STATE/BT_PRIORITY2PCM_IN3PCM_OUT4PCM_SYNC5PCM_CLK6VDD_USB10VDD_IO11MASTER_VIN12SPI_CS14SPI_MISO15SPI_CLK16SPI_MOSI17PIO_2/DSR18LED_EXT17LED_EXT08PIO_0/BT_ACTIVE21GND222AUDIO_GND23SPKR_A_N24SPKR_A_P25SPKR_B_N26SPKR_B_P27MIC_BIAS 28BC05_RST 54PIO_6/WLAN_ACTIVE 53USB_D+ 46USB_D- 45PIO_7/RF_ACTIVE 52GND447UART_RTS 48UART_CTS 49NC444NC543NC642NC15 41NC14 40NC13 39NC12 38NC11 37NC10 36ANT 34NC9 35NC8 33MIC_AN_C 32MIC_AP_C 31MIC_BN_C 30MIC_BP_C 29UART_RX 51UART_TX 50GND19GND313PIO_3/RI19PIO_1/DCD20R71130RR71130R1 2R4710KR4710K12R540RR540R1 2R6510KR6510K12R66 0RR66 0R12JP4NFJP4NF1234567 89 10R6310KR6310K1 2R4010KR4010K1 2R5710KR5710K1 2R680RR680R12C15100nC15100n12R5010KR5010K1 2C21100nC21100n12R4310KR4310K12R5510KR5510K12D2HSMC-A100-Q00J1D2HSMC-A100-Q00J121U2NC7SZ125U2NC7SZ125OE_1IN2GND3OUT 4VCC 5R4610KR4610K1 2R1001K5R1001K512R6210KR6210K12TP5TP51R690RR690R12R670RR670R12JP3NFJP3NF135642R6010KR6010K1 2R5210KR5210K12C19100nC19100n12R5910KR5910K1 2C17100nC17100n12U3NC7SZ125U3NC7SZ125OE_1IN2GND3OUT 4VCC 5R450RR450R1 2R4210KR4210K12JP2NFJP2NF135 642JP1NF Header 6X2JP1NF Header 6X21 23 45 67891011 12C18100nC18100n12C16100nC16100n12R5810KR5810K1 2U574LCX244U574LCX244OE1_1I02O43I14O55I26O67I38O79GND10 I7 11O3 12I6 13O2 14I5 15O1 16I4 17O0 18OE2_ 19VCC 20R4410KR4410K12R490RR490R1 2R6410KR6410K12R6110KR6110K1 2R5610KR5610K1 2J5HEADER 10 X 1J5HEADER 10 X 112345678910C20100nC20100n12R48 0RR48 0R1 2R5310KR5310K12TP6TP61R70130RR70130R1 2MECHANICAL DRAWINGS
44 www.lairdtech.com Laird Technologies BTM510/511Bluetooth® Multimedia Module5544332211D DC CBBAAD-50ohm Track 50_ohm TrackD+VDD_3V3_IOVDD_USBVDD_3V3_IOVDD_CONNVDD_USBVCC_3V3VCC_3V3VCC_3V3VDD_CONNVDD_USBVCC_3V3VCC_3V3USB-USB+USB_PWRENUSB_SLEEPUSB_RTSUSB_CTSUSB_RXUSB_TXUSB-USB+USB_PWRENRESET_FTDIUSB_DTRUSB_DSRUSB_DCDUSB_PIO_3/RIRESET_ANTUSB_MOD_D+USB_MOD_D-TitleSize Document Number RevDate: Sheet ofBTVMD-R-001-04 04Mini_Dev_Power_SuppliesC3 3Friday, October 31, 2008TitleSize Document Number RevDate: Sheet ofBTVMD-R-001-04 04Mini_Dev_Power_SuppliesC3 3Friday, October 31, 2008TitleSize Document Number RevDate: Sheet ofBTVMD-R-001-04 04Mini_Dev_Power_SuppliesC3 3Friday, October 31, 2008M3Mounting HoleM3Mounting HoleJ6SMA_VertJ6SMA_Vert12345C23100nC23100n12TP12TH_TEST_POINTTP12TH_TEST_POINT1C2510NC2510N12R740.1R 0805R740.1R 080512C301nC301n12R85 N/FR85 N/F12R7910KR7910K1 2R729K1R729K112D5HSMG-A100-HO1J1D5HSMG-A100-HO1J121R761K3R761K312C28NFC28NF12M2Mounting HoleM2Mounting HoleR94 NF 0RR94 NF 0R1 2R8610KR8610K1 2C24100nC24100n12M1Mounting HoleM1Mounting HoleR8410KR8410K1 2R73110RR73110R12R900RR900R1 2L5BLM18PG221SN1DL5BLM18PG221SN1D1 2FID2FiducialFID2FiducialD3Diode_S1AD3Diode_S1A1 2R11NF 9K1R11NF 9K112CN1DC Power jack_2.1mmCN1DC Power jack_2.1mm123R771KR771K1 2R91NF 9K1R91NF 9K112R81 0RR81 0R12U6MCP1726-ADJE/MFU6MCP1726-ADJE/MFVin_11Vin_22/SHDN3GND4PWRGD 5Cdelay 6ADJ 7Vout 8GND 9R884K7R884K712C27100nC27100n12Q1 IRF5810Q1 IRF5810156423C222u2C222u212TP7TP71R7810KR7810K12R801KR801K1 2TP15TP15FID1FiducialFID1FiducialTP11TH_TEST_POINTTP11TH_TEST_POINT1R8710KR8710K12OFFSW53 position switchOFFSW53 position switch213JP5-USB BJP5-USB BVcc 1D- 2D+ 3GND 45566TP8TP81D6BAT54CD6BAT54C123R75 10KR75 10K12R93 NF 0RR93 NF 0R1 2C29100nC29100n12U8FT232RU8FT232RTXD30DTR#31RTS#32VCCIO 1RXD2RI#3GND4DSR#6DCD#7CTS#8CBUS3 11CBUS2 10OSCO28 OSCI27TEST26AGND24CBUS1 21CBUS4 9GND20 VCC 19RESET#18GND173V3OUT 16USBDM 15USBDP 14NC_55NC_412NC_613CBUS0 22NC_1 23NC_2 25NC_3 29THPAD33R834.7KR834.7K12SW6BFS-1000SW6BFS-1000132 4M4Mounting HoleM4Mounting HoleTP13TP13R82 0RR82 0R1 2TP14TP14R92NF 9K1R92NF 9K112C262u2C262u212U7NC7SV17U7NC7SV17NC11IN2GND3OUT 4VCC 5C31100nC31100n12MECHANICAL DRAWINGS
45 BTM510/511Bluetooth® Multimedia Moduleglobal solutions: local supportTMUSA: +1.800.492.2320Europe: +44.1628.858.940Asia: +852.2268.6567 wirelessinfo@lairdtech.comwww.lairdtech.com/wirelessORDERING INFORMATIONBTM510 Bluetooth® Multimedia Module (external antenna)BTM511 Bluetooth® Multimedia Module with integrated antenna Q2-2009DVK-BTM510 Development Board with BTM510 soldered in place Q1-2009DVK-BTM511 Development Board with BTM511 soldered in place Q2-2009GENERAL COMMENTSThis is a preliminary datasheet. Please check with Laird Technologies for the latest information before commencing a design. If in doubt, ask.Refer to the schematic BTV-R-003.pdf for the Development Kit on the following two pages for examples of typical pin connections. A pdf of the schematic can be downloaded from the product web page.ORDERING INFORMATION
46 Laird Technologies is the world leader in the design and manufacture of customized, performance-critical products for wireless and other advanced electronics applications. Laird Technologies partners with its customers to nd solutions for applications in various industries such as: Network EquipmentTelecommunicationsData Communications Automotive ElectronicsComputersAerospaceMilitaryMedical EquipmentConsumer ElectronicsLaird Technologies offers its customers uniqueproduct solutions, dedication to research anddevelopment, as well as a seamless network ofmanufacturing and customer supportfacilities across the globe.LWS-UM-BTM510-511 0609Copyright © 2009 Laid Technologies, Inc. All rights reserved.The information contained in this manual and the accompanying software programs are copyrighted and all rights are reserved by Laird Technologies, Inc. Laird Technologies, Inc. reserves the right to make periodic modicationsofthisproductwithoutobligationtonotifyanypersonorentityofsuchrevision.Copying,duplicating,selling,orotherwisedistributinganypartofthisproductoraccompanyingdocumentation/softwarewithout the prior consent of an authorized representative of Laird Technologies,Inc. is strictly prohibited. All brands and product names in this publication are registered trademarks or trademarks of their respective holders. This material is preliminary InformationfurnishedbyLairdTechnologiesinthisspecicationisbelievedtobeaccurate.DevicessoldbyLairdTechnologiesarecoveredbythewarrantyandpatentindemnicationprovisionsappearinginitsTermsofSaleonly.LairdTechnologiesmakesnowarranty,express,statutory,andimpliedorbydescription,regardingtheinformationsetforthherein.LairdTechnologiesreservestherighttochangespecicationsatanytime and without notice. Laird Technologies’ products are intended for use in normal commercial and industrial applications. Applications requiring unusual environmental requirements such as military, medical life-supportorlife-sustainingequipmentarespecicallynotrecommendedwithoutadditionaltestingforsuchapplication.Limited Warranty, Disclaimer, Limitation of Liability For a period of one (1) year from the date of purchase by the OEM customer, Laird Technologies warrants the OEM transceiver against defects in materials and workmanship. Laird Technologies will not honor this warranty (and this warranty will be automatically void) if there has been any (1) tampering, signs of tampering; 2) repair or attempt to repair by anyone other than an Laird Technologies authorized technician. This warranty does not cover and 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.InnoeventshallLairdTechnologiesberesponsibleorliableforanydamagesarising:Fromtheuseofproduct;Fromthelossofuse,revenueorprotoftheproduct;orAs a 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’ determines that there is a defect, Laird Technologies will repair or replace the OEM transceiver at their discretion. If the product is replaced, it may be a new or refurbished product.

Navigation menu