ZMS Provisioning Data
Overview
This sample demonstrates how to pre-populate a ZMS partition with data generated at build time.
It uses gen_zms_provision_data.py to create provisioning records from an input file
(example_data.txt) and from inline ID/data pairs defined in CMakeLists.txt.
The provisioning script generates a standalone provisioning-only image, provisioned_raw.hex
(no application code), which is then merged with zephyr.hex into zephyr_with_provision.hex.
west flash is configured to program that merged image, so a single west flash call
programs both the application and the provisioning data.
provisioned_raw.hex remains available as a separate artifact, e.g. to flash or inspect the
provisioning data independently of the application.
Requirements
nrf54h20dk/nrf54h20/cpuapp
Building and Running
Build the sample for nrf54h20dk/nrf54h20/cpuapp:
west build -b nrf54h20dk/nrf54h20/cpuapp samples/subsys/kvss/zms/zms_provisioning
Flash the sample:
west build -b nrf54h20dk/nrf54h20/cpuapp samples/subsys/kvss/zms/zms_provisioning
west flash
Generated Artifacts
The build always produces these files in build/zephyr:
zephyr.hex: application imageprovisioned_raw.hex: standalone provisioning-only image (no application code)zephyr_with_provision.hex: merged image, used bywest flash