Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[nrftoup] docs: guides: update nrfconnect factory data guide #535

Merged
merged 1 commit into from
Jan 22, 2025
Merged

[nrftoup] docs: guides: update nrfconnect factory data guide #535

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 7 additions & 14 deletions docs/guides/nrfconnect_factory_data_configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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:

Expand Down Expand Up @@ -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`).

<hr>

Expand Down Expand Up @@ -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
Expand Down
Loading