D a t a S h e e t - SemiconductorStore.com

More documents

Recommendations

Info

• Radio transmitter enable/disable – a simple command connects to a dedicated hardware switch that determines whether the radio can transmit • The firmware can read the voltage on a pair of the chip’s external pins. This is normally used to build a battery monitor, using either VM or host code • A block of BCCMD commands provides access to the chip’s “persistent store” configuration database (PS). The database sets the device’s Bluetooth address, Class of Device, radio (transmit class) configuration, SCO routing, LM, USB and DFU constants, etc. • A UART “break” condition can be used in three ways: • Presenting a UART break condition to the chip can force the chip to perform a hardware reboot • Presenting a break condition at boot time can hold the chip in a low power state, preventing normal initialization while the condition exists • With BCSP, the firmware can be configured to send a break to the host before sending data – normally used to wake the host from a deep sleep state • The DFU standard has been extended with public/private key authentication, allowing manufacturers to control the firmware that can be loaded onto their Bluetooth modules • A modified version of the DFU protocol allows firmware upgrade via the chip’s UART • A block of “radio test” or BIST commands allows direct control of the chip’s radio. This aids the development of modules’ radio designs, and can be used to support Bluetooth qualification. • Virtual Machine (VM). The firmware provides the VM environment in which to run application-specific code. Although the VM is mainly used with BlueLab and “RFCOMM builds” (alternative firmware builds providing L2CAP, SDP and RFCOMM), the VM can be used with this build to perform simple tasks such as flashing LED’s via the chip’s PIO port. • Hardware low power modes: shallow sleep and deep sleep. The chip drops into modes that significantly reduce power consumption when the software goes idle. • SCO channels are normally routed via HCI (over BCSP). However, up to three SCO channels can be routed over the chip’s single PCM port (at the same time as routing any remaining SCO channels over HCI). • Co-operative existence with 802.11b/g chipsets. The device can be optionally configured to support a number of different co-existence schemes including: o o o TDMA - Bluetooth and WLAN avoid transmitting at the same time. FDMA - Bluetooth avoids transmitting within the WLAN channel Combination TDMA & FDMA - Bluetooth avoids transmitting in the WLAN channel only when WLAN is active. • Please refer to separate documentation for full details of the co-existence schemes that CSR supports. Notes: 1. Supports basic data rate up to 723.2kbps asymmetric, maximum allowed by Bluetooth v2.0 + EDR specification 2. WT12 supports all combinations of active ACL and SCO channels for both Master and 3. Always refer to the Firmware Release Note for the specific functionality of a particular build. 37
6.3 RFCOMM Stack RFCOMM SDP L2CAP HCI LM LC 48kB RAM Baseband MCU Host USB UART I/O PCM Host I/O PCM I/O Radio Figure 24: WRAP THOR RFCOMM stack In the version of the firmware, shown in Figure 25, 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. Features of RFCOMM Stack Interfaces to Host: • RFCOMM, an RS-232 serial cable emulation protocol • SDP, a service database look-up protocol Connectivity: • Maximum number of active slaves: 3 • Maximum number of simultaneous active ACL connections: 3 • Maximum number of simultaneous active SCO connections: 3 • Data Rate: up to 350kbps 1 Security: • Full support for all Bluetooth security features up to and including strong (128-bit) • encryption. 38
Page 1 and 2: WT12 Data Sheet V e r s i o n 2 . 3
Page 3 and 4: Contents: 1. Block Diagram and Desc
Page 5 and 6: TERMS & ABBREVIATIONS Term or Abbre
Page 7 and 8: 1. BLOCK DIAGRAM AND DESCRIPTIONS F
Page 9 and 10: Since the details of some methods a
Page 11 and 12: Radio characteristics and general s
Page 13 and 14: 6. Measured at F0= 2441MHz. 7. Up t
Page 15 and 16: 2.2 Radio Characteristics - Enhance
Page 17 and 18: 3. WT12 PIN DESCRIPTION WT12 31 30
Page 19 and 20: CMOS input with weak internal pull-
Page 21 and 22: has to be connected to UART_RX. UAR
Page 23 and 24: 4.2 USB Interface WT12 USB devices
Page 25 and 26: USB_D+ WT12 USB_D- USB_ON VBUS Volt
Page 27 and 28: 4.3 SPI Interface The synchronous s
Page 29 and 30: PCM_OUT WT12 PCM_IN PCM_CLK Up to 2
Page 31 and 32: PCM_SYNC PCM_CLK PCM_OUT 1 2 3 4 5
Page 33 and 34: Name Bit position Description - 0 S
Page 35 and 36: 6. SOFTWARE STACKS WT12 is supplied
Page 37: The firmware has been written again
Page 41 and 42: main WRAP THOR firmware. The user i
Page 43 and 44: 7. ENHANCED DATA RATE EDR has been
Page 45 and 46: 8. LAYOUT AND SOLDERING CONSIDERATI
Page 47 and 48: • Routing should be done in the i
Page 49 and 50: Figure 30: WT12 foot print and dime
Page 51 and 52: Figure 33: Tape information 50
Page 53 and 54: 11.2 FCC Federal Communications Com
Page 55 and 56: 12. ROHS STATEMENT WITH A LIST OF B

D a t a S h e e t - SemiconductorStore.com

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?