Working DeviceTree configuration on v2.5.2 fails for v2.6 and later SDK versions

RE: Working DeviceTree configuration on v2.5.2 fails for v2.6 and later SDK versions

runsiv — Mon, 03 Feb 2025 14:12:09 GMT

Can you add

&uicr {
nfct-pins-as-gpios;
};

to your overlay? It should fix the issue i think. This was changed between the NCS versions you wear using to NCS 2.6

Regards

Runar

RE: Working DeviceTree configuration on v2.5.2 fails for v2.6 and later SDK versions

Gene Roylance — Fri, 31 Jan 2025 17:43:43 GMT

Runar,

Yes, I have been using v2.8 for several weeks and I have converted by custom hardware model into the hardware model v2 version.

I can run an RTT terminal version of the code with NO issues. I can program a version of my code compiled with SDK v2.5.2 using the "Erase and Flash", have this boot and run normally, and then program my UART version of SDK v2.8.0 code using just the "Flash" option and have the UART work perfectly with the SDK v2.8.0 code.

Gene

RE: Working DeviceTree configuration on v2.5.2 fails for v2.6 and later SDK versions

runsiv — Fri, 31 Jan 2025 08:07:52 GMT

When you build for NCS 2.8, do you use sysbuild?
From the release note of NCS 2.7
"

This release introduces significant, potentially breaking, changes to the SDK:

The previous method to define a board (hardware model) is deprecated and being replaced by a new method (hardware model v2).
The previous method to define multi-image builds (parent-child images) is deprecated and being replaced by Sysbuild (System build).

All samples and applications in the SDK have been migrated. Consult respective documentation as additional or changed parameters might be needed to build them successfully. Applications that are outside of the SDK and use custom-defined boards should not be affected by these changes. However, modifications might still be required as per the migration procedure described in Migration guide for nRF Connect SDK v2.7.0. nRF Connect for VS Code users migrating to the latest version of the SDK might be affected.

All samples and applications in the SDK are built with sysbuild by default. Applications that are outside the SDK are not built with sysbuild by default.

The deprecated methods are scheduled for removal after the next release. We recommend transitioning to the alternatives as soon as possible. Consult migration guides for Migrating to the current hardware model and Migrating from multi-image builds to sysbuild. Exercise caution when migrating production environments to the latest SDK."

RE: Working DeviceTree configuration on v2.5.2 fails for v2.6 and later SDK versions

Gene Roylance — Fri, 31 Jan 2025 00:23:35 GMT

Runar,

Yes, I can run the standard Matter template and it works with the UART on the nrf52840DK board.

I also ran some additional experiments. It seems that the Openthread cli sample works with my overlay when using SDK v2.6.x but it does not work when using the SDK v2.8.0 Openthread cli sample.

Gene

RE: Working DeviceTree configuration on v2.5.2 fails for v2.6 and later SDK versions

runsiv — Thu, 30 Jan 2025 13:13:19 GMT

That is true, I missed it after looking to much into changelogs. I will ask internally if anyone has a good explanation for what is going wrong. From the changelogs I can't see any reason why this is happening.
However when I compere the sample in the two different versions of the SDK there is a lot of changes to the application itself.

If you run the standard Matter template and don't change anything other then the board target, do UART work then?

Regards

Runar

RE: Working DeviceTree configuration on v2.5.2 fails for v2.6 and later SDK versions

Gene Roylance — Wed, 29 Jan 2025 14:48:46 GMT

Runar,

Thanks for the feedback. I have had the CONFIG_PRINTK_SYNC=y line in prj.conf for some time. It is the 7th line in the prj.conf listed above.

Gene

RE: Working DeviceTree configuration on v2.5.2 fails for v2.6 and later SDK versions

runsiv — Wed, 29 Jan 2025 08:45:29 GMT

Thanks for the update.

Since the thread sample works we can at least suspect is related to matter. Is there any error message or just nothing works?

