9.4 HCI Command Packet – Disconnect Command (Opcode – 0x0406)

The host MCU uses the disconnect command (opcode – 0x0406) to terminate an existing connection. The connection handle field identifies the connection to terminate and the reason parameter indicates the reason for the host MCU request for disconnection. With respect to programming memory, the host MCU also uses this command to terminate the programming connection. After processing this command by the BM70/71 module, the only way to restart programming operations is by sending the HCI command packet – create connection command (opcode – 0x0405) to establish the programming flow again. If any HCI-ISDAP commands are active when this disconnect command is received by the BM70/71 module, undefined device operation may occur.

Command Format – Host MCU to BM70/71 Module

Table 9-8. Create Connection Command Format
StartOpcodeLengthData
Byte Number01-234-6
Size (bytes)1213
Value0x010x04060x03See the following table
Note: The opcode field for the HCI vendor command is formatted as LE. For the opcode (0x0406), byte[1] is 0x06, byte[2] is 0x04.
Table 9-9. Data Field Parameters
Byte NumberValueParameter DescriptionLength
4-50x0FFFConnection handle2 bytes
60x00

0x00 – Programming Complete.

0x01-0xFF – See Table 11-13.

With respect to programming, this value must always be zero from the host MCU.		1 byte
Figure 9-4. Message Sequence for Disconnect Command

Response Format – BM70/71 Module to Host MCU

The BM70/71 module responds with the following:
  • HCI event response – Command status event (opcode – 0x0F) packet
  • HCI Event Response – Disconnection complete event (opcode – 0x05) packet
There are no additional parameters appended to these packets.