This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Adding Z-Stack OTA Server functionality in a custom project

Other Parts Discussed in Thread: Z-STACK, SIMPLELINK-CC13X2-26X2-SDK


I want to add Z-Stack OTA Server functionality (from "zc_ota_server") in the "dmm_zc_switch_remote_display_app" example.

I didn't found any guide how to add OTA Server in a custom project, it is described only for OTA Client.

Did I miss something? Are there any examples of OTA Server implementation?

  • Hi Alex,

    TI does not provide documentation for porting OTA server functionality to a separate application, you will need to develop this solution on your own.  You can reference the provided projects and further understand how to add endpoints,, and/or add DMM functionality to an existing project, 


  • Z-Stack User Guide refers to files ota_srv_app.c and ota_srv_app.h, but these files are not included in SDK since version, they were merged with ota_server.c and ota_server.h examples. The latest SDK where the files ota_srv_app.c and ota_srv_app.h are separate, is SDK

    It looks like if I want to implement OTA Server functionality in my project, it makes sense to use ota_srv_app.c and ota_srv_app.h from the old SDK, because they are separate and it is easier to integrate them into my project than extracting the same functions from the ota_server.c example from the latest SDK

    What was a reason to merge them in SDK -

    Are there any restrictions on use the separate files as it was in the

  • Thanks for pointing out the changes in the OTA server application, I will be sure to revise the documentation accordingly for the SIMPLELINK-CC13X2-26X2-SDK release.  The functions were merged into ota_server files to reduce the application dependencies but it is understandable that your use case benefits from their separation.  Please make sure to run a difference comparison between the v4.20 and v5.10 functions to make sure you are using the latest solution, or separate the v5.10 application on your own.