CC1352P: OAD Split image support

but that was 3 years back. 

thats why m checking again. 

because if TI dont support Split OAD, why are these macros still present in the code. 

Also how will it be scalable for large deployments. 

defaults OAD(app+stack+lib) takes lot of time.

this feature is not supported by only TI or nobody supports?

Also what is the alternate way to achieve,  if TI continue to ignore this important feature.

Hello Dhanraj,

The Zigbee OTA solution developed by TI still only supports image types of OAD_IMG_TYPE_APPSTACKLIB and does not plan to expand on this functionality in the near future.  The ZCL 7 Specification does allow for separate stack updates or application patches, thus it is the developer's responsibility to incorporate this functionality.  This would include figuring out a method for separating the application portion from the stack inside the project to generate a valid OAD image, as this is not managed by the SimpleLink SDK.  The macros are still present to allow users to expand on the OAD's capabilities, and BIM projects along with OAD image header files are shared between other TI stacks (BLE, 15.4, etc).

Regards,
Ryan

Thanks Ryan!

Just want to understand - 

1) During your setup/testing How much time does ZR_SW_OTA_CLIENT project take for upgrade when there is only 1 coordinator (with OTA server tool) and 1 router ?  

2) During your setup/testing How much time does ZR_SW_OTA_CLIENT project take for upgrade when there is only 1 coordinator/znp (with OTA server tool/gateway) and  more then 10 router , (more then ZR 10 node in network but OTA update only 1 at a time )?  

According to my experiences, there should be much differences for two cases when there’s no other heavy traffics between other routers. The OTA process of single router should be done in 5 minutes.

for a single router it takes more than 15 minutes, in my case.  

Default project. 

using CC2652P, coordinator and router are within 3 meter distance.

In real environments, I would say this is still within expectation.

Is there a way to improve this time ?

we have large network setups, 50+ nodes. 

I am not aware of approach to improve this.

Hi Dhanraj,

In my experience, OTA updates typically take 5 to 10 minutes depending on network reliability, OTA settings, and download image size.  Please consider doubling the OTA_MAX_MTU (see this relevant E2E post) or look for reductions to your generated image size.

Regards,
Ryan