Skip to content

Commit cf597a1

Browse files
nvlsianpunvlsianpu
committed
doc/nrf/app_dev/dfu: prefer nrfutil over nrfjprog
As nrfjprog get deprecated, need to replace its cmd with nrfutil. ref.: NCSDK-30141 Signed-off-by: Andrzej Puzdrowski <[email protected]>
1 parent 3227327 commit cf597a1

File tree

3 files changed

+9
-15
lines changed

3 files changed

+9
-15
lines changed

‎doc/nrf/app_dev/bootloaders_dfu/mcuboot_nsib/bootloader_signature_keys.rst‎

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -214,14 +214,11 @@ To test that the bootloader no longer boots images signed with the earlier keys,
214214
CONFIG_SB_SIGNING_KEY_FILE="/path/to/priv_b.pem"
215215
CONFIG_FW_INFO_FIRMWARE_VERSION=3
216216
217-
#. To facilitate testing, use nrfjprog to program this image directly into a slot:
217+
#. To facilitate testing, use `nRF Util`_ to program this image directly into a slot:
218218

219219
.. code-block:: console
220220
221-
nrfjprog -f nRF52 -r --verify --program build/zephyr/signed_by_b0_s0_image.hex --sectorerase
222-
223-
.. note::
224-
|nrfjprog_deprecation_note|
221+
nrfutil device program --x-family nrf52 --options chip_erase_mode=ERASE_RANGES_TOUCHED_BY_FIRMWARE,verify=VERIFY_HASH,reset=RESET_SOFT --firmware build/zephyr/signed_by_b0_s0_image.hex
225222
226223
#. Observe the bootloader skipping the invalid image and booting the valid image in the other slot:
227224

‎doc/nrf/app_dev/config_and_build/output_build_files.rst‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -36,12 +36,12 @@ Which files you are going to use depends on the application configuration and no
3636
| File | Description | Programming scenario |
3737
+======================================+========================================================================================================+=====================================================================================+
3838
| :file:`zephyr.hex` | Default full image. | * Programming board targets with :ref:`NSPE <app_boards_spe_nspe>` or single-image. |
39-
| | In a project with multiple images, several :file:`zephyr.hex` files are generated, one for each image. | * Testing DFU procedure with nrfjprog (programming directly to device). |
39+
| | In a project with multiple images, several :file:`zephyr.hex` files are generated, one for each image. | * Testing DFU procedure with nRF Util (programming directly to device). |
4040
| | ``zephyr`` is the value of :kconfig:option:`CONFIG_KERNEL_BIN_NAME`. | |
4141
| | The file is located in the :file:`build/<your_application_name>/zephyr` directory. | |
4242
+--------------------------------------+--------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------+
4343
| :file:`merged.hex` | The result of merging all HEX files for all images for a specific core | * Programming multi-core application. |
44-
| | In multi-core builds, several :file:`merged_<core>.hex` fields | * Testing DFU procedure with nrfjprog (programming directly to device). |
44+
| | In multi-core builds, several :file:`merged_<core>.hex` fields | * Testing DFU procedure with nRF Util (programming directly to device). |
4545
| | are generated, where *<core>* indicates the CPU core. | |
4646
+--------------------------------------+--------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------+
4747
| :file:`tfm_s.hex` | Secure firmware image created by the TF-M build system in the background of the Zephyr build. | Programming :ref:`SPE-only <app_boards_spe_nspe>` and multi-core board targets. |
@@ -52,7 +52,7 @@ Which files you are going to use depends on the application configuration and no
5252
| | Can also be used standalone for a single-image DFU. | |
5353
| | Contains the signed version of the application. | |
5454
| | This file is transferred in the real-life update procedure, as opposed to HEX files | |
55-
| | that are transferred with nrfjprog when emulating an update procedure. | |
55+
| | that are transferred with nRF Util when emulating an update procedure. | |
5656
| | :ref:`Compatible with MCUboot <mcuboot:mcuboot_ncs>`. | |
5757
| | ``zephyr`` is the value of :kconfig:option:`CONFIG_KERNEL_BIN_NAME`. | |
5858
| | The file is located in the :file:`build/<your_application_name>/zephyr` directory. | |
@@ -68,7 +68,7 @@ Which files you are going to use depends on the application configuration and no
6868
| | Can also be used standalone for a single-image DFU. | |
6969
| | Contains the signed and encrypted version of the application. | |
7070
| | This file is transferred in the real-life update procedure, as opposed to HEX files | |
71-
| | that are transferred with nrfjprog when emulating an update procedure. | |
71+
| | that are transferred with nRF Util when emulating an update procedure. | |
7272
| | :ref:`Compatible with MCUboot <mcuboot:mcuboot_ncs>`. | |
7373
| | ``zephyr`` is the value of :kconfig:option:`CONFIG_KERNEL_BIN_NAME`. | |
7474
| | The file is located in the :file:`build/<your_application_name>/zephyr` directory. | |

‎samples/nrf5340/netboot/README.rst‎

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -111,18 +111,15 @@ After programming the sample to your development kit, complete the following ste
111111
I: Jumping to the first image slot
112112
*** Booting Zephyr OS build v2.7.99-ncs1-2195-g186cf4539e5a ***
113113
114-
#. Program the network core update image using nrfjprog:
114+
#. Program the network core update image using nRF Util:
115115

116116
.. code-block:: console
117117
118-
nrfjprog --program zephyr/net_core_app_moved_test_update.hex --sectorerase
118+
nrfutil device program --options chip_erase_mode=ERASE_RANGES_TOUCHED_BY_FIRMWARE --firmware zephyr/net_core_app_moved_test_update.hex
119119
120120
.. note::
121121
Typically, the update image is received through serial interface or Bluetooth.
122-
For testing purposes, use nrfjprog to program the update image directly into the update slot.
123-
124-
.. note::
125-
|nrfjprog_deprecation_note|
122+
For testing purposes, use nRF Util to program the update image directly into the update slot.
126123

127124
#. Reset the kit.
128125
#. Observe that the output includes the following lines indicating that the MCUBoot in the application core has read the update image and performed a firmware update of the network core:

0 commit comments

Comments
 (0)