FCC ID: QOQWRAP2022-1-B2B Bluetooth Board-to-Board Module

ASCII Interface 2.0.0 Manual

$Revision: 1.4 $

Bluegiga Technologies ASCII Interface 2.0.0 Manual by Bluegiga Technologies Copyright 2004 Bluegiga Technologies Bluegiga Technologies assumes no responsibility for any errors, which may appear in this manual. Furthermore, Bluegiga Technologies reserves the right to alter the hardware, software, and/or specications detailed herein at any time without notice, and does not make any commitment to update the information contained herein. Bluegiga Technologies products are not authorized for use as critical components in life support devices or systems. The WRAP is a registered trademark of Bluegiga Technologies The Bluetooth trademark is owned by the Bluetooth SIG Inc., USA, and is licensed to Bluegiga Technologies. All other trademarks listed herein are owned by their respective owners. Table of Contents Preface..................................................................................................................................... i Typographical Conventions........................................................................................ i 1. Usage ...................................................................................................................................1 2. Operational Modes...........................................................................................................3 Command Mode...........................................................................................................3 Data mode .....................................................................................................................3 3. Commands .........................................................................................................................5 CALL..............................................................................................................................5 CLOSE............................................................................................................................6 INQUIRY .......................................................................................................................6 LIST ................................................................................................................................8 NAME ..........................................................................................................................10 RESET...........................................................................................................................10 SELECT........................................................................................................................10 SET................................................................................................................................11 SET BT ................................................................................................................12 SET CONTROL .................................................................................................14 TESTMODE.................................................................................................................16 4. Events ................................................................................................................................17 CONNECT ..................................................................................................................17 INQUIRY_PARTIAL ..................................................................................................17 NO CARRIER .............................................................................................................18 READY.........................................................................................................................18 NAME ..........................................................................................................................18 NAME ERROR ...........................................................................................................19 RING ............................................................................................................................19 SYNTAX ERROR ........................................................................................................19 5. Troubleshooting ..............................................................................................................21 A. Acronyms and Denitions...........................................................................................23 iii iv Preface WRAP THOR ASCII Interface is rmware which allows easy access to Bluetooth functionality. It makes the radio interface totally transparent and host system can control connections with simple ASCII commands strings. This makes transition to wireless world easy as no specic Bluetooth know-how has to be obtained. Typographical Conventions Different typographical conventions used in this manual are described in this chap-

ter. Screen output seen on terminal is presented as follows:

OUTPUT FROM ASCII Interface INPUT FROM USER MORE OUTPUT Command and output synopsis are presented as follows:

COMMAND {required parameter} [optional parameter] STATIC TEXT [2nd op-

tional parameter]

Command and event references are presented as follows:

COMMAND and EVENT. i Preface ii Chapter 1. Usage ASCII Interface is terminal controlled rmware which means it can be used with any terminal emulation software, such as Hyperterminal in Windows or Minicom in Linux. Initial port settings for ASCII interface are 115200,8n1 (baud rate 115200 bps, 8 data bits, no parity, one stop bit) and hardware ow control enabled. When you power-on the module or evaluation kit you should see the command prompt appear on the terminal emulation software. After power-on you can check ASCII Interface conguration, such as Bluetooth de-

vice address, by command SET. Example 1-1. ASCII Interface at initial state WRAP THOR AI (version 2.0.0-rc1 build 344 $ bt1.1) Copyright (c) 2003-2004 Bluegiga Technologies Inc. READY. SET SET BT BDADDR 00:07:80:a5:c1:11 SET BT NAME WRAP AI SET BT CLASS 001f00 SET Control BAUD 115200,8n1 SET Control ECHO 7 SET 1 Chapter 1. Usage 2 Chapter 2. Operational Modes ASCII Interface has two operational modes, command mode and data mode. Com-

mand mode is default mode when there is no connections. It is possible to switch between modes at any time when there are any connections. Data mode is not avail-

able if there is no connections (because there is not any data available). Switching from data mode to command mode is issued with the following escape sequence:

<at least 1 second sleep> +++ <at least 1 second sleep>

Same sequence or command SELECT may be used to return to data mode. When ASCII Interface enters to command mode READY event is delivered (unless masked away with SET CONTROL ECHO). Command Mode Command mode is default mode when ASCII Interface is powered. In command mode commands can be entered to ASCII Interface to perform various activities. Incoming data from remote devices is buffered when ASCII Interface is in command mode. Note: Because of embedded nature of ASCII Interface buffering capabilities are low and only small amounts of data can be received to buffers. Mode is changed from command mode to data mode when User switches mode either using escape sequence <1s>+++<1s> or using com-

mand SELECT. Connection is successfully created using command CALL (CONNECT event is used to notify for successful link creation). Remote device has connected us (RING event is used to notify for incoming con-

nections). Data mode Data mode is default mode when there are any connections. In data mode all data is sent totally transparently from UART over the Bluetooth RFCOMM link to other device and vice versa. Mode is changed from data mode to command mode when User switches mode using escape sequence <1s>+++<1s>. Link is terminated (closed by remote device or link loss) (NO CARRIER event is used to notify for link termination). 3 Chapter 2. Operational Modes 4 Chapter 3. Commands This chapter describes different commands used to control the behaviour of ASCII Interface. Every command is typed into one line and is executed by line feed (CR+LF, ASCII13+ASCII10). ASCII Interface is case insensitive ie. command may be entered in upper-, lower- or even mixed case letters. CALL Synopsis Command CALL is used to initiate connections to the remote device. Connections are closed using command CLOSE. Currently open connections can be viewed using command LIST. CALL {address} {target} RFCOMM Description address target channel uuid16 uuid32 uuid128 Bluetooth device address of the remote device RFCOMM target for the connection. Target may be one of the following:

RFCOMM channel number Format: xx (hex) 16 bit UUID for searching channel Format: xxxx (hex) 32 bit UUID for searching channel Format: xxxxxxxx (hex) 128 bit UUID for searching channel Format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (hex) Response CALL {link_id}

5 Chapter 3. Commands link_id Events Examples Numeric connection identier CONNECT event is delivered after successful CALL command. NO CARRIER event is delivered if CALL fails. Example 3-1. Creating successful connection to 00:07:80:bf:bf:01 channel 1 CALL 00:07:80:bf:bf:01 1 RFCOMM CALL 0 CONNECT 0 RFCOMM 1 Example 3-2. Creating successful connection to 00:07:80:bf:bf:01 Serial Port Prole

(UUID16 SPP = 1101) CALL 00:07:80:bf:bf:01 1101 RFCOMM CALL 0 CONNECT 0 RFCOMM 2 Example 3-3. Unsuccessful connection attempt to 00:07:80:bf:bf:01 CALL 00:07:80:bf:bf:01 1 RFCOMM CALL 0 NO CARRIER 0 ERROR 406 RFC_CONNECTION_FAILED CLOSE Synopsis Command CLOSE is used to terminate previously opened connection. See command CALL for more information about opening connections. CLOSE {link_id}

Description link_id Numeric connection identier from previously used command CALL or from event RING. Response Events No response. NO CARRIER event is delivered after link is closed. INQUIRY Command INQUIRY is used to nd other Bluetooth devices in the area. 6 Chapter 3. Commands Synopsis INQUIRY {timeout} [NAME]

Description timeout The maximum amount of time (in units of 1.28 seconds) before the inquiry pro-

