Building the Asset Tracker V2 for Actinius Icarus v2 fails with error

I am attempting to configure and build the Asset Tracker v2 for my Actinius Icarus v2 board.but the build is failing.

Setup:

  • nRF Connect SDK v 2.9.0
  • Board target: actinius_icarus/nrf9160/ns (in VS-code)

Initially, I had the following error

In file included from <command-line>:
C:/actinius/asset_tracker_v2/build/asset_tracker_v2/zephyr/include/generated/zephyr/autoconf.h:71:35: fatal error: led_state_def.h: No such file or directory
71 | #define CONFIG_LED_STATE_DEF_PATH "led_state_def.h"

 After following the steps here: Building the Asset Tracker for Actinius Icarus v2 fails  - in the folder "include", copy the folder "thingy91_nrf9160_ns" and its contents into a new folder "actinius_icarus_ns"

I am now getting the following failure:

[186/191] Linking C executable zephyr\zephyr_pre0.elf
FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map C:/actinius/asset_tracker_v2/build/mcuboot/zephyr/zephyr_pre0.map
cmd.exe /C "cd . && C:\ncs\toolchains\b620d30767\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -Os -DNDEBUG -gdwarf-4 -gdwarf-4 zephyr/CMakeFiles/zephyr_pre0.dir/misc/empty_file.c.obj -o zephyr\zephyr_pre0.elf zephyr/CMakeFiles/offsets.dir/./arch/arm/core/offsets/offsets.c.obj -T zephyr/linker_zephyr_pre0.cmd -Wl,-Map=C:/actinius/asset_tracker_v2/build/mcuboot/zephyr/zephyr_pre0.map -Wl,--whole-archive app/libapp.a zephyr/libzephyr.a zephyr/arch/common/libarch__common.a zephyr/arch/arch/arm/core/libarch__arm__core.a zephyr/arch/arch/arm/core/cortex_m/libarch__arm__core__cortex_m.a zephyr/arch/arch/arm/core/cortex_m/cmse/libarch__arm__core__cortex_m__cmse.a zephyr/lib/libc/minimal/liblib__libc__minimal.a zephyr/lib/libc/common/liblib__libc__common.a zephyr/soc/soc/nrf9160/libsoc__nordic.a zephyr/boards/actinius/icarus/actinius_common/libboards__actinius__common.a zephyr/drivers/clock_control/libdrivers__clock_control.a zephyr/drivers/console/libdrivers__console.a zephyr/drivers/flash/libdrivers__flash.a zephyr/drivers/gpio/libdrivers__gpio.a zephyr/drivers/pinctrl/libdrivers__pinctrl.a zephyr/drivers/serial/libdrivers__serial.a zephyr/drivers/timer/libdrivers__timer.a modules/nrf/lib/fprotect/lib..__nrf__lib__fprotect.a modules/nrf/subsys/fw_info/lib..__nrf__subsys__fw_info.a modules/nrf/drivers/hw_cc3xx/lib..__nrf__drivers__hw_cc3xx.a modules/mcuboot/boot/bootutil/zephyr/libmcuboot_util.a modules/hal_nordic/nrfx/libmodules__hal_nordic__nrfx.a -Wl,--no-whole-archive zephyr/kernel/libkernel.a -LC:/actinius/asset_tracker_v2/build/mcuboot/zephyr zephyr/arch/common/libisr_tables.a -mcpu=cortex-m33 -mthumb -mabi=aapcs -mfpu=fpv5-sp-d16 -mfloat-abi=hard -mfp16-format=ieee -fuse-ld=bfd -Wl,--gc-sections -Wl,--build-id=none -Wl,--sort-common=descending -Wl,--sort-section=alignment -Wl,-u,_OffsetAbsSyms -Wl,-u,_ConfigAbsSyms -nostdlib -static -Wl,-X -Wl,-N -Wl,--orphan-handling=warn -Wl,-no-pie C:/ncs/v2.9.1/nrfxlib/crypto/nrf_cc310_platform/lib/cortex-m33/hard-float/no-interrupts/libnrf_cc310_platform_0.9.19.a C:/ncs/v2.9.1/nrfxlib/crypto/nrf_cc310_bl/lib/cortex-m33/hard-float/no-interrupts/libnrf_cc310_bl_0.9.12.a -L"c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/thumb/v8-m.main+fp/hard" -lc -lgcc && cmd.exe /C "cd /D C:\actinius\asset_tracker_v2\build\mcuboot\zephyr && C:\ncs\toolchains\b620d30767\opt\bin\cmake.exe -E true""
c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/flash/libdrivers__flash.a(spi_nor.c.obj):(.rodata.spi_nor_0_config+0x0): undefined reference to `__device_dts_ord_117'
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
[10/20] No configure step for 'asset_tracker_v2'
FAILED: _sysbuild/sysbuild/images/bootloader/mcuboot-prefix/src/mcuboot-stamp/mcuboot-build C:/actinius/asset_tracker_v2/build/_sysbuild/sysbuild/images/bootloader/mcuboot-prefix/src/mcuboot-stamp/mcuboot-build
cmd.exe /C "cd /D C:\actinius\asset_tracker_v2\build\mcuboot && C:\ncs\toolchains\b620d30767\opt\bin\cmake.exe --build ."
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\b620d30767\opt\bin\cmake.EXE' --build C:/actinius/asset_tracker_v2/build
Any clues as of the issue?
Parents Reply
  • There's a larger difference between NCS 2.5.0 and the current NC 2.9.0/1.

    As in the other ticket, I guess asking the manufacturer Actinius will be the fastest way.

    > rodata.spi_nor_0_config+0x0

    I guess, this is caused by using somehow an external flash (spi_nor), which is then missing in the device tree. Does your Ikarus board have a flash (AFAIK it requires 2.0 of that board)? If so, you may need to ensure, that the right version of the ikarus 2.0 board files are used. And ensure, that CONFIG_SPI is enabled (maybe in the application board files).

    > CONFIG_SECURE_BOOT=n


    That's not longer working for sysbuilds (NCS 2.9.0). This has moved to the Kconfig.sysbuild.

    Anyway: all in all, I guess you need to ask Actinius.

Children
No Data
Related