nrf-sdk bootloader example fails to build with NCS 2.8.0

We're trying to get ahead of the Sysbuild / hardware model migration in order to pin to the latest LTS. Sysbuild, MCUboot, and cpunet are proving difficult to port. We're trying to use https://github.com/nrfconnect/sdk-nrf/tree/main/samples/bootloader as a reference but this build is failing.

west build -b nrf5340dk/nrf5340/cpuapp --sysbuild
...
/opt/nordic/ncs/v2.8.0/nrf/samples/bootloader/src/main.c:116:33: error: 'PM_B0_ADDRESS' undeclared (first use in this function); did you mean 'PM_ADDRESS'?
  116 |         int err = fprotect_area(PM_B0_ADDRESS, PM_B0_SIZE);
      |                                 ^~~~~~~~~~~~~
      |                                 PM_ADDRESS
/opt/nordic/ncs/v2.8.0/nrf/samples/bootloader/src/main.c:116:33: note: each undeclared identifier is reported only once for each function it appears in
/opt/nordic/ncs/v2.8.0/nrf/samples/bootloader/src/main.c:116:48: error: 'PM_B0_SIZE' undeclared (first use in this function); did you mean 'PM_OTP_SIZE'?
  116 |         int err = fprotect_area(PM_B0_ADDRESS, PM_B0_SIZE);
      |                                                ^~~~~~~~~~
      |                                                PM_OTP_SIZE
[28/36] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/opt/nordic/ncs/v2.8.0/modules/hal/nordic/nrfx/drivers/src/nrfx_dppi.c.obj
ninja: build stopped: subcommand failed.
FAILED: _sysbuild/sysbuild/images/bootloader-prefix/src/bootloader-stamp/bootloader-build /opt/nordic/ncs/v2.8.0/nrf/samples/bootloader/build/_sysbuild/sysbuild/images/bootloader-prefix/src/bootloader-stamp/bootloader-build 
cd /opt/nordic/ncs/v2.8.0/nrf/samples/bootloader/build/bootloader && /opt/nordic/ncs/toolchains/15b490767d/Cellar/cmake/3.21.0/bin/cmake --build .
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /opt/nordic/ncs/toolchains/15b490767d/bin/cmake --build /opt/nordic/ncs/v2.8.0/nrf/samples/bootloader/build

  • This is fresh NCS 2.8.0 installation
  • west update / west zephyr-export are all okay
  • vscode validate toolchain passes
  • vscode build fails with the same output

Is this is a known issue?

Parents Reply Children
Related