cess is halted Note: It may take up to 10.24 seconds for Bluetooth device to answer inquiry scan and thus timeout value should be at least 8 if it is necessary to nd every device in the area. NAME Response Optional ag to automatically request friendly name for found devices, see com-

mand NAME for more information about remote name request INQUIRY {num_of_devices}

INQUIRY {addr} {class_of_device}*

num_of_devices Amount of found devices addr Bluetooth device address of found device class_of_device Bluetooth Class of Device of found device Note: Response from INQUIRY comes after specied timeout. Events Examples INQUIRY_PARTIAL events are delivered as devices are found. NAME events are delivered after INQUIRY if NAME ag is present. Example 3-4. Inquiry without friendly name request INQUIRY 10 INQUIRY_PARTIAL 00:07:80:bf:bf:01 001f00 INQUIRY_PARTIAL 00:07:80:80:05:65 920300 INQUIRY_PARTIAL 00:07:80:80:32:e0 920300 INQUIRY 3 INQUIRY 00:07:80:bf:bf:01 001f00 INQUIRY 00:07:80:80:05:65 920300 INQUIRY 00:07:80:80:32:e0 920300 7 Chapter 3. Commands Example 3-5. Inquiry with friendly name request INQUIRY 10 NAME INQUIRY_PARTIAL 00:07:80:bf:bf:01 001f00 INQUIRY_PARTIAL 00:07:80:80:05:65 920300 INQUIRY_PARTIAL 00:07:80:80:32:e0 920300 INQUIRY 3 INQUIRY 00:07:80:bf:bf:01 001f00 INQUIRY 00:07:80:80:05:65 920300 INQUIRY 00:07:80:80:32:e0 920300 NAME 00:07:80:bf:bf:01 "AI bf:01"

NAME 00:07:80:80:05:65 "WRAP AS"

NAME 00:07:80:80:32:e0 "WRAP THOR"

LIST Synopsis Command LIST shows information about connections currently open. LIST Response LIST {num_of_links}

LIST {link_id} CONNECTED RFCOMM {blocksize} 0 0 {elapsed_time}

{local_msc} {remote_msc} {addr} {channel} {direction} {powermode}

{role} {crypt}*

num_of_links link_id blocksize elapsed_time Number of currently open links Numeric connection identier Data packet size, ie. how many bytes data can be sent in one packet Link life time in seconds local_msc & remote_msc Serial port status bits, "8d" is normal value addr channel direction

"OUTGOING"

8 Bluetooth device address of the remote device RFCOMM channel number at remote device Direction of the link Link is initiated by local device (using command CALL)

"INCOMING"

Link is initiated by the remote device Chapter 3. Commands powermode

"ACTIVE"

"SNIFF"

"HOLD"

"PARK"

role

"MASTER"

"SLAVE"

crypt

"PLAIN"

Power mode for the link Link is in active mode Link is in sniff mode Link is in hold mode Link is in park mode Role of the link ASCII Interface is the master device of this link ASCII Interface is the slave device of this link Encryption state of the link Link is not encrypted Link is encrypted

"ENCRYPTED"

Events Examples None. Example 3-6. List with 1 active connection and 1 connection in sniff mode LIST LIST 2 LIST 0 CONNECTED RFCOMM 669 0 0 40 8d 8d 00:07:80:80:31:e6 1 INCOMING SNIFF SLAVE EN-

CRYPTED 9 Chapter 3. Commands LIST 1 CONNECTED RFCOMM 669 0 0 18 8d 8d 00:07:80:80:32:0e 1 OUTGOING AC-

TIVE MASTER ENCRYPTED NAME Synopsis Command NAME is used retrieve friendly name of the device. NAME {address}

Description addr Bluetooth device address of the device. Response None. Events NAME event is delivered when friendly name is known. NAME ERROR event is delivered if friendly name lookup fails. Examples Example 3-7. Successful name query NAME 00:07:80:bf:bf:01 NAME 00:07:80:bf:bf:01 "AI bf:01"

Example 3-8. Unsuccessful name query NAME 00:07:80:bf:bf:bf NAME ERROR 104 00:07:80:bf:bf:bf HCI_ERROR_PAGE_TIMEOUT RESET Synopsis Command RESET is used to reset ASCII Interface. Response Events RESET None. None. SELECT 10 Command SELECT is used to switch to data mode. Chapter 3. Commands Synopsis SELECT {link_id}

Description link_id Numeric connection identier None. ASCII Interface goes to data mode with the link link_id. None. SET displays or sets conguration values of ASCII Interface. Response Events SET Synopsis SET [{category} {option} {value}]

Description Without any parameters SET displays current conguration. category

"BT"

"CONTROL"

option value Response Category of setting Changes different Bluetooth related settings. See SET BT for more informa-

tion about options. Changes different ASCII Interface settings. See SET CONTROL for more information about options. Option name, depends on category. See following sections for more information. Value for option. See following sections for more information. If issued without parameters:

SET {category} {option} [value]*

SET If issued with parameters:

11 Chapter 3. Commands None. Events None. SET BT Bluetooth related settings. SET BT BDADDR List format SET BT BDADDR {addr}

addr Bluetooth device address of local device Note: This value is read-only. SET BT NAME List format Set format SET BT NAME {friendly_name}

SET BT NAME [friendly_name]

friendly_name Friendly name of local device Warning If friendly_name is left empty some device may have prob-

lems showing device. SET BT CLASS List format SET BT CLASS {class_of_device}

12 Chapter 3. Commands Set format SET BT CLASS {class_of_device}

Bluetooth Class of Device of local device class_of_device SET BT AUTH List format SET BT AUTH * {pin_code}

Note: SET BT AUTH is not visible if pin_code is disabled. Set format SET BT AUTH * [pin_code]

Pin code for authorized connections. Authorization is required if this option is present. pin_code SET BT PAIR List format SET BT PAIR {addr} {link_key}

Note: SET BT PAIR is not visible if there are not paired devices. Set format addr SET BT PAIR {addr} [link_key]

Bluetooth device address of the paired device 13 Chapter 3. Commands link_key Link key for authenticated connection To remove device from list of known devices left link_key parameter empty. Tip: To remove every known device use * as addr (SET BT PAIR *). SET CONTROL Common ASCII Interface settings. SET CONTROL BAUD List format Set format SET CONTROL BAUD {baud_rate},8{parity}{stop_bits}

SET CONTROL BAUD {baud_rate} ,8 {parity} {stop_bits}

Important: Parameters in SET CONTROL BAUD must be typed together!

baud_rate UART baud rate in bps

",8"

parity

"n"

"e"

"o"

stop_bits 14 Static string indicating UART uses 8 data bits UART parity setting None parity Even parity Odd parity Number of stop bits in UART communications Chapter 3. Commands

"1"

"2"

One stop bit Two stop bits SET CONTROL ECHO List format Set format SET CONTROL ECHO {echo_mask}

SET CONTROL ECHO {echo_mask}

echo_mask Bit 0 Bit 1 Bit 2 Bit mask for controlling echo and events displaying If set start-up banner is visible If set characters are echoed back to client in command mode If set events are displayed when in command mode Default value for SET CONTROL ECHO is 7 (bits 0..2 set). Warning If every bit is set off (value 0) it is quite impossible to know the status of ASCII Interface. If Bit 2 is set off it is very hard to detect whether ASCII Interface is in command mode or in data mode. SET CONTROL INIT List format SET CONTROL INIT {command}

