Seeed Studio XIAO nRF54L15(Sense) | Seeed Studio Wiki

[giscus[bot]]

Seeed Studio XIAO nRF54L15(Sense) | Seeed Studio Wiki

https://wiki.seeedstudio.com/xiao_nrf54l15_sense_getting_started/

[msfujino]

Are there any plans to release a BSP that can be used with Arduino?

[lboue]

Could you provide me a tutorial for building Nordic Matter samples for XIAO nRF54L15 board?

[msfujino]

Can I upload to XIAO_nRF54L15 via USB?
Or do I need to use SWDIO/SWCLK?

[bleaaach]

Hi, you can upload the program via USB; no additional interfaces are needed. Just follow our tutorial.

[lboue]

Hi,

Could you provide a Zigbee tutorial for XIAO nRF54L15.
There is Zigbee support with the last nRF Connect SDK v3.1.0 version: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/zigbee.html

Regards

[bleaaach]

Hi, thank you for your feedback. We have already passed it on to the product line and are waiting for their response. We will get back to you as soon as we receive any reply.

[bleaaach]

Hi, more Zigbee tutorials will be released later. Currently, they are still in the verification phase. You can follow our wiki for the latest updates.

[rdorys]

Hi, I didn"t manage to get the low power example working. Is it supposed to be battery powered to get to the couple of uA goals ?
When I power it from 3.3V pin, I get about 750uA consumption (and I didn't forget to add overlay with
&pdm_imu_pwr{
/delete-property/ regulator-boot-on;
};
)
When powering from battery pin, I get about 250uA, and from 5V input, I get about 400uA.

Do you have a precise tutorial to reproduce zephyr low power example ??

Thx !

[bleaaach]

Hi,

1. The issue lies in the configuration of the app.overlay and prj.conf files. After making modifications, the test results are consistent with those in the wiki.

2. Specific modification requirements:
   2.1 Modify the app.overlay file with the following content:

   &pdm_imu_pwr {
       /delete-property/ regulator-boot-on;
   };
   

   2.2 Modify the prj.conf file with the following content:

   CONFIG_PM_DEVICE=y
   CONFIG_NRFX_POWER=y
   CONFIG_POWEROFF=y
   CONFIG_HWINFO=y
   CONFIG_CRC=y
   CONFIG_GPIO=y
   

3. Important note for power consumption testing:
   The power supply should be connected to the battery interface on the back of the board; do not use the Type-C interface for testing. This is because the Type-C path includes a voltage step-down circuit, which will increase power consumption. Additionally, the recommended power supply voltage ranges from 3.7V to 4.2V.

[luwent]

where can I find XIAO nRF54L15 Kicad symbol and footprint?

[luftruepel]

Hi,

what is the charging current?

[bleaaach]

Hi, please refer to the schematic diagram. The default/factory circuit sets the charging current to approximately 200 mA (when powered via USB and the battery is not fully charged).

[msfujino]

When flashing the built zephyr.hex using “west flash”, the flash process completes successfully, but running the program causes an MPU FAULT and it does not function.
When flashing the same hex file using JLink, it runs without issues.
Comparing the contents of both memories revealed that when written via “west flash”, the last 8 bytes are not written.
As it stands, “west flash” is unusable, and I'm in a real bind. Is there any workaround?

[Jasionf]

Is this only happening with specific programs, or does it occur when burning other examples as well?

[msfujino]

I believe it stems from the byte count rather than the program's content.

[shmuelzon]

From what I see, it seems that flash writes are done in 16-byte segments (complete lines in the HEX firmware file). This is probably some bug with the OpenOCD configuration or with the firmware running on the SAMD11 implementing the debugger interface. In any case, as a workaround, I pad the firmware file right before flashing with the attached file: pad_hex.py ./build/merged.hex

pad_hex.py

[Chibi-Robo96]

Hello, are there any plans to release a working example of the channel sounding functionality, i have been unsuccessful in porting nordics initiator_ras and reflector_ras sample applications

[Jasionf]

At the moment, there are no plans to release this feature. All existing examples are based on the official code provided. If you encounter issues, please feel free to share the detailed error information in the community

[suhaimiannuar]

Hi, I got issue that i cannot upload the code anymore. What should i do?

Open On-Chip Debugger 0.12.0
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
nrf54l-load
Info : Using CMSIS-DAPv2 interface with VID:PID=0x2886:0x0066, serial=57BD6409
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: FW Version = 2.0.0
Info : CMSIS-DAP: Serial# = 57BD6409
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 0
Info : CMSIS-DAP: Interface ready
Info : clock speed 1000 kHz
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
Error: Failed to read memory at 0xe000ed00
Warn : target nrf54l.cpu examination failed
Info : starting gdb server for nrf54l.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : gdb port disabled
    TargetName         Type       Endian TapName            State       
--  ------------------ ---------- ------ ------------------ ------------
 0* nrf54l.cpu         cortex_m   little nrf54l.cpu         unknown
 1  nrf54l.aux         mem_ap     little nrf54l.cpu         running

Info : SWD DPIDR 0x6ba02477
Error: Failed to read memory at 0xe000ed00
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
Info : [nrf54l.cpu] AP write error, reset will not halt
Info : SWD DPIDR 0x6ba02477
Error: [nrf54l.cpu] DP initialisation failed

FATAL ERROR: command exited with status 1: /opt/homebrew/bin/openocd -s /opt/nordic/ncs/v3.2.0/zephyr/boards/seeed/xiao_nrf54l15/support -s /opt/nordic/ncs/toolchains/322ac893fe/opt/zephyr-sdk/sysroots/arm64-pokysdk-linux/usr/share/openocd/scripts -f /opt/nordic/ncs/v3.2.0/zephyr/boards/seeed/xiao_nrf54l15/support/openocd.cfg '-c init' '-c targets' -c 'reset init' -c 'nrf54l-load /Users/suhaimiannuar/Development/nrf/panama11/build/merged.hex' -c 'reset run' -c shutdown

[suhaimiannuar]

i am using USB port. No debugger other than USB port.

(base) suhaimiannuar@macbook-pro ~/Development/nrf/panama11 $ nrfjprog --recover
ERROR: No debuggers were discovered.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
(base) suhaimiannuar@macbook-pro ~/Development/nrf/panama11 $

[suhaimiannuar]

i have tried double tap on RST button quickly. i still cannot upload the firmware.

[jhs-crypto]

Are there any 3D CAD-files available for the nRF54L15 (sense)? This would be usefull for implementation into design.

[Carla-Guo]

Hi @jhs-crypto, you can refer to this page: https://www.flux.ai/seeedstudio

[lolren]

I've just ported Arduino core to for this board. Happy testing. https://github.com/lolren/NRF54L15-Arduino-core

[daleobrien]

The KiCad XIAO-nRF54l15-SMD footprint seems to be missing from the footprint library linked on this page?

[AYproject]

Seeed_Studio_XIAO_Series.pretty.zip
Hi, this is the latest, the zip package contains files related to XIAO nRF54L15

[daleobrien]

Very nice, thank you.

[savigny030]

the kicad footprint of the nRF54L15 of the whole SMD is missing. please add that soon, it's holding my project back. thanks.

[AYproject]

Seeed_Studio_XIAO_Series.pretty.zip
Hi, this is the latest, the zip package contains files related to XIAO nRF54L15
The wiki will be updated soon as well. Thank you for your feedback

[shmuelzon]

Hey, from what I can tell, the RF switch CTL pin is connected to P2.05, i.e., GPIO port 2. The problem is that this port isn't associated with GPIOTE peripherals, meaning it can't be configured as a front-end module for the radio and be turned on/off automatically according to the OS requirements. See https://github.com/nrfconnect/sdk-nrf/blob/main/doc/nrf/app_dev/device_guides/fem/fem_simple_gpio.rst:

On nRF54L Series devices, make sure the GPIO pins of the SoC selected to control ctx-gpios and crx-gpios support GPIOTE. For example, on the nRF54L15 device, use pins belonging to GPIO P1 or GPIO P0 only. You cannot use the GPIO P2 pins, because there is no related GPIOTE peripheral.

This seems like a big oversight in design as that RF switch alone consumes 100uA and having it constantly off impacts RF power.

Is there anything that can be done about this, apart from removing it and hardwiring the antenna to either the IPEX connector or the ceramic antenna?

[benjaminmales]

Hey guys, has anyone got an Eagle lib for this? Thanks in advance!!