Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

RE: Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

NoRG — Thu, 19 Jun 2025 13:50:29 GMT

Hi,

thanks for tracking that down!

Best regards,

/NoRG

RE: Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

Marte Myrvold — Thu, 19 Jun 2025 07:25:19 GMT

Hi,

It seems like the light bulb's custom_nrf54l15dk_nrf54l15_cpuapp.conf file is not included in the build when manually selecting prj.conf. The MCUboot board config is included (light_bulb/sysbuild/mcuboot/boards/custom_nrf54l15dk_nrf54l15_cpuapp.conf), but not the main application (light_bulb/boards/custom_nrf54l15dk_nrf54l15_cpuapp.conf).

I have reported this internally to the VS Code team.

As a workaround, you can manually add custom_nrf54l15dk_nrf54l15_cpuapp.conf in the build configuration or avoid selecting any files in the base configuration file.

Best regards,
Marte

RE: Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

NoRG — Tue, 17 Jun 2025 17:26:05 GMT

Hi Marte,

thank you for your support!

I was able to narrow it down! It seems to cause problems with custom boards (and only there!) when specifying the project file ‘prj.conf’ in the build configuration. If you leave the field blank, it works! Maybe you have an idea what could be causing this, because of course it's also about different project configurations and this way you can only ever use the standard configuration prj.conf.

My goal is to collect all board dependencies in the board directory and only save the different configurations of the project (prj.conf, prj_release.prj, etc.) in the project folder. This is no longer possible with custom boards. With DK, specifying the *.prj files works as expected.

/NoRG

RE: Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

Marte Myrvold — Tue, 17 Jun 2025 08:31:18 GMT

Hi,

I have attached the custom board files and light bulb with the build folder included.

devzone.nordicsemi.com/.../custom_5F00_54l_5F00_matter_5F00_bulb.zip

Best regards,
Marte

RE: Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

NoRG — Mon, 16 Jun 2025 14:42:56 GMT

Hi Marte,

I really appreciate your time. I tried to repeat all your steps - but without success. Can you send me the two directories (board and light_bulb) including the binaries?

Here are mine:

-rw-r--r--@ 1 xxx yyy 2461648 16 Jun 16:35 light_bulb_cust/Custom/merged.hex
-rw-r--r--@ 1 xxx yyy 2461956 7 Jun 09:23 light_bulb_cust/NordicDK/merged.hex

Regards
/NoRG

RE: Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

Marte Myrvold — Mon, 16 Jun 2025 13:54:22 GMT

Hi,

I had to add the following:

CONFIG_CHIP_SPI_NOR=y
CONFIG_SPI_NOR_FLASH_LAYOUT_PAGE_SIZE=4096

With this, the application started up. I added it in light_bulb/boards/custom_nrf54l15dk_nrf54l15_cpuapp.conf.

Best regards,
Marte

RE: Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

NoRG — Tue, 10 Jun 2025 18:19:22 GMT

Hi,

I overlooked that you also mentioned the activation of the GPIOs. The serial is not necessary for the test, but without any GPIO it makes no sense at all :-)

Unfortunately it does not work even WITH these changes.

To try further I added more lines:

# SPI
CONFIG_SPI=y
CONFIG_SPI_NOR=y
CONFIG_SPI_NOR_SFDP_DEVICETREE=y
CONFIG_SPI_NOR_FLASH_LAYOUT_PAGE_SIZE=4096

# required by SPI driver
CONFIG_MULTITHREADING=y

... but it doesn't work either. I used to try everything possible, but it hasn't worked.

And here is the problem: there is no inheritance of a given board configuration or a way to copy at least all configuration from an existing board. Is it possible for you to check out if the binary runs on the nRF54L15DK? In my case there is no sign of life: no flashing leds, no uart etc.

You can also send me your binary - so I can check it out quickly!

Thank you for your help!

/NoRG

RE: Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

Marte Myrvold — Tue, 10 Jun 2025 11:25:31 GMT

Hi,

