User's Manual

Enhanced Class 1 Bluetooth v2.1 Module
User’s Guide
Americas: [phone] Option 2
Europe: [phone]
Hong Kong: [phone]
www.lairdtech.com/wireless
115
CONN-GUIDE-BT740_v0.2
Since all data is transparently treated in the module, the endienness of DATA[N] should be determined by
trial and error with the aid of an HDP manager and finalized to be correct by the time the implementation
submits for certification by the Continua Alliance. However, if the attribute data type is a 16 or 32 bit
integer/float, then it is little endian.
8.17.11 Write Attribute Value
This command is valid for agent role only and writes the value of the attribute, already preloaded in HDP
data channel 0xB0, where the attribute ID and the qualifierID is supplied in the command packet.
Command Packet
Offset
Field
Value
Comments
0
LENGTH
10
Fixed
1
CHANNEL
0
Fixed
2
COMMAND
[CMD_HDP_ATTRIBUTE_WRITE]
3
FLOW_IN
??
Runtime value
4..5
HANDLE[2]
[4]=msb,[5]=lsb
Handle identifying an instance of
data specialization
agent/manager combination
6..7
ATTRID[2]
[6]=msb,[7]=lsb
8..9
QUALIFIERID[2]
[8]=msb,[9]=lsb
See Note 1
Response Packet
Offset
Field
Value
Comments
0
LENGTH
8
Fixed
1
CHANNEL
0
Fixed
2
COMMAND
[CMD_HDP_ATTRIBUTE_WRITE]
3
FLOW_OUT
??
Runtime value
4
STATUS
As appropriate
5
HOSTCONTEXT
XX
This echoes back from the
command
6..7
HANDLE[2]
[6]=msb,[7]=lsb
Echoes back from the command
1. For manager role, this is the object ID (MDS=0,NU=1 etc). As more data specializations are added, the qualifierID
specifies appropriately for that specialization.
The host waits until the response receives before submiting further commands.
If the attribute exists, then the data moves from channel 0xB0 to the attribute container variable. If the attribute does not
exist, then the data discards. All the data in the channel is treated as the data for the attribute; that is, there is no
qualifying information affixed to the data. In addition, if the attribute exists but the data length does not match that of the
attribute, then the write fails (with an appropriate error code) and the data in the channel is discarded.
Since all data is transparently treated in the module, the endienness of DATA[N] should be determined by
trial and error with the aid of a HDP manager and finalized to be correct by the time the implementation is
submitted for certification by the Continua Alliance. However, if the attribute data type is a 16 or 32 bit
integer/float, then it will be little endian.