| Electronic Components Datasheet Search |
|
UM1865 Datasheet(PDF) 10 Page - STMicroelectronics |
|
|
|||||||||||||||||||||||||||||
UM1865 Datasheet(HTML) 10 Page - STMicroelectronics |
|
10 / 132 page ![]() ACI command data format UM1865 10/132 DocID027514 Rev 1 All HCI commands are grouped into logical groups by the Bluetooth specification and each group is assigned a unique OGF value. Depending on the OGF, the commands can be categorized into 3 sets: 1. Standard HCI commands: the commands with an OGF value other than 0x3F. These commands are designed for the controller. All standard HCI command are clearly defined in the Bluetooth specification, so they are not described in this document. 2. Vendor specific (VS) HCI commands: the commands with an OGF value 0x3F and are designed for the controller. Each vendor can define their own VS commands based on the hardware implementation. The VS commands defined for the BlueNRG-MS are described in this document. 3. Vendor specific (VS) ACI commands: the commands also with an OGF value 0x3F, but these commands are designed to control/access the host. The Bluetooth specification does not define any command for the host, so all the ACI commands are naturally vendor specific. The ACI commands for the BlueNRG-MS are described in this document. To clarify, the commands designed to control the controller are called HCI commands. This name is defined by the Bluetooth specification and we maintain it here in order to comply with the specification. The commands designed to control the host are called ACI commands. We give it a different name to indicate that this command is rather assigned to the host, i.e. to the whole BLE system, and not only to the controller at the lower level. However, because both ACI and HCI commands are the commands received from the external device via the ACI interface, and both of them share the same data format, sometimes it is not very important to differentiate between the two. So in this document, when referring in general to commands, we use the term “ACI commands”. In practice, the value of the OpCode is more important. Each command, regardless of whether it is an HCI or an ACI command, matches only one OpCode value. The user application should guarantee the OpCode value is used correctly. Please note that the Bluetooth specification uses bit-wise little endian format for the OpCode. So in Figure 4, the OGF field is placed to the right. But in this document, when writing an OpCode in the format of 0xXXXX, we imply the most significant bit to the left. For example, if an OpCode is 0xFE81, its top 6-bit OGF is “111111”, i.e. 0x3F, so it is a vendor specific command. And its OCF is 10-bit 0x281. For another example, if an OpCode is Table 1. OGF value Group Name OGF Value Link Control Commands 0x01 Link Policy Commands 0x02 Controller and Baseband Commands 0x03 Information Parameters 0x04 Status Parameters 0x05 Testing Commands 0x06 LE Controller Commands 0x08 Vendor Specific Commands 0x3F |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |