Lines Matching +full:modules +full:- +full:start +full:- +full:from +full:- +full:right
1 .. zephyr:code-sample:: updatehub-fota
2 :name: UpdateHub embedded Firmware Over-The-Air (FOTA) update
3 :relevant-api: updatehub
5 Perform Firmware Over-The-Air (FOTA) updates using UpdateHub.
10 UpdateHub is an enterprise-grade solution which makes it simple to remotely
12 Firmware Over-the-Air (FOTA) updates with maximum security and efficiency,
33 :zephyr:board:`Freedom-K64F <frdm_k64f>` kit using the ethernet connectivity. The
52 Zephyr sub-systems and it uses CoAP over UDP.
60 directory. This allows to construct and run everything from a common place.
62 .. code-block:: console
65 bootloader modules tools zephyr
75 .. zephyr-app-commands::
78 :build-dir: mcuboot-frdm_k64f
82 Step 2: Start the UpdateHub Server
85 Step 2.1: UpdateHub-CE (Community Edition)
86 ------------------------------------------
88 The Zephyr sample application is configured by default to use the UpdateHub-CE
90 UpdateHub-CE is distributed as a docker container and can be on your local
92 To start using the UpdateHub-CE simple execute the docker command with the
95 .. code-block:: console
97 docker run -it -p 8080:8080 -p 5683:5683/udp --rm
98 updatehub/updatehub-ce:latest
101 -------------------------
103 The UpdateHub Cloud is an enterprise-grade solution. It provides almost same
104 resources than UpdateHub-CE with the DTLS as main diferential. For more
107 If you want to use the CoAPS/DTLS, simply add the ``overlay-dtls.conf`` when
112 .. code-block:: console
114 openssl genrsa -out privkey.pem 512
115 openssl req -new -x509 -key privkey.pem -out servercert.pem
121 .. code-block:: console
123 openssl x509 -in servercert.pem -outform DER -out servercert.der
124 openssl pkcs8 -topk8 -inform PEM -outform DER -nocrypt -in privkey.pem
125 -out privkey.der
134 ``overlay-prj.conf`` with option :kconfig:option:`CONFIG_UPDATEHUB_CE` equal ``n``.
144 value will select UpdateHub-CE otherwise ``n`` selects UpdateHub Cloud.
147 UpdateHub-CE server edition. If your are using a service provider a DNS name
148 is a valid option too. This option is only valid when using UpdateHub-CE.
155 UpdateHub-CE the valid is available at ``overlay-prj.conf.example`` file.
162 More information about overlay files in :ref:`important-build-vars`.
166 features. However, the configuration and use is similar to the start
170 ----------------------------
172 The ethernet depends only from base configuration.
174 .. zephyr-app-commands::
175 :zephyr-app: samples/subsys/mgmt/updatehub
177 :build-dir: app
178 :gen-args: -DEXTRA_CONF_FILE=overlay-prj.conf
183 ------------------------
185 For WiFi, it needs add ``overlay-wifi.conf``. Here a shield provides WiFi
189 .. zephyr-app-commands::
190 :zephyr-app: samples/subsys/mgmt/updatehub
192 :build-dir: app
193 :gen-args: -DEXTRA_CONF_FILE="overlay-wifi.conf;overlay-prj.conf"
199 The board disco_l475_iot1 is not supported. The es-WIFI driver currently
203 ------------------------------------------------
205 For IEEE 802.15.4 needs add ``overlay-802154.conf``. This requires two nodes:
211 .. zephyr-app-commands::
212 :zephyr-app: samples/subsys/mgmt/updatehub
214 :build-dir: app
215 :gen-args: -DEXTRA_CONF_FILE="overlay-802154.conf;overlay-prj.conf"
219 .. zephyr-app-commands::
220 :zephyr-app: samples/subsys/mgmt/updatehub
222 :build-dir: app
223 :gen-args: -DEXTRA_CONF_FILE="overlay-802154.conf;overlay-prj.conf"
229 -----------------------------------------------------
231 The OpenThread requires the ``overlay-ot.conf``. It requires two nodes:
233 validation needs a Linux kernel >= 4.9 with optional NAT-64 support. The
234 start point is try reproduce the `OpenThread Router`_. It is
238 .. zephyr-app-commands::
239 :zephyr-app: samples/subsys/mgmt/updatehub
241 :build-dir: app
242 :gen-args: -DEXTRA_CONF_FILE="overlay-ot.conf;overlay-prj.conf"
259 .. code-block:: console
261 west sign -t imgtool -d build/app -- --version 1.0.0 --pad
262 --key bootloader/mcuboot/root-rsa-2048.pem
267 rom start offset: 512 (0x200)
276 .. code-block:: console
278 west flash -d build/app --bin-file build/app/zephyr/zephyr.signed.bin
281 ``west flash -d build/app --hex-file build/app/zephyr/zephyr.signed.hex``
286 .. code-block:: console
288 minicom -D /dev/ttyACM0
295 to make sure you are creating the right signed image. The test image will be
298 .. code-block:: console
300 west sign --no-hex --bin -B build/zephyr-2.0.0.bin -t imgtool -d build/app --
301 --version 2.0.0 --key bootloader/mcuboot/root-rsa-2048.pem
306 rom start offset: 512 (0x200)
309 signed bin: build/zephyr-2.0.0.bin
317 .. code-block:: console
319 pip3 install --user uhu
321 After installing uhu you will need to set the ``product-uid``. The value for
322 UpdateHub-CE can be found at ``overlay-prj.conf.example`` file. For UpdateHub
323 Cloud, you need copy the value from the web interface.
325 .. code-block:: console
331 .. code-block:: console
333 uhu package add build/zephyr-2.0.0.bin -m zephyr
337 .. code-block:: console
343 .. code-block:: console
345 uhu package archive --output build/zephyr-2.0.0.pkg
347 The remaining steps are dedicated to UpdateHub-CE. If you are using UpdateHub
355 URL, ``<your-ip-address>:8080``, and logging into the server using ``admin``
367 .. code-block:: console
375 be used to speed-up.
381 content of ``overlay-prj.conf`` file.
387 In the browser where the UpdateHub-CE is open, click on ``menu Rollout``
399 .. code-block:: console
415 .. code-block:: console
419 Your board will reboot and then start with the new image. After rebooting,
424 .. code-block:: console
439 .. csv-table::
445 2, WIFI, :ref:`ESP-8266 <module_esp_8266>`
451 .. csv-table::
463 .. _OpenThread Router: https://openthread.io/guides/border-router