DFU on nrf52832

RE: DFU on nrf52832

AHaug — Wed, 05 Feb 2025 08:45:40 GMT

Hi,

[quote user="Moh"]do I need to reset the MCU manually? [/quote]

The swap won't happen unless you reset the nRF. This should be explained here https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/. It is also illustrated here https://docs.nordicsemi.com/bundle/ncs-2.6.1/page/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/README.html and the following section.

[quote user="Moh"] Lastly, why can I not send reset commands from the DFU app? Thanks, Mo[/quote]

See the two previous links

[quote user="Moh"] How do I need to reduce flash and RAM usage?[/quote]

In general you would need to follow the steps in https://docs.nordicsemi.com/bundle/ncs-2.6.0/page/nrf/test_and_optimize/optimizing/index.html.

You have plenty of available flash (you're only using 279kB for your application). But you're using almost all of the RAM. See if there's something in the optimization documentation (such as reducing stack sizes) that might help you.

You're also using a device that is quite small (512kB flash/64kB RAM). An alternative is to upgrade to the 52833 (128 KB RAM)

Kind regards,
Andreas

RE: DFU on nrf52832

Moh — Mon, 03 Feb 2025 16:31:04 GMT

Hi Andreas, do I need to reset the MCU manually? How do I need to reduce flash and RAM usage? Lastly, why can I not send reset commands from the DFU app? Thanks, Mo

RE: DFU on nrf52832

AHaug — Sun, 02 Feb 2025 13:03:53 GMT

Hi,

No worries, I hope you had a good holiday :)

[quote user="Moh"]Problem I am facing is that when I ran the update via the app, the update runs fine but when it completes, it doesn't reset the MCU automatically.[/quote]

You need to add a reset command at the end of the DFU process manually. Typically in the samples we just reset the DK with either nrfjprog --reset or by pressing the reset button

I will have a look at the zip this week unless the above suggestion resolves the issue! :)

Kind regards,
Andreas

RE: DFU on nrf52832

Moh — Sat, 01 Feb 2025 19:53:52 GMT

Hi Andreas, I also would like to mention why my application size is big. This is a very basic application. It uses a lot of flash and RAM. I am building with size compiler optimisation and here is the result

Memory region         Used Size  Region Size  %age Used
           FLASH:      279108 B     441856 B     63.17%
             RAM:       62578 B        64 KB     95.49%
        IDT_LIST:          0 GB        32 KB      0.00%

RE: DFU on nrf52832

Moh — Fri, 31 Jan 2025 21:46:47 GMT

Hi Andreas, sorry for the late reply as away on holiday. Please find the cut down version of my project. FYI I have ran on my board and I am till seeing the same behavior.

Problem I am facing is that when I ran the update via the app, the update runs fine but when it completes, it doesn't reset the MCU automatically.

devzone.nordicsemi.com/.../dfu_5F00_spi.zip

RE: DFU on nrf52832

AHaug — Mon, 27 Jan 2025 14:16:45 GMT

Hi Moh,

Looks to me that you're stuck in an infinite restart-loop when setting up the JESD216 sample. Please zip the project you were using for your custom board together with the build log and I'll have a look.

Do you see the same thing with the SPI NOR flash sample?. I can't really help you isolating the issue in your application unless you verify that your configuring of the external flash is working in NCS 2.6.0 with a reference sample.

[quote user="Moh"]I have good news is that I have managed to build my app with mcuboot with slot 1 using external flash. Issue I noticed that It builds if I use conf file as prj.conf but when I build the app with either prj_debug.conf or prj_release.conf, it doesn't build. I have no idea why it does. See prj.conf attached.8877.prj.conf[/quote]

Thats good and all, but I unfortunally can't extract anything from this. What build command did you use and/or how did you select the debug/release configuration? What did the build logs look like?

[quote user="Moh"]Lastly, how I can erase external flash from nrfjprog or Jlink?[/quote]

As of now we only have the -qspierasell in nrfjprog. This does unfortunately not work for SPI devices, so what other developers have done is to create their own solution based that handles this. I know this is a WIP to implement for SPI eraseall, but with an unkown ETA.

