I have an nRF54L15DK and a custom-designed nRF54L15 board. These two boards use different pins for peripherals. The NCS version used is v2.9.0. I compiled a Matter project, which runs on the nRF54L15DK, but there is no response when flashing it to our custom board. Then I compiled a periodic_adv project, which works on both the nRF54L15DK and our custom board. I can scan the advertisements from the device using nRFConnect. Why does the Matter project fail to run on our custom board?
Hello,
The Matter samples include the bootloader (MCUBoot) by default. When using the nRF54L15DK as the build target, the onboard SPI flash is used for the secondary FW slot (as defined by the pm_static_nrf54l15dk_nrf54l15_cpuapp.yml file). This means that if you use this build target on a board that doesn't have this flash, or uses a different pinout, the bootloader will not be able to access the secondary slot and will refuse to boot the application.
Default memory layout for Matter lock sample
Does your custom board include SPI flash?
Best regards,
Vidar
Hello,
The Matter samples include the bootloader (MCUBoot) by default. When using the nRF54L15DK as the build target, the onboard SPI flash is used for the secondary FW slot (as defined by the pm_static_nrf54l15dk_nrf54l15_cpuapp.yml file). This means that if you use this build target on a board that doesn't have this flash, or uses a different pinout, the bootloader will not be able to access the secondary slot and will refuse to boot the application.
Default memory layout for Matter lock sample
Does your custom board include SPI flash?
Best regards,
Vidar
