NUCODE NU54V DK

Overview

The NUCODE NU54V DK is a development board for the NU54V module, which is based on the Nordic Semiconductor nRF54L15. The module provides 1.5 MB of RRAM, 256 KB of RAM, and a 2.4 GHz radio supporting Bluetooth Low Energy and IEEE 802.15.4. The board includes four user LEDs, four push buttons, a Qwiic connector, a Cortex 10-pin debug connector, and an onboard DAPLink CMSIS-DAP debug probe.

This board definition targets the NU54V DK with the nRF54L15. The NU54 module family also contains nRF54L05 and nRF54L10 variants, which are not covered by this board definition.

The pin assignments are based on the NUCODE NU54 DK board files [2], NUCODE NU54 DK pinout [3], and the current NUCODE NU54 DK schematic [5]. See the NUCODE NU54 software page [1] and NUCODE NU54V DK product page [6] for more information.

Hardware

  • Nordic Semiconductor nRF54L15 Arm Cortex-M33 application processor

  • 1.5 MB RRAM and 256 KB RAM

  • 2.4 GHz multiprotocol radio

  • Four user LEDs and four user push buttons

  • Qwiic I2C connector

  • Onboard DAPLink CMSIS-DAP probe with two CDC ACM UART interfaces

  • Cortex 10-pin SWD connector for an external probe

Supported Features

The nucode_nu54 board supports the hardware features listed below.

on-chip / on-board
Feature integrated in the SoC / present on the board.
2 / 2
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files.
vnd,foo
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.

nucode_nu54/nrf54l15/cpuapp target

On-target memory for this board target: 256 KiB of RAM, 1524 KiB of Flash.

Type

Location

Description

Compatible

CPU

on-chip

ARM Cortex-M33F CPU1

arm,cortex-m33f

ADC

on-chip

Nordic Semiconductor nRF family SAADC node1

nordic,nrf-saadc

ARM architecture

on-chip

Nordic UICR (User Information Configuration Registers)1

nordic,nrf-uicr

on-chip

Nordic EGU (Event Generator Unit)2

nordic,nrf-egu

Audio

on-chip

Nordic PDM (Pulse Density Modulation interface)2

nordic,nrf-pdm

Clock control

on-chip

Generic fixed-rate clock provider2

fixed-clock

on-chip

Nordic nRF low-frequency crystal oscillator (nRF54L series)1

nordic,nrf54l-lfxo

on-chip

Nordic nRF high-frequency crystal oscillator (nRF54L series)1

nordic,nrf54l-hfxo

on-chip

Nordic nRF clock control node1

nordic,nrf-clock

on-chip

Nordic nRF XO clock control node1

nordic,nrf-clock-xo

on-chip

Nordic nRF LFCLK clock control node1

nordic,nrf-clock-lfclk

Comparator

on-chip

Nordic nRF COMP (analog COMParator)1

nordic,nrf-comp

Counter

on-chip

Nordic nRF timer node7

nordic,nrf-timer

Debug

on-chip

ARMv8 instrumentation trace macrocell1

arm,armv8m-itm

Flash controller

on-chip

Nordic RRAMC (Resistive random access memory controller)1

nordic,rram-controller

GPIO & Headers

on-chip

NRF5 GPIO3

nordic,nrf-gpio

on-chip

NRF5 GPIOTE2

nordic,nrf-gpiote

on-board

STEMMA QT is a 4-pin JST-SH connector for I2C devices1

stemma-qt-connector

I2C

on-chip

Nordic nRF family TWIM (TWI master with EasyDMA)13

nordic,nrf-twim

I2S

on-chip

Nordic I2S (Inter-IC sound interface)1

nordic,nrf-i2s

IEEE 802.15.4

on-chip

Nordic nRF IEEE 802.15.4 node1

nordic,nrf-ieee802154

Input

on-board

Group of GPIO-bound input keys1

gpio-keys

Interrupt controller

on-chip

ARMv8-M NVIC (Nested Vectored Interrupt Controller)1

arm,v8m-nvic

LED

on-board