15 Chapter 3. Commands Set format SET CONTROL INIT [command]

Any ASCII Interface command string. This command is automatically executed every time ASCII Interface starts

(after power-on, RESET or watchdog event) command TESTMODE Command TESTMODE enables Bluetooth Test Mode in which Bluetooth Testers may be used to test radio environment. Synopsis TESTMODE Response Events TEST 0 None. 16 Chapter 4. Events Events are mechanism that ASCII Interface uses to notify the User for completed commands, incoming connections, etc. If ASCII Interface is in data mode only possi-

ble event is NO CARRIER event for corresponding link. Events may be masked away by removing Bit 2 on command SET CONTROL ECHO. Note: ASCII Interface is designed so that unwanted events can be safely ignored. Events CONNECT, NO CARRIER and RING change the mode of operation and therefore they cannot be ignored. CONNECT CONNECT event is used to notify for successful link establishment. Note: ASCII Interface automatically goes into data mode after CONNECT event. Synopsis CONNECT {link_id} RFCOMM {channel}

Description link_id channel See also Numeric connection identier. Connected RFCOMM channel number. CALL, LIST INQUIRY_PARTIAL INQUIRY_PARTIAL event is used to notify found Bluetooth device. This event pre-

cedes response for INQUIRY command. Synopsis INQUIRY_PARTIAL {addr} {class_of_device}

Description addr Bluetooth device address of found device. class_of_device Bluetooth Class of Device of found device. 17 Chapter 4. Events See also INQUIRY NO CARRIER NO CARRIER event is used to notify for link loss or alternatively failure in link estab-

lishment. Synopsis NO CARRIER {link_id} RFCOMM {error_code} [message]

Description link_id error_code message See also READY Synopsis See also NAME Synopsis Numeric connection identier Code describing error Optional verbose error message CALL, CLOSE, LIST, RING READY event is used to notify for switching to command mode. READY. Operational modes NAME event is used to notify for successful lookup for Bluetooth friendly name of the remote device. NAME {addr} {"friendly_name"}

Description addr friendly_name 18 Bluetooth device address of the device. Friendly name of the device. Chapter 4. Events See also INQUIRY, NAME NAME ERROR NAME ERROR event is used to notify for Bluetooth friendly name lookup failure. Synopsis NAME ERROR {error_code} {addr} [message]

Description error_code Code describing error. Bluetooth device address of the device. Optional verbose error message. INQUIRY, NAME RING event is used to notify for incoming connection. Incoming connections are ac-

cepted only if there is no existing links. addr message See also RING Synopsis RING {link_id} {addr} {channel} RFCOMM Description link_id addr channel See also Numeric connection identier Bluetooth device address of the remote device Local RFCOMM channel CLOSE, LIST SYNTAX ERROR SYNTAX ERROR is not an actual event but error message describing faulty typed com-

mand or error in command parameters. 19 Chapter 4. Events Synopsis SYNTAX ERROR 20 Chapter 5. Troubleshooting This chapter introduces some usual error situations with possible solutions. Before contacting Bluegiga Technologies Technical Support at <support@bluegiga.com>

please carefully check through this chapter. Problem ASCII Interface does not start or output is just some garbage Possible solutions Check your cable and terminal emulation settings. Default terminal settings are 115200,8n1

(baud rate 115200 bps, 8 data bits, no par-

ity, one stop bit). 21 Chapter 5. Troubleshooting 22 Appendix A. Acronyms and Denitions BluetoothTM bps hold mode park mode RFCOMM sniff mode UART UUID WRAP Set of technologies providing audio and data transfer over short-range radio connections bits per second Bluetooth low power mode Bluetooth low power mode Serial cable emulation protocol; element of Bluetooth Bluetooth low power mode Universal Asynchronous Receiver Transmitter Universally Unique Identier Wireless Remote Access Platform;

Bluegiga Technologies wireless product family 23 Appendix A. Acronyms and Denitions 24

WRAP THOR 2022-1-B2B BLUETOOTH MODULE USERS MANUAL (V 1.0) WRAP THOR 2022-1-B2B Bluegiga Proprietary 1 Version 1.0 TABLE OF CONTENTS 1 6 2 8 3 4 5 OVERVIEW..................................................................................................................................4 1.1 FEATURE SUMMARY ................................................................................................................4 1.2 TARGET APPLICATIONS ...........................................................................................................4 1.3 USE OF THE ASCII-INTERFACE................................................................................................4 BLOCK DIAGRAMS......................................................................................................................5 2.1 BLOCK DIAGRAM OF WRAP THOR 2022-1-B2B...................................................................5 COMMON PHYSICAL LAYER SPECIFICATIONS............................................................................6 GENERAL SPECIFICATIONS ........................................................................................................6 RADIO FREQUENCY CHARACTERISTICS.....................................................................................7 5.1 TRANSMITTER CHARACTERISTICS............................................................................................7 5.2 RECEIVER CHARACTERISTICS ..................................................................................................8 PIN DESCRIPTION........................................................................................................................9 6.1 PIN DESCRIPTION OF WRAP 2022-1-B2B...............................................................................9 7 MECHANICS..............................................................................................................................11 7.1 PHYSICAL OUTLOOK OF WRAP 2022-1-B2B........................................................................11 7.2 MECHANICAL DRAWING OF WRAP THOR 2022-1-B2B ......................................................11 7.3 RECOMMENDED LAND PATTERN OF WRAP THOR 2022-1-B2B ..........................................13 7.4 ..................................................................................................................................................13 BLUETOOTH SOFTWARE STACKS ............................................................................................14 8.1 RFCOMM STACK.................................................................................................................14 8.2 VIRTUAL MACHINE STACK....................................................................................................15 UART INTERFACE ...................................................................................................................16 9 10 USB INTERFACE.......................................................................................................................18 10.1 USB DATA CONNECTIONS ..................................................................................................18 10.2 USB PULL-UP RESISTOR .....................................................................................................18 10.3 POWER SUPPLY....................................................................................................................18 10.4 SELF-POWERED MODE ........................................................................................................18 10.5 BUS-POWERED MODE .........................................................................................................19 10.6 SUSPEND CURRENT .............................................................................................................19 10.7 DETACH AND WAKE_UP SIGNALLING.................................................................................21 10.8 USB DRIVER.......................................................................................................................21 10.9 USB 1.1 COMPLIANCE ........................................................................................................21 10.10 USB 2.0 COMPATIBILITY ..................................................................................................21 SERIAL PERIPHERAL INTERFACE ............................................................................................22 11.1 INSTRUCTION CYCLE...........................................................................................................22 11.2 SINGLE-CYCLE OPERATION.................................................................................................22 11.3 MULTI-SLAVE OPERATION..................................................................................................22 11.4 WRITING TO WRAP THOR 2022-1 ....................................................................................22 11.5 AUTO-INCREMENT OPERATION ...........................................................................................22 11.6 READING FROM WRAP THOR 2022-1...............................................................................24 12 PCM .........................................................................................................................................25 12.1 PCM INTERFACE MASTER/SLAVE.......................................................................................25 12.2 SHORT FRAME SYNC ...........................................................................................................27 12.3 MULTI-SLOT OPERATION ....................................................................................................28 12.4 GCI INTERFACE...................................................................................................................28 12.5 SLOTS AND SAMPLE FORMATS ............................................................................................29 12.6 ADDITIONAL FEATURES.......................................................................................................30 12.7 PCM TIMING INFORMATION................................................................................................30 13 PIO ...........................................................................................................................................33 14 APPROVAL INFORMATION........................................................................................................34 11 Bluegiga Proprietary 2 Version 1.0 Bluegiga Proprietary 3 Version 1.0 1 OVERVIEW 1.1 FEATURE SUMMARY The summary of the technical features are listed below. Wireless communication module corresponding to Bluetooth Specification V1.1. Bluetooth Class 1 device. Supports 100 m link range. Compact package size (25.6 * 14 * 2.5 mm). Up to 7 ACL connections and up to 3 SCO connections. UART interface with programmable baud rate. GPIO control. SPI 13-bit PCM interface. Built-in link controller and Link Manager Protocol. Command interface options. WRAP THOR ASCII Interface using UART. HCI using UART / USB. Built-in flash memory and system clock. Support for Virtual Machine applications inside the module. 1.2 TARGET APPLICATIONS The target applications are telemetry, telematics, M2M applications, industrial instruments, sensors, and devices, hand-held devices, network appliances, embedded Linux systems, professional transportation systems, lifestyle electronics, cable replacement, Symbian phone accessories. 1.3 USE OF THE ASCII-INTERFACE This is described separately in the ASCII-Interface manual. Bluegiga Proprietary 4 Version 1.0 2 BLOCK DIAGRAMS 2.1 BLOCK DIAGRAM OF WRAP THOR 2022-1-B2B Antenna Band Pass Filter RF Switch Low Noise Amp. RF Power Amp. Balun BlueCore02 8 Mbit Flash Memory 16 MHz Crystal 3.3 V Reg. Bluegiga WRAP THOR 2022-1-B2B UART SPI PCM USB PIO 4.0 V 9.0 V