Kind regards,
Andreas

RE: DFU on nrf52832

Moh — Fri, 24 Jan 2025 20:31:24 GMT

Hi Andreas, sorry for late reply. Here is output of JESD216 sample. It doesn't seem working as expected though

*** Booting nRF Connect SDK v3.5.99-ncs1 ***

spi@40023000 SPI flash testing
==========================

Perform test on single sector
Test 1: Flash erase
*** Booting nRF Connect SDK v3.5.99-ncs1 ***

spi@40023000 SPI flash testing
==========================

Perform test on single sector
Test 1: Flash erase
*** Booting nRF Connect SDK v3.5.99-ncs1 ***

spi@40023000 SPI flash testing
==========================

Perform test on single sector
Test 1: Flash erase
*** Booting nRF Connect SDK v3.5.99-ncs1 ***

I have good news is that I have managed to build my app with mcuboot with slot 1 using external flash. Issue I noticed that It builds if I use conf file as prj.conf but when I build the app with either prj_debug.conf or prj_release.conf, it doesn't build. I have no idea why it does. See prj.conf attached.devzone.nordicsemi.com/.../8877.prj.conf

I do manage to run DFU using the device manager app, but when I select Test & Confirm, I am expecting MCU to reset towards the completion of update firmware, but it doesn't. When I try to reset from the app, it doesn't either. I can read two slots though.

devzone.nordicsemi.com/.../7217.mcuboot.conf

Lastly, how I can erase external flash from nrfjprog or Jlink?

Thanks, Moh

RE: DFU on nrf52832

AHaug — Fri, 24 Jan 2025 10:01:20 GMT

Hi,

[quote user="AHaug"]Did you see the expected output when hooking the device up to a terminal? If you ran the JESD216 sample as well, which output did you get?[/quote]

I still want a confirmation on this. Please attach the device logs or let me know if you need help in getting the logs from the device.

[quote user="AHaug"]

Next after getting these two samples up and running, which means that if you got the correct output, then the external flash would've been correctly configured, I intended for you to compare those two samples with https://github.com/aHaugl/samples_for_NCS/tree/main/bootloader/spi/smp_ble_feat_spi and replace the mx25 flash I've used here with your at25x flash. One difference I can spot immedeatly is the difference between the mcuboot.overlay in the smp_ble_feat_spi sample with your application and your mcuboot.overlay is that you're missing to add the spi device into mcuboot.overlay (which you've done in your board file. MCUboot also needs to be aware of the external flash for it to use it.

Try to get https://github.com/aHaugl/samples_for_NCS/blob/main/bootloader/spi/smp_ble_feat_spi/child_image up and running with your external flash and compare the setup there with your application

[/quote]

How about https://github.com/aHaugl/samples_for_NCS/blob/main/bootloader/spi/smp_ble_feat_spi? Are you able to run this sample with your external flash and board?

Kind regards,
Andreas

RE: DFU on nrf52832

Moh — Thu, 23 Jan 2025 21:04:27 GMT

Here is the generated dts as part of the failed build for your reference.devzone.nordicsemi.com/.../4571.zephyr.dts

RE: DFU on nrf52832

Moh — Thu, 23 Jan 2025 20:37:50 GMT

Hi Andreas, I have managed to build https://docs.zephyrproject.org/latest/samples/drivers/spi_flash/README.html with below dts

&spi2 {
    compatible = "nordic,nrf-spi";
    status = "okay";
    pinctrl-0 = <&spi2_default>;
    pinctrl-1 = <&spi2_sleep>;
    pinctrl-names = "default", "sleep";
    cs-gpios = <&gpio0 16 GPIO_ACTIVE_LOW>;
	at25xe321d: at25xe321d@0 {
        #address-cells = <1>;
        #size-cells = <1>;
		partitions {
			compatible = "fixed-partitions";
			#address-cells = <1>;
			#size-cells = <1>;

			slot1_partition: partition@0 {
				label = "image-1";
				reg = <0x0000000 DT_SIZE_K(472)>;
			};
			/* to be used in firmware */
			store_partition: partition@100000 {
				label = "store";
				reg = <0x00100000 0x00400000>;
			};
		};
		compatible = "jedec,spi-nor";
        reg = <0>; // Chip select 0
        spi-max-frequency = <100000000>;
        jedec-id = [1F 47 0C];
        // size = <0x400000>;  // 4 MB
		size = <DT_SIZE_M(4)>;
		has-dpd;
		t-enter-dpd = < 3000 >;
		t-exit-dpd = < 1200000 >;
    };
};

