Error building Matter sample for XIAO nRF54L15 board

[lboue]

@grobasoz

EFR32MG24 as used in the XIAO MG24 supports OTA updates with Matter when using the Silicon Labs SDKs for development. The same applies to Zigbee.

OK for the SL ‘Explorer Kit’, but do you have a tutorial explaining how to do it for the XIAO-MG24 board?

[TT0m]

Hi. Is there any acitve community for nrf 52840 sense anywhere? I am stucked, but I see very little user base here and cannot even start a topic. Thanks

[grobasoz]

@lboue

do you have a tutorial explaining how to do it for the XIAO-MG24 board?

Nope - I don’t use the XIAO MG24 for Matter projects utilising OTA, I use my own modules in products I design.

Since there is sufficient flash on the XIAO MG24, I don’t see why it can’t be used.

[lboue]

@grobasoz

Nope - I don’t use the XIAO MG24 for Matter projects utilising OTA, I use my own modules in products I design.

So if I understand correctly:

1. Create a project in SimplicityStudio v5.
2. Add your code.
3. Build the binary.
4. Flash the binary onto your board with OpenOCD

Right?

[grobasoz]

Essentially
(I wish it was that simple )

Since this is an NRF post perhaps we should start a new post with the XIAO MG24 as the topic?

[lboue]

Here

Build projects for XIAO MG24 using SimplicityStudio

This is the continuation of the other thread about MG24 boards @grobasoz What would be the missing steps to add to the list?

[Seeed_Atom]

Hi PJ,

Thank you for your feedback, and we totally understand your expectation for external flash. What you pointed out is indeed a very practical limitation: Nordic nRF54L15 DK and XIAO nRF52840 do include onboard flash, which makes supporting OTA and a broader feature set much smoother.

For this XIAO series, our initial design goal was to maintain the ultra-compact size and low cost, which is why we did not add extra external flash at the beginning. That said, we completely acknowledge your concern and will seriously evaluate whether to introduce an external flash option in future versions, so users can fully leverage the potential of the nRF54 series.

The current compressed partition scheme is mainly to provide the community with a workable OTA entry point, ensuring Matter examples can compile and run properly. While it is a temporary compromise, we are conducting strict stability and functionality validation, and once it passes, we will update the Wiki and GitHub repositories immediately.

And yes — we also heard the strong request for bringing back the RGB LED. We’ll discuss this with the hardware team internally and see if it can be restored in future batches.

Thank you again for your continuous attention and suggestions — they are really helpful for us to optimize our product direction. Please keep the feedback coming, and we’ll make sure to update you here with the latest progress.

Best,
Atom

[lboue]

@Seeed_Atom

The current compressed partition scheme is mainly to provide the community with a workable OTA entry point, ensuring Matter examples can compile and run properly. While it is a temporary compromise, we are conducting strict stability and functionality validation, and once it passes, we will update the Wiki and GitHub repositories immediately.

Hello,

Do you think you can publish this in September?

Regards

[PJ_Glasso]

Hi there,

Awesome, Thank you for ALL the hard work and I believe it could be the BEST Xiao in the family. I can appreciate your efforts on the Tiny Size being “Xiao”. Like fitting 10 pounds of stuff in a 1 lb. bag.

Thank you for continuing to make GREAT products. I’ll be watching, waiting and creating in the meantime.

Great Stuff…
GL PJ

@Seeed_Atom

we also heard the strong request for bringing back the RGB LED.

LOL, such a tiny thing… like the pea under the mattress story. ends up a big bump! it IS a BIG deal for Visually eyeballing the status. (everyone agrees)

[Toastee0]

Hmm, neopixel on a single gpio, or 3 gpio to rgb channels?

[StarSphere-1024]

Here is an example of successful compilation and normal operation.
https://github.com/StarSphere-1024/thermostat

Can you help me to verify it?

Note: Please make sure to use the latest platform-seeedboards and correctly configure it to the board root of nrf Connect.

