nRF54L15-DK Matter Over Thread start

[ADM1N]

Hello to everyone!

I bought nRF54L15-DK for Matter Over Thread developing and prototyping. 

Before nRF54L15 I tried ESP32C6 XIAO + Arduino IDE and it worked but it was Matter Over WiFi. 

I want to run real Matter Over WiFi on nRF54L15-DK because as I understand it can do this and Nordic made examples in VS Code (NCS). 

I tried to compile and flash: Hello World, BLE Beacon, Thread CLI. And it works without any issues. I opened example, setup build target (nrf54l15dk/nrf54l15/cpuapp and nrf54l15dk/nrf54l15/cpuapp/ns) I tried both targets and here is no different. In Hello World, BLE Beacon, Thread CLI everything perfect and any matter example doesn't work. 

I didn't touch config on any examples.

Add Build Configuration (added target which nordic recommends (with /ns))

proj.conf and other files are original (I didn't edit it).

After compiling and flash it - nothing in UARTs VCOM0/VCOM1

proj.conf from ./

Fullscreen 7382.prj.txt Download

#
# Copyright (c) 2022 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#

# This sample uses Kconfig.defaults to set options common for all
# samples. This file should contain only options specific for this sample
# or overrides of default values.

# Enable CHIP
CONFIG_CHIP=y
CONFIG_CHIP_PROJECT_CONFIG="src/chip_project_config.h"

# Configure ZAP file name
CONFIG_NCS_SAMPLE_MATTER_ZAP_FILE_PATH="${APPLICATION_CONFIG_DIR}/src/default_zap/lock.zap"

# 32774 == 0x8006 (example lock-app)
CONFIG_CHIP_DEVICE_PRODUCT_ID=32774
CONFIG_STD_CPP17=y

# Enable Matter extended announcement and increase duration to 1 hour.
CONFIG_CHIP_BLE_EXT_ADVERTISING=y
CONFIG_CHIP_BLE_ADVERTISING_DURATION=60

# Add support for LEDs and buttons on Nordic development kits
CONFIG_DK_LIBRARY=y

# Bluetooth Low Energy configuration
CONFIG_BT_DEVICE_NAME="MatterLock"

# Suspend devices when the CPU goes into sleep
CONFIG_PM_DEVICE=y

# Other settings
CONFIG_THREAD_NAME=y
CONFIG_MPU_STACK_GUARD=y
CONFIG_RESET_ON_FATAL_ERROR=n
CONFIG_CHIP_LIB_SHELL=y
CONFIG_NCS_SAMPLE_MATTER_TEST_SHELL=y

# Reduce application size
CONFIG_USE_SEGGER_RTT=n
CONFIG_MATTER_LOG_LEVEL_INF=y
CONFIG_CHIP_APP_LOG_LEVEL=3

# Enable Factory Data feature
CONFIG_CHIP_FACTORY_DATA=y
CONFIG_CHIP_FACTORY_DATA_BUILD=y

txt because website can't upload *.conf

./build/zephyr/.conf

Fullscreen 0458.config.txt Download

# SB_CONFIG_WIFI_NRF70 is not set
SB_CONFIG_NRF_DEFAULT_IPC_RADIO=y
SB_CONFIG_DFU_MULTI_IMAGE_PACKAGE_BUILD=y
SB_CONFIG_DFU_MULTI_IMAGE_PACKAGE_APP=y
SB_CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY=y
SB_CONFIG_MCUBOOT_UPDATEABLE_IMAGES=1
SB_CONFIG_PM_OVERRIDE_EXTERNAL_DRIVER_CHECK=y
SB_CONFIG_MATTER_FACTORY_DATA_GENERATE=y
SB_CONFIG_BOARD="nrf54l15dk"
SB_CONFIG_BOARD_REVISION=""
SB_CONFIG_BOARD_NRF54L15DK=y
SB_CONFIG_BOARD_NRF54L15DK_NRF54L15_CPUAPP_NS=y
SB_CONFIG_BOARD_QUALIFIERS="nrf54l15/cpuapp/ns"
SB_CONFIG_SOC="nrf54l15"
SB_CONFIG_SOC_SERIES="nrf54l"
SB_CONFIG_SOC_FAMILY="nordic_nrf"
SB_CONFIG_SOC_FAMILY_NORDIC_NRF=y
SB_CONFIG_SOC_SERIES_NRF54LX=y
SB_CONFIG_SOC_NRF54L15=y
SB_CONFIG_SOC_NRF54L15_CPUAPP=y
SB_CONFIG_ARMV8_1_M_PMU_EVENTCNT=8

#
# Sysbuild image configuration
#

#
# Modules
#

#
# Available modules.
#

#
# nrf (/opt/nordic/ncs/v3.1.0/nrf)
#
SB_CONFIG_PARTITION_MANAGER=y
SB_CONFIG_PM_MCUBOOT_PAD=0x800
SB_CONFIG_BUILD_OUTPUT_BIN=y
SB_CONFIG_BUILD_OUTPUT_HEX=y
SB_CONFIG_BOARD_IS_NON_SECURE=y
SB_CONFIG_APPCORE_REMOTE_BOARD_TARGET_CPUCLUSTER="cpuapp"
SB_CONFIG_APPCORE_REMOTE_DOMAIN="CPUAPP"
SB_CONFIG_SUPPORT_FLPRCORE=y
SB_CONFIG_FLPRCORE_REMOTE_BOARD_TARGET_CPUCLUSTER="cpuflpr"

#
# Secure Bootloader
#
# SB_CONFIG_SECURE_BOOT_APPCORE is not set
# end of Secure Bootloader

#
# MCUboot configuration
#
# SB_CONFIG_MCUBOOT_HARDWARE_DOWNGRADE_PREVENTION is not set
SB_CONFIG_MCUBOOT_MAX_UPDATEABLE_IMAGES=4
SB_CONFIG_MCUBOOT_APPLICATION_IMAGE_NUMBER=0
SB_CONFIG_MCUBOOT_NETWORK_CORE_IMAGE_NUMBER=-1
SB_CONFIG_MCUBOOT_WIFI_PATCHES_IMAGE_NUMBER=-1
SB_CONFIG_MCUBOOT_QSPI_XIP_IMAGE_NUMBER=-1
SB_CONFIG_MCUBOOT_MCUBOOT_IMAGE_NUMBER=-1
SB_CONFIG_MCUBOOT_MIN_UPDATEABLE_IMAGES=1
SB_CONFIG_MCUBOOT_MIN_ADDITIONAL_UPDATEABLE_IMAGES=0
SB_CONFIG_MCUBOOT_ADDITIONAL_UPDATEABLE_IMAGES=0
SB_CONFIG_MCUBOOT_APP_SYNC_UPDATEABLE_IMAGES=y
# SB_CONFIG_BOOT_SIGNATURE_TYPE_PURE is not set
SB_CONFIG_BOOT_IMG_HASH_ALG_SHA512=y
# SB_CONFIG_MCUBOOT_SIGNATURE_USING_KMU is not set
# SB_CONFIG_MCUBOOT_USE_ALL_AVAILABLE_RAM is not set
# end of MCUboot configuration

#
# Bluetooth Fair Pair
#
SB_CONFIG_BT_FAST_PAIR_MODEL_ID=0x1000000
SB_CONFIG_BT_FAST_PAIR_ANTI_SPOOFING_PRIVATE_KEY=""
# end of Bluetooth Fair Pair

SB_CONFIG_DFU_ZIP=y
SB_CONFIG_DFU_ZIP_APP=y
# SB_CONFIG_DFU_ZIP_BLUETOOTH_MESH_METADATA is not set
SB_CONFIG_MATTER=y
SB_CONFIG_MATTER_FACTORY_DATA_MERGE_WITH_FIRMWARE=y
SB_CONFIG_MATTER_OTA=y
SB_CONFIG_MATTER_OTA_IMAGE_FILE_NAME="matter.ota"

#
# Wi-Fi
#
# end of Wi-Fi

# SB_CONFIG_HPF is not set
# SB_CONFIG_APPROTECT_DISABLE is not set
# SB_CONFIG_APPROTECT_LOCK is not set
# SB_CONFIG_APPROTECT_USER_HANDLING is not set
SB_CONFIG_APPROTECT_NO_SYSBUILD=y
# SB_CONFIG_SECURE_APPROTECT_DISABLE is not set
# SB_CONFIG_SECURE_APPROTECT_LOCK is not set
# SB_CONFIG_SECURE_APPROTECT_USER_HANDLING is not set
SB_CONFIG_SECURE_APPROTECT_NO_SYSBUILD=y
SB_CONFIG_SUPPORT_CRACEN=y

#
# CRACEN
#
SB_CONFIG_CRACEN_MICROCODE_LOAD_MCUBOOT=y
SB_CONFIG_CRACEN_MICROCODE_LOAD_ONCE=y
# end of CRACEN

#
# TF-M
#
# SB_CONFIG_TFM_OTP_PSA_CERTIFICATE_REFERENCE is not set
# end of TF-M

SB_CONFIG_SUPPORT_FIRMWARE_LOADER_SMP_SVR_MINI_BOOT=y
SB_CONFIG_ZEPHYR_NRF_MODULE=y
# end of nrf (/opt/nordic/ncs/v3.1.0/nrf)

SB_CONFIG_ZEPHYR_HOSTAP_MODULE=y
SB_CONFIG_ZEPHYR_MCUBOOT_MODULE=y
SB_CONFIG_ZEPHYR_MBEDTLS_MODULE=y
SB_CONFIG_ZEPHYR_OBERON_PSA_CRYPTO_MODULE=y
SB_CONFIG_ZEPHYR_TRUSTED_FIRMWARE_M_MODULE=y
SB_CONFIG_ZEPHYR_PSA_ARCH_TESTS_MODULE=y
SB_CONFIG_ZEPHYR_CJSON_MODULE=y
SB_CONFIG_ZEPHYR_AZURE_SDK_FOR_C_MODULE=y
SB_CONFIG_ZEPHYR_CIRRUS_LOGIC_MODULE=y
SB_CONFIG_ZEPHYR_OPENTHREAD_MODULE=y
SB_CONFIG_ZEPHYR_MEMFAULT_FIRMWARE_SDK_MODULE=y
SB_CONFIG_ZEPHYR_COREMARK_MODULE=y
SB_CONFIG_ZEPHYR_CANOPENNODE_MODULE=y
SB_CONFIG_ZEPHYR_CHRE_MODULE=y
SB_CONFIG_ZEPHYR_LZ4_MODULE=y
SB_CONFIG_ZEPHYR_NANOPB_MODULE=y
SB_CONFIG_ZEPHYR_TF_M_TESTS_MODULE=y
SB_CONFIG_ZEPHYR_ZSCILIB_MODULE=y
SB_CONFIG_ZEPHYR_CMSIS_MODULE=y
SB_CONFIG_ZEPHYR_CMSIS_DSP_MODULE=y
SB_CONFIG_ZEPHYR_CMSIS_NN_MODULE=y
SB_CONFIG_ZEPHYR_CMSIS_6_MODULE=y
SB_CONFIG_ZEPHYR_FATFS_MODULE=y
SB_CONFIG_ZEPHYR_HAL_NORDIC_MODULE=y
SB_CONFIG_ZEPHYR_HAL_ST_MODULE=y
SB_CONFIG_ZEPHYR_HAL_TDK_MODULE=y
SB_CONFIG_ZEPHYR_HAL_WURTHELEKTRONIK_MODULE=y
SB_CONFIG_ZEPHYR_LIBLC3_MODULE=y
SB_CONFIG_ZEPHYR_LIBMETAL_MODULE=y
SB_CONFIG_ZEPHYR_LITTLEFS_MODULE=y
SB_CONFIG_ZEPHYR_LORAMAC_NODE_MODULE=y
SB_CONFIG_ZEPHYR_LVGL_MODULE=y
SB_CONFIG_ZEPHYR_MIPI_SYS_T_MODULE=y
SB_CONFIG_ZEPHYR_NRF_WIFI_MODULE=y
SB_CONFIG_ZEPHYR_OPEN_AMP_MODULE=y
SB_CONFIG_ZEPHYR_PERCEPIO_MODULE=y
SB_CONFIG_ZEPHYR_PICOLIBC_MODULE=y
SB_CONFIG_ZEPHYR_SEGGER_MODULE=y
SB_CONFIG_ZEPHYR_TINYCRYPT_MODULE=y
SB_CONFIG_ZEPHYR_UOSCORE_UEDHOC_MODULE=y
SB_CONFIG_ZEPHYR_ZCBOR_MODULE=y
SB_CONFIG_ZEPHYR_NRFXLIB_MODULE=y
SB_CONFIG_ZEPHYR_NRF_HW_MODELS_MODULE=y
SB_CONFIG_ZEPHYR_CONNECTEDHOMEIP_MODULE=y

#
# Unavailable modules, please install those via the project manifest.
#
# end of Modules

# SB_CONFIG_WARN_EXPERIMENTAL is not set
SB_CONFIG_WARN_DEPRECATED=y
SB_CONFIG_SUPPORT_BOOTLOADER=y
SB_CONFIG_SUPPORT_BOOTLOADER_MCUBOOT_ZEPHYR=y
# SB_CONFIG_BOOTLOADER_NONE is not set
SB_CONFIG_BOOTLOADER_MCUBOOT=y
# SB_CONFIG_MCUBOOT_MODE_SINGLE_APP is not set
# SB_CONFIG_MCUBOOT_MODE_SWAP_USING_OFFSET is not set
SB_CONFIG_MCUBOOT_MODE_SWAP_USING_MOVE=y
# SB_CONFIG_MCUBOOT_MODE_SWAP_WITHOUT_SCRATCH is not set
# SB_CONFIG_MCUBOOT_MODE_SWAP_SCRATCH is not set
# SB_CONFIG_MCUBOOT_MODE_OVERWRITE_ONLY is not set
# SB_CONFIG_MCUBOOT_MODE_DIRECT_XIP is not set
# SB_CONFIG_MCUBOOT_MODE_DIRECT_XIP_WITH_REVERT is not set
# SB_CONFIG_MCUBOOT_MODE_RAM_LOAD is not set
# SB_CONFIG_MCUBOOT_MODE_FIRMWARE_UPDATER is not set
# SB_CONFIG_MCUBOOT_MODE_SINGLE_APP_RAM_LOAD is not set
SB_CONFIG_SIGNATURE_TYPE="ED25519"
# SB_CONFIG_BOOT_SIGNATURE_TYPE_NONE is not set
# SB_CONFIG_BOOT_SIGNATURE_TYPE_RSA is not set
# SB_CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256 is not set
SB_CONFIG_BOOT_SIGNATURE_TYPE_ED25519=y
SB_CONFIG_BOOT_SIGNATURE_KEY_FILE="/opt/nordic/ncs/v3.1.0/bootloader/mcuboot/root-ed25519.pem"
SB_CONFIG_SUPPORT_BOOT_ENCRYPTION=y
# SB_CONFIG_BOOT_ENCRYPTION is not set
SB_CONFIG_SUPPORT_FIRMWARE_LOADER_SMP_SVR=y

#
# Build options
#
# SB_CONFIG_COMPILER_WARNINGS_AS_ERRORS is not set
# end of Build options

Build Logs:

5238.build_logs.txt

PC: 
MacBook Pro 15 2017 (intel mac);
OS: Mac OS Ventura Version 13.7.8 (22H730);
Tried on Bootcamp: Windows 11 Pro;

Hope for your help =)

[Sunil vignesh]

Hi, 
try to build it with prj.conf and ns.overlay, also check the VCOM1 is connect in board configurator.

ADM1N said:

real Matter Over WiFi on nRF54L15-DK

nRF54L15 is not a WiFi device , its a Thread device (Matter over Thread will support)

 nRF7002 DK will support Matter over Wifi 

[ADM1N]

Sorry, my mistake. I mean "Real Matter Over Thread". 

I added config like you said. But there is still no logs on VCOM1/0 (UART). 
I also tried force torn it on:

# Enable all debug features

CONFIG_USE_SEGGER_RTT=n

CONFIG_SHELL=y

CONFIG_OPENTHREAD_SHELL=y

CONFIG_CONSOLE=y

CONFIG_UART_CONSOLE=y

CONFIG_SERIAL=y

CONFIG_LOG=y

CONFIG_LOG_MODE_MINIMAL=n

CONFIG_ASSERT_VERBOSE=y

CONFIG_ASSERT_NO_FILE_INFO=y

CONFIG_PRINTK=y

CONFIG_PRINTK_SYNC=y

CONFIG_THREAD_NAME=y

CONFIG_LOG_DEFAULT_LEVEL=3

 

Fullscreen 2061.prj.txt Download

#
# Copyright (c) 2022 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#

# Config from ./prj.conf

# Enable CHIP
CONFIG_CHIP=y
CONFIG_CHIP_PROJECT_CONFIG="src/chip_project_config.h"

# Configure ZAP file name
CONFIG_NCS_SAMPLE_MATTER_ZAP_FILE_PATH="${APPLICATION_CONFIG_DIR}/src/default_zap/light_bulb.zap"

# 32773 == 0x8005 (example lighting-app)
CONFIG_CHIP_DEVICE_PRODUCT_ID=32773
CONFIG_STD_CPP17=y

# Enable Matter pairing automatically on application start.
CONFIG_CHIP_ENABLE_PAIRING_AUTOSTART=y

# Enable Matter extended announcement and increase duration to 1 hour.
CONFIG_CHIP_BLE_EXT_ADVERTISING=y
CONFIG_CHIP_BLE_ADVERTISING_DURATION=60

# Add support for LEDs and buttons on Nordic development kits
CONFIG_DK_LIBRARY=y
CONFIG_PWM=y

# Bluetooth Low Energy configuration
CONFIG_BT_DEVICE_NAME="MatterLight"

# Other settings
CONFIG_THREAD_NAME=y
CONFIG_MPU_STACK_GUARD=y
CONFIG_RESET_ON_FATAL_ERROR=n
CONFIG_CHIP_LIB_SHELL=y
CONFIG_NCS_SAMPLE_MATTER_TEST_SHELL=y