When I try to build my application without mciboot/DFU, it doesn't build. When I commented out

bt_enable(NULL); from my code base, it builds. I am figuring out why this is the case as I need BLE enabled in my application.

RE: DFU on nrf52832

AHaug — Thu, 23 Jan 2025 13:44:52 GMT

Hi,

Some times it takes longer than a day to get back for a reply, which is why I didn't get back to you before now. In these unfortunate cases, here are some resources for you to use to spend more time debugging while waiting for a reply: https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-2-debugging/ and https://docs.nordicsemi.com/bundle/ncs-latest/page/zephyr/develop/west/build-flash-debug.html#permanent_cmake_arguments

The https://github.com/aHaugl/samples_for_NCS/blob/main/bootloader/spi/smp_ble_feat_spi/child_image sample should've also been enough to use for comparison together with the two zephyr samples I sent in my previous reply

[quote user="Moh"]I have managed to build and run the sample with that dts spi2 configurations.[/quote]

Which of the two samples are you referring to here? And great! Did you see the expected output when hooking the device up to a terminal? If you ran the JESD216 sample as well, which output did you get?

Try to get https://github.com/aHaugl/samples_for_NCS/blob/main/bootloader/spi/smp_ble_feat_spi/child_image up and running with your external flash and compare the setup there with your application

I hope that you're successful in this and please feel free to ask follow up questions regarding the configuration and samples if needed

Kind regards,
Andreas

RE: DFU on nrf52832

Moh — Thu, 23 Jan 2025 12:13:47 GMT

Hi Andreas, do you have any update? Thanks Moh

RE: DFU on nrf52832

Moh — Wed, 22 Jan 2025 20:00:16 GMT

Hi Andreas, I have managed to build the application (without mcuboot) with above spi2 dts configuration if I comment out bt_enable(NULL); from my application. I have no idea why it's causing that.

RE: DFU on nrf52832

Moh — Wed, 22 Jan 2025 15:23:27 GMT

Hi Andreas, I have managed to build and run the sample with that dts spi2 configurations. I don't know why my application doesn't build.

&spi2 {
    compatible = "nordic,nrf-spi";
    status = "okay";
    pinctrl-0 = <&spi2_default>;
    pinctrl-1 = <&spi2_sleep>;
    pinctrl-names = "default", "sleep";
    cs-gpios = <&gpio0 16 GPIO_ACTIVE_LOW>;
	at25xe321d: at25xe321d@0 {
        #address-cells = <1>;
        #size-cells = <1>;
		partitions {
			compatible = "fixed-partitions";
			#address-cells = <1>;
			#size-cells = <1>;

			slot1_partition: partition@0 {
				label = "image-1";
				reg = <0x0000000 DT_SIZE_K(472)>;
			};
			/* to be used in firmware */
			store_partition: partition@100000 {
				label = "store";
				reg = <0x00100000 0x00400000>;
			};
		};
		compatible = "jedec,spi-nor";
        reg = <0>; // Chip select 0
        spi-max-frequency = <100000000>;
        jedec-id = [1F 47 0C];
        // size = <0x400000>;  // 4 MB
		size = <DT_SIZE_M(4)>;
		has-dpd;
		t-enter-dpd = < 3000 >;
		t-exit-dpd = < 1200000 >;
    };
};

RE: DFU on nrf52832

AHaug — Wed, 22 Jan 2025 14:31:07 GMT

Do you also get the expected output from the sample, i.e are you able to run it?

Kind regards,
Andreas

RE: DFU on nrf52832

Moh — Wed, 22 Jan 2025 14:30:12 GMT

