CONFIG_FPROTECT_APP

Lock image partition using FPROTECT

Type: bool

Help

The flash partition which contains the image hex file should never be
written to. Set this option to enable a module which will perform
a 'fprotect_area' operation during system initialization before
the kernel is initialized. This will ensure that the appropriate
locking mechanism is configured to not allow write operations to the
memory partition which contains the image hex file. Note that this
imposes a requirement to the start address and size of the image
hex file: they must both be aligned with the locking granularity
of the locking mechanism available for the current hardware. See
'FPROTECT_BLOCK_SIZE' and set the partition sizes in the system so
that this is aligned with the 'app' partition. The start and size
of the 'app' partition can be found by either inspecting the file
'pm_config.h' in your build directory, or by invoking the
'partition_manager_report' target.

Direct dependencies

PARTITION_MANAGER_ENABLED && FPROTECT

(Includes any dependencies from ifs and menus.)

Defaults

No defaults. Implicitly defaults to n.

Kconfig definition

At <nRF>/lib/fprotect/Kconfig:69

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:33 → <Zephyr>/modules/Kconfig:6 → <nRF>/doc/_build/kconfig/Kconfig.modules:2 → <nRF>/Kconfig.nrf:94 → <nRF>/lib/Kconfig:17

Menu path: (Top) → Modules → nrf (/home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf) → Nordic nRF Connect → Libraries

config FPROTECT_APP
    bool "Lock image partition using FPROTECT"
    depends on PARTITION_MANAGER_ENABLED && FPROTECT
    help
      The flash partition which contains the image hex file should never be
      written to. Set this option to enable a module which will perform
      a 'fprotect_area' operation during system initialization before
      the kernel is initialized. This will ensure that the appropriate
      locking mechanism is configured to not allow write operations to the
      memory partition which contains the image hex file. Note that this
      imposes a requirement to the start address and size of the image
      hex file: they must both be aligned with the locking granularity
      of the locking mechanism available for the current hardware. See
      'FPROTECT_BLOCK_SIZE' and set the partition sizes in the system so
      that this is aligned with the 'app' partition. The start and size
      of the 'app' partition can be found by either inspecting the file
      'pm_config.h' in your build directory, or by invoking the
      'partition_manager_report' target.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)