Lines Matching full:updatehub
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
14 about at `docs.updatehub.io`_.
16 This sample shows how to use UpdateHub in both a polling and manual update
27 :zephyr_file:`samples/subsys/mgmt/updatehub/src/main.c`.
32 * The Zephyr port of ``UpdateHub`` was initially developed to run on a
45 * The MCUboot bootloader is required for ``UpdateHub`` function properly.
47 to it. UpdateHub currently uses two slots to perform the upgrade. More
51 * ``UpdateHub`` acts like a service on Zephyr. It is heavily dependent on
58 The below steps describe how to build and run the ``UpdateHub`` sample in
82 Step 2: Start the UpdateHub Server
85 Step 2.1: UpdateHub-CE (Community Edition)
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
98 updatehub/updatehub-ce:latest
100 Step 2.2: UpdateHub Cloud
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
105 details on how to use the UpdateHub Cloud please refer to the documentation on
106 `updatehub.io`_. The UpdateHub Cloud has the option to use CoAPS/DTLS or not.
133 When using UpdateHub Cloud server it is necessary update your own
137 Step 3: Configure UpdateHub Sample
140 The updatehub have several Kconfig options that are necessary configure to
143 Set :kconfig:option:`CONFIG_UPDATEHUB_CE` select between UpdateHub edition. The ``y``
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.
158 Step 4: Build UpdateHub App
161 In order to correctly build UpdateHub the overlay files must be use correctly.
175 :zephyr-app: samples/subsys/mgmt/updatehub
190 :zephyr-app: samples/subsys/mgmt/updatehub
212 :zephyr-app: samples/subsys/mgmt/updatehub
220 :zephyr-app: samples/subsys/mgmt/updatehub
239 :zephyr-app: samples/subsys/mgmt/updatehub
251 will connect to UpdateHub server and check for new images. The image will be
312 Step 8: Create a package with UpdateHub Utilities (uhu)
315 First, install UpdateHub Utilities (``uhu``) on your system, using:
322 UpdateHub-CE can be found at ``overlay-prj.conf.example`` file. For UpdateHub
347 The remaining steps are dedicated to UpdateHub-CE. If you are using UpdateHub
348 Cloud you can find the proper procedure at `docs.updatehub.io`_.
354 Now, add the package to the updatehub server. Open your browser to the server
363 If you chose ``Manual``, register your device at updatehub server by using the
369 updatehub run
374 :kconfig:option:`CONFIG_UPDATEHUB_POLL_INTERVAL` minutes. The ``updatehub run`` can
379 able to reached the updatehub server for some reason. The most common
387 In the browser where the UpdateHub-CE is open, click on ``menu Rollout``
401 updatehub run
426 uart:~$ updatehub info
430 UpdateHub Server: <server ip/dns>
436 The below list of hardware have been used by UpdateHub team.
461 .. _updatehub.io: https://updatehub.io
462 .. _docs.updatehub.io: https://docs.updatehub.io/