From 88632c9af8509b1f99fea177ad557fe1e520fbbd Mon Sep 17 00:00:00 2001 From: Dustin Frisch Date: Sun, 11 Jun 2017 15:03:49 +0200 Subject: [PATCH] Order of implementation changed --- ...cture.tex => 6-1-multidevice_build_structure.tex | 2 +- ...c-deployment.tex => 6-2-automatic-deployment.tex | 0 ...update_mechanism.tex => 6-3-update_mechanism.tex | 0 6-implementation.tex | 13 ++++++------- 4 files changed, 7 insertions(+), 8 deletions(-) rename 6-2-multidevice_build_structure.tex => 6-1-multidevice_build_structure.tex (96%) rename 6-3-automatic-deployment.tex => 6-2-automatic-deployment.tex (100%) rename 6-1-update_mechanism.tex => 6-3-update_mechanism.tex (100%) diff --git a/6-2-multidevice_build_structure.tex b/6-1-multidevice_build_structure.tex similarity index 96% rename from 6-2-multidevice_build_structure.tex rename to 6-1-multidevice_build_structure.tex index 79a2ce2..5536e59 100644 --- a/6-2-multidevice_build_structure.tex +++ b/6-1-multidevice_build_structure.tex @@ -4,7 +4,7 @@ \subsubsection{Framework integration} -The framework has been changed to keep control over the application life-cycle. +The framework is build to keep control over the application life-cycle. It ensures that the device unspecific code is executed at the right time and provides an API for device specific functionality. The framework specifies a simple interface, which must be implemented by each device. diff --git a/6-3-automatic-deployment.tex b/6-2-automatic-deployment.tex similarity index 100% rename from 6-3-automatic-deployment.tex rename to 6-2-automatic-deployment.tex diff --git a/6-1-update_mechanism.tex b/6-3-update_mechanism.tex similarity index 100% rename from 6-1-update_mechanism.tex rename to 6-3-update_mechanism.tex diff --git a/6-implementation.tex b/6-implementation.tex index 1fbe0db..0917d04 100644 --- a/6-implementation.tex +++ b/6-implementation.tex @@ -2,11 +2,10 @@ Implementing \textit{OTA} updates under the given requirements involves three different components, which interact closely. -The first component implements the update mechanism in the firmware running on the embedded device. -It is responsible for checking and downloading the updates and installing them. -Second, the build system is in charge of building the firmware from source and publishing the built binary images. -Finally, the deployment provides infrastructure for downloading the binary firmware images and triggering the update on all devices. +The first component is the build system which is in charge of building the firmware from source and publishing the built binary images. +Second, the deployment provides infrastructure for downloading the binary firmware images and triggering the update on all devices. +Finally, the implementation of the update mechanism as part of the firmware running on the embedded device which is responsible for downloading and checking the updates and installing them. -\input{6-1-update_mechanism} -\input{6-2-multidevice_build_structure} -\input{6-3-automatic-deployment} \ No newline at end of file +\input{6-1-multidevice_build_structure} +\input{6-2-automatic-deployment} +\input{6-3-update_mechanism} \ No newline at end of file