Group of GPIO-controlled LEDs1

gpio-leds

on-board

Group of PWM-controlled LEDs1

pwm-leds

Mailbox

on-chip

Nordic VEVIF (VPR Event Interface) - TASK TX MODE1

nordic,nrf-vevif-task-tx

on-chip

Nordic VEVIF (VPR Event Interface) - EVENT RX MODE1

nordic,nrf-vevif-event-rx

Miscellaneous

on-chip

Nordic FICR (Factory Information Configuration Registers)1

nordic,nrf-ficr

on-chip

Nordic DPPIC (Distributed Programmable Peripheral Interconnect Controller)4

nordic,nrf-dppic

on-chip

Nordic PPIB (Programmable Peripheral Interconnect Bridge)8

nordic,nrf-ppib

on-chip

Nordic Memory Privilege Controller (MPC)1

nordic,nrf-mpc

MTD

on-chip

Flash node1

soc-nv-flash

Networking

on-chip

Nordic nRF family RADIO peripheral1

nordic,nrf-radio

on-chip

Nordic nRF family NFCT (Near Field Communication Tag)1

nordic,nrf-nfct-v2

Pin control

on-chip

Nordic nRF family Pin Controller1

nordic,nrf-pinctrl

Power management

on-chip

Nordic nRF power control node1

nordic,nrf-power

PWM

on-chip

nRF PWM12

nordic,nrf-pwm

Regulator

on-chip

Nordic REGULATORS (voltage regulators control module) on nRF54L1

nordic,nrf54l-regulators

on-chip

Nordic nRF5X regulator (fixed stage of the core supply)1

nordic,nrf5x-regulator

Retained memory

on-chip

Nordic GPREGRET (General Purpose Register Retention) device11

nordic,nrf-gpregret

RISC-V architecture

on-chip

VPR coprocessor1

nordic,nrf-vpr-coprocessor

RNG

on-chip

Nordic nRF CRACEN CTR_DRBG based (Random Number Generator)1

nordic,nrf-cracen-ctrdrbg

Sensors

on-chip

Nordic nRF family TEMP node1

nordic,nrf-temp

on-chip

Nordic nRF quadrature decoder (QDEC) node2

nordic,nrf-qdec

Serial controller

on-chip

Nordic nRF family UARTE (UART with EasyDMA)14

nordic,nrf-uarte

SPI

on-chip

Nordic nRF family SPIM (SPI controller with EasyDMA)5

nordic,nrf-spim

SRAM

on-chip

Generic on-chip SRAM2

mmio-sram

Timer

on-chip

Nordic GRTC (Global RTC)1

nordic,nrf-grtc

on-chip

ARMv8-M System Tick1

arm,armv8m-systick

Watchdog

on-chip

Nordic nRF family WDT (Watchdog Timer)11

nordic,nrf-wdt

Connections and IOs

LEDs

  • LED0 = P2.09 (active high)

  • LED1 = P1.10 (active high)

  • LED2 = P2.07 (active high)

  • LED3 = P1.14 (active high)

Push Buttons

  • button0/sw0 = board signal SW1 = component SW2 = P1.13 (active low, pull-up)

  • button1/sw1 = board signal SW2 = component SW3 = P1.09 (active low, pull-up)

  • button2/sw2 = board signal SW3 = component SW4 = P1.08 (active low, pull-up)

  • button3/sw3 = board signal SW4 = component SW5 = P0.04 (active low, pull-up)

Component SW1 is the two-pole DISABLE_SWD/DISABLE_UART switch, not a user push button. The sw0 through sw3 names above are Zephyr aliases.

UART Console

The board schematic routes the primary onboard debugger UART path to UART20. The default console speed is 115200 baud. RTS and CTS are routed to the debug interface, but hardware flow control is not enabled by default.

  • TX = P1.04

  • RX = P1.05

  • RTS = P1.06

  • CTS = P1.07

UART30 is available to the CPUAPP as a disabled optional configuration on P0.00 through P0.03. Before enabling it, see Onboard Debug Probe Limitations.

