Warning: This is an old version. The latest stable version is Version 5.2.0.
OTAcast consists of 3 different parts:
a. the encoding algorithm which generates equations from a data-file/memory section at the server side (the code to be integrated into, e.g., a firmware management server), b. the decoding algorithm which converts equations back into a data-file/memory section for use on the client side (the code to be integrated into, e.g., the user terminals or IoT devices).
The reference design, is a reference implementation which shows how to use the core library in a typical implementation both on the server and client side. The reference design will typically be used as the basis or as a template for the real implementation of OTAcast in your application.
The application is meant to be an easy way to set up an evaluation environment where a server can broadcast a file, and a set of clients can be used to receive it. The stand-alone application is implemented using the The reference design.
In conclusion, the core library and the reference design is to be used for the actual implementation of OTAcast in real products. whereas the stand-alone application is to be used for evaluation.
The OTAcast repository is located here: https://gitlab.com/steinwurf/otacast
examples folder contains some programs that demonstrate the usage
of the available API.