Hi Andreas, When I try to build the sample (without mcuboot) with above attached spi2 dts configurations, I got similar error

/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: zephyr/libzephyr.a(flash_map_default.c.obj):(.rodata.default_flash_map+0x4c): undefined reference to `__device_dts_ord_122'
/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: zephyr/libzephyr.a(flash_map_default.c.obj):(.rodata.default_flash_map+0x5c): undefined reference to `__device_dts_ord_122'

but when I build with without partitions defined, It builds and runs fine.

&spi2 {
    compatible = "nordic,nrf-spi";
    status = "okay";
    pinctrl-0 = <&spi2_default>;
    pinctrl-1 = <&spi2_sleep>;
    pinctrl-names = "default", "sleep";
    cs-gpios = <&gpio0 16 GPIO_ACTIVE_LOW>;
	at25xe321d: at25xe321d@0 {
        #address-cells = <1>;
        #size-cells = <1>;
		compatible = "jedec,spi-nor";
        reg = <0>; // Chip select 0
        spi-max-frequency = <100000000>;
        jedec-id = [1F 47 0C];
        // size = <0x400000>;  // 4 MB
		size = <DT_SIZE_M(4)>;
		has-dpd;
		t-enter-dpd = < 3000 >;
		t-exit-dpd = < 1200000 >;
    };
};

RE: DFU on nrf52832

AHaug — Wed, 22 Jan 2025 14:15:17 GMT

[quote user="Moh"]Please find the log attached. I have also attached the prj_release file. As you can see, I have commented out [/quote]

My bad, I didn't spot the #.

Could you check with this sample (and your external flash) if you're able to get the external flash device running? https://docs.zephyrproject.org/latest/samples/drivers/spi_flash/README.html

You might need to run https://docs.zephyrproject.org/latest/samples/drivers/jesd216/README.html if the parameters in &spi2 is wrong

&spi2 {
    compatible = "nordic,nrf-spi";
    status = "okay";
    pinctrl-0 = <&spi2_default>;
    pinctrl-1 = <&spi2_sleep>;
    pinctrl-names = "default", "sleep";
    cs-gpios = <&gpio0 16 GPIO_ACTIVE_LOW>;

    at25xe321d: at25xe321d@0 {
        #address-cells = <1>;
        #size-cells = <1>;
		partitions {
			compatible = "fixed-partitions";
			#address-cells = <1>;
			#size-cells = <1>;

			slot1_partition: partition@0 {
				label = "image-1";
				reg = <0x0000000 DT_SIZE_K(472)>;
			};
			/* to be used in firmware */
			store_partition: partition@100000 {
				label = "store";
				reg = <0x00100000 0x00400000>;
			};
		};
		compatible = "jedec,spi-nor";
        reg = <0>; // Chip select 0
        spi-max-frequency = <100000000>;
        jedec-id = [1F 47 0C];
        // size = <0x400000>;  // 4 MB
		size = <DT_SIZE_M(4)>;
		has-dpd;
		t-enter-dpd = < 3000 >;
		t-exit-dpd = < 1200000 >;
    };
};

Kind regards,
Andreas

RE: DFU on nrf52832

Moh — Wed, 22 Jan 2025 09:07:37 GMT

Hi Andreas,

Please find the log attached. I have also attached the prj_release file. As you can see, I have commented out CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU. I have also attached log from devicetree.generated.h for undefined __device_dts_ord_105

/* Node's dependency ordinal: */

#define DT_N_S_soc_S_i2c_40004000_ORD 105

#define DT_N_S_soc_S_i2c_40004000_ORD_STR_SORTABLE 00105

devzone.nordicsemi.com/.../0005.prj_5F00_release.conf

-- west build: building application
[1/349] Preparing syscall dependency handling

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