[quote user="NoRG"]Unfortunately, the second one does not work. The LEDs on the board remain off (LED2 does not flash and there is no UART output). I have no idea where to look next.[/quote]

This could be related to this:

[quote user="Marte.M"]Please note that I have not enabled serial, console, or GPIO in custom_nrf54l15dk_nrf54l15_cpuapp_defconfig. If you plan to use these, I recommend adding them as in custom_nrf54l15dk_nrf54l15_cpuapp_defconfig.[/quote]

Please try adding this to custom_nrf54l15dk_nrf54l15_cpuapp_defconfig:

# Enable UART driver
CONFIG_SERIAL=y

# Enable console
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y

# Enable GPIO
CONFIG_GPIO=y

Best regards,
Marte

RE: Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

NoRG — Sat, 07 Jun 2025 08:22:34 GMT

Hi Marte,

Thanks for your reply!

I also managed to create the binary file.

I used exactly your two ZIP files and added 1) a build configuration with the original DK and 2) a build configuration for the custom DK (both with proj.conf):

-rw-r--r--@ 1 xxx yyy 2461956 7 Jun 09:23 NordicDK/merged.hex
-rw-r--r--@ 1 xxx yyy 2461340 7 Jun 10:04 Custom/merged.hex

Unfortunately, the second one does not work. The LEDs on the board remain off (LED2 does not flash and there is no UART output). I have no idea where to look next.

Which files do you need from me to investigate the problem further?

By the way, when I changed the original DK configuration, I even managed to change the pins and get my own board working without an external flash (using my own partition table that fits completely in the internal flash). But I really want to run both boards just by changing the board configuration and share the sources in one place.

Best regards
/NoRG

RE: Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

Marte Myrvold — Fri, 06 Jun 2025 08:43:16 GMT

Hi,

I have made a version of the light bulb and a custom nRF54L15 board that builds. Please check if this fixes your problem, and let me know if you have any issues.

Here are the things I did.

Light bulb sample:

Added board Kconfig and overlay file under boards/
Added board Kconfig and overlay file under sysbuild/mcuboot/boards/
Added static partition file

Board files

Generated the board with "create new board" in VS Code
Created the following files:
- custom_nrf54l15dk_common.dtsi: copied everything from nrf54l15dk_common.dtsi
- custom_nrf54l15dk_cpuapp.dtsi: copied everything from nrf54l_05_10_15_cpuapp_common.dtsi
Modified the following files:
- custom_nrf54l15dk_nrf54l15_cpuapp.dts: included custom_nrf54l15dk_cpuapp.dtsi
- custom_nrf54l15dk-pinctrl.dtsi: copied everything from nrf54l15dk_nrf54l_05_10_15-pinctrl.dtsi
- Kconfig.defconfig: added that ROM_START_OFFSET is 0 if MCUboot is not enabled

Please note that I have not enabled serial, console, or GPIO in custom_nrf54l15dk_nrf54l15_cpuapp_defconfig. If you plan to use these, I recommend adding them as in custom_nrf54l15dk_nrf54l15_cpuapp_defconfig.

I have not tested the sample, only that it builds successfully.

To build for a custom board, you need to set the board root. You can set this in settings in VS Code like this:

You can also add it as a part of the build command, e.g.:

west build -b custom_nrf54l15dk/nrf54l15/cpuapp -- -DBOARD_ROOT=<my_board_root>

Please note that the board root is where the 'boards' directory is located. So, if you for example have a board under /home/username/nordic/boards/vendorname/custom_nrf54l15dk, then the board root is /home/username/nordic.

Best regards,
Marte

devzone.nordicsemi.com/.../custom_5F00_nrf54l15dk.zip devzone.nordicsemi.com/.../6825.light_5F00_bulb.zip

RE: Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

NoRG — Thu, 05 Jun 2025 15:11:23 GMT

Hi Marte,

thanks for the quick reply. I would say it's easier to do these few steps in a clean SDK environment:

- Create a custom board
- Generate a new app as a copy of the Matter light_bulb app
- build it with the new custom board

