Yes build works properly on version 3.0.2.
For 3.1 branch, maybe the 3.1.1 fixes some issues: Release nRF Connect SDK v3.1.1 · nrfconnect/sdk-nrf · GitHub.
I think the compilation issue with nfc_t2t_lib is due to the nfct node being disabled in the device tree. It is on in the nrf54l15dk device tree, and when enabled in my overlay file the compile issue went away.
&nfct {
status = “okay”;
};
2 Likes
Any news about the compressed partition scheme?
I had edit also the boards\xiao_nrf54l15_nrf54l15_cpuapp.overlay file in my project.
Be careful with the syntax. I had to correct the quotation marks:
&nfct {
status = "okay";
};
Not it fails at another error.
There is a tutorial for NCS >=3.0.2:
Hi everyone,
Just a quick update — the Wiki for XIAO nRF54L15 has been updated with a Matter example! 
You can check it out and give it a try here: Seeed Studio XIAO nRF54L15 Matter | Seeed Studio Wiki
We’ve completed the initial work, and more examples are on the way — we’re currently working on adapting them.
Looking forward to hearing your feedback!
Currently, only two routines are supported. Additional routines will be gradually added in the future.
Could you clarify the list of compatible Matter samples?
Regards
Guess I’m going to be busy today!
2 Likes
Hi there,
SO, Check it… You must open the Nrf Terminal window even if you don’t use it, for it to build or make the merged.hex YMMV 
(bug or undocumented enhancement) 
even if you use the SWD. 
HTH
GL 
PJ 
All of the samples in the list will build now.
Hi there,
I’m concerned and can you verify " * WE are basically trading off features (factory data, OTA, fallback) to make the build fit in internal memory. is this the case ?
- It’s fragile: if you corrupt the single image, recovery must be via hardware (e.g. SWD) rather than fallback.
I hope this is NOT the case, I hope someone tests for this as well.
Bleeding edge here so expect to get some cuts folks. 
HTH
GL PJ
Hi there,
So I was able to build and setup the Matter light_bult with the nRF54L15_DK board. Next will be the Xiao as the Target
after Building and flashing, I get the proper output.
D: 215 [IN]SecureSession[0x20011e48]: Allocated Type:2 LSID:19038
I: 221 [SVR]Server Listening...
I: 224 [DL]Device Configuration:
I: 227 [DL] Serial Number: 11223344556677889900
I: 231 [DL] Vendor Id: 65521 (0xFFF1)
I: 235 [DL] Product Id: 32773 (0x8005)
I: 238 [DL] Product Name: not-specified
I: 242 [DL] Hardware Version: 0
I: 245 [DL] Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
I: 250 [DL] Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
I: 257 [DL] Manufacturing Date: 2022-01-01
I: 260 [DL] Device Type: 65535 (0xFFFF)
I: 264 [SVR]SetupQRCode: [MT:6FCJ142C00KA0648G00]
I: 269 [SVR]Copy/paste the below URL in a browser to see the QR Code:
I: 275 [SVR]https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A6FCJ142C00KA0648G00
I: 284 [SVR]Manual pairing code: [34970112332]
E: 288 [DL]Long dispatch time: 247 ms, for event type 2
I: 294 [DL]CHIPoBLE advertising started
I: 297 [DL]NFC Tag emulation started
uart:~$ I: 30297 [DL]CHIPoBLE advertising mode changed to slow
I: 30303 [DL]CHIPoBLE advertising started
and the QR code
Alexa, Finds it without issue.
HTH
GL PJ
1 Like
I tried to build the xiao_nrf54l15 Thermostat sample. OK for NCS 3.0.2, but not 3.1.x.
Testing it with Home Assistant
I think more useful would be the steps you used to create this, along with pictures. We knew you could do it as the resident NRF expert, but now we would like to know just “how” you did it.
Yes, I know - “go watch the videos”, but there’s a lot of “fluff” in the videos that isn’t required, as well as some “gotchas” that are never mentioned.
Hi there,
LOL, not so fast , there with the “expert buissnatch”
I couldn’t get it to go with the Xiao yet with the two additional files from the wiki, so still a WIP. That was with the nRF54L15_DK board.
I updated the Toolchain in NRF_SDK_connect for vs code first, then
made sure the python and west were updated as well.
I followed the changes in the wiki, but targeted the DK instead on the Xiao, just as a sanity check. (ie. no ovelays or any custom stuff)
I used both 3.1.1 sdk & toolchain, YMMV
open “nrf/samples/matter/light_bulb”
build it…& Flash it. Roberts your uncle
same thing worked for the nRF52840_DK good QR was generated.
For the nFR54L15 Xiao it’s a different build command and you need to add the two overlays. Then build and flash. (you can use what you like to flash btw)
"west build -b xiao_nrf54l15/nrf54l15/cpuapp/ns nrf/samples/matter/light_bulb
– -DOVERLAY_CONFIG=overlay-xiao-nosys.conf
-DDTC_OVERLAY_FILE=xiao_nrf54l15.overlay
west flash
once it builds and flashes ok, a reset will give you the Web address out of the com port(second port on the DK HIGHER one) for QR code(or manual code too), the rest is up to what system your adding it to, HA, Alexa, Google_home , etc.
I’ll run through it a few more times, so I’ll try and do a step by step with some desktop video.
HTH
GL PJ
Switching to the xiao to flash(ext) from the DK (built-in) is not working nice and easy like the 52840_DK so some cockpit troubles there, may jump to the seeed debugger and openOCD.
all a WIP
With the matter sample overlay files, I don’t think you actually need to select the overlay because they are placed in the boards directory and named in such a way that NRF connect automatically picks them up during build if you choose the right CPU app.
But I could be wrong.
Hi there,
So , two things I see on this. Success is totally toolchain & SDK version dependent and if you have been a good little developer updating your system. it may come up YMMV
in @Toastee0 situ he’s up to date and correct about the Overlay, check it" from the dev forum…
Nordic’s commit explicitly adds matter-idl to build requirements for 3.1.0, which is why v3.0.x worked and 3.1.0 doesn’t until you add this. GitHub
- Make sure your repos are actually at 3.1.0 (I’ve seen Matter fail to update while west keeps going):
west update
west list | findstr matter
The DevZone thread calls this out. If connectedhomeip/matter isn’t at the v3.1.0 rev from the manifest, fix that first.
west build -p always -b nrf54l15dk/nrf54l15/cpuapp -d build . # from the sample dir
Extras / notes:
- The “
__ASSERT() statements are globally ENABLED” line is just a warning (debug-friendly default). You can turn it off withCONFIG_ASSERT=nif you want, but it’s unrelated. - You can also follow Nordic’s sample doc for the Thermostat on nRF54L15 if you want to sanity-check your build flags/board string. docs.nordicsemi.com
- If you insist on using the Zephyr SDK toolchain instead of the NCS toolchain, you’ll have to manually install all the Python deps the NCS toolchain bundles (including
matter-idl). That mismatch is exactly why some people see it build in VS Code (NCS toolchain) but fail from a “plain” shell (Zephyr SDK). Nordic’s accepted answer calls that out.
HTH
GL PJ
Working on a walk through…Stay tuned.
My situation is even more complex, as I’m running a custom 3.1.99 from my own forked nrf-sdk and zephyr-rtos repositories, as that’s what’s required to add a driver. I’m having decent success getting things going, but it’s certainly a steep learning curve.
1 Like
Hi there,
In the words of the legendary Super bowl Dis’ser’ Kendrick Lamar "Somebody’s got-ta’ do it!
Lead the way, LOL… right watch out for the crevasse 
Good stuff, seeedineers appreciate the help, discovery and progress we report. So the more the merrier
GL PJ
Bottom line too many ways to get to the end piece with these Parts sadly, more work is definitely needed.
I’ve created a repository with adaptations for the XIAO nRF54L15, enabling all Matter examples from NCS v3.0.2 to run successfully.
2 Likes
Great, thank you very much.
Is the OTA working properly with your configuration?