You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nrf-regtool is no longer used, instead the script that generates
PERIPHCONF entries from devicetree lives in zephyr.
Update the description of the generation procedure accordingly.
Ref: NCSDK-36373
Signed-off-by: Jonathan Nilsen <[email protected]>
Copy file name to clipboardExpand all lines: doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_ironside.rst
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -488,27 +488,29 @@ After applying the entry, |ISE| performs a read-back check: it reads back the re
488
488
The configuration procedure is aborted if an entry fails either the validation or the read-back check.
489
489
If a failure occurs, BOOTSTATUS.BOOTERROR is set to indicate the error condition, and a description of the failed entry is written to the boot report.
490
490
491
-
Peripheral configuration using nrf-regtool
492
-
------------------------------------------
491
+
PERIPHCONF generation from devicetree
492
+
-------------------------------------
493
493
494
-
The ``nrf-regtool`` utility generates a UICR.PERIPHCONF configuration from the devicetree.
495
-
To determine which peripherals are in use, it analyzes the devicetree as follows:
494
+
When :kconfig:option:`CONFIG_NRF_PERIPHCONF_GENERATE_ENTRIES` is enabled, the build system automatically generates entries for the PERIPHCONF partition based on the devicetree.
495
+
To determine which peripherals are in use, the build system analyzes the devicetree as follows:
496
496
497
497
#. Enumerate all peripheral nodes and include only those with a ``status`` property set to ``okay``.
498
498
#. Parse peripheral-specific attributes (for example, the ``owned-channels`` property in DPPIC nodes).
499
499
#. Collect GPIO pin assignments from all pin references (for example, ``pinctrl`` entries).
500
500
501
501
It then generates the appropriate configuration values by reusing existing properties.
502
+
The build system outputs the generated entries as a C file named :file:`periphconf_entries_generated.c` in the build directory, which is added as a source file to the build.
503
+
The generated C code uses the macros defined in :file:`zephyr/soc/nordic/common/uicr/uicr.h` to insert entries into a special PERIPHCONF section in the ELF file which can be read by the UICR image.
502
504
503
-
See the following table for a mapping between the devicetree input used by ``nrf-regtool`` and the resulting output in the automatically migrated :file:`periconf_migrated.c` file.
505
+
See the following table for a mapping between the devicetree input used by the PERIPHCONF entry generator script and the resulting output in the :file:`periphconf_entries_generated.c` file.
504
506
505
-
.. list-table:: Mapping between devicetree and Migrated PERIPHCONF output (UICR Configuration)
507
+
.. list-table:: Mapping between devicetree and PERIPHCONF entry output (UICR Configuration)
0 commit comments