Both UART paths pass through the onboard debug interface. Probe firmware may expose them as two CDC ACM interfaces named UART0 and UART1. If there is no console output, verify that the DISABLE_UART half of SW1 allows the UART level shifters to drive the target. UART20 also depends on SB9 through SB12; UART30 depends on SB5 through SB8. The switch direction, solder-bridge population, and onboard probe firmware must be checked against the actual board revision. A CDC ACM interface appearing on the host does not by itself confirm that the probe firmware is forwarding the corresponding target UART.

Qwiic I2C

The Qwiic connector uses I2C22.

  • SCL = P1.03

  • SDA = P1.02

Pin Sharing

P1.02 and P1.03 are shared with NFC, so NFCT is disabled by default. P1.10 is shared by led1 and pwm-led0. P2.07 can be connected to SWO through SB13. P1.08 and P0.04 are connected to buttons which short the pins to ground when pressed. Do not route GRTC clock outputs to these pins unless the physical button paths have been isolated.

Programming and Debugging

The nucode_nu54 board supports the runners and associated west commands listed below.

flash debug rtt reset attach debugserver
jlink ✅ ✅ ✅ ✅ ✅ ✅
pyocd ✅ (default) ✅ (default) ✅ ✅ ✅ ✅

The onboard probe enumerates as a DAPLink CMSIS-DAP device. Build and flash a sample with pyOCD as follows. The board’s USB-C connection powers the board and carries CMSIS-DAP, mass-storage, and CDC ACM interfaces; a second USB-UART cable is not required by the board design.

# From the root of the zephyr repository
west build -b nucode_nu54/nrf54l15/cpuapp samples/hello_world
west flash

The board does not have a pyOCD board-ID entry, so the board runner explicitly selects the built-in nrf54l target. It also disables pyOCD’s automatic unlock operation so that connecting to a protected target fails instead of implicitly mass-erasing it. An external J-Link can also be used through the Cortex 10-pin connector by selecting the J-Link runner.

On Linux, pyOCD needs permission to access the onboard probe’s composite USB device. If the probe is listed only when running pyOCD as root, install the following udev rule as root:

# echo 'SUBSYSTEM=="usb", ATTR{idVendor}=="0d28", ATTR{idProduct}=="0204", MODE="0666"' > /etc/udev/rules.d/50-nucode-nu54-cmsis-dap.rules

Reload the rules, and then unplug and reconnect the board:

$ sudo udevadm control --reload-rules

The supported board target is nucode_nu54/nrf54l15/cpuapp. When using an external probe, isolate the onboard SWD interface before driving the same signals.

Onboard Debug Probe Limitations

DAPLink firmware NU54DK_v2_Pre-release (build ID 3601db04e83571edc43dbfacacf2cddbe34be5b9) has two reported issues. See the NU54V DK debug probe report [7] for the test results.

  • Sending data from the host through VCOM0 (UART30), or driving its RTS signal (P0.02) low, can make SWD accesses fail with No ACK while UART communication continues.

  • Copying a HEX file to the probe’s mass-storage drive can cause a HardFault, recorded in ASSERT.TXT.

Leave UART30 disabled with this firmware and use UART20 (VCOM1), the default console, which worked normally in the reported tests. Removing RTS/CTS from pinctrl does not prevent the failure when the host sends data through VCOM0. Use west flash with pyOCD instead of copying HEX files to the USB drive.

Unplugging and reconnecting USB restored SWD after the host sent data and recovered the probe after the HEX file copy. If the application drives RTS at startup, SWD can fail again immediately. To recover, disconnect the onboard SWD interface with SW1 DISABLE_SWD, then connect an external probe to J4 and flash an application with UART30 disabled.

Hardware Configuration Notes

The internal HFXO and LFXO load-capacitance values and the DCDC mode follow NUCODE’s current board files. The board’s oscillator path depends on its BOM and the SB18 through SB21 population. If an external LFXO is populated, update the devicetree configuration as described in the NUCODE NU54 DK hardware notes [4]. Verify these settings when supporting a board revision with a different BOM or solder-bridge population.

References