Figure 1: Block diagram of WRAP THOR 2022-1-B2B Bluegiga Proprietary 5 Version 1.0 3 COMMON PHYSICAL LAYER SPECIFICATIONS The common physical layer specifications are shown in the table below. Item 1 Operating Frequency 2 Carrier Spacing 3 Channels 4 Duplexing 5 6 TX Modulation Polarity Symbol Rate 7 RX Data Out Polarity Specification 2400 MHz to 2483.5 MHz (In the ISM-Band) 1.0 MHz 79 TDD 1 Mbps Binary one: Positive frequency deviation Binary zero: Negative frequency deviation FC + dF: "H"

FC - dF: "L"

Table 1: Common physical layer specifications 4 GENERAL SPECIFICATIONS The general specifications are show in the table below. Item Specification Pin 39: 4.0 V 9.0 V unregulated voltage. 1 Supply voltage WRAP THOR 2022-1-B2B Pin 40: 3.3 V 0.1 V regulated voltage. (Noise < 10 mVP-P.) 2 Supply current WRAP THOR 2022-1-B2B Maximum current in TX mode: 160 mA. Maximum current in RX mode: 60 mA. 3 Frequency range 2400 MHz 2483.5 MHz. (ISM-Band.) 2 MHz < F < 3.5 MHz. (Europe, Japan, USA.) 4 Guard band 5 Carrier frequency 2402 MHz 2480 MHz. F = 2402 + k MHz; k = 0 78. 6 Modulation method GFSK, 1 Mbps, 0.5 Gaussian. 1600 hops/s, 1 MHz channel space. 7 Hopping Asynchronous, 723.2 kbps / 57.6 kbps. 8 Maximum data rate Synchronous: 433,9 kbps/433.9kbps. 9 Receiving signal range

-82 to -20 dBm. (Typical.) 1.5 MHz. (Center frequency.) 10 Receiver IF frequency Minimum: -18 -16 dBm. Maximum +14 +17 dBm.

(Class 1 device with 6 power control levels.) 50 . 16 MHz. 6 GPIO, PCM, SPI, UART, USB. 273 K 328 K. (0 C + 55 C). 233 K 358 K. (- 40 C + 85 C.) Bluetooth specification, version 1.1. USB specification, version 1.1. 12 RF input impedance 13 Baseband crystal OSC 14 Output interfaces 15 Operation temperature 16 Storage temperature 17 Compliance 18 USB specification Table 2: General specifications 11 Transmission power Bluegiga Proprietary 6 Version 1.0 5 RADIO FREQUENCY CHARACTERISTICS 6 5 2400

-20

-40

+18 20 Min

+12 dBm dBm dBm TRM/CA/01/C. (NTC, ETC.) dBm TRM/CA/02/C. (ETC.) Typ Max Unit Bluetooth test purpose

+16 2483.5 MHz TRM/CA/04/C. (NTC, ETC.) 1.0 MHz TRM/CA/05/C. (NTC, ETC.) TRM/CA/06/C. (NTC, ETC.) 5.1 TRANSMITTER CHARACTERISTICS The transmitter characteristics have been measured according to the test purposes of the Bluetooth test specification. The details of the initial condition and the test procedure may be found from the document mentioned above. The transmitter characteristics are show in the table below. No Item 1 Output power. 2 Power density. 3 Frequency range. 4

-20 dB band width. Adjacent channel power. M N = 2. M N 3. Modulation characteristics. F1AVG. F2MAX. (99.9 %.) F2AVG/F1AVG. Initial carrier frequency tolerance. Carrier frequency drift. DH1. DH3. DH5. Drift rate. Out-of-band spurious emissions. Operation mode. 30 MHz 1 GHz. 1 GHz 12.75 GHz. 1.8 GHz 1.9 GHz. 5.15 GHz 5.3 GHz. Idle mode. 30 MHz 1 GHz. 1 GHz 12.75 GHz. 1.8 GHz 1.9 GHz. 5.15 GHz 5.3 GHz. TRM/CA/07/C. (NTC, ETC.) kHz TRM/CA/08/C. (NTC, ETC.) TRM/CA/09/C. (NTC, ETC.) TRC/CA/01/C. (NTC.)

+25

+40

+40 20000 dBm dBm dBm dBm dBm dBm dBm dBm 140 115 0.8

-75 kHz kHz kHz Hz

-57

-47

-47

-47

-36

-30

-47

-47

-25

-40

-40 75 kHz kHz 0 175 7 8 9

Table 3: Transmitter characteristics Bluegiga Proprietary 7 Version 1.0 NTC: Normal Test Condition. Nominal power supply voltage (VDD = 3.3 V) and nominal operating temperature (TNOM = 298 K = 25 C). ETC: Extreme Test Condition. Extreme power supply voltages (VDD = 3.3 V 0.1 V) and extreme operating temperatures (TMIN = 253 K = 0 C, TMAX = 328 K = 55 C) in all combinations. 5.2 RECEIVER CHARACTERISTICS The receiver characteristics have been measured according to the test purposes of the Bluetooth test specification. The details of the initial condition and the test procedure may be found from the document mentioned above. The receiver characteristics are show in the table below. No Item 1 Sensitivity. 2 Sensitivity. Typ Max Unit Bluetooth test purpose

-82 dBm RCV/CA/01/C. (NTC, ETC.) dBm RCV/CA/02/C. (NTC, ETC.) Single slot packets. Min

-87

-82

-87

-75

-75 Multi-slot packets. C/I performance. C/I0MHz. (Co-Channel) C/I1MHz. C/I2MHz. C/I3MHz. C/IIMAGE. C/IIMAGE+1MHz. Blocking performance. 30 MHz2000 MHz. 2000 MHz2400 MHz. 2500 MHz3000 MHz. 3000 MHz12.75 GHz. Intermodulation performance.

