Adding FOTA Support to custom board

Hi,

Im currently trying to add FOTA via BLE to my project.

To get familiar with this i wanted to add FOTA as described in the nrf connect intermediate course lesson 5.

So i added FOTA and it worked like a charm using the nrf54l15DK. So i edited the board to be my custom board. Thats wqhere the problems started.

So i thought lets make a new board to eliminate all problems coming with my real custom board.

I followed the instructions in the intermediate course lessong 3 excercise 2 to add my own board.

I used the nrf54l15DK as the base and made all changes described as well as removed the configurations for the soc´s other that the L15.

Currently my board definition looks like this:



To make sure everything works fine i compiled everything using the DK -> That worked.
I changed the Board to be this new board -> now im missing the spi?

The error message displayed is:

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

I made no changes to any dts file other than the ones described in the exercise and removing all mentions of the other soc variants.

Can you help me what my Problem is?
Maybe you can provide a minimal board definition for BLE FOTA?

Thank you in advance
Hendrik

Parents
  • Hi,

    MCUboot has some board overlays over here. As you can see, there is one for the nRF54L15 in there.
    I suspect you are missing some of those. Try for example to put them in your_project/sysbuild/mcuboot.conf.

    Regards,
    Sigurd Hellesvik

  • Hi,

    After building as well as pristine building it, it seemed to work.

    Now i wonder how the buildsystem knows where to look for the specific KConfig Files.
    It was the same for the sysbuild.conf (wich is in the main folder btw).
    How does sysbuild know what to look for?

    Do you have any resources on that?

    Regards
    Hendrik

  • Hi,

        I followed the instructions in the intermediate course lessong 3 excercise 2 to add my own board and facing the exact same issue which you were facing, can you tell how did you resolve it.

    My app is buiding successfully but mcuboot is failing and giving below error.

    "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_114'"

    I didn't change anything in any dts file.

Reply
  • Hi,

        I followed the instructions in the intermediate course lessong 3 excercise 2 to add my own board and facing the exact same issue which you were facing, can you tell how did you resolve it.

    My app is buiding successfully but mcuboot is failing and giving below error.

    "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_114'"

    I didn't change anything in any dts file.

Children
Related