michaelh/zephyr
1
0
Fork 0
Code Releases Activity

samples: mgmt: hawkbit: make references to "frdm_k64f" consistent

Browse source 
The "frdm_k64f" is referred as frdm_k64f and ``frdm_k64f`` in
places, update them to ":ref:`Freedom-K64F <frdm_k64f>`" or
``frdm_k64f``.

Signed-off-by: Yong Cong Sin <yongcong.sin@gmail.com>
This commit is contained in:
Yong Cong Sin 2024-04-04 15:11:43 +08:00 • committed by Fabio Baltieri
commit 80b3f15a03
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
samples/subsys/mgmt/hawkbit/README.rst
View file

@ -78,7 +78,7 @@ the server URL, ``<your-ip-address>:8080``, and logging into the server using
Step 4: Build hawkBit
=====================
hawkBit can be built for the frdm_k64f as follows:
hawkBit can be built for the :ref:`Freedom-K64F <frdm_k64f>` as follows:
.. zephyr-app-commands::
:zephyr-app: samples/subsys/mgmt/hawkbit
@ -117,7 +117,7 @@ of your board.
Once the image is flashed and booted, the sample will print the image build
time to the console. After it connects to the internet, in hawkbit server UI,
you should see the frdm_k64f show up in the Targets pane. It's time to
you should see the ``frdm_k64f`` show up in the Targets pane. It's time to
upload a firmware binary to the server, and update it using this UI.
Step 7: Building and signing the test image
@ -284,7 +284,7 @@ Step 11: Build hawkBit HTTPS
* Convert the server.pem file to self_sign.der and place the der file in
hawkbit/src directory
``hawkBit https`` can be built for the frdm_k64f as follows:
``hawkBit https`` can be built for the :ref:`Freedom-K64F <frdm_k64f>` as follows:
.. zephyr-app-commands::
:zephyr-app: samples/subsys/mgmt/hawkbit