+1 MHz

+2 MHz

>+3 MHz Image frequency Adjacent (1 MHz) to in-

band image 3 4 5 6 11 0

-30

-40

-9

-20

-10

-27

-27

-10

-39 4

-30

-40

-6

-16 RCV/CA/03/C. (NTC.) dB dB dB dB dB dB RCV/CA/04/C. (NTC.) dBm dBm dBm dBm dBm RCV/CA/05/C. (NTC.) dB dB dB dB dB

-20 7 Maximum input level. Table 4: Receiver characteristics NTC: Normal Test Condition. Nominal power supply voltage (VDD = 3.3 V) and nominal operating temperature (TNOM = 298 K = 25 C). ETC: Extreme Test Condition. Extreme power supply voltages (VDD = 3.3 V 0.1 V) and extreme operating temperatures (TMIN = 253 K = 0 C, TMAX = 328 K = 55 C) in all combinations. dBm RCV/CA/06/C. (NTC.) Bluegiga Proprietary 8 Version 1.0 6 PIN DESCRIPTION I/O I

I/O

I/O I/O I/O I/O I/O

Description Reset if high. (Internal 1 Kohm pull-down resistor.) Not connected. Programmable I/O lines. Not connected. Programmable I/O lines. Programmable I/O lines. Programmable I/O lines. Programmable I/O lines. Programmable I/O lines. Not connected. Not connected. Not connected. Not connected. Not connected. Not connected. Not connected. 6.1 PIN DESCRIPTION OF WRAP 2022-1-B2B The pin description of WRAP 2022-1-B2B is shown in the table below. No Pin name RESET_IN 1 NC 2 3 PIO (2) NC 4 PIO (3) 5 PIO (4) 6 7 PIO (6) PIO (5) 8 9 PIO (7) 10 NC 11 NC 12 NC 13 NC 14 NC 15 NC 16 NC 17 GND 18 GND 19 20 21 22 23 NC 24 NC 25 NC 26 NC 27 28 29 Synchronous data strobe (pull-down). Synchronous data clock (pull-down). Synchronous 8 kbps data in (pull-down). Synchronous 8 kbps data out (pull-down). Not connected. Not connected. Not connected. Not connected. Synchronous Serial Interface data input (pull down). Synchronous Serial Interface Clock (pull down). Chip select for synchronous serial interface (pull-up). Active low. Synchronous Serial Interface data output (strong pull-

down). Asynchronous serial data CTS (pull-up). Active low. USB data minus. Asynchronous serial data RTS (pull-up). Active low. USB data plus. Asynchronous serial data out. Asynchronous serial data. GND Ground. GND Ground. I/O I/O I O

I I I PCM_SYNC PCM_CLK PCM_IN PCM_OUT SPI_MOSI SPI_CLK SPI_CSB O I A O A O I GND Ground. GND Ground. VDD VDD Power supply connection. (Unregulated power input.) Power supply connection. (Regulated power input.) SPI_MISO 30 31 UART_CTS 32 USB_D-

33 UART_RST 34 USB_D+

35 UART_TX 36 UART_RX 37 GND 38 GND 5V0 39 40 3V3 Bluegiga Proprietary 9 Version 1.0 Table 5: Pin configuration List of abreviations: Analog (A), Input (I), Output (O), Ground (GND), Radio Frequency port (RF). Notes: Voltage level of input (I), output (O) and input/output (I/O) pins is 3.3 V. Bluegiga Proprietary 10 Version 1.0 7 MECHANICS 7.1 PHYSICAL OUTLOOK OF WRAP 2022-1-B2B The physical outlook of WRAP THOR 2022-1-B2B is shown in the image below. Figure 1: Outlook of WRAP THOR 2022-1-B2B 7.2 MECHANICAL DRAWING OF WRAP THOR 2022-1-B2B The mechanical drawing of WRAP THOR 2022-1-B2B is shown in the figure below. Bluegiga Proprietary 11 Version 1.0 Figure 2: Mechanical drawing of WRAP THOR 2022-1-B2B Bluegiga Proprietary 12 Version 1.0 7.3 RECOMMENDED LAND PATTERN OF WRAP THOR 2022-1-B2B WRAP THOR 2022-1-B2B module utilize AMP 4-353512-0 connector. The opposite connector for the application board is AMP 4-353515-0. The recommended land pattern of WRAP THOR 2022-

1-B2B opposite connector and the module positioning is shown in the figure below. Figure 3: Recommended land pattern of WRAP THOR 2022-1-B2B 7.4 Bluegiga Proprietary 13 Version 1.0 8 BLUETOOTH SOFTWARE STACKS WRAP THOR 2022-1 is supplied with Bluetooth stack firmware which runs on the internal RISC microcontroller. This is compliant with the Bluetooth specification v1.1. The WRAP THOR 2022-1 software architecture allows Bluetooth processing overheads to be shared in different ways between the internal RISC microcontroller and the host processor. The upper layers of the Bluetooth stack (above HCI) can be run either on-chip or on the host processor. Running the upper stack on WRAP THOR 2022-1 reduces (or eliminates, in the case of a virtual machine (VM) application) the need for host-side software and processing time. Running the upper layers on the host processor allows greater flexibility. 8.1 RFCOMM STACK Figure 4: RFCOMM stack Bluegiga Proprietary 14 Version 1.0 In this version of the firmware the upper layers of the Bluetooth stack up to RFCOMM are run on-

chip. This reduces host-side software and hardware requirements at the expense of some of the power and flexibility of the HCI only stack. 8.2 VIRTUAL MACHINE STACK Figure 5: Virtual Machine This version of the stack firmware requires no host processor. All software layers, including application software, run on the internal RISC processor in a protected user software execution environment known as a Virtual Machine (VM). The user may write custom application code to run on the BlueCore VM using BlueLaM software development kit (SDK) supplied with the BlueLab and Casira development kits, available separately from CSR. This code will then execute alongside the main BlueCore firmware. The user is able to make calls to the BlueCore firmware for various operations. The execution environment is structured so the user application does not adversely affect the main software routines, thus ensuring that the Bluetooth stack software component does not need re-qualification when the application is changed. Using the VM and the BlueLab SDK the user is able to develop applications such as a cordless headset or other profiles without the requirement of a host controller. BlueLab is supplied with example code including a full implementation of the headset profile. Note:

Sample applications to control PIO lines can also be written with BlueLab SDK and the VM for the HCI stack. Bluegiga Proprietary 15 Version 1.0 9 UART INTERFACE WRAP THOR 2022-1 Universal Asynchronous Receiver Transmitter (UART) interface provides a simple mechanism for communicating with other serial devices using the RS232 standard (1). WRAP THOR 2022-1 Figure 6: Universal Asynchronous Receiver Four signals are used to implement the UART function, as shown in Figure 5. When WRAP THOR 2022-1 is connected to another digital device, UART_RX and UART_TX transfer data between the two devices. The remaining two signals, UART_CTS and UART_RTS, can be used to implement RS232 hardware flow control where both are active low indicators. All UART connections are implemented using CMOS technology and have signalling levels of 0V and VDD_PADS. UART configuration parameters, such as Baud rate and packet format, are set using WRAP THOR 2022-1 software. Notes:

In order to communicate with the UART at its maximum data rate using a standard PC, an accelerated serial port adapter card is required for the PC.