[lboue]

@StarSphere-1024

https://github.com/StarSphere-1024/thermostat

I tried but it failed:

C:/GitHub/nRF_matter_thermostat/prj_release.conf:50: warning: attempt to assign the value 'n' to the undefined symbol CHIP_NFC_COMMISSIONING
Parsing C:/GitHub/nRF_matter_thermostat/Kconfig
Loaded configuration 'C:/GitHub/Seeed-platform-seeedboards/zephyr/boards/arm/xiao_nrf54l15/xiao_nrf54l15_nrf54l15_cpuapp_defconfig'
Merged configuration 'C:/GitHub/nRF_matter_thermostat/prj_release.conf'

error: Aborting due to Kconfig warnings

Merged configuration 'C:/GitHub/nRF_matter_thermostat/xiao_nRF54/nRF_matter_thermostat/zephyr/.config.sysbuild'
CMake Error at C:/ncs/v3.1.0/zephyr/cmake/modules/kconfig.cmake:377 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  C:/ncs/v3.1.0/nrf/cmake/modules/kconfig.cmake:83 (include)
  C:/ncs/v3.1.0/zephyr/cmake/modules/zephyr_default.cmake:131 (include)
  C:/ncs/v3.1.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/ncs/v3.1.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:9 (find_package)


-- Configuring incomplete, errors occurred!
CMake Error at cmake/modules/sysbuild_extensions.cmake:530 (message):
  CMake configure failed for Zephyr project: nRF_matter_thermostat

  Location: C:/GitHub/nRF_matter_thermostat
Call Stack (most recent call first):
  cmake/modules/sysbuild_images.cmake:43 (ExternalZephyrProject_Cmake)
  cmake/modules/sysbuild_default.cmake:21 (include)
  C:/ncs/v3.1.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
  C:/ncs/v3.1.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  C:/ncs/v3.1.0/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
  template/CMakeLists.txt:10 (find_package)

-- Configuring incomplete, errors occurred!

[StarSphere-1024]

You seem to be compiling the release version that I didn’t test.Can you try the debug version first?

[lboue]

Same issue. I had to comment this line:
CONFIG_CHIP_NFC_COMMISSIONING=y

I also had to tinker with quite a few files to get the paths recognized.

It also seems the nfc_t2t_lib.h file included in

#include <nfc_t2t_lib.h>

Error:

NFCOnboardingPayloadManagerImpl.cpp is missing in the SDK
obj/src/platform/nrfconnect/nrfconnect.NFCOnboardingPayloadManagerImpl.cpp.o
c:\ncs\v3.1.0\modules\lib\matter\src\platform\nrfconnect\nfconboardingpayloadmanagerimpl.cpp:28:10: fatal error: nfc_t2t_lib.h: No such file or directory
   28 | #include <nfc_t2t_lib.h>
      |          ^~~~~~~~~~~~~~~
compilation terminated.

It looks a lot like DIY.

[StarSphere-1024]

Perhaps the NCS versions we are using are not the same. The version I am using is v3.0.2. I’m currently installing the v3.1.0 environment for testing.
Waiting for my good news

[lboue]

Yes I have the v3.1.0 version installed.

[lboue]

@StarSphere-1024

I’m currently installing the v3.1.0 environment for testing.

Do you manage to build the Matter sample with v3.1.0?

[Toastee0]

The current seeed board defs, and a fresh install of both the 3.1.0 SDK and toolchain cleared up a bunch of issues. I recommend doing that, as they Incorporated all the fixes that were useful in my repo.

[lboue]

I have already downloaded the latest commit from the Seeed git repository but I a getting errors regarding NFC in the nRF SDK.

[StarSphere-1024]

I tested it, and there is a problem with NCS v3.1.0 that makes it impossible to compile. I’m trying to fix it. By the way, can you help me try to see if it works properly on version 3.0.2?