In NCS 2.6 the the following was changed
"The CONFIG_PRINTK_SYNC Kconfig option has been disabled to avoid potential interrupts blockage in Matter applications that can violate time-sensitive components, like nRF 802.15.4 Radio Driver."

Could you try to update the prj.conf to follow this?

Regards

Runar

RE: Working DeviceTree configuration on v2.5.2 fails for v2.6 and later SDK versions

Gene Roylance — Wed, 29 Jan 2025 02:24:01 GMT

Greetings,

I have tried a couple of other experiments. I tried a new application by copying from a sample. When I run the "OpenThread cli sample" with my overlay, the UART works (I used the v2.6.1 SDK version).

However, when I try the "Matter Template" sample code with my overlay, it fails as I described above. This would make sense, as we leveraged the Matter Template sample for our current development code.

Gene

RE: Working DeviceTree configuration on v2.5.2 fails for v2.6 and later SDK versions

Gene Roylance — Tue, 28 Jan 2025 19:04:30 GMT

Runar,

1. I have not probed the pins with a logic analyzer. It is not easy for me to do that. In addition, since I can literally load one set of code on the hardware and have it work, while a different version on the same hardware does not work, I am struggling to see the value in this experiment.

2. I would have to see how difficult it would be to connect a RS232 connection to the nrf52840dk board, I don't know how I could test this on the DK board.

3. Attached is the overlay and prj.conf files.

prj.conf:

CONFIG_ASSERT_NO_FILE_INFO=n
CONFIG_RESET_ON_FATAL_ERROR=n
CONFIG_ASSERT_VERBOSE=y
CONFIG_THREAD_NAME=y
CONFIG_BOOT_BANNER=y
CONFIG_PRINTK=y
CONFIG_PRINTK_SYNC=y
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y
CONFIG_RTT_CONSOLE=n
CONFIG_SHELL=y
CONFIG_OPENTHREAD_SHELL=y
CONFIG_CHIP_LIB_SHELL=y
CONFIG_SERIAL=y
CONFIG_USE_SEGGER_RTT=n
CONFIG_SHELL_BACKENDS=y
CONFIG_SHELL_BACKEND_SERIAL=y
CONFIG_SHELL_BACKEND_RTT=n
CONFIG_LOG=n
CONFIG_LOG_BACKEND_UART=n
CONFIG_LOG_BACKEND_RTT=n
#CONFIG_LOG_BACKEND_RTT_BUFFER=1
CONFIG_LOG_MODE_MINIMAL=n
#CONFIG_NFCT_PINS_AS_GPIOS=y # deprecated as of SDK v2.6.0
CONFIG_PM_DEVICE=y
CONFIG_I2C=y
CONFIG_ADC=y
CONFIG_PWM=y
CONFIG_WATCHDOG=y
CONFIG_WDT_DISABLE_AT_BOOT=y
CONFIG_RAM_POWER_DOWN_LIBRARY=y

# Start ** Additions for the PuzL ExtFlash part.
CONFIG_FLASH=y
CONFIG_SPI=y
CONFIG_NORDIC_QSPI_NOR=y
CONFIG_NORDIC_QSPI_NOR_FLASH_LAYOUT_PAGE_SIZE=4096
CONFIG_OPENTHREAD_NORDIC_LIBRARY_MTD=y
CONFIG_MPU_ALLOW_FLASH_WRITE=y
# End ** Additions for the PuzL ExtFlash part.

CONFIG_NET_L2_OPENTHREAD=y
CONFIG_OPENTHREAD_MTD=y
CONFIG_OPENTHREAD_MTD_SED=y
CONFIG_CHIP=y
CONFIG_CHIP_ENABLE_ICD_SUPPORT=y
CONFIG_CHIP_ICD_IDLE_MODE_DURATION=120
CONFIG_CHIP_ICD_ACTIVE_MODE_DURATION=300
CONFIG_CHIP_ICD_SLOW_POLL_INTERVAL=1000
CONFIG_CHIP_ICD_FAST_POLLING_INTERVAL=200