[4/271] Generating include/generated/version.h
-- Zephyr version: 3.5.99 (/opt/nordic/ncs/v2.6.0/zephyr), build: v3.5.99-ncs1
[266/271] Linking C executable zephyr/zephyr_pre0.elf
FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map /Users/mohsin/path-feel-zephyr-fw/app/build_release/mcuboot/zephyr/zephyr_pre0.map 
: && ccache /opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc  -gdwarf-4 zephyr/CMakeFiles/zephyr_pre0.dir/misc/empty_file.c.obj -o zephyr/zephyr_pre0.elf  zephyr/CMakeFiles/offsets.dir/./arch/arm/core/offsets/offsets.c.obj  -fuse-ld=bfd  -T  zephyr/linker_zephyr_pre0.cmd  -Wl,-Map=/Users/mohsin/path-feel-zephyr-fw/app/build_release/mcuboot/zephyr/zephyr_pre0.map  -Wl,--whole-archive  app/libapp.a  zephyr/libzephyr.a  zephyr/arch/common/libarch__common.a  zephyr/arch/arch/arm/core/libarch__arm__core.a  zephyr/arch/arch/arm/core/cortex_m/libarch__arm__core__cortex_m.a  zephyr/arch/arch/arm/core/mpu/libarch__arm__core__mpu.a  zephyr/lib/libc/minimal/liblib__libc__minimal.a  zephyr/lib/libc/common/liblib__libc__common.a  zephyr/soc/soc/arm/nordic_nrf/libsoc__arm__nordic_nrf.a  zephyr/drivers/clock_control/libdrivers__clock_control.a  zephyr/drivers/console/libdrivers__console.a  zephyr/drivers/flash/libdrivers__flash.a  zephyr/drivers/gpio/libdrivers__gpio.a  zephyr/drivers/pinctrl/libdrivers__pinctrl.a  zephyr/drivers/serial/libdrivers__serial.a  zephyr/drivers/timer/libdrivers__timer.a  modules/nrf/lib/fprotect/lib..__nrf__lib__fprotect.a  modules/nrf/lib/fatal_error/lib..__nrf__lib__fatal_error.a  modules/mcuboot/boot/bootutil/zephyr/libmcuboot_util.a  modules/mbedtls/libmbedTLSBase.a  modules/mbedtls/libmbedTLSCrypto.a  modules/mbedtls/libmbedTLSX509.a  modules/mbedtls/libmodules__mbedtls.a  modules/hal_nordic/nrfx/libmodules__hal_nordic__nrfx.a  modules/segger/libmodules__segger.a  -Wl,--no-whole-archive  zephyr/kernel/libkernel.a  -L"/opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/thumb/v7e-m/nofp"  -L/Users/mohsin/path-feel-zephyr-fw/app/build_release/mcuboot/zephyr  -lgcc  zephyr/arch/common/libisr_tables.a  modules/mbedtls/libmbedTLSBase.a  modules/mbedtls/libmbedTLSCrypto.a  modules/mbedtls/libmbedTLSX509.a  -mcpu=cortex-m4  -mthumb  -mabi=aapcs  -mfp16-format=ieee  -Wl,--gc-sections  -Wl,--build-id=none  -Wl,--sort-common=descending  -Wl,--sort-section=alignment  -Wl,-u,_OffsetAbsSyms  -Wl,-u,_ConfigAbsSyms  -nostdlib  -static  -Wl,-X  -Wl,-N  -Wl,--orphan-handling=warn  -Wl,-no-pie && cd /Users/mohsin/path-feel-zephyr-fw/app/build_release/mcuboot/zephyr && /opt/nordic/ncs/toolchains/580e4ef81c/Cellar/cmake/3.21.0/bin/cmake -E true
/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: zephyr/drivers/flash/libdrivers__flash.a(spi_nor.c.obj): in function `k_sleep':
/Users/mohsin/path-feel-zephyr-fw/app/build_release/mcuboot/zephyr/include/generated/syscalls/kernel.h:135: undefined reference to `z_impl_k_sleep'
/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: /Users/mohsin/path-feel-zephyr-fw/app/build_release/mcuboot/zephyr/include/generated/syscalls/kernel.h:135: undefined reference to `z_impl_k_sleep'
/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: zephyr/drivers/flash/libdrivers__flash.a(spi_nor.c.obj):(.rodata.spi_nor_config_0+0x0): undefined reference to `__device_dts_ord_105'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

