I noticed the board files linked to in the getting started page do not have separate versions for the sense and non-sense versions of the board similar to how it is set up for the xiao nrf52840.
When using the linked board files the lsm6dso defaults to status “okay”, but that hardware doesn’t exist on the non-sense version. I also see that pdm_imu_pwr defaults with “regulator-boot-on”, but there is no status property. Maybe that implies it is not really enabled. I see that that property is deleted in the zephyr-lowpower example, so it seems like it might actually be doing something.
I don’t have much expertise with these files, but it seems like it could be a source of issues, or at least confusion.
Below is what I added to my .overlay to delete/disable nodes for non-existent HW. I’m thinking it might be better to delete the disabled nodes instead of disable. Any advice from the experts?
&gpio0 {
/* Not installed on the plain non-sense xiao. */
/delete-node/ imu_power_default_on;
};
/* Not installed on the plain non-sense xiao. Left in the deletion
* of the regulator-boot-on property just in case.
*/
&pdm_imu_pwr{
/delete-property/ regulator-boot-on;
status = "disabled";
};
/* Not installed on the plain non-sense xiao.
*/
&lsm6dso {
status = "disabled";
};
SO I’m seeing this on the Zephyr side and ALL the DK examples are working for it, I think the NRF_SDK pulls the boards from Zephyr ?
AI is offering this… I think you are the tip of the spear
What is supported right now
Zephyr’s official board listing already includes xiao_nrf54l15 as a supported board. Zephyr Project Documentation
A pull request was merged to add support for XIAO nRF54L15 under the “seeed” board set. GitHub+1
The board file set includes files like:
pre_dt_board.cmake
seeed_xiao_connector.dtsi
openocd.cfg
xiao_nrf54l15-pinctrl.dtsi
…along with docs and DTS under boards/seeed/xiao_nrf54l15 in Zephyr upstream. GitHub
So any builds targeting xiao_nrf54l15 will use that set of files.
However, in Zephyr’s board support, I did not locate a separate board name or DTS variant specifically for “sense” vs “non-sense.” The supported board is just xiao_nrf54l15.
That implies the “sense” features may be added via overlay DTS or optional sensor nodes in the board or application level, rather than via a completely separate board file in Zephyr currently.
What to check / verify in your environment
In your local Zephyr (or NCS) tree, check under boards/seeed/xiao_nrf54l15/ — you should see the files listed above.
Check the compatible = "seeed,xiao_nrf54l15" in the DTS and see whether any sensor nodes are enabled conditionally.
If you have a “sense” hardware variant, you may need an overlay (e.g. boards/seeed/xiao_nrf54l15_sense.dts or a board overlay in your application) to enable the IMU/microphone devices.
It is a bit confusing with things influx, and my guess is the items below will be out of date quickly, but here is my understanding:
If your building applications that rely on nrf connect (e.g. matter), then nrf connect 3.1.1 looks like the right baseline.
The zephyr branch in 3.1.1 doesn’t yet include the seeed 54l15 board. So far it appears the boards in the platform-seeedboards repo and linked to in the getting started page are the best to use. I was able to get this board to work with my matter app after a few modifications.
The board in platform-seeedboards is not configured correctly for optimal power.
The xiao_nrf54 board on the the latest zephyr branch from a few days ago doesn’t seem to be configured for builds that use the radio. Nodes such as radio and temp are disabled. I gave up trying to use it. However, it does seem to be configured for optimal power.
On the original topic - The one board definition for the xiao nrf54l15 is configured for the Sense. You need to delete/disable nodes in order to align with the Hw of the non-sense board.
Maybe it is a non-issue, but I worry it might cause side effects.
Is there an official place where things like this are reported and tracked?
I think you are the tip of the spear 
PJ 