Quick Start Demo¶

Overview¶

The Quick Start Demo application enables you to test various features of the nRF54L15 Connect Kit such as Zephyr Shell, LED, Button, NFC tag, and Bluetooth Low Energy connectivity.

Requirements¶

Before you start, check that you have the required hardware and software:

• 1x nRF54L15 Connect Kit
• 1x U.FL cabled 2.4 GHz Antenna (included in the box)
• 1x U.FL cabled 13.56 MHz NFC Antenna (included in the box)
• 1x USB-C Cable
• A smartphone or a tablet with NFC support
• A computer running macOS, Ubuntu, or Windows 10 or newer

Installing nRF Blinky App¶

nRF Blinky is a simple mobile app for developers new to Bluetooth Low Energy. It can:

Scan and connect to a peripheral device advertising with the proprietary/vendor-specific LED Button Service (LBS) UUID

Write to the LED Characteristic to change the state of an LED

Be notified when the Button Characteristic changes state because of a button press

Setting up your board¶

Attach the U.FL cabled 2.4 GHz Antenna.

Attach the U.FL cabled 13.56 MHz NFC Antenna.

Connect the nRF54L15 Connect Kit to the computer with a USB-C cable.

Building the application¶

To build the application, follow the instructions in Getting Started Guide to set up your preferred building environment.

Use the following steps to build the Quick Start Demo application on the command line.

1. Open a terminal window.

2. Go to NCS-Project/nrf54l15-connectkit repository cloned in the Getting Started Guide.

3. Build the application using the west build command, specifying the board (following the -b option) as nrf54l15_connectkit/nrf54l15/cpuapp.

   west build -p always -b nrf54l15_connectkit/nrf54l15/cpuapp applications/quick_start_demo
   

   Tip

   The -p always option forces a pristine build, and is recommended for new users. Users may also use the -p auto option, which will use heuristics to determine if a pristine build is required, such as when building another application.

4. After building the application successfully, the firmware with the name merged.hex can be found in the build directory.

Flashing the firmware¶

Flash the application firmware using west flash:

west flash

pyocd load --target nrf54l --frequency 4000000 build/merged.hex

Testing¶

After programming the application, test it by performing the following steps:

Connecting to Zephyr Shell¶

Once the board is connected, it exposes two COM ports, the primary COM port is connected to the Zephyr Shell whose terminal prompt appears as uart:~$.

Open up a serial terminal, specifying the Zephyr Shell COM port:

screen <serial-port-name> 115200

screen <serial-port-name> 115200

Press the DFU/RST button to reset the nRF54L15. Observe the output of the terminal. You should see the output, similar to what is shown in the following:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21

*** Booting Quick Start Demo v3.1.0-5da6f6aae060 ***
*** Using nRF Connect SDK v3.1.0-6c6e5b32496e ***
*** Using Zephyr OS v4.1.99-1612683d4010 ***
[00:00:00.001,155] <inf> main: NFC configuration done
[00:00:00.001,802] <inf> fs_zms: 2 Sectors of 4096 bytes
[00:00:00.001,812] <inf> fs_zms: alloc wra: 0, c60
[00:00:00.001,819] <inf> fs_zms: data wra: 0, 190
[00:00:00.002,139] <inf> bt_sdc_hci_driver: SoftDevice Controller build revision:
                                            fc de 41 eb a2 d1 42 24  00 b5 f8 57 9f ac 9d 9e |..A...B$ ...W....
                                            aa c9 b4 34                                      |...4