RE: DFU on nrf52832

AHaug — Wed, 22 Jan 2025 08:50:27 GMT

[quote user="Moh"]Any chance to have a live session? Thanks Moh[/quote]

Unfortunately we typically don't do live sessions and when we do they have to be arranged through your regional sales manager.

[quote user="Moh"]If I don't include at25xe321d in overlay, mcuboot builds fine and eventually the app[/quote]

Ok, this is good since we now have isolated that the issue is with configuring the external flash and presumably that everything else works as it should. Could you post the build log with errors for the unsuccessful build with the external flash (for the setup without using CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU)? I still see in the latest 1581.prj_release.conf that you're using this configuration

Kind regards,
Andreas

RE: DFU on nrf52832

Moh — Tue, 21 Jan 2025 16:47:39 GMT

Hi Andreas, If I don't include at25xe321d in overlay, mcuboot builds fine and eventually the app. Any idea why it doesn't like at25xe321d?

/delete-node/ &at25xe321d;

/delete-node/ &i2c0;

/delete-node/ &i2c1;

/ {

chosen {

// nordic,pm-ext-flash = &at25xe321d;

};

RE: DFU on nrf52832

Moh — Tue, 21 Jan 2025 15:27:48 GMT

Hi Andreas, bootloader is not getting build. Getting same above errors. For some reason, it doesn't like SPI. See files attached.

Any chance to have a live session? Thanks Moh

devzone.nordicsemi.com/.../3644.mcuboot.overlay devzone.nordicsemi.com/.../8424.mcuboot.conf

devzone.nordicsemi.com/.../1581.prj_5F00_release.conf

RE: DFU on nrf52832

AHaug — Tue, 21 Jan 2025 14:37:11 GMT

You can stick with 2.6.0, no worries

As mentioned here: "In Zephyr, a set of configurations are needed to enable FOTA. An example of how to set this up can be seen in the SMP Server sample. However, the nRF Connect SDK includes the option CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU, which sets all needed configurations for us. This option makes it easier for us to enable FOTA, so we will use that. This configuration is named CONFIG_NCS_SAMPLE… as it makes some assumptions about the project. For your custom project, I recommend that you look at what configurations CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU set for you, and include the ones from there you need instead."

Meaning that you can have a look at https://docs.nordicsemi.com/bundle/ncs-2.6.1/page/kconfig/index.html#CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU and choose to add the relevant configurations line by line instead of using the "include all NCS_SAMPLE" configuration option which I've done here in the sample I sent you: https://github.com/aHaugl/samples_for_NCS/blob/f2dc920a9edd84dea711febb6f642fcbb3155e55/bootloader/spi/smp_ble_feat_spi/prj.conf.

Kind regards,
Andreas

RE: DFU on nrf52832

Moh — Tue, 21 Jan 2025 14:30:47 GMT

Hi Andreas, thanks for your response. Do I need to move to 2.8.0 ncs or how I can disable QSPI on 2.6.0? Thanks Moh

RE: DFU on nrf52832

AHaug — Tue, 21 Jan 2025 14:28:30 GMT

Aha, of course! (not really, but this is an issue I've ran into when trying to set up the SPI sample I sent you earlier). In NCS 2.6, CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y implies that QSPI should be selected. In other words, no matter how hard you try to disable qspi, it will still be added in if you have CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y, meaning that your sample won't compile for the nRF52832/33

https://docs.nordicsemi.com/bundle/ncs-2.6.1/page/kconfig/index.html#CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU

If I remember correct, this config was changed in 2.8.0 due to the issues this config caused for projects based on a sample that were not going to use SPI

Let me know if this explains things for you

Kind regards,
Andreas

RE: DFU on nrf52832

AHaug — Tue, 21 Jan 2025 14:18:37 GMT

[quote user="Moh"]As far as I understand, nRF52832 doesn't support QSPI. I [/quote]

You're absolutely right. I was mixing up the available peripherals in the nRF52 family socs.

Could you then provide the .config file from the previous failed build with the undefined references to qspi?

Kind regards,
Andreas