I've tried so many versions, but without success. I'd be surprised if it works for you in first place ;-)

But of course, I can send you my project and the board directory. Can I send you a PM?

Best regards

/NoRG

RE: Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

Marte Myrvold — Thu, 05 Jun 2025 14:56:30 GMT

Hi,

Can you share the complete build log?

Please also share your board files and project so I can test it on my side.

Best regards,
Marte

RE: Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

NoRG — Thu, 05 Jun 2025 13:02:02 GMT

Yes, these are the detailed steps:

- create an application by copying the light_bulb example
- create build config "build" -> works
- create board "mydk" in an external folder, added path to BOARD_ROOT (settings of VS-Extension)
- create build config "myDKConf" wit board "mydk", base config: prj.conf

[11/23] Generating new Factory Data...
FAILED: light_bulb_mydk/zephyr/factory_data.hex ... nrfconnect/nrfconnect_factory_data.schema --offset --size
generate_nrfconnect_chip_factory_data.py: error: argument --offset: expected one argument

- pm_static_nrf54l15dk_nrf54l15_cpuapp.yml nach pm_static_mydk_nrf54l15_cpuapp.yml kopiert

-> Partition manager failed: Incorrect amount of gaps found in static configuration. There must be exactly one gap in the static configuration to support placing the dynamic partitions (such as 'app'). Gaps found (2):0xd800-0x165000 0x17d000-0x172000 The most common solution to this problem is to fill the smallest of these gaps with statically defined partition(s) until there is only one gap left. Alternatively re-order the already defined static partitions so that only one gap remains.
Failed to partition region flash_primary, size of region: 1462272

(base) xxx:projects/nordic/light_bulb_mydk $ find . -name \*.overlay
./sysbuild/mcuboot/app.overlay
./sysbuild/mcuboot/boards/nrf7002dk_nrf5340_cpuapp.overlay
./sysbuild/mcuboot/boards/nrf5340dk_nrf5340_cpuapp.overlay
./sysbuild/mcuboot/boards/nrf52840dk_nrf52840.overlay
./sysbuild/mcuboot/boards/nrf54l15dk_nrf54l15_cpuapp.overlay
./boards/nrf7002dk_nrf5340_cpuapp.overlay
./boards/nrf54l15dk_nrf54l15_cpuapp_ns.overlay
./boards/nrf5340dk_nrf5340_cpuapp.overlay
./boards/nrf21540dk_nrf52840.overlay
./boards/nrf52840dk_nrf52840.overlay
./boards/nrf54l15dk_nrf54l15_cpuapp.overlay

Where shall I put what overlay?

I did:

- sysbuild/mcuboot/boards $ cp nrf54l15dk_nrf54l15_cpuapp.conf mydk_nrf54l15_cpuapp.conf
- sysbuild/mcuboot/boards $ cp nrf54l15dk_nrf54l15_cpuapp.overlay mydk_nrf54l15_cpuapp.overlay

->

- Found devicetree overlay: projects/nordic/light_bulb_mydk/sysbuild/mcuboot/boards/mydk_nrf54l15_cpuapp.overlay
devicetree error: projects/nordic/light_bulb_mydk/sysbuild/mcuboot/boards/mydk_nrf54l15_cpuapp.overlay:23 (column 1): parse error: undefined node label 'mx25r64'
CMake Error at /opt/nordic/ncs/v3.0.2/zephyr/cmake/modules/dts.cmake:305 (execute_process):
execute_process failed command indexes:

Whatever I do, I get always new funny error messages ...

No idea what to do. And this is only part 1 where I just want get a clone of my DK.

/NoRG

RE: Problems building an example (matter light bulb) on a "custom board" that is identically configured as the dev kit nRF54L15DK

Patrick — Thu, 05 Jun 2025 10:32:13 GMT

I have run into similar problems in the past. In the sysbuild/mcuboot folder in your project, have you created overlays and pm_static_<board>.yml for your board definition?