migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

RE: migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

Stian Røed Hafskjold — Wed, 04 Mar 2026 10:26:38 GMT

This whole thread is based on a false assumption that enabling the GPIOTE peripheral results in a current consumption increase.

From a hardware perspective there is no way to disable the GPIOTE peripheral. There is no ENABLE register. It is always enabled. By removing the gpiote instance from the device tree you will get build errors, because it is an integral part of other libraries.

If you have the gpiote instance in your device tree and you have a high current consumption. There is something else causing the high current consumption.

The only exception to this is if you have configured a pin as input, sensing for a edge transition. In this configuration the NRF_GPIOTE->CONFIG[] register will be linked to the relevant GPIO and it will enable the GPIOTE IN event, for sensing the edge. This will lead to from 5 to 100 uA current increase (depending on the product type, nRF52/53/54 etc..) If you want to mitigate this you need to use level trigger on the GPIO instead of edge trigger. It will then use the PORT event instead of the IN event. And there will be no extra current consumption.

So the solution is to use level triggering on the pin, not disabling GPIOTE in the devicetree. How this is done has changed a bit throughout the years. Earlier you had to add the property sense-edge-mask = < 0xffffffff >; to the gpio0 or gpio1 instance in the overlay file. In newer NCS versions you do this in the interrupt configuration, e.g.:

gpio_pin_interrupt_configure_dt(&button,GPIO_INT_EDGE_TO_ACTIVE);

or:
gpio_pin_interrupt_configure_dt(&button,GPIO_INT_LEVEL_ACTIVE);

https://docs.zephyrproject.org/latest/doxygen/html/group__gpio__interface.html#ga35d2ff0e041236d82004a4bb2b5bf634

Some more information on the GPIO library can be found here: https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-2-reading-buttons-and-controlling-leds/topic/gpio-generic-api/

In this thread there are multiple mentions of "major current increase", but I was not able to see any actual numbers. Writing the actual current consumption differences will help in pin pointing the real problem.

To summarize:

If you are using a GPIO as input trigger, you can choose between edge triggering and level triggering. Edge triggering will add some 10s of micro amps to the current, while level triggering will not increase the current.
If you are not using a GPIO input trigger, you do not need to do anything.
If you still see higher current, it is cause by some other peripheral

RE: migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

GerardB — Thu, 26 Feb 2026 16:37:41 GMT

Any hope of solving this problem soon..!?

is it solved in SDK v3.x?

this is really a show-stopper for me…

major power draw increase when disabling gpiote!

thx

Gerard

RE: migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

GerardB — Tue, 23 Sep 2025 16:45:58 GMT

Hi grzegorz

I still have this problem (major power increase when I enable GPIOTE - which I don’t use!). And new SDK version won’t build if disabled it.

Can you clarify for me what you mean by the ‘delete-property directive’? Where and how is it used to resolve this issue?

thanks!

Gerard

RE: migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

grzegorz — Sat, 01 Feb 2025 13:18:44 GMT

Hi,

I have seen this thread, you can even find my posts there. It seems that we need to stick with the /delete-property/ hack for now.

RE: migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

Kazi Afroza Sultana — Thu, 23 Jan 2025 16:52:36 GMT

Hello,

You do not want to use port event. can you try to do this(+) Unable to disable GPIOTE for nRF Connect SDK 2.6.1 - Nordic Q&A - Nordic DevZone - Nordic DevZone?

The Zephyr GPIO API implementation uses GPIOTE for certain operations, particularly for interrupt handling.

zephyr/drivers/gpio/gpio_nrfx.c, this refers using GPIOTE is configured when GPIO needs to be used.

RE: migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

grzegorz — Tue, 14 Jan 2025 15:25:11 GMT

Hello

I don't want to use any events. I want to have particular GPIO port enabled and e.g. drive LED, but have GPIOTE disabled. Now I can't do that because the code in zephyr/drivers/gpio/gpio_nrfx.c checks if GPIO has corresponding GPIOTE enabled. Why was this check introduced? The current solution is to remove the link between GPIO and GPIOTE with the "delete-property" directive. But we shouldn't need to do that.

RE: migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

Kazi Afroza Sultana — Mon, 06 Jan 2025 16:45:25 GMT

Hello,

Can you try to use port even in device tree file instead GPIOTE event? When port even is enabled in the device tree file of board or in the overlay file. This configuration will make the GPIO driver use the GPIOTE PORT event for all pins on both GPIO ports, even if GPIOTE is enabled in the device tree file.

RE: migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

grzegorz — Tue, 31 Dec 2024 17:47:01 GMT