(1) Uses RS232 protocol but voltage levels are 0V to VDD_PADS, (requires external RS232 transceiver IC) Table 6: Possible UART Settings Bluegiga Proprietary 16 Version 1.0 The UART interface is capable of resetting WRAP THOR 2022-1 upon reception of a break signal. A Break is identified by a continuous logic low on the UART_RX terminal, as shown in figure 9.16. If tBRK is longer than the value, defined by the Persistent Store Key PSKEY_HOST_IO_UART_RESET_TIMEOUT, (0x1a4), a reset will occur. This feature allows a host to initialise the system to a known state. Also, WRAP THOR 2022-1 can emit a Break character that may be used to wake the Host. Figure 7: Break signal Note:

The DFU boot-loader must be loaded into the Flash device before the UART or USB interfaces can be used. This initial Flash programming can be done via the serial peripheral interface. Table 9.10 shows a list of commonly used Baud rates and their associated values for the Persistent Store Key PSKEY_UART_BAUD_RATE (0x204). There is no requirement to use these standard values any Baud rate within the supported range (see Table 9.8) can be set in the Persistent Store Key according to the following formula. Table 7: Standard Baud Rates Bluegiga Proprietary 17 Version 1.0 10 USB INTERFACE WRAP THOR 2022-1 USB devices contain a full-speed (12Mbits/s) USB interface, capable of driving a USB cable directly. No external USB transceiver is required. The device operates as a USB peripheral, responding to requests from a master host controller such as a PC. Both the OHCI and the UHCI standards are supported. The set of USB endpoints implemented behave as specified in the USB section of the Bluetooth specification v1.1 and v1.2 part H2. As USB is a master-slave orientated system, WRAP THOR 2022-1 only supports USB slave operation. 10.1 USB DATA CONNECTIONS The USB data lines emerge as pins USB_D+ and USB_D- on the package. These terminals are connected to the internal USB I/O buffers of WRAP THOR 2022-1 and therefore have a low output impedance. To match the connection to the characteristic impedance of the USB cable, series resistors must be connected to both USB_D+ and USB_D-. 10.2 USB PULL-UP RESISTOR WRAP THOR 2022-1 features an internal USB pull-up resistor. This pulls the USB_D+ pin weakly high when WRAP THOR 2022-1 is ready to enumerate. It signals to the PC that it is a full-speed

(12Mbit/s) USB device. The USB internal pull-up is implemented as a current source, and is compliant with 7.1.5 of the USB specification v1.1. The internal pull-up pulls USB D+ high to at least 2.8V when loaded with a 15Kohm-5% pull-down resistor (in the hub/host) when VDD_PADS=3.1V). This presents a thevenin resistance to the host of at least 900 ohms. Alternatively, an external 1.5Kohm pull-up resistor can be placed between a PIO line and D+ on the USB cable. The firmware must be alerted to which mode is used by setting Persistent Store Key PSKEY_USB_PIO_PULLUP (0x2d0) appropriately. The default setting uses the internal pull_up resistor. 10.3 POWER SUPPLY The minimum output high voltage for USB data lines is 2.8V. To safely meet the USB specification, the voltage on terminals must be an absolute minimum of 3.1V. CSR recommends 3.3V for optimal USB signal quality. 10.4 SELF-POWERED MODE In self-powered mode, the circuit is powered from its own power supply and not from the VBUS