[00:00:00.003,843] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.003,858] <inf> bt_hci_core: HW Variant: nRF54Lx (0x0005)
[00:00:00.003,871] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 252.16862 Build 1121034987
[00:00:00.004,026] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:00.004,033] <inf> main: Bluetooth initialized
[00:00:00.004,528] <inf> bt_hci_core: HCI transport: SDC
[00:00:00.004,578] <inf> bt_hci_core: Identity: EF:11:48:A5:EA:6D (random)
[00:00:00.004,595] <inf> bt_hci_core: HCI: version 6.1 (0x0f) revision 0x3069, manufacturer 0x0059
[00:00:00.004,610] <inf> bt_hci_core: LMP: version 6.1 (0x0f) subver 0x3069
[00:00:00.006,087] <inf> main: Advertising successfully started
uart:~$

Type Tab to list all supported commands. When you type a command with --help, the terminal shows its usage, for example gpio --help:

21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49

uart:~$
  adc      bt       clear    date     device   devmem   gatt     gpio
  help     history  kernel   log      rem      resize   retval   shell
  stats
uart:~$ gpio --help
gpio - GPIO commands
Subcommands:
  conf     : Configure GPIO pin
             Usage: gpio conf <device> <pin> <configuration
             <i|o>[u|d][h|l][0|1]> [vendor specific]
             <i|o> - input|output
             [u|d] - pull up|pull down, otherwise open
             [h|l] - active high|active low, otherwise defaults to active high
             [0|1] - initialise to logic 0|logic 1, otherwise defaults to logic
             0
             [vendor specific] - configuration flags within the mask 0xFF00
             see include/zephyr/dt-bindings/gpio/
  get      : Get GPIO pin value
             Usage: gpio get <device> <pin>
  set      : Set GPIO pin value
             Usage: gpio set <device> <pin> <level 0|1>
  toggle   : Toggle GPIO pin
             Usage: gpio toggle <device> <pin>
  devices  : List all GPIO devices
             Usage: gpio devices
  blink    : Blink GPIO pin
             Usage: gpio blink <device> <pin>
  info     : GPIO Information
             Usage: gpio info [device]

LED Blinking Test¶

Now you can blink the Green LED using GPIO commands in the Zephyr Shell.

1. To control the Green LED, configure the GPIO pin P0.2 as an output:

   gpio conf gpio0 2 o
   

2. Blink the Green LED using the gpio blink command:

   gpio blink gpio0 2
   

3. The Green LED starts to blink. Observe the output of the terminal. You should see the output, similar to what is shown in the following:

   Terminal
   50 51 52	uart:~$ gpio conf gpio0 2 o uart:~$ gpio blink gpio0 2 Hit any key to exit

4. Hit any key in the Shell to stop the LED blinking.

Button Input Test¶

When the application starts, it prints any input event using the Input APIs. Press the USR button and observe the output of the terminal. You should see the output, similar to what is shown in the following:

53
54
55
56
57

[00:20:46.758,664] <inf> input: input event: dev=buttons SYN type= 1 code= 11 value=1
[00:20:47.441,742] <inf> input: input event: dev=buttons SYN type= 1 code= 11 value=0
[00:36:18.853,192] <inf> input: input event: dev=buttons SYN type= 1 code= 11 value=1
[00:36:19.004,974] <inf> input: input event: dev=buttons SYN type= 1 code= 11 value=0
uart:~$ 

NFC Tag Test¶

When the application starts, it initializes the NFC tag and generates a URI message with a URI record containing the URL "https://makerdiary.com". Test it by performing the following steps:

1. Touch the NFC antenna with the smartphone or tablet.

2. Observe that the smartphone or tablet tries to open the URL "https://makerdiary.com" in a web browser.

BLE Connectivity Test¶

The application exposes a Nordic LED Button Service (LBS). It sends the state of USR button on the board to the connected device, such as a phone or tablet. The nRF Blinky app can display the received button state and control the state of Green LED on the board. Test it by performing the following steps:

1. Open the nRF Blinky app, observe that the board is advertising with the Device Name Nordic_LBS.

   

2. Tap Nordic_LBS to establish a connection with the board, then:

   • Toggle the LED switch in the app to turn the Green LED ON/OFF
   • Press the USR button on the board, and the app will show its state (Pressed/Released)