CONFIG_CHIP_ENABLE_PAIRING_AUTOSTART=n
CONFIG_CHIP_PROJECT_CONFIG="src/chip_project_config.h"
CONFIG_CHIP_DEVICE_TYPE=67
CONFIG_STD_CPP17=y
CONFIG_DK_LIBRARY=n
CONFIG_BT_DEVICE_NAME="PuzlMatter"

CONFIG_THREAD_NAME=y
CONFIG_MPU_STACK_GUARD=y
CONFIG_CHIP_NFC_COMMISSIONING=n
CONFIG_CHIP_FACTORY_DATA=y
CONFIG_CHIP_FACTORY_DATA_BUILD=y

# ***************************

overlay file:

/*
* Copyright (c) 2021-2022 Nordic Semiconductor ASA
*
* SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
*/

// For more help, browse the DeviceTree documentation at docs.zephyrproject.org/.../index.html
// You can also visit the nRF DeviceTree extension documentation at nrfconnect.github.io/.../nrfdevicetree.html

/ {
        /*
        * In some default configurations within the nRF Connect SDK,
        * e.g. on nRF52840, the chosen zephyr,entropy node is &cryptocell.
        * This devicetree overlay ensures that default is overridden wherever it
        * is set, as this application uses the RNG node for entropy exclusively.
        */
        chosen {
                zephyr,entropy = &rng;
        };
};

// The 0x100 bytes of the PuzL MfgBlock starts at 0x20000000. To reserve it for Mfg we'll tell the
// linker that it can put code related items starting at 0x20000100. This conflicts what is called
// out in <SDK>/zephyr/dts/arm/nordic/nrf52840.dtsi but does take precedence.
// Note: or alternatively specify with CONFIG_SRAM_... settings in prj.conf file.
&sram0 {
    reg = < 0x20000100 (DT_SIZE_K(256)-0x100)>; /* PuzL: override stock 0x20000000 setting. */
};

/* PuzL Persistent Storage (Internal Flash).
        Note: puzl_partition is defined in
                  ./configuration/nrf52840dk_nrf52840/pm_static_dfu.yml
*/

// PuzL Labs Quad Flash (External Flash).
&qspi_default {
        group1 {
                psels = <NRF_PSEL(QSPI_SCK, 0, 19)>,
                        <NRF_PSEL(QSPI_IO0, 0, 20)>,
                        <NRF_PSEL(QSPI_IO1, 0, 22)>,
                        <NRF_PSEL(QSPI_IO2, 0, 23)>,
                        <NRF_PSEL(QSPI_IO3, 0, 21)>,
                        <NRF_PSEL(QSPI_CSN, 0, 17)>;
                nordic,drive-mode = <NRF_DRIVE_H0H1>;
        };
};

&qspi_sleep {
        group1 {
                psels = <NRF_PSEL(QSPI_SCK, 0, 19)>,
                        <NRF_PSEL(QSPI_IO0, 0, 20)>,
                        <NRF_PSEL(QSPI_IO1, 0, 22)>,
                        <NRF_PSEL(QSPI_IO2, 0, 23)>,
                        <NRF_PSEL(QSPI_IO3, 0, 21)>;
                low-power-enable;
        };
        group2 {
                psels = <NRF_PSEL(QSPI_CSN, 0, 17)>;
                low-power-enable;
                bias-pull-up;
        };
};

/ {
        chosen {
                nordic,pm-ext-flash = &mx25r64;
        };
};

// PuzL Labs Button and LED
&button0 {
        gpios = <&gpio0 30 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>;
};
&led0 {
        gpios = <&gpio0 14 (GPIO_ACTIVE_LOW | GPIO_OPEN_DRAIN | (1 << 8))>; //(1<<8) sets high drive stength.
};

&button1 {
        gpios = <&gpio0 2 (GPIO_ACTIVE_HIGH )>; //| GPIO_PULL_DOWN)>; do not set pull-dwn as default so gpio_pin_configure_dt can config
};

