sysbuild: fast_pair: Separate provisioning data generation

[mkapala-nordic]

Changed FP provisioning data generation to be handled separately from the SB_CONFIG_BT_FAST_PAIR under the sysbuild Kconfig option SB_CONFIG_BT_FAST_PAIR_PROVISIONING_DATA_GENERATE. It allows to build the app image with FP provisioning data but without the Fast Pair stack enabled, which could be added for example after DFU.
The SB_CONFIG_BT_FAST_PAIR option has been left to keep backwards compability in how the Fast Pair stack is enabled and enables the FP provisioning data generation by default.

Jira: NCSDK-31128

TODO:

• docs update after solution review

[NordicBuilder]

CI Information

^{To view the history of this post, clich the 'edited' button above}
Build number: 2

Inputs:

Sources:

sdk-nrf: PR head: 6b7493695716bf8c059bcec1fd8933b892d10e15

more details

sdk-nrf:

PR head: 6b7493695716bf8c059bcec1fd8933b892d10e15
merge base: 444b6e0383ab83bd6036536e56be87f7d36b6e86
target head (main): c2e0a5880f68268b0974e7af56a65c40ee7de635
Diff

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (5)

cmake
│  ├── sysbuild
│  │  │ fast_pair_hex.cmake
subsys
│  ├── bluetooth
│  │  ├── services
│  │  │  ├── fast_pair
│  │  │  │  ├── CMakeLists.txt
│  │  │  │  │ fp_registration_data.c
sysbuild
│  ├── CMakeLists.txt
│  │ Kconfig.bt_fast_pair

Outputs:

Toolchain

Version: aedb4c0245
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:aedb4c0245_bece0367df

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

• ◻️ Toolchain - Skipped: existing toolchain is used
• ✅ Build twister
• ❌ Integration tests
  • ✅ test-sdk-audio
  • ✅ desktop52_verification
  • ✅ test-fw-nrfconnect-boot
  • ✅ test-fw-nrfconnect-apps
  • ✅ test_ble_nrf_config
  • ✅ test-fw-nrfconnect-ble_mesh
  • ✅ test-fw-nrfconnect-ble_samples
  • ✅ test-fw-nrfconnect-chip
  • ✅ test-fw-nrfconnect-nfc
  • ❌ test-fw-nrfconnect-nrf-iot_cloud
  • ✅ test-fw-nrfconnect-nrf-iot_libmodem-nrf
  • ✅ test-fw-nrfconnect-nrf-iot_serial_lte_modem
  • ✅ test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • ✅ test-fw-nrfconnect-nrf-iot_samples
  • ✅ test-fw-nrfconnect-nrf-iot_lwm2m
  • ✅ doc-internal
  • ✅ test-fw-nrfconnect-nrf-iot_thingy91
  • ✅ test-fw-nrfconnect-nrf_crypto
  • ✅ test-fw-nrfconnect-proprietary_esb
  • ✅ test-fw-nrfconnect-rpc
  • ✅ test-fw-nrfconnect-rs
  • ✅ test-fw-nrfconnect-fem
  • ✅ test-fw-nrfconnect-tfm
  • ✅ test-fw-nrfconnect-thread
  • ✅ test-fw-nrfconnect-zigbee
  • ✅ test-sdk-find-my
  • ✅ test-fw-nrfconnect-nrf-iot_mosh
  • ✅ test-fw-nrfconnect-nrf-iot_positioning
  • ✅ test-sdk-sidewalk
  • ✅ test-sdk-wifi
  • ✅ test-low-level
  • ✅ test-sdk-pmic-samples
  • ✅ test-sdk-mcuboot
  • ✅ test-sdk-dfu
  • ✅ test-fw-nrfconnect-ps
  • ✅ test-secdom-samples-public

Note: This message is automatically posted and updated by the CI

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud