Created the file boards\xiao_nrf54l15_nrf54l15_cpuapp.overlay
with the following content:
/ {
chosen {
ncs,zigbee-timer = &timer20;
};
};
// Restore full RRAM and SRAM space - by default some parts are dedicated to FLRP
&cpuapp_rram {
reg = <0x0 DT_SIZE_K(1524)>;
};
&cpuapp_sram {
reg = <0x20000000 DT_SIZE_K(256)>;
ranges = <0x0 0x20000000 0x40000>;
};
// TODO: re-enable HWFC once it's fixed
&uart20 {
/delete-property/ hw-flow-control;
};
&timer20 {
status = "okay";
};
// Disable lsm6dso to avoid MPU FAULT error
&lsm6dso {
status = "disabled";
};
// Disable uart21 to avoid MPU FAULT error
&uart21 {
status = "disabled";
};
In the file platform-seeedboards/zephyr/boards/arm/xiao_nrf54l15/Kconfig.defconfig,
I replaced:
config HAS_BT_CTLR
default BT
with:
config BT_CTRL
bool
default BT
However, I donāt understand why uart21 triggers an MPU FAULT. This is annoying because it prevents me from using the UART on pins D6/D7.
If anyone has a solution, Iād be very interested.
Itās working fine when the module is powered via USB, but when powering it through the 3.3V or 5V pins, the module doesnāt start. I donāt know why. Any ideas?
Thanks, itās working now. I had removed the line CONFIG_CONSOLE=y, but apparently that wasnāt enough. Itās necessary to explicitly set CONFIG_CONSOLE=n.
Hi, PJ
Haha, thatās right, youāve discovered a hidden easter egg. But itās still under development. I believe it will be ready with a better experience and meet everyone soon!
Small inquiry: is Zigbee being deprioritized by Nordic? The nRF Connect SDK is already at version 3.2, yet the Zigbee plugin remains at 2.9. I would have expected it to follow the SDKās ongoing updates.