Skip to content

Commit d1da1f5

Browse files
doublemis1kkasperczyk-no
authored andcommitted
[nrftoup] docs: guides: update nrfconnect factory data guide
Since the `nrfjprog` tool become deprecated all documents shall mention the `nrfutil device` tool. Signed-off-by: Michał Szablowski <michal.szablowski@nordicsemi.no>
1 parent 8b54137 commit d1da1f5

File tree

1 file changed

+7
-14
lines changed

1 file changed

+7
-14
lines changed

docs/guides/nrfconnect_factory_data_configuration.md

+7-14
Original file line numberDiff line numberDiff line change
@@ -358,7 +358,7 @@ To use this script, complete the following steps:
358358
> `factory_data.hex` and `factory_data.bin` files are created in the
359359
> `output` directory. The first file contains the required memory offset.
360360
> For this reason, it can be programmed directly to the device using a
361-
> programmer (for example, `nrfjprog`).
361+
> programmer (for example, `nrfutil device`).
362362
363363
l. (optional) The maximum partition size in device's NVM memory, where
364364
factory data will be stored.
@@ -372,7 +372,7 @@ To use this script, complete the following steps:
372372
> `factory_data.hex` and `factory_data.bin` files are created in the
373373
> `output` directory. The first file contains the required memory offset.
374374
> For this reason, it can be programmed directly to the device using a
375-
> programmer (for example, `nrfjprog`).
375+
> programmer (for example, `nrfutil device`).
376376
377377
4. Run the script using the prepared list of arguments:
378378
@@ -766,7 +766,7 @@ $ python scripts/tools/nrfconnect/nrfconnect_generate_partition.py -i build/ligh
766766
As a result, `factory_data.hex` and `factory_data.bin` files are created in the
767767
`/build/light_bulb/zephyr/` directory. The first file contains the memory
768768
offset. For this reason, it can be programmed directly to the device using a
769-
programmer (for example, `nrfjprog`).
769+
programmer (for example, `nrfutil device`).
770770
771771
<hr>
772772
@@ -901,22 +901,15 @@ achieve the desired behavior of your application.
901901
## Programming factory data
902902
903903
The HEX file containing factory data can be programmed into the device's flash
904-
memory using `nrfjprog` and the J-Link programmer. To do this, use the following
904+
memory using `nrfutil device` and the J-Link programmer. To do this, use the following
905905
command:
906906
907907
```
908-
$ nrfjprog --program factory_data.hex
908+
$ nrfutil device program --firmware factory_data.hex
909909
```
910910
911-
In this command, you can add the `--family` argument and provide the name of the
912-
DK: `NRF52` for the nRF52840 DK or `NRF53` for the nRF5340 DK. For example:
913-
914-
```
915-
$ nrfjprog --family NRF52 --program factory_data.hex
916-
```
917-
918-
> Note: For more information about how to use the `nrfjprog` utility, visit
919-
> [Programming SoCs with nrfjprog](https://docs.nordicsemi.com/bundle/ug_nrf_cltools/page/UG/cltools/nrf_nrfjprogexe.html)
911+
> Note: For more information about how to use the `nrfutil device` utility, visit
912+
> [Programming SoCs with nrfutil's device module](https://docs.nordicsemi.com/bundle/nrfutil/page/README.html)
920913
921914
Another way to program the factory data to a device is to use the nRF Connect
922915
platform build system described in

0 commit comments

Comments
 (0)