caf_sensor_manager - parse error: undefined node label 'cpuapp_bellboard'

[tldr]

parse error: undefined node label 'cpuapp_bellboard'

https://developer.nordicsemi.com/nRF_Connect_SDK/doc-legacy/latest/nrf/releases_and_maturity/migration/nRF54H20_migration_2.7/migration_guide_2.6.99-cs2_to_2.7_application.html
I see there is some change with bellboard.

bellboard_cpuapp

cpuapp_bellboard

I am able to get the caf_sensor_manager to work using the nrf5340dk and v2.7.0-rc3.  I would like to use the thingy.  I've defined overlay and conf files to match the ones provided for the DK.  I am getting an error about cpuapp_bellboard not being defined.

[Sigurd]

Hi

v2.7.0-rc3

This is just a release candidate version. Please test with v2.7.0 when that is ready.

[tldr]

Uninstalled all my old toolchains.  Using thingy53 I understand this isn't a supported target so here's hoping.

I am running into:

CMake Warning at C:/ncs/v2.7.0/zephyr/CMakeLists.txt:895 (message):
No SOURCES given to Zephyr library: ..__nrf__subsys__caf__modules

-- Found partition manager static configuration : C:/ncs/v2.7.0/zephyr/boards/nordic/thingy53/pm_static_thingy53_nrf5340_cpuapp.yml
Partition 'mcuboot' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_pad' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_primary' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_primary_app' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_primary_1' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_secondary' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_secondary_1' is not included in the dynamic resolving since it is statically defined.
Partition 'pcd_sram' is not included in the dynamic resolving since it is statically defined.
-- Found partition manager static configuration CPUNET: C:/ncs/v2.7.0/zephyr/boards/nordic/thingy53/pm_static_thingy53_nrf5340_cpuapp.yml
Traceback (most recent call last):
File "C:\ncs\v2.7.0\nrf\scripts\partition_manager.py", line 2045, in <module>
main()
File "C:\ncs\v2.7.0\nrf\scripts\partition_manager.py", line 1022, in main
args, ranges_configuration = parse_args()
File "C:\ncs\v2.7.0\nrf\scripts\partition_manager.py", line 928, in parse_args
parser.add_argument(f'--{x}-size', required=True, type=lambda z: int(z, 0))
File "argparse.py", line 1441, in add_argument
File "argparse.py", line 1806, in _add_action
File "argparse.py", line 1643, in _add_action
File "argparse.py", line 1455, in _add_action
File "argparse.py", line 1592, in _check_conflict
File "argparse.py", line 1601, in _handle_conflict_error
argparse.ArgumentError: argument --sram_primary-size: conflicting option string: --sram_primary-size
CMake Error at C:/ncs/v2.7.0/nrf/cmake/sysbuild/partition_manager.cmake:145 (message):
Partition Manager failed, aborting. Command:
C:/ncs/toolchains/ce3b5ff664/opt/bin/python.exe;C:/ncs/v2.7.0/nrf/scripts/partition_manager.py;--input-files;C:/ncs/v2.7.0/nrf/samples/caf_sensor_manager/build/b0n/zephyr/include/generated/pm.yml;C:/ncs/v2.7.0/nrf/samples/caf_sensor_manager/build/b0n/modules/nrf/subsys/partition_manager/pm.yml.secure_boot_storage;C:/ncs/v2.7.0/nrf/samples/caf_sensor_manager/build/zephyr/include/generated/pm.yml;C:/ncs/v2.7.0/nrf/samples/caf_sensor_manager/build/b0n/zephyr/include/generated/pm.yml;C:/ncs/v2.7.0/nrf/samples/caf_sensor_manager/build/b0n/modules/nrf/subsys/partition_manager/pm.yml.secure_boot_storage;C:/ncs/v2.7.0/nrf/samples/caf_sensor_manager/build/zephyr/include/generated/pm.yml;--regions;sram_primary;flash_primary;sram_primary;flash_primary;--output-partitions;C:/ncs/v2.7.0/nrf/samples/caf_sensor_manager/build/partitions_CPUNET.yml;--output-regions;C:/ncs/v2.7.0/nrf/samples/caf_sensor_manager/build/regions_CPUNET.yml;--flash_primary
-dynamic-partition;remote;--sram_primary-size;0x10000;--sram_primary-base-address;0x21000000;--sram_primary-placement-strategy;complex;--sram_primary-dynamic-partition;sram_primary;--flash_primary-size;0x40000;--flash_primary-base-address;0x1000000;--flash_primary-placement-strategy;complex;--flash_primary-device;flash_controller;--flash_primary-default-driver-kconfig;CONFIG_SOC_FLASH_NRF;--sram_primary-size;0x10000;--sram_primary-base-address;0x21000000;--sram_primary-placement-strategy;complex;--sram_primary-dynamic-partition;sram_primary;--flash_primary-size;0x40000;--flash_primary-base-address;0x1000000;--flash_primary-placement-strategy;complex;--flash_primary-device;flash_controller;--flash_primary-default-driver-kconfig;CONFIG_SOC_FLASH_NRF

[Sigurd]

Hi!

I've defined overlay and conf files to match the ones provided for the DK

Could you post the files that you added? And what command you used for building the project?

[tldr]

the whole tree is up there;  I committed the changes for caf_sensor_manager here.
github.com/.../ca5f244a45ee3dfedd1441f4bdafc282109a87fd

west build -b thingy53_nrf5340_cpuapp . 

[Sigurd]

Yeah, I see the same. Likely a conflict since the thingy uses the pm_static_thingy53_nrf5340_cpuapp.yml and the DK just uses dynamic partitioning.