Developing with ZBOSS
zb_buf_hdr_s Struct Reference

#include <zboss_api_buf.h>

Data Fields

zb_uint16_t len
 
zb_uint16_t data_offset
 
zb_uint8_t multiplicity
 
zb_uint8_t handle
 
zb_bitfield_t is_in_buf:1
 
zb_bitfield_t encrypt_type:3
 
zb_bitfield_t use_same_key:1
 
zb_bitfield_t zdo_cmd_no_resp:1
 
zb_bitfield_t is_rx_buf:1
 
zb_bitfield_t has_aps_payload:1
 
zb_int16_t status
 
zb_uint8_t reserved_to_align [ZB_RESERVED_BUF_TO_ALIGN_HDR_SIZE]
 

Detailed Description

Packet buffer header.

Field Documentation

◆ data_offset

zb_uint16_t zb_buf_hdr_s::data_offset

data offset in buffer buf

◆ encrypt_type

zb_bitfield_t zb_buf_hdr_s::encrypt_type

payload must be encrypted before send, if !0.

See also
zb_secur_buf_encr_type_e.

◆ handle

zb_uint8_t zb_buf_hdr_s::handle

The handle associated with the NSDU to be transmitted by the NWK layer entity.

◆ has_aps_payload

zb_bitfield_t zb_buf_hdr_s::has_aps_payload

if 1, than packet comes from APS

◆ is_in_buf

zb_bitfield_t zb_buf_hdr_s::is_in_buf

if 1, this is input buffer

◆ is_rx_buf

zb_bitfield_t zb_buf_hdr_s::is_rx_buf

if 1, this is buffer with received packet and nwk_mac_addrs_t is at buffer tail

◆ len

zb_uint16_t zb_buf_hdr_s::len

current layer buffer length

◆ multiplicity

zb_uint8_t zb_buf_hdr_s::multiplicity

if greater that 1, then the following (multiplicity - 1) buffers are occupied with payload data and should not be treated as having valid headers, etc.

◆ reserved_to_align

zb_uint8_t zb_buf_hdr_s::reserved_to_align[ZB_RESERVED_BUF_TO_ALIGN_HDR_SIZE]

this field serves to keep following buf[ZB_IO_BUF_SIZE] aligned to a word

◆ status

zb_int16_t zb_buf_hdr_s::status

some status to be passed with packet

◆ use_same_key

zb_bitfield_t zb_buf_hdr_s::use_same_key

if 1, use same nwk key# packet was encrypted by

◆ zdo_cmd_no_resp

zb_bitfield_t zb_buf_hdr_s::zdo_cmd_no_resp

if 1, this is ZDO command with no response - call callback at confirm


The documentation for this struct was generated from the following file: