蓝牙CSRFirmware.pptVIP

CSR Firmware Firmware Categories Several variants of the BlueCore firmware are available. These target different application areas and market segments. All the variants are produced from the same source code tree. Firmware Categories - HCI Build The traditional architecture splits functionality between the Bluetooth module and a host at the HCI level. This offers the most hardware flexibility. A separate microprocessor is required to implement the “higher layers”. Firmware Categories - RFCOMM Build Additional layers of the Bluetooth protocol stack can be run on the BlueCore. This removes some processing load from host. The maximum data throughput may be reduced. Currently no support for DFU. Firmware Categories - RFCOMM Build The BlueCore firmware incorporates a virtual machine (VM). The complete application can run on the BlueCore, without requiring an external host processor. Suitable for small applications such as mobile phone headsets and audio gateways. The VM is also present in HCI-only builds. Firmware Categories - Application Specific Special build variants are produced for some applications, where the VM does not provide sufficient flexibility or performance: HID (mouse etc.) HID proxy (presents a USB HID interface to the PC) DUN server Additional variants are being developed: BNEP (IPv4 or IPv6) Some of these may revert to using a custom application with a standard firmware build once the VM has been enhanced sufficiently. Firmware Categories - Host Transport BlueCore supports several transports between itself and the host: H:2 (HCI USB Transport Layer) H:4 (HCI UART Transport Layer) BCSP (BlueCore Serial Protocol) Raw UART (enables custom protocols from VM applications) Combining support for all of these transports with RFCOMM requires more than 4Mbit of program memory. Hence, some firmware builds only contain support for a single host transport. Support for self-test in production may be omitted from some builds for the same reason. Firmw