Kazi Afroza Sultana Why do I have to enable GPIOTE? I don't want to use it and enabling it makes power consumption higher.

RE: migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

Sofar — Tue, 05 Nov 2024 09:26:39 GMT

I add '/delete-property/ gpiote-instance;' to my gpio nodes in overlay file, and it can be build correctly without gpiote enable.

refer: devzone.nordicsemi.com/.../unable-to-disable-gpiote-for-nrf-connect-sdk-2-6-1

RE: migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

Kazi Afroza Sultana — Tue, 19 Mar 2024 15:35:53 GMT

Hello Gerad,

For custom board, you have to enable GPIOTE node in the board dts manually. Can you try to

&gpiote {
status = "disabled";
}; change this to status enabled?

RE: migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

GerardB — Tue, 19 Mar 2024 03:34:49 GMT

I don't understand the above response! We specifically do NOT want to enable (or use) the gpiote device (as I mentioned earlier).

Although we have a custom board, we do not have a custom board file (yet). So we use the nrf5340dk_nrf5340_cpuapp "board" & use an nrf5340dk_nrf5340_cpuapp.overlay file for our board.

The "problem" with SDK v2.6.0 is that when we disable the gpiote device in the overlay file (as we have done in all earlier SDK's) we get the errors mentioned. So to get a clean build with SDK v2.6.0, we have to remove all references to gpiote in our overlay file BUT then the gpiote device is obviously enabled and the CRITICAL side effect is that power consumption is dramatically increased. So the real question is "how do we disable the gpiote device in SDK v2.6.0.??"

Below is the overlay file we successfully use for SDK v2.5.2 (& earlier SDK's):

&pinctrl {
	/*
	uart0_default: uart0_default {
		group1 {
			psels = <NRF_PSEL(UART_TX, 1, 4)>,
				<NRF_PSEL(UART_RTS, 1, 6)>;
		};
		group2 {
			psels = <NRF_PSEL(UART_RX, 1, 5)>,
				<NRF_PSEL(UART_CTS, 1, 7)>;
			bias-pull-up;
		};
	};

	uart0_sleep: uart0_sleep {
		group1 {
			psels = <NRF_PSEL(UART_TX, 1, 4)>,
				<NRF_PSEL(UART_RX, 1, 5)>,
				<NRF_PSEL(UART_RTS, 1, 6)>,
				<NRF_PSEL(UART_CTS, 1, 7)>;
			low-power-enable;
		};
	};
	*/ 
	i2c1_default: i2c1_default {
		group1 {
			psels = <NRF_PSEL(TWIM_SDA, 1, 2)>,
				<NRF_PSEL(TWIM_SCL, 1, 3)>;
			bias-pull-up;
			nordic,drive-mode = < NRF_DRIVE_S0D1 >;
		};
	};

	i2c1_sleep: i2c1_sleep {
		group1 {
			psels = <NRF_PSEL(TWIM_SDA, 1, 2)>,
				<NRF_PSEL(TWIM_SCL, 1, 3)>;
			low-power-enable;
		};
	};

};

&adc {
	status = "okay";
};

&gpio0 {
	status = "okay";
};
&gpio1 {
	status = "okay";
};

&gpiote {
	status = "disabled";
};

&i2c1 {
	status = "okay";
	/*
    accelerometer: accelerometer@5 {
        compatible = "i2c-device";
        reg = < 0x05 >;
        label = "ACCELEROMETER";
    };
	tdksensor: TDKsensor@8 {
        compatible = "i2c-device";
        reg = < 0x08 >;
        label = "TDKSENSOR";
    };
	*/
};

&uart0 {
	status = "disabled";
    pinctrl-0 = <&uart0_default>;
    pinctrl-1 = <&uart0_sleep>;
    pinctrl-names = "default", "sleep";
};
&uart1 {
	status = "disabled";
};

&qspi {
	status = "disabled";
};

&led0 {
	status = "disabled";
};
&led1 {
	status = "disabled";
};
&led2 {
	status = "disabled";
};
&led3 {
	status = "disabled";
};

&pwm_led0 {
	status = "disabled";
};

&button0 {
	status = "disabled";
};
&button1 {
	status = "disabled";
};
&button2 {
	status = "disabled";
};
&button3 {
	status = "disabled";
};

&zephyr_udc0 {
    status = "disabled";
	/*
	cdc_acm_uart0: cdc_acm_uart0 {
		compatible = "zephyr,cdc-acm-uart";
		label = "CDC_ACM_0";
	};
	*/
};
/*
/ {
	chosen {
			zephyr,console = &cdc_acm_uart0;
	};
};
*/
/* Enabling external flash partitions as a workaround to let the partition manager 
 *  create the 'ram_flash' partition for us. 
 */
 / {
    chosen {
        nordic,pm-ext-flash = &mx25r64;
    };
};

For SDK v2.6.0, the build errors are caused by the disabling of the gpiote device (as I explained earlier).

As I also mentioned earlier, to save power, we config SERIAL=n and CONSOLE=n and LOG=n. Below is our CONFIG file:

CONFIG_REBOOT=y

# Activate Power Management (reduce power requirements
# see: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/optimizing-power-on-nrf53-designs
# CONFIG_PM=y
CONFIG_PM_DEVICE=y
CONFIG_PM_DEVICE_RUNTIME=y
CONFIG_BOARD_ENABLE_DCDC_APP=y
CONFIG_BOARD_ENABLE_DCDC_NET=y
CONFIG_BOARD_ENABLE_DCDC_HV=y
CONFIG_SERIAL=n

# Errata 160 included in v2.3.0 & later - ensure System Clock is enabled
CONFIG_SYS_CLOCK_EXISTS=y

CONFIG_LOG=n
CONFIG_USE_SEGGER_RTT=n

CONFIG_RESET_ON_FATAL_ERROR=y   # not sure this works for non "Nordic DK" boards!?       
CONFIG_ASSERT=n    # crashes i2c init when turned on (=y) with RTT logging - need to investigate...!?

CONFIG_LOG_DEFAULT_LEVEL=3

# disable all things related to uarts, usb & console (for max power savings) - CONFIG_SERIAL=n already set above
CONFIG_CONSOLE=n

# set stack & heap sizes.
CONFIG_HEAP_MEM_POOL_SIZE=8192
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=8192
CONFIG_MAIN_STACK_SIZE=10240
CONFIG_BT_RX_STACK_SIZE=4096

# Disable the DK (nordic dev Boards) LED and Buttons library for WearSense boards
CONFIG_DK_LIBRARY=n

# required for generating random number for suffix of original BLE NAME set for device. 
CONFIG_ENTROPY_GENERATOR=y
CONFIG_ENTROPY_DEVICE_RANDOM_GENERATOR=y

# configure Settings to be stored in NVS Flash on nrf5340 SoC
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_NVS=y
CONFIG_SETTINGS=y
CONFIG_SETTINGS_NVS=y
CONFIG_SETTINGS_RUNTIME=y

# BLE Settings
CONFIG_BT=y
CONFIG_BT_SETTINGS=n                        # for now we take care of our own BLE settings.
CONFIG_BT_CENTRAL=n
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_NAME="WearSense Sensor"    # Name is re-defined & replaced at runtime
CONFIG_BT_DEVICE_NAME_DYNAMIC=y
CONFIG_BT_MAX_CONN=1
CONFIG_BT_MAX_PAIRED=1

# appearance 1344 = "Generic Sensor" 
# (see: https://specificationrefs.bluetooth.com/assigned-values/Appearance%20Values.pdf )
CONFIG_BT_DEVICE_APPEARANCE=1344

# configure BLE "Device Information Service" (BT_DIS) characteristics.
CONFIG_BT_DIS=y
CONFIG_BT_DIS_MODEL="WearSense LS2"
CONFIG_BT_DIS_MANUF="wear-sense.com"
CONFIG_BT_DIS_FW_REV=y
CONFIG_BT_DIS_SETTINGS=y            # allows following values to be assigned at runtime
CONFIG_BT_DIS_SERIAL_NUMBER=y       # assigned at runtime in code
CONFIG_BT_DIS_HW_REV=y              # assigned at runtime in code
CONFIG_BT_DIS_SW_REV=n              # not required for WearSense app. 
CONFIG_BT_DIS_PNP=n                 # not required for WearSense app.

CONFIG_BT_NUS=y         # Enable the NUS service (in advertising)

CONFIG_BT_BAS=y         # Enable the Battery Level service (in advertising)

CONFIG_BT_USER_DATA_LEN_UPDATE=y

CONFIG_BT_GAP_PERIPHERAL_PREF_PARAMS=y
CONFIG_BT_GAP_AUTO_UPDATE_CONN_PARAMS=y

# set BLE 'connect parameters' for lowest power consumption 
# so lower data transfer speed but low power when connected but not sending data... 
# 36 = 30ms, 48 = 60ms
# 24 = able to 'miss' max of 24 intervals of 60ms each to keep BLE connection alive.
# 500 = 5000 ms - max allowed by Apple (& probably others)
CONFIG_BT_PERIPHERAL_PREF_MIN_INT=36
CONFIG_BT_PERIPHERAL_PREF_MAX_INT=48    
CONFIG_BT_PERIPHERAL_PREF_LATENCY=24
CONFIG_BT_PERIPHERAL_PREF_TIMEOUT=500

CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_NEWLIB_LIBC_FLOAT_SCANF=y

# Enable mcumgr (used for reset over BLE and OTA firmware updates).
CONFIG_MCUMGR=y

# Ensure an MCUboot-compatible binary is generated.
CONFIG_BOOTLOADER_MCUBOOT=y

# CONFIG_MCUMGR_SMP_BT_AUTHEN=n
CONFIG_DFU_MULTI_IMAGE=y
CONFIG_DFU_MULTI_IMAGE_MAX_IMAGE_COUNT=2
CONFIG_NRF53_UPGRADE_NETWORK_CORE=y
CONFIG_MCUBOOT_IMG_MANAGER=y

# Enable core DFU/OTA features.
# CONFIG_MCUMGR_CMD_IMG_MGMT=y
CONFIG_MCUMGR_GRP_IMG=y

# CONFIG_MCUMGR_CMD_OS_MGMT=y
CONFIG_MCUMGR_GRP_OS=y

CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU_VALIDATION=y
CONFIG_DFU_MULTI_IMAGE_PACKAGE_BUILD=y
CONFIG_DFU_MULTI_IMAGE_PACKAGE_NET=y

# CONFIG_MCUMGR_SMP_WORKQUEUE_STACK_SIZE=8192
CONFIG_MCUMGR_TRANSPORT_WORKQUEUE_STACK_SIZE=8192

# added after devzone case example.
CONFIG_MCUBOOT_USE_ALL_AVAILABLE_RAM=y
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU_SPEEDUP=y

# CONFIG_MCUBOOT_IMAGE_VERSION="2.3.0+0" (replaced by VERSION file in v2.5.x)

CONFIG_UPDATEABLE_IMAGE_NUMBER=2
CONFIG_ADD_MCUBOOT_MEDIATE_SIM_FLASH_DTS=y
CONFIG_SIZE_OPTIMIZATIONS=y

# Enable the SAADC ADC support
CONFIG_ADC=y
CONFIG_ADC_ASYNC=y
CONFIG_ADC_NRFX_SAADC=y

CONFIG_FPU=y

# I2C required to read Pressure Sensor & Accelerometer
CONFIG_I2C=y

So for now we are reverting back to SDK v2.5.2 but we would still like to move over to SDK v2.6.0 asap. So still need your help with that!

Thanks!

Gerard

RE: migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

Kazi Afroza Sultana — Mon, 18 Mar 2024 10:36:19 GMT

Hello,

This is perhaps related to the changes in nrfx3.2.0. I got feedback from team.

Because of adding multi-instance GPIOTE support in nrfx, now the user needs to explicitly enable gpiote node in the board dts. We do it by default for Nordic DKs, but if customer is using custom board it needs to be done manually.

RE: migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

GerardB — Thu, 14 Mar 2024 16:47:20 GMT

More information on this:

When I remove the lines:

&gpiote {

status = "disabled";

};

from the overlay file ( nrf5340dk_nrf5340_cpuapp.overlay ) , all the errors magically disappear & it builds OK and it seems to work (including multi-image DFU over BLE).

The new build log now looks like this:

 *  Executing task: nRF Connect: Build [pristine]: sensor_firmware/build (active) 

Building sensor_firmware
west build --build-dir /Users/gerardbucas/GitHub/sensor_firmware/build /Users/gerardbucas/GitHub/sensor_firmware --pristine --board nrf5340dk_nrf5340_cpuapp --no-sysbuild -- -DNCS_TOOLCHAIN_VERSION=NONE -Dhci_ipc_OVERLAY_CONFIG=/opt/nordic/ncs/v2.6.0/nrf/samples/common/mcumgr_bt_ota_dfu/rpmsg_child_image_overlay.conf;/opt/nordic/ncs/v2.6.0/nrf/subsys/bootloader/image/secure_boot.conf;/opt/nordic/ncs/v2.6.0/nrf/subsys/partition_manager/partition_manager_enabled.conf -Dmcuboot_CONF_FILE=/Users/gerardbucas/GitHub/sensor_firmware/child_image/mcuboot/boards/nrf5340dk_nrf5340_cpuapp.conf -Dmcuboot_DTC_OVERLAY_FILE=/opt/nordic/ncs/v2.6.0/nrf/modules/mcuboot/flash_sim.overlay -Dmcuboot_OVERLAY_CONFIG=/opt/nordic/ncs/v2.6.0/nrf/subsys/pcd/pcd.conf;/opt/nordic/ncs/v2.6.0/nrf/subsys/partition_manager/ext_flash_mcuboot_secondary.conf;/opt/nordic/ncs/v2.6.0/nrf/subsys/partition_manager/partition_manager_enabled.conf -DCACHED_CONF_FILE=/Users/gerardbucas/GitHub/sensor_firmware/prj.conf -DDTC_OVERLAY_FILE=/Users/gerardbucas/GitHub/sensor_firmware/nrf5340dk_nrf5340_cpuapp.overlay

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: /Users/gerardbucas/GitHub/sensor_firmware
-- CMake version: 3.21.0
-- Found Python3: /opt/nordic/ncs/toolchains/580e4ef81c/opt/python@3.9/bin/python3.9 (found suitable version "3.9.6", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: /Users/gerardbucas/Library/Caches/zephyr
-- Zephyr version: 3.5.99 (/opt/nordic/ncs/v2.6.0/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: nrf5340dk_nrf5340_cpuapp
-- Found host-tools: zephyr 0.16.5 (/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.5 (/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk)
-- Found Dtc: /opt/nordic/ncs/toolchains/580e4ef81c/bin/dtc (found suitable version "1.6.1", minimum required is "1.4.6") 
-- Found BOARD.dts: /opt/nordic/ncs/v2.6.0/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpuapp.dts
-- Found devicetree overlay: /Users/gerardbucas/GitHub/sensor_firmware/nrf5340dk_nrf5340_cpuapp.overlay
-- Generated zephyr.dts: /Users/gerardbucas/GitHub/sensor_firmware/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /Users/gerardbucas/GitHub/sensor_firmware/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: /Users/gerardbucas/GitHub/sensor_firmware/build/zephyr/dts.cmake

warning: UART_CONSOLE (defined at drivers/console/Kconfig:43) was assigned the value 'y' but got the
value 'n'. Check these unsatisfied dependencies: SERIAL (=n), SERIAL_HAS_DRIVER (=n), CONSOLE (=n).
See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_UART_CONSOLE and/or look up
UART_CONSOLE in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.


warning: LOG_DEFAULT_LEVEL (defined at subsys/logging/Kconfig.filtering:13) was assigned the value
'3' but got the value ''. Check these unsatisfied dependencies: LOG (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LOG_DEFAULT_LEVEL and/or look up
LOG_DEFAULT_LEVEL in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

Parsing /opt/nordic/ncs/v2.6.0/zephyr/Kconfig
Loaded configuration '/opt/nordic/ncs/v2.6.0/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpuapp_defconfig'
Merged configuration '/Users/gerardbucas/GitHub/sensor_firmware/prj.conf'
Configuration saved to '/Users/gerardbucas/GitHub/sensor_firmware/build/zephyr/.config'
Kconfig header saved to '/Users/gerardbucas/GitHub/sensor_firmware/build/zephyr/include/generated/autoconf.h'
-- Found GnuLd: /opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd (found version "2.38") 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc

=== child image hci_ipc - CPUNET begin ===
loading initial cache file /Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc/child_image_preload.cmake
Loading Zephyr default modules (Zephyr base).
-- Application: /opt/nordic/ncs/v2.6.0/zephyr/samples/bluetooth/hci_ipc
-- CMake version: 3.21.0
-- Found Python3: /opt/nordic/ncs/toolchains/580e4ef81c/opt/python@3.9/bin/python3.9 (found suitable version "3.9.6", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: /Users/gerardbucas/Library/Caches/zephyr
-- Zephyr version: 3.5.99 (/opt/nordic/ncs/v2.6.0/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: nrf5340dk_nrf5340_cpunet
-- Found host-tools: zephyr 0.16.5 (/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.5 (/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk)
-- Found Dtc: /opt/nordic/ncs/toolchains/580e4ef81c/bin/dtc (found suitable version "1.6.1", minimum required is "1.4.6") 
-- Found BOARD.dts: /opt/nordic/ncs/v2.6.0/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpunet.dts
-- Generated zephyr.dts: /Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: /Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc/zephyr/dts.cmake
Parsing /opt/nordic/ncs/v2.6.0/zephyr/Kconfig
Loaded configuration '/opt/nordic/ncs/v2.6.0/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpunet_defconfig'
Merged configuration '/opt/nordic/ncs/v2.6.0/zephyr/samples/bluetooth/hci_ipc/prj.conf'
Merged configuration '/opt/nordic/ncs/v2.6.0/nrf/samples/common/mcumgr_bt_ota_dfu/rpmsg_child_image_overlay.conf'
Merged configuration '/opt/nordic/ncs/v2.6.0/nrf/subsys/bootloader/image/secure_boot.conf'
Merged configuration '/opt/nordic/ncs/v2.6.0/nrf/subsys/partition_manager/partition_manager_enabled.conf'
Merged configuration '/Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc/zephyr/misc/generated/extra_kconfig_options.conf'
Configuration saved to '/Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc/zephyr/.config'
Kconfig header saved to '/Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc/zephyr/include/generated/autoconf.h'
-- Found GnuLd: /opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd (found version "2.38") 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc

=== child image b0n - CPUNET (inherited) begin ===
loading initial cache file /Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc/b0n/child_image_preload.cmake
Loading Zephyr default modules (Zephyr base).
-- Application: /opt/nordic/ncs/v2.6.0/nrf/samples/nrf5340/netboot
-- CMake version: 3.21.0
-- Found Python3: /opt/nordic/ncs/toolchains/580e4ef81c/opt/python@3.9/bin/python3.9 (found suitable version "3.9.6", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: /Users/gerardbucas/Library/Caches/zephyr
-- Zephyr version: 3.5.99 (/opt/nordic/ncs/v2.6.0/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: nrf5340dk_nrf5340_cpunet
-- Found host-tools: zephyr 0.16.5 (/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.5 (/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk)
-- Found Dtc: /opt/nordic/ncs/toolchains/580e4ef81c/bin/dtc (found suitable version "1.6.1", minimum required is "1.4.6") 
-- Found BOARD.dts: /opt/nordic/ncs/v2.6.0/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpunet.dts
-- Generated zephyr.dts: /Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc/b0n/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc/b0n/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: /Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc/b0n/zephyr/dts.cmake
Parsing /opt/nordic/ncs/v2.6.0/nrf/samples/nrf5340/netboot/Kconfig
Loaded configuration '/opt/nordic/ncs/v2.6.0/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpunet_defconfig'
Merged configuration '/opt/nordic/ncs/v2.6.0/nrf/samples/nrf5340/netboot/prj.conf'
Merged configuration '/opt/nordic/ncs/v2.6.0/nrf/subsys/partition_manager/partition_manager_enabled.conf'
Configuration saved to '/Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc/b0n/zephyr/.config'
Kconfig header saved to '/Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc/b0n/zephyr/include/generated/autoconf.h'
-- Found GnuLd: /opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd (found version "2.38") 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
-- Using ccache: /opt/nordic/ncs/toolchains/580e4ef81c/bin/ccache
CMake Warning at /opt/nordic/ncs/v2.6.0/zephyr/CMakeLists.txt:1957 (message):
  __ASSERT() statements are globally ENABLED


-- Configuring done
-- Generating done
-- Build files have been written to: /Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc/b0n
=== child image b0n - CPUNET (inherited) end ===

CMake Warning at /opt/nordic/ncs/v2.6.0/nrf/subsys/bootloader/cmake/debug_keys.cmake:36 (message):
  

      --------------------------------------------------------------
      --- WARNING: Using generated NSIB public/private key-pair. ---
      --- It should not be used for production.                  ---
      --- See CONFIG_SB_SIGNING_KEY_FILE                         ---
      --------------------------------------------------------------
      

Call Stack (most recent call first):
  /opt/nordic/ncs/v2.6.0/nrf/subsys/bootloader/cmake/provision_hex.cmake:47 (include)
  /opt/nordic/ncs/v2.6.0/nrf/subsys/CMakeLists.txt:20 (include)


-- libmetal version: 1.4.0 (/opt/nordic/ncs/v2.6.0/zephyr/samples/bluetooth/hci_ipc)
-- Build type:  
-- Host:    Darwin/x86_64
-- Target:  Generic/arm
-- Machine: arm
-- Looking for include file stdatomic.h
-- Looking for include file stdatomic.h - found
-- open-amp version: 1.4.0 (/opt/nordic/ncs/v2.6.0/modules/lib/open-amp/open-amp)
-- Host:    Darwin/x86_64
-- Target:  Generic/arm
-- Machine: arm
-- C_FLAGS :  -Wall -Wextra
-- Looking for include file fcntl.h
-- Looking for include file fcntl.h - found
-- Using ccache: /opt/nordic/ncs/toolchains/580e4ef81c/bin/ccache
CMake Warning at /opt/nordic/ncs/v2.6.0/nrf/cmake/partition_manager.cmake:79 (message):
  

          ---------------------------------------------------------------------
          --- WARNING: Using a bootloader without pm_static.yml.            ---
          --- There are cases where a deployed product can consist of       ---
          --- multiple images, and only a subset of these images can be     ---
          --- upgraded through a firmware update mechanism. In such cases,  ---
          --- the upgradable images must have partitions that are static    ---
          --- and are matching the partition map used by the bootloader     ---
          --- programmed onto the device.                                   ---
          ---------------------------------------------------------------------
          

Call Stack (most recent call first):
  /opt/nordic/ncs/v2.6.0/zephyr/cmake/modules/kernel.cmake:248 (include)
  /opt/nordic/ncs/v2.6.0/zephyr/cmake/modules/zephyr_default.cmake:138 (include)
  /opt/nordic/ncs/v2.6.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  /opt/nordic/ncs/v2.6.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:5 (find_package)


-- Configuring done
-- Generating done
-- Build files have been written to: /Users/gerardbucas/GitHub/sensor_firmware/build/hci_ipc
=== child image hci_ipc - CPUNET end ===

-- Found Python3: /opt/nordic/ncs/toolchains/580e4ef81c/opt/python@3.9/bin/python3.9 (found version "3.9.6") found components: Interpreter 

=== child image mcuboot -  begin ===
loading initial cache file /Users/gerardbucas/GitHub/sensor_firmware/build/mcuboot/child_image_preload.cmake
Loading Zephyr default modules (Zephyr base).
-- Application: /opt/nordic/ncs/v2.6.0/bootloader/mcuboot/boot/zephyr
-- CMake version: 3.21.0
-- Found Python3: /opt/nordic/ncs/toolchains/580e4ef81c/opt/python@3.9/bin/python3.9 (found suitable version "3.9.6", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: /Users/gerardbucas/Library/Caches/zephyr
-- Zephyr version: 3.5.99 (/opt/nordic/ncs/v2.6.0/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: nrf5340dk_nrf5340_cpuapp
-- Found host-tools: zephyr 0.16.5 (/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.5 (/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk)
-- Found Dtc: /opt/nordic/ncs/toolchains/580e4ef81c/bin/dtc (found suitable version "1.6.1", minimum required is "1.4.6") 
-- Found BOARD.dts: /opt/nordic/ncs/v2.6.0/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpuapp.dts
-- Found devicetree overlay: /opt/nordic/ncs/v2.6.0/nrf/modules/mcuboot/flash_sim.overlay
-- Generated zephyr.dts: /Users/gerardbucas/GitHub/sensor_firmware/build/mcuboot/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /Users/gerardbucas/GitHub/sensor_firmware/build/mcuboot/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: /Users/gerardbucas/GitHub/sensor_firmware/build/mcuboot/zephyr/dts.cmake
Parsing /opt/nordic/ncs/v2.6.0/bootloader/mcuboot/boot/zephyr/Kconfig
Loaded configuration '/opt/nordic/ncs/v2.6.0/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpuapp_defconfig'
Merged configuration '/Users/gerardbucas/GitHub/sensor_firmware/child_image/mcuboot/boards/nrf5340dk_nrf5340_cpuapp.conf'
Merged configuration '/opt/nordic/ncs/v2.6.0/nrf/subsys/pcd/pcd.conf'
Merged configuration '/opt/nordic/ncs/v2.6.0/nrf/subsys/partition_manager/ext_flash_mcuboot_secondary.conf'
Merged configuration '/opt/nordic/ncs/v2.6.0/nrf/subsys/partition_manager/partition_manager_enabled.conf'
Merged configuration '/Users/gerardbucas/GitHub/sensor_firmware/build/mcuboot/zephyr/misc/generated/extra_kconfig_options.conf'
Configuration saved to '/Users/gerardbucas/GitHub/sensor_firmware/build/mcuboot/zephyr/.config'
Kconfig header saved to '/Users/gerardbucas/GitHub/sensor_firmware/build/mcuboot/zephyr/include/generated/autoconf.h'
-- Found GnuLd: /opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd (found version "2.38") 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
-- Using ccache: /opt/nordic/ncs/toolchains/580e4ef81c/bin/ccache
MCUBoot bootloader key file: /opt/nordic/ncs/v2.6.0/bootloader/mcuboot/root-rsa-2048.pem
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/gerardbucas/GitHub/sensor_firmware/build/mcuboot
=== child image mcuboot -  end ===

CMake Warning at /opt/nordic/ncs/v2.6.0/nrf/modules/mcuboot/CMakeLists.txt:382 (message):
  

          ---------------------------------------------------------
          --- WARNING: Using default MCUBoot key, it should not ---
          --- be used for production.                           ---
          ---------------------------------------------------------
          



-- libmetal version: 1.4.0 (/Users/gerardbucas/GitHub/sensor_firmware)
-- Build type:  
-- Host:    Darwin/x86_64
-- Target:  Generic/arm
-- Machine: arm
-- Looking for include file stdatomic.h
-- Looking for include file stdatomic.h - found
-- open-amp version: 1.4.0 (/opt/nordic/ncs/v2.6.0/modules/lib/open-amp/open-amp)
-- Host:    Darwin/x86_64
-- Target:  Generic/arm
-- Machine: arm
-- C_FLAGS :  -Wall -Wextra
-- Looking for include file fcntl.h
-- Looking for include file fcntl.h - found
-- Using ccache: /opt/nordic/ncs/toolchains/580e4ef81c/bin/ccache
-- Found partition manager static configuration: /Users/gerardbucas/GitHub/sensor_firmware/pm_static.yml
Partition 'mcuboot' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_pad' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_primary' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_primary_app' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_secondary' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_secondary_1' is not included in the dynamic resolving since it is statically defined.
Partition 'pcd_sram' is not included in the dynamic resolving since it is statically defined.
Partition 'rpmsg_nrf53_sram' is not included in the dynamic resolving since it is statically defined.
Partition 'settings_storage' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_primary_1' is not included in the dynamic resolving since it is statically defined.
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/gerardbucas/GitHub/sensor_firmware/build
-- west build: building application
[1/315] Preparing syscall dependency handling

[6/315] Generating include/generated/version.h
-- Zephyr version: 3.5.99 (/opt/nordic/ncs/v2.6.0/zephyr), build: v3.5.99-ncs1
[1/224] Preparing syscall dependency handling

[3/224] Generating include/generated/version.h
-- Zephyr version: 3.5.99 (/opt/nordic/ncs/v2.6.0/zephyr), build: v3.5.99-ncs1
[1/139] Preparing syscall dependency handling

[3/139] Generating include/generated/version.h
-- Zephyr version: 3.5.99 (/opt/nordic/ncs/v2.6.0/zephyr), build: v3.5.99-ncs1
[139/139] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       23710 B      34176 B     69.38%
             RAM:        3528 B        64 KB      5.38%
           SRAM1:          0 GB        64 KB      0.00%
        IDT_LIST:          0 GB        32 KB      0.00%
[220/224] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      175900 B       222 KB     77.38%
             RAM:       58252 B        64 KB     88.89%
           SRAM1:          0 GB        64 KB      0.00%
        IDT_LIST:          0 GB        32 KB      0.00%
[175/315] Generating ../../zephyr/net_core_app_update.bin
image.py: sign the payload
[189/315] Generating ../../zephyr/net_core_app_signed.hex
image.py: sign the payload
[199/315] Generating ../../zephyr/net_core_app_test_update.hex
image.py: sign the payload
[1/248] Preparing syscall dependency handling

[5/248] Generating include/generated/version.h
-- Zephyr version: 3.5.99 (/opt/nordic/ncs/v2.6.0/zephyr), build: v3.5.99-ncs1
[248/248] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       27592 B        64 KB     42.10%
             RAM:      286824 B       440 KB     63.66%
        IDT_LIST:          0 GB        32 KB      0.00%
[305/315] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      184984 B     351744 B     52.59%
             RAM:       81060 B       440 KB     17.99%
        IDT_LIST:          0 GB        32 KB      0.00%
[308/315] Generating ../../zephyr/app_update.bin
image.py: sign the payload
[310/315] Generating ../../zephyr/app_signed.hex
image.py: sign the payload
[311/315] Generating ../../zephyr/app_test_update.hex
image.py: sign the payload
[315/315] Generating zephyr/merged_domains.hex
 *  Terminal will be reused by tasks, press any key to close it.

----------> EDIT: POWER CONSUMPTION IS DRAMATICALLY INCREASED NOW! <----------

HOWEVER, power consumption is dramatically increased (probably caused by the fact that we can't disable gpiote in the overlay).

NOTE: our prj.conf file is optimized for lowest possible power consumption, so:

CONFIG_PM_DEVICE=y

CONFIG_PM_DEVICE_RUNTIME=y

CONFIG_BOARD_ENABLE_DCDC_APP=y

CONFIG_BOARD_ENABLE_DCDC_NET=y

CONFIG_BOARD_ENABLE_DCDC_HV=y

CONFIG_SERIAL=n

CONFIG_CONSOLE=n

So we are forced to revert back to SDK v2.5.2 for now. Hope you can fix this issue going forward.

Thanks

Gerard

RE: migrating to sdk v2.6.0 - build errors (caused by gpiote being disabled?)

Kazi Afroza Sultana — Thu, 14 Mar 2024 14:59:08 GMT

Hello,

I have asked the relevant team. I will get back to you soon.

Thanks.

Kazi