// PuzL UART
&uart0_default {
        group1 {
                psels = <NRF_PSEL(UART_TX, 0, 10)>;
        };
        group2 {
                psels = <NRF_PSEL(UART_RX, 0, 9)>;
        };
};

&uart0_sleep {
        group1 {
                psels = <NRF_PSEL(UART_TX, 0, 10)>,
                        <NRF_PSEL(UART_RX, 0, 9)>;
        };
};

// PuzL ADC
/ {
        zephyr,user {
                io-channels = <&adc 4>,<&adc 7>;
        };
};

&adc {
        #address-cells = <1>;
        #size-cells = <0>;

        channel@4 {
                reg = <4>;
                zephyr,gain = "ADC_GAIN_1_4"; // gain=1/4 VDD/4/(1/4)=VDD FS
                zephyr,reference = "ADC_REF_VDD_1_4"; // VDD/4
                zephyr,acquisition-time = <ADC_ACQ_TIME_DEFAULT>;
                zephyr,input-positive = <NRF_SAADC_AIN4>; // P0.28
                zephyr,resolution = <12>;
        };
        channel@7 {
                reg = <7>;
                zephyr,gain = "ADC_GAIN_1_6"; // gain=1/6 .6/(1/6)=3.6v FS
                zephyr,reference = "ADC_REF_INTERNAL"; // Vref=.6v
                zephyr,acquisition-time = <ADC_ACQ_TIME_DEFAULT>; //
                zephyr,input-positive = <NRF_SAADC_VDD>; // battery
                zephyr,resolution = <12>;
        };
};

&arduino_adc {
        io-channel-map = <0 &adc 1>, <1 &adc 2>, <2 &adc 4>, <3 &adc 0>, <4 &arduino_adc 0>, <5 &adc 7>;
};

// PuzL PWM (Buzzer)
&pwm0_default {
        group1 {
                psels = <NRF_PSEL(PWM_OUT0, 1, 15)>;
                /delete-property/ nordic,invert; // sets PWM level=1 (no DC current)
        };
};

&pwm0_sleep {
        group1 {
                psels = <NRF_PSEL(PWM_OUT0, 1, 15)>;
                low-power-enable;
        };
};

// PuzL I2C (temp/humidity)
&i2c0_default {
        group1 {
                psels = <NRF_PSEL(TWIM_SDA, 0, 4)>,
                        <NRF_PSEL(TWIM_SCL, 0, 5)>;
        };
};

&i2c0_sleep {
        group1 {
                psels = <NRF_PSEL(TWIM_SDA, 0, 4)>,
                        <NRF_PSEL(TWIM_SCL, 0, 5)>;
                low-power-enable;
        };
};

// *****************************************************
// Some default nordic settings do not apply for PuzL.
// Disable unused peripherals to reduce power consumption.
&button2 {
        status = "disabled";
};
&button3 {
        status = "disabled";
};
&led1 {
        status = "disabled";
};
&led2 {
        status = "disabled";
};
&led3 {
        status = "disabled";
};
&uart1 {
        status = "disabled";
};
&i2c1 {
        status = "disabled";
};
&spi0 {
        status = "disabled";
};
&spi1 {
        status = "disabled";
};
&spi2 {
        status = "disabled";
};
&spi3 {
        status = "disabled";
};
&usbd {
        status = "disabled";
};

&power {
        status = "disabled";
};

// ***************************************************** END *************************

Gene

RE: Working DeviceTree configuration on v2.5.2 fails for v2.6 and later SDK versions

runsiv — Tue, 28 Jan 2025 13:03:42 GMT

Hi Gene

I will be looking into your case. Just a few question to start with:

1. Have you tried to probe the pins with a logic analyzer?

2. Can you replicate this on a DK?

3. Can you post the overlay so I can have a look at it and prj.conf?

Regards

Runar