(5V) line of the USB cable. It draws only a small leakage current (below 0.5mA) from VBUS on the USB cable. This is the easier mode for which to design for, as the design is not limited by the power that can be drawn from the USB hub or root port. However, it requires that VBUS be connected to WRAP THOR 2022-1 via a resistor network (Rvb1 and Rvb2), so WRAP THOR 2022-1 can detect when VBUS is powered up. WRAP THOR 2022-1 will not pull USB_D+ high when VBUS is off. Bluegiga Proprietary 18 Version 1.0 WRAP THOR 2022-1 Figure 8: Connections to WRAP THOR 2022-1 for Self-Powered Mode The terminal marked USB_ON can be any free PIO pin. The PIO pin selected must be registered by setting PSKEY_USB_PIO_VBUS (0x2d1) to the corresponding pin number. 10.5 BUS-POWERED MODE In bus-powered mode the application circuit draws its current from the 5V VBUS supply on the USB cable. WRAP THOR 2022-1 negotiates with the PC during the USB enumeration stage about power consumption. For Class 2 Bluetooth applications, CSR recommends that the regulator used to derive 3.3V from VBUS is rated at 100mA average current and should be able to handle peaks of 120mA without foldback or limiting. In bus-powered mode, WRAP THOR 2022-1 requests 100mA during enumeration. For Class 1 Bluetooth applications, the USB power descriptor should be altered to reflect the amount of power required. This is accomplished by setting the Persistent Store Key PSKEY_USB_MAX_POWER (0x2c6). This is higher than for a Class 2 application due to the extra current drawn by the Transmit RF PA. When selecting a regulator, be aware that VBUS may go as low as 4.4V. The inrush current (when charging reservoir and supply decoupling capacitors) is limited by the USB specification (see USB 1.1 specification, section 7.2.4.1). Some applications may require soft-start circuitry to limit inrush current if more than 10pF is present between VBUS and GND. The 5V VBUS line emerging from a PC is often electrically noisy. As well as regulation down to 3.3V and 1.8V, applications should include careful filtering of the 5V line to attenuate noise that is above the voltage regulators bandwidth. Excessive noise on the 1.8V supply to the analogue supply pins of WRAP THOR 2022-1 will result in reduced receive sensitivity and a distorted transmit signal. 10.6 SUSPEND CURRENT USB devices that run off VBUS must be able to enter a suspended state, whereby they consume less that 0.5mA from VBUS. The voltage regulator circuit itself should draw only a small quiescent current (typically less than 100 mA) to ensure adherence to the suspend-current requirement of the Bluegiga Proprietary 19 Version 1.0 USB specification. This is not normally a problem with modern regulators. Ensure that external LEDs and/or amplifiers can be turned off by WRAP THOR 2022-1. The entire circuit must be able to enter the suspend mode. WRAP THOR 2022-1 Figure 9: Connections to WRAP THOR 2022-1 for Bus-Powered Mode Figure 10: USB_DETACH and USB_WAKE_UP Signal Bluegiga Proprietary 20 Version 1.0 10.7 DETACH AND WAKE_UP SIGNALLING WRAP THOR 2022-1 can provide out-of-band signalling to a host controller by using the dedicated control lines called USB_DETACH and USB_WAKE_UP. These are outside the USB specification (no wires exist for them inside the USB cable), but can be useful when embedding WRAP THOR 2022-1 into a circuit where no external USB is visible to the user. Both control lines are shared with PIO pins and can be assigned to any PIO pin by setting the Persistent Store Keys PSKEY_USB_PIO_DETACH (0x2ce) and PSKEY_USB_PIO_WAKEUP (0x2cf) to the selected PIO number). USB_DETACH, is an input which, when asserted high, causes WRAP THOR 2022-1 to put USB_D- and USB_D+ in a high-impedance state and to 1.5kY pull-up resistor on USB_D+. This detaches the device from the bus and is logically equivalent to unplugging the device. When USB_DETACH is taken low, WRAP THOR 2022-1 will connect back to USB and await enumeration by the USB host. USB_WAKE_UP, is an active high output (used only when USB_DETACH is active) to wake up the host and allow USB communication to recommence. It replaces the function of the software USB WAKE_UP message (which runs over the USB cable proper), and cannot be sent while WRAP THOR 2022-1 is effectively disconnected from the bus. 10.8 USB DRIVER A USB Bluetooth device driver is required to provide a software interface between WRAP THOR 2022-1 and Bluetooth applications running on the host. 10.9 USB 1.1 COMPLIANCE WRAP THOR 2022-1 is qualified to the USB specification v1.1, details of which are available from http://www.usb.org. The specification contains valuable information on aspects such as PCB track impedance, supply inrush current and product labeling. Although WRAP THOR 2022-1 meets the USB specification, CSR cannot guarantee that an application circuit designed around the chip is USB compliant. The choice of application circuit, component choice and PCB layout all affect USB signal quality and electrical characteristics. The information in this document is intended as a guide and should be read in association with the USB specification, with particular attention being given to Chapter 7. Independent USB qualification must be sought before an application is deemed USB compliant and can bear the USB logo. Such qualification can be obtained from a USB plugfest or from an independent USB test house. Terminals USB_D+ and USB_D- adhere to the USB specification 1.1 (Chapter 7) electrical requirements. For ac and dc specifications for terminals USB_DETACH, USB_WAKE_UP, USB_PULL_UP and USB_ON, refer to section 9.10 PIO specification. 10.10 USB 2.0 COMPATIBILITY WRAP THOR 2022-1 is compatible with USB specification 2.0 masters; under these circumstances the two ends agree the mutually acceptable rate of 12Mbits/s according to the USB 2.0 specification. Bluegiga Proprietary 21 Version 1.0 11 SERIAL PERIPHERAL INTERFACE WRAP THOR 2022-1 uses 16-bit data and 16-bit address during serial peripheral interface transactions. Such transactions will occur whether the internal processor is running or is stopped. This section details the considerations required when interfacing to WRAP THOR 2022-1 via the four dedicated serial peripheral interface terminals. Data may be written or read one word at a time or the auto-increment feature may be used to access blocks. 11.1 INSTRUCTION CYCLE Before WRAP THOR 2022-1 can be addressed, SPI_CSB must be taken low (SPI_CSB = 0). Data on SPI_MOSI is then clocked into WRAP THOR 2022-1 on the rising edge of the clock line SPI_CLK. When reading, WRAP THOR 2022-1 will reply to the Master on MISO (the data being valid on the falling edge of the SPI_CLK). The Master provides the clocking. 11.2 SINGLE-CYCLE OPERATION After a serial peripheral interface transaction completes, the Master toggles SPI_CLK with SPI_CSB high to initiate a new transaction. SPI_CSB must be high for at least two SPI_CLK cycles. 11.3 MULTI-SLAVE OPERATION WRAP THOR 2022-1 should not be connected in a multi-slave arrangement by simple parallel connection of slave MISO lines. When WRAP THOR 2022-1 is deselected (SPI_CSB = 1), the SPI_MISO line does not float. Instead, WRAP THOR 2022-1 outputs 0 if the processor is running or 1 if it is stopped. 11.4 WRITING TO WRAP THOR 2022-1 To write to WRAP THOR 2022-1, the 8-bit write command (00000010) is sent first (C[7:0]) followed by a 16-bit address (A[15:0]). After that, 16-bits of data (D[15:0]) are sent. 11.5 AUTO-INCREMENT OPERATION Sending a command word and the address of a register every time it is to be read or written can be a significant overhead, especially when large amounts of data are to be transferred. To overcome this WRAP THOR 2022-1 offers increased data transfer efficiency via an auto-increment operation. During operation, WRAP THOR 2022-1 increments the address automatically. Only the data is transmitted or received over the serial peripheral interface. WRAP THOR 2022-1 keeps the previous command word. Auto-increment mode is invoked by keeping SPI_CSB low after the last bit of a read or write operation, while providing an extra 16 clock cycles. If the previous command was a write, continuous 16-bit words of data may then be written to the WRAP THOR 2022-1 without the need to send the address or command word. Similarly, if the previous command was a read, then data may be read. T[15:0] are not returned after the first read, just D[15:0]. Bluegiga Proprietary 22 Version 1.0 Figure 11: Example Auto-Increment Operation Figure 12: Write Operation A Figure 13: Write Operation B Bluegiga Proprietary 23 Version 1.0 11.6 READING FROM WRAP THOR 2022-1 Reading from WRAP THOR 2022-1 is similar to writing to it. An 8-bit read command (00000011) is sent first, followed by the address of the location to be read. WRAP THOR 2022-1 then outputs the 16-bit contents of the location on MISO with a check-word during T[15:0] and data during bits D[15:0]. The check-word is composed of {command, address [15:8]}. The check-word may be used to confirm a read operation to a memory location. This overcomes the problems encountered with typical serial peripheral interface slaves, whereby it is impossible to determine whether the data returned by a read operation is valid data or the result of the slave device not responding. Figure 14: Read Operation A Figure 15: Read Operation B Bluegiga Proprietary 24 Version 1.0 12 PCM Pulse Code Modulation (PCM) is the standard method used to digitise human voice patterns for transmission over digital communication channels. Through its PCM interface, WRAP THOR 2022-1 has hardware support for continual transmission and reception of PCM data, thus reducing processor overhead for wireless headset applications. WRAP THOR 2022-1 offers a bi-directional digital audio interface that routes directly into the baseband layer of the on-chip firmware. It does not pass through the HCI protocol layer. Hardware on WRAP THOR 2022-1 allows the data to be sent to and received from a SCO connection. Up to three SCO connections can be supported by the PCM interface at any one time.(1) WRAP THOR 2022-1 can operate as the PCM interface Master generating an output clock of 128, 256 or 512kHz. When configured as PCM interface slave it can operate with an input clock up to 2048kHz. WRAP THOR 2022-1 is compatible with a variety of clock formats, including Long Frame Sync, Short Frame Sync and GCI timing environments. It supports 13 or 16-bit linear, 8-bit o-law or A-law companded sample formats at 8ksamples/s and can receive and transmit on any selection of three of the first four slots following PCM_SYNC. The PCM configuration options are enabled by setting the Persistent Store Key PS KEY_PCM_CONFIG (0x1b3). WRAP THOR 2022-1 interfaces directly to PCM audio devices includes the following:

. Qualcomm MSM 3000 series and MSM 5000 series CDMA baseband devices

. OKI MSM7705 four channel A-law and o-law CODEC

. Motorola MC145481 8-bit A-law and"o-law CODEC

. Motorola MC145483 13-bit linear CODEC WRAP THOR 2022-1 is also compatible with the Motorola SSITM interface Note:

(1) Subject to firmware support, contact CSR for current status. 12.1 PCM INTERFACE MASTER/SLAVE When configured as the Master of the PCM interface, WRAP THOR 2022-1 generates PCM_CLK and PCM_SYNC. Bluegiga Proprietary 25 Version 1.0 WRAP THOR 2022-1 Figure 16: WRAP THOR 2022-1 as PCM Interface Master When configured as the Slave of the PCM interface, WRAP THOR 2022-1 accepts PCM_CLK rates up to 2048kHz. WRAP THOR 2022-1 Figure 17: WRAP THOR 2022-1 as PCM Interface Slave Bluegiga Proprietary 26 Version 1.0 Note:

A minimum of 3 clock cycles needs to be applied before a SCO is established Long Frame Sync Long Frame Sync is the name given to a clocking format that controls the transfer of PCM data words or samples. In Long Frame Sync, the rising edge of PCM_SYNC indicates the start of the PCM word. When WRAP THOR 2022-1 is configured as PCM Master, generating PCM_SYNC and PCM_CLK, then PCM_SYNC is 8-bits long. When WRAP THOR 2022-1 is configured as PCM Slave, PCM_SYNC may be from two consecutive falling edges of PCM_CLK to half the PCM_SYNC rate (i.e., 62.5os) long. Figure 18: Long Frame Sync (Shown with 8-bit Companded Sample) WRAP THOR 2022-1 samples PCM_IN on the falling edge of PCM_CLK and transmits PCM_OUT on the rising edge. PCM_OUT may be configured to be high impedance on the falling edge of PCM_CLK in the LSB position or on the rising edge. 12.2 SHORT FRAME SYNC In Short Frame Sync the falling edge of PCM_SYNC indicates the start of the PCM word. PCM_SYNC is always one clock cycle long. Figure 19: Short Frame Sync (Shown with 16-bit Sample) Bluegiga Proprietary 27 Version 1.0 As with Long Frame Sync, WRAP THOR 2022-1 samples PCM_IN on the falling edge of PCM_CLK and transmits PCM_OUT on the rising edge. PCM_OUT may be configured to be high impedance on the falling edge of PCM_CLK in the LSB position or on the rising edge. 12.3 MULTI-SLOT OPERATION More than one SCO connection over the PCM interface is supported using multiple slots. Up to three SCO connections can be carried over any of the first four slots. Figure 20: Multi-slot Operation with Two Slots and 8-bit Companded Samples 12.4 GCI INTERFACE WRAP THOR 2022-1 is compatible with the General Circuit Interface, a standard synchronous 2B+D ISDN timing interface. The two 64Kbps B channels can be accessed when this mode is configured. In the GCI interface two clock cycles are required for each bit of the voice sample. The voice sample format is 8-bit companded. As for the standard PCM interface up to 3 SCO connections can be carried over the first four slots. Figure 21: CGI Interface Bluegiga Proprietary 28 Version 1.0 The start of frame is indicated by PCM_SYNC and runs at 8kHz. With WRAP THOR 2022-1 in Slave mode, the frequency of PCM_CLK can be up to 4.096MHz. In order to configure the PCM interface to work in GCI mode it is necessary to set GCI_MODE bit in PSKEY_PCM_CONFIG32. The SAMPLE_FORMAT bits should be set to 0x0b01 to allow for the double clocking of each. 12.5 SLOTS AND SAMPLE FORMATS WRAP THOR 2022-1 can receive and transmit on any selection of the first four slots following each sync pulse. Slot durations can be either 8 or 16 clock cycles. Durations of 8 clock cycles may only be used with 8-bit sample formats. Durations of 16 clocks may be used with 8, 13 or 16-bit sample formats. WRAP THOR 2022-1 supports 13-bit linear, 16-bit linear and 8-bit o-law or A-law sample formats. The sample rate is 8ksamples/s. The bit order may be little or big endian. When 16-bit slots are used, the 3 or 8 unused bits in each slot may be filled with sign extension, padded with zeros or a programmable 3-bit audio attenuation compatible with some Motorola CODECs. Figure 22: 16-bit Slot Length and Sample Formats Bluegiga Proprietary 29 Version 1.0 12.6 ADDITIONAL FEATURES WRAP THOR 2022-1 has a mute facility that forces PCM_OUT to be 0. In Master mode, PCM_SYNC may also be forced to 0 while keeping PCM_CLK running (which some CODECS use to control power-down). 12.7 PCM TIMING INFORMATION PCM Master Timing Note:

(1) Assumes normal system clock operation. Figures will vary during low power modes, when system clock speeds are reduced.

(2) Valid for temperatures between -40C and +105C Bluegiga Proprietary 30 Version 1.0 Figure 23: PCM Master Timing Bluegiga Proprietary 31 Version 1.0 PCM Slave Timing

(1) Valid for temperatures between -40C and +105C Figure 24: PCM Slave Timing Bluegiga Proprietary 32 Version 1.0 13 PIO The Parallel Input Output (PIO) Port is a general-purpose I/O interface to WRAP THOR 2022-1. The port consists of six programmable, bi-directional I/O lines, PIO[2:7]. Programmable I/O lines can be accessed either via an embedded application running on WRAP THOR 2022-1 or via private channel or manufacturer-specific HCI commands. PIO[2]/USB_PULL_UP (1) This is a multifunction terminal. The function depends on whether WRAP THOR 2022-1 is a USB or UART capable version. On UART versions, this terminal is a programmable I/O. On USB versions, it can drive a pull-up resistor on USB_D+. For application using external RAM this terminal may be programmed for chip select. PIO[3]/USB_WAKE_UP (1) This is a multifunction terminal. On UART versions of WRAP THOR 2022-1 this terminal is a programmable I/O. On USB versions, its function is selected by setting the Persistent Store Key PSKEY_USB_PIO_WAKEUP (0x2cf) either as a programmable I/O or as a USB_WAKE_UP function. PIO[4]/USB_ON (1) This is a multifunction terminal. On UART versions of WRAP THOR 2022-1 this terminal is a programmable I/O. On USB versions, the USB_ON function is also selectable (see USB Interface section 9.6). PIO[5]/USB_DETACH (1) This is a multifunction terminal. On UART versions of WRAP THOR 2022-1 this terminal is a programmable I/O. On USB versions, the USB_DETACH function is also selectable (see USB Interface section 9.6). PIO[6]/CLK_REQ This is multifunction terminal, its function is determined by Persistent Store Keys. Using PSKEY_CLOCK_REQUEST_ENABLE, (0x246) this terminal can be configured to be low when WRAP THOR 2022-1 is in deep sleep and high when a clock is required. The clock must be supplied within 4ms of the rising edge of PIO[6] to avoid losing timing accuracy in certain Bluetooth operating modes. PIO[7]

Programmable I/O terminal. Note:

(1) USB functions can be software mapped to any PIO terminal. Bluegiga Proprietary 33 Version 1.0 14 APPROVAL INFORMATION Installation of the module The module is intended only for installation inside equipment. Bluetooth qualification The Board-to-board module is Bluetooth qualified and listed as an end product. If not modified in any way, it is a complete Bluetooth entity, containing both functionality as well as the whole RF-

part including the antenna. This means: If the module is used without modification of any kind, it does not need any Bluetooth approval work. If changes are made in the parameter set, added profiles or in the antenna design, it is required to be submitted to a BQB (Bluetooth Qualification Body) for evaluation on what needs to be tested. CE marking The B2B module carries the CE marking. The module has been submitted to the Notified Body No. 0682 FCC statement This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. The FCC requires the user to be notified that any changes or modifications made to this device that are not expressly approved by Bluegiga Technologies may void the user's authority to operate the equipment. FCC ID: QOQWRAO2022-1-B2B Industry Canada The Canadian registration number is:

IC: 5123A-20221B2B 2004 BlueGiga Technologies. WRAP and WRAP THOR are trademarks of BlueGiga Technologies Oy. The Bluetooth trademark is owned by Bluetooth SIG Inc., USA, and is licensed to BlueGiga Technologies. Linux is a trademark of Linus Torvalds. Bluegiga Proprietary 34 Version 1.0