From 02accb7a855229bd3728eb169e14651b9c81d29c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Szablowski?= Date: Mon, 20 Jan 2025 13:51:43 +0100 Subject: [PATCH] [nrftoup] docs: guides: update nrfconnect factory data guide MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Since the `nrfjprog` tool become deprecated all documents shall mention the `nrfutil device` tool. Signed-off-by: Michał Szablowski --- .../nrfconnect_factory_data_configuration.md | 21 +++++++------------ 1 file changed, 7 insertions(+), 14 deletions(-) diff --git a/docs/guides/nrfconnect_factory_data_configuration.md b/docs/guides/nrfconnect_factory_data_configuration.md index 84be3ca1eb..95ad304a7e 100644 --- a/docs/guides/nrfconnect_factory_data_configuration.md +++ b/docs/guides/nrfconnect_factory_data_configuration.md @@ -358,7 +358,7 @@ To use this script, complete the following steps: > `factory_data.hex` and `factory_data.bin` files are created in the > `output` directory. The first file contains the required memory offset. > For this reason, it can be programmed directly to the device using a - > programmer (for example, `nrfjprog`). + > programmer (for example, `nrfutil device`). l. (optional) The maximum partition size in device's NVM memory, where factory data will be stored. @@ -372,7 +372,7 @@ To use this script, complete the following steps: > `factory_data.hex` and `factory_data.bin` files are created in the > `output` directory. The first file contains the required memory offset. > For this reason, it can be programmed directly to the device using a - > programmer (for example, `nrfjprog`). + > programmer (for example, `nrfutil device`). 4. Run the script using the prepared list of arguments: @@ -766,7 +766,7 @@ $ python scripts/tools/nrfconnect/nrfconnect_generate_partition.py -i build/ligh As a result, `factory_data.hex` and `factory_data.bin` files are created in the `/build/light_bulb/zephyr/` directory. The first file contains the memory offset. For this reason, it can be programmed directly to the device using a -programmer (for example, `nrfjprog`). +programmer (for example, `nrfutil device`).
@@ -901,22 +901,15 @@ achieve the desired behavior of your application. ## Programming factory data The HEX file containing factory data can be programmed into the device's flash -memory using `nrfjprog` and the J-Link programmer. To do this, use the following +memory using `nrfutil device` and the J-Link programmer. To do this, use the following command: ``` -$ nrfjprog --program factory_data.hex +$ nrfutil device program --firmware factory_data.hex ``` -In this command, you can add the `--family` argument and provide the name of the -DK: `NRF52` for the nRF52840 DK or `NRF53` for the nRF5340 DK. For example: - -``` -$ nrfjprog --family NRF52 --program factory_data.hex -``` - -> Note: For more information about how to use the `nrfjprog` utility, visit -> [Programming SoCs with nrfjprog](https://docs.nordicsemi.com/bundle/ug_nrf_cltools/page/UG/cltools/nrf_nrfjprogexe.html) +> Note: For more information about how to use the `nrfutil device` utility, visit +> [Programming SoCs with nrfutil's device module](https://docs.nordicsemi.com/bundle/nrfutil/page/README.html) Another way to program the factory data to a device is to use the nRF Connect platform build system described in