This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

The Block Request Delay and Maximum Data Size attributes for the Zigbee OTA upgrade

While using the Zigbee OTA examples (nRF Thread and ZigBee SDK v3.1.0), I have noticed by the sniffer, that the attribute “Block Request Delay” is presented in the OTA Upgrade Image Block Request from the client, and it’s equal to 0x00b8 milliseconds. But I have not found, where this value is set in the OTA client example? I need to slow down the request rate by increasing the default delay value on the OTA client side. Is it possible for this Zigbee stack/SDK version?

Also, I tried to increase the BACKGROUND_DFU_DEFAULT_BLOCK_SIZE (which corresponds to the Maximum Data Size attribute) to the value of 1024, which seemed okay according to the sdk_config.h comment Block size used by background DFU.  <1-4096>. But the warning message large integer implicitly truncated to unsigned type -woverflow appeared in SES. So, I looked further, and have seen, that the max_data_size field of zb_zcl_ota_upgrade_client_variable_s has the zb_uint8_t type limiting the maximum value up to 255 instead of 4096.

So, could the BACKGROUND_DFU_DEFAULT_BLOCK_SIZE be actually set up to 4096 somehow in the mentioned stack/SDK version?

I tried to look through the PICS document with the information about OTA features implemented by the Zigbee stack, but this link from infocenter seems to be dead (produce the 404 error).

Parents Reply Children
No Data
Related