Issue on SX128X using nRF Connect SDK 3.0.0

RE: Issue on SX128X using nRF Connect SDK 3.0.0

runsiv — Tue, 13 May 2025 07:22:25 GMT

Out of curriosty is there anything else that is not working in your application? For I don't see anything that stands out.

CONFIG_SOC_ENABLE_LFXO=n has been deprecated in NCS 3.0 and you should set this in the devicetree like you see here and here

Regards

Runar

RE: Issue on SX128X using nRF Connect SDK 3.0.0

Luis Santos — Mon, 12 May 2025 14:15:53 GMT

haha ok.

my custom _defconfig:

# SPDX-License-Identifier: Apache-2.0

# Enable MPU
CONFIG_ARM_MPU=y

# Enable hardware stack protection
CONFIG_HW_STACK_PROTECTION=y

# Enable TrustZone-M
CONFIG_ARM_TRUSTZONE_M=y

# enable GPIO
CONFIG_GPIO=y
CONFIG_SPI=y

# Enable uart driver
CONFIG_SERIAL=y

# enable console
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y

# Clock
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_SYNTH=n
CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=n
CONFIG_SOC_ENABLE_LFXO=n
CONFIG_NORDIC_QSPI_NOR=n

# NFC
CONFIG_NFCT_PINS_AS_GPIOS=y

# BMI270
CONFIG_SENSOR=y
CONFIG_BMI270=y
CONFIG_I2C=y
CONFIG_LOG=y
CONFIG_SENSOR_LOG_LEVEL_DBG=y
CONFIG_I2C_LOG_LEVEL_DBG=y
CONFIG_RTC_LOG_LEVEL_DBG=y

my prj.conf:

# Enable logging and RTT DEBUG output
CONFIG_LOG=y
CONFIG_LOG_MODE_IMMEDIATE=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_PRINTK=y
CONFIG_LOG_MODE_DEFERRED=n
CONFIG_SEGGER_RTT_BUFFER_SIZE_UP=64
CONFIG_LOG_BUFFER_SIZE=4096
CONFIG_LOG_BACKEND_RTT_BUFFER_SIZE=4096
CONFIG_LOG_PROCESS_THREAD_STACK_SIZE=4096

# LVGL
CONFIG_MAIN_STACK_SIZE=4096
CONFIG_LV_Z_MEM_POOL_SIZE=40000
CONFIG_DISPLAY=y
CONFIG_ST7789V=y
CONFIG_ST7789V_RGB565=y
CONFIG_LVGL=y
# CONFIG_LV_CONF_MINIMAL=y
# CONFIG_LV_USE_ARC=y
# CONFIG_LV_USE_BAR=y
# CONFIG_LV_USE_LABEL=y
# CONFIG_LV_USE_IMG=y
# CONFIG_LV_USE_TEXTAREA=y
# CONFIG_LV_USE_THEME_DEFAULT=y

# Font
CONFIG_LV_FONT_MONTSERRAT_18=y
CONFIG_LV_FONT_MONTSERRAT_20=y
CONFIG_LV_FONT_MONTSERRAT_24=y
CONFIG_LV_FONT_MONTSERRAT_30=y
CONFIG_LV_FONT_MONTSERRAT_48=y
CONFIG_LV_COLOR_DEPTH_16=y
CONFIG_LV_COLOR_16_SWAP=y

# Debug
CONFIG_DEBUG_THREAD_INFO=y
CONFIG_DEBUG=y
CONFIG_DEBUG_OPTIMIZATIONS=y

# MIPI
CONFIG_MIPI_DBI=y

CONFIG_PWM=y
CONFIG_PWM_NRFX=y
CONFIG_LED=y
CONFIG_GPIO=y
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096

# SPI
CONFIG_SPI=y

# RTC
CONFIG_RTC=y
CONFIG_RTC_RV8263=y
CONFIG_RTC_ALARM=y
CONFIG_RTC_UPDATE=y
CONFIG_RTC_CALIBRATION=y
CONFIG_RTC_LOG_LEVEL_DBG=n
CONFIG_COUNTER=y
CONFIG_RTC_INIT_PRIORITY=90

# RNG
CONFIG_ENTROPY_DEVICE_RANDOM_GENERATOR=y
CONFIG_TEST_RANDOM_GENERATOR=y
CONFIG_ENTROPY_GENERATOR=y
CONFIG_ENTROPY_NRF5_RNG=y
CONFIG_ENTROPY_NRF5_BIAS_CORRECTION=y

# Buttons
CONFIG_GPIO=y
CONFIG_CAF_BUTTONS=y

# System
CONFIG_REBOOT=y
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096
CONFIG_THREAD_STACK_INFO=y
CONFIG_THREAD_MONITOR=y
CONFIG_THREAD_NAME=y

# Watchdog
CONFIG_WATCHDOG=y
CONFIG_WDT_NRFX=y

# BMI270
CONFIG_I2C=y
CONFIG_SENSOR=y
CONFIG_BMI270=y

# ADC
CONFIG_ADC=y

My custom .pinctrl and custom.dts was on first message.

RE: Issue on SX128X using nRF Connect SDK 3.0.0

runsiv — Mon, 12 May 2025 14:09:50 GMT

Haha no worries. I would still like the overlay and the prj.conf.

You can for the moment ignore everything I have written regarding pins as it would not be relevant for the 5340

Regards

Runar

RE: Issue on SX128X using nRF Connect SDK 3.0.0

Luis Santos — Mon, 12 May 2025 12:50:47 GMT

I apologize for the confusion. Although I plan to use the nRF54L15 in my future project, right now I’m adapting my existing code—originally developed for a custom nRF5340 board running nRF Connect SDK 2.9.0—to nRF Connect SDK 3.0.0. While the application works perfectly under SDK 2.9.0, after upgrading to SDK 3.0.0 I no longer see any SPI0 activity on the oscilloscope.

RE: Issue on SX128X using nRF Connect SDK 3.0.0

runsiv — Mon, 12 May 2025 12:30:24 GMT

My mistake. I was a bit to haste when looking at your pins.

Remember SPIM should use a dedicated clock pin pr Pin assignments

I would like to see your overlay for the 54L15 and your prj.conf

The atteched .dts shows has includes to the 5340 so I can't be sure regarding that file.

Also there is no spi0 on the 54l15. Are you refeering to SPIM00?

Runar

RE: Issue on SX128X using nRF Connect SDK 3.0.0

Luis Santos — Mon, 12 May 2025 12:14:43 GMT

No. I'm using a custom board with SPI on:

spi0_sx128x_default: spi0_sx128x_default {

group1 {

psels = <NRF_PSEL(SPIM_SCK, 0, 22)>,

<NRF_PSEL(SPIM_MOSI, 0, 0)>,

<NRF_PSEL(SPIM_MISO, 0, 4)>;

bias-pull-down;

};

spi0_sx128x_sleep: spi0_sx128x_sleep {

group1 {

psels = <NRF_PSEL(SPIM_SCK, 0, 22)>,

<NRF_PSEL(SPIM_MOSI, 0, 0)>,

<NRF_PSEL(SPIM_MISO, 0, 4)>;

low-power-enable;

};

I already using this macro CONFIG_NFCT_PINS_AS_GPIOS

RE: Issue on SX128X using nRF Connect SDK 3.0.0

runsiv — Mon, 12 May 2025 11:16:36 GMT

Are you using a DK? If so then you need to set the config option CONFIG_NFCT_PINS_AS_GPIOS=Y as the pins are used for NFC on the DK

Regards

Runar