running DECT samples on the Feather 9151

EWIZZ · 2025-10-15T14:28:37+00:00

Hi I’m trying to get the nRF DECT sample programs running on the Feather 9151. These have been tested on our 9151 DK board. I’ve hit a few issues with tryi...

jaredwolff

@EWIZZ I noticed that the Thingy91 overlay had the bootloader enabled.

You’ll need a sysbuild.conf in the root of that sample with:

SB_CONFIG_BOOTLOADER_MCUBOOT=y

Then in sysbuild/mcuboot.conf

# Disable Zephyr console
CONFIG_CONSOLE=n

# Multithreading
CONFIG_MULTITHREADING=y

# MCUBoot settings
CONFIG_BOOT_MAX_IMG_SECTORS=256

By default sysbuild is turned on in Zephyr Tools, so all you should have to do is re-build.

I did add an overlay boards/circuitdojo_feather_nrf9151_ns.conf but it’s not critical for getting it working:

# Pmic LED driver
CONFIG_LED=y
CONFIG_LED_NPM1300=y

# Regulator control
CONFIG_REGULATOR=y
CONFIG_REGULATOR_NPM1300=y

Output:

All pins have been configured as non-secure
Booting TF-M v2.1.1-ncs4-2
[Sec Thread] Secure image initializing!
TF-M isolation level is: 0x00000001
TF-M Float ABI: Hard
Lazy stacking enabled
*** Booting nRF Connect SDK v3.0.1-9eb5615da66b ***
*** Using Zephyr OS v4.0.99-77f865b8f8d0 ***

[00:00:00.283,050] <inf> app_startup: *** Vsys Current Limit: 1000 mA ***
desh:~$ 
Reset reason: PIN reset

Mine is crashing since I don’t have the DECT+ mfw installed. Hopefully yours should be OK since you do.

EWIZZ

Ok good stuff. We have life!!

I added the following files, with your edits, into the project root

sysbuild.conf
sysbuild/mcuboot.conf

I added the following file, with your edits, into the “boards” directory
circuitdojo_feather_nrf9151_ns.conf

Below are the results of the performance test in DECT_SHELL
Server

`---- Sent utf8 encoded message: "dect perf -s -t 15 --channel 1671\r\n" ----
dect perf -s -t 15 --channel 1671
Starting server RX: channel 1671, exp_rssi_level 0, duration 15 secs.
perf command started.
RESULT_REQ received from tx id 38
server: sending result response of total length: 415:
"perf server rx operation from tx id 38:
  total amount of data:   3062500 bytes
  packet count:           4375
  elapsed time:           10.02 secs
  data rates:             2444.13 kbits/secs
  rx restarted count:     0
  PCC CRC errors: 0
  PDC CRC errors: 0
  out of seqs:    0
  PCC RX: MCS:    4
  PCC RX: RSSI: min:  -49, max: -44dBm
  PCC RX: TX pwr: min -12, max -8 dBm
  PCC RX: SNR: min:    87, max: 113
"

Server results TX scheduled: 419 bytes (7 slots, MCS-1).
RESULT_RESP sent.
perf command done.`

Client

`---- Sent utf8 encoded message: "dect perf -c --c_gap_subslots 3 --c_tx_mcs 4 --c_slots 4 --s_tx_id 39 -t 10 --channel 1671\r\n" ----
dect perf -c --c_gap_subslots 3 --c_tx_mcs 4 --c_slots 4 --s_tx_id 39 -t
 10 --channel 1671
Starting perf client on channel 1671: byte count per TX: 700, slots 4, gap 43200 mdm ticks, mcs 4, duration 10 secs, expected RSSI level on RX 0.
perf command started.
perf tx operation completed:
  total amount of data sent: 3062500 bytes
  packet count:              4375
  elapsed time:              10.00 seconds
  data rates:                2450.00 kbits/seconds
Requested results from the server...
RESULT_REQ sent.
Server results received:
perf server rx operation from tx id 38:
  total amount of data:   3062500 bytes
  packet count:           4375
  elapsed time:           10.02 secs
  data rates:             2444.13 kbits/secs
  rx restarted count:     0
  PCC CRC errors: 0
  PDC CRC errors: 0
  out of seqs:    0
  PCC RX: MCS:    4
  PCC RX: RSSI: min:  -49, max: -44dBm
  PCC RX: TX pwr: min -12, max -8 dBm
  PCC RX: SNR: min:    87, max: 113

RX for perf results done.
perf command done.`

EWIZZ

@jaredwolff
Hi Jared,
Would you be able to explain why the 9151 DK did not need these extra config files for the DECT to work?

jaredwolff

9151 DK must have something in the board config that’s turning on the bootloader by default. You can see they turned it on in the Thingy91:

# MCUBOOT
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_IMG_MANAGER=y
CONFIG_STREAM_FLASH=y
CONFIG_MCUBOOT_IMG_MANAGER=y
CONFIG_IMG_ERASE_PROGRESSIVELY=y

I don’t see anything apparent in the application itself. It may be better to ask Nordic since it’s their application.

« Previous Page