# Reduce application size
CONFIG_USE_SEGGER_RTT=n

# Enable Factory Data feature
CONFIG_CHIP_FACTORY_DATA=y
CONFIG_CHIP_FACTORY_DATA_BUILD=y

# Enable all debug features
CONFIG_USE_SEGGER_RTT=n
CONFIG_SHELL=y
CONFIG_OPENTHREAD_SHELL=y
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_LOG=y
CONFIG_LOG_MODE_MINIMAL=n
CONFIG_ASSERT_VERBOSE=y
CONFIG_ASSERT_NO_FILE_INFO=y
CONFIG_PRINTK=y
CONFIG_PRINTK_SYNC=y
CONFIG_THREAD_NAME=y
CONFIG_LOG_DEFAULT_LEVEL=3

[ADM1N]

Still nothing. Did you edit config? And could you send me your merged.hex for test?
As I see you using linux. Im using Mac and windows. Can it be a problem?
My merged.hex:
50625.merged.hex

[Sunil vignesh]

Your Merged.hex is worked for me 
please check and confirm the LED0 is blinking after merged.hex flashed on the board 

[Sunil vignesh]

Also in nrf connect for Desktop -> BOARD CONFIGURATOR. open it connect the DK and check all these are ON

[ADM1N]

looks strange. I will make a video +-1 minute duration. I hope you will see my mistake (video on YouTube)

[Sunil vignesh]

okay, share the link. I'll see

[ADM1N]

My try to run Matter Light Build example (7:30 because I demonstrated all settings): https://youtu.be/P0tIRNcn8rQ

Hello World in Quick Start: https://youtu.be/rhQDEHtsJpI

[Sunil vignesh]

I noticed that after the terminal stopped working, you disconnected and reconnected the device.
Instead of doing that, please press the RESET button on the DK to restart it.

Also, instead of using the VS Code terminal, try using the serial terminal in nRF Connect for Desktop or a terminal-based tool like picocom.

Make sure to open the terminal before programming the board so that we can capture the logs immediately.

After programming the device:

Verify that LED0 on the board is blinking.

Open the nRF Connect mobile app and perform a BLE scan to check if any BLE device is advertising.

Note:
Please confirm that the same serial terminal works with the Quickstart sample. After flashing the Quickstart sample, check whether the terminal you selected displays logs correctly. If not, switch to a different serial terminal.  check the SERIAL PORT is selected in 115200 BAUD RATE

[ADM1N]

As I know reconnect usb is the same as click RESET. I tried to do everything. 
Also I tried to read logs in different programs but no result on Mac and windows. 
LED0 didn’t blink. I think I’m doing something wrong. 
I seen https://wiki.seeedstudio.com/xiao_nrf54l15_sense_matter/ tutorial. And I tried it. 

[ADM1N]

Finally! I did it! Thank you! 
What I did:

1. Used windows 11 pro (bootcamp)

2. Copied new project example - light bulb

3. created configuration (like you said)

4. Connected board to pc

5. opened nRF Connect for Desctop > Serial Terminal > COM6(vcom1) and turned on autodetect lines in config. 
6. Erase memory in programmer. 
7. Turned on Dev mode in windows:

Settings > Privacy & Security > For Developers > Developer Mode

8. Restart VS Code

9. First Build 

10. Flash Using UI (maybe west flash-d)

11. Look at console (Serial Terminal at nrf connect for desktop)