sysbuild/DFU OTA build error: undefined reference to '__device_dts_ord_116'

[Ryan S]

Hi,

I'd like to raise this issue I am having with the v3.0.1 sdk wherein the final build stages I get the message attached 

• I am using the Lesson 9 exercise 5 sample
  https://github.com/NordicDeveloperAcademy/ncs-inter/tree/main/l9/l9_e5_sol
• I did not have this issue when I last built with 2.7.0 sdk.
• I have also carefully followed instructions from the intermediate course.
  https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-9-bootloaders-and-dfu-fota/topic/exercise-5-fota-over-bluetooth-low-energy/
• I am building for bl54l15_dvk/nrf54l15/cpuapp

Fullscreen 5518.build_error.txt Download

FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map <path>/zephyr_pre0.map
cmd.exe /C "cd . && <toolchain path>/arm-zephyr-eabi-gcc.exe -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=<path>/zephyr_pre0.map \
-Wl,--whole-archive app/libapp.a zephyr/libzephyr.a ... \
-Wl,--no-whole-archive zephyr/kernel/libkernel.a \
-L<build path> -lgcc && \
cmd.exe /C "cd /D <path>/mcuboot/zephyr && cmake -E true""

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_116'

collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

If anybody has advice for this issue, that would be greatly appreciated. 

Thanks!

[Turbo J]

There are significant config and DTS overlay changes between 2.7.x and 3.x NCS SDK versions. Look at example code from the 3.0.x SDK.

[Ryan S]

Hi, 

Thanks for your fast response. 

Confirming that it does seem to be a board issue since I was able to build it with the standard nrf54l15 files. 

I will look into this more for my board (from a different manufacturer) which expands on the nordic nrf54l15 chip

Still, if anyone has further advice I would like to hear it. 

Thanks

[Edvin]

Hello,

It is probably something that is not enabled properly in the board files, yes. To investigate, you need to check in your build folder. Go to build\<application_name>\zephyr\include\generated\zephyr\devicetree_generated.h.

At the start of this file, you will see a list of the nodes. If your build log still says "undefined reference to '__device_dts_ord_116", then check what node number 116 is. But check your build log. The number may change when you do modifications to your application.

Best regards,

Edvin

[Ryan S]

Hi Edvin, 

I've just found this thread which highlights something that might be related

https://devzone.nordicsemi.com/f/nordic-q-a/123497/ncs-3-0-2-nrf54l15_ns_partition-dtsi-missing?focus=true

I recompiled the firmware using my manufacturer board and the nordic board from the latest sdk-zephyr repo. As it turns out, I was using older nordic board files

I get this error referencing a missing file for both boards 

D:/ncs/v3.0.1/zephyr/boards/nordic/nrf54l15dk/nrf54l15dk_nrf54l15_cpuapp.dts:23:10: fatal error: nordic/nrf54l15_partition.dtsi: No such file or directory
   23 | #include <nordic/nrf54l15_partition.dtsi>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Thanks!

[Edvin]

Are you using board files from the correct NCS version?

Did you find the missing "undefined reference to __device dts_ord_116"?

Best regards,

Edvin