WiFi not able to connect due to MCUBOOT

RE: WiFi not able to connect due to MCUBOOT

Håkon Alseth — Tue, 12 Aug 2025 10:21:59 GMT

Hi,

You can use any other unused GPIO for that purpose.

Kind regards,

Håkon

RE: WiFi not able to connect due to MCUBOOT

Aarnav — Tue, 12 Aug 2025 10:12:20 GMT

Hey Hakon,

After disabling the UART1, I was able to connect to the wifi!
But in the case if I want to do serial DFU through this UART in future, is there any way to do that?

Thanks a lot for your help!

RE: WiFi not able to connect due to MCUBOOT

Håkon Alseth — Tue, 12 Aug 2025 06:49:24 GMT

Hi,

It looks like you have a pin conflict with:

iovdd-ctrl-gpios = <&gpio1 14 (GPIO_ACTIVE_HIGH | GPIO_PULL_DOWN)>;

and uart1:

	uart1_default: uart1_default {
		group1 {
			psels = <NRF_PSEL(UART_TX, 1, 14)>;
		};
		group2 {
			psels = <NRF_PSEL(UART_RX, 1, 15)>;
			bias-pull-up;
		};
	};

Kind regards,

Håkon

RE: WiFi not able to connect due to MCUBOOT

Aarnav — Mon, 11 Aug 2025 15:05:43 GMT

I disabled spi4 and uart0(for which I also set CONFIG_UART_CONSOLE=n in mcuboot.conf) in mcuboot.overlay but still the same error.

I have attached the build/mcuboot folder. Please have a look.
Also out of curiosity, explain what you meant by ths statement: "Without seeing the build artifacts for mcuboot, it is hard to state what is enabled"?
devzone.nordicsemi.com/.../0066.mcuboot.zip

RE: WiFi not able to connect due to MCUBOOT

Håkon Alseth — Mon, 11 Aug 2025 14:43:44 GMT

Without seeing the build artifacts for mcuboot, it is hard to state what is enabled, but I do see that you should explicitly disable these in mcuboot.overlay:

&uart0 { status = "disabled"; };
&spi4 { status = "disabled"; };

If you still have issues, please share the .zip'ed build/mcuboot folder.

Kind regards,

Håkon

RE: WiFi not able to connect due to MCUBOOT

Aarnav — Mon, 11 Aug 2025 14:34:43 GMT

The folder you asked includes the folllowing files:
devzone.nordicsemi.com/.../0652.mcuboot.conf devzone.nordicsemi.com/.../5432.mcuboot.overlay

Also, I had the wifi driver init problem when you suggested me this and it worked. So it is already present.

RE: WiFi not able to connect due to MCUBOOT

Håkon Alseth — Mon, 11 Aug 2025 14:31:20 GMT

Hi,

What does your sysbuild/mcuboot folder include?

Please share these application specific files (if present). There shall be atleast one entry to disable gpio_fwd, due to your CSN pin being P1.05.

Kind regards,

Håkon

RE: WiFi not able to connect due to MCUBOOT

Aarnav — Mon, 11 Aug 2025 14:24:22 GMT

Just these 2 lines are relevant, rest come from my application logic which are as follows:

CONFIG_HEAP_MEM_POOL_SIZE=15600 is set but anyway it gets set to 41440 as

CONFIG_HEAP_MEM_POOL_IGNORE_MIN is set to n.

In the setup without MCUBOOT, I set CONFIG_NET_BUF_FIXED_DATA_SIZE=y and also all the prj.conf including the heap allocation options were exactly same except the mcuboot options.

Definitely I can have it variable if needed but what I meant was that is not an issue in my understanding, let me know if I'm wrong.

RE: WiFi not able to connect due to MCUBOOT

Håkon Alseth — Mon, 11 Aug 2025 14:16:25 GMT

There must be more than these two lines that are printed?

<err> wifi_nrf: nrf_wifi_wpa_supp_scan_abort: nrf_wifi_wpa_supp_scan_abort: Timedout waiting for scan abort response, ret = -11
<err> wifi_interface: wifi_mgmt_event_handler: WIFI connect failed (-116 - Unknown)

In your prj.conf, this is too low:

CONFIG_HEAP_MEM_POOL_SIZE=15600

This should be higher to accommodate for a higher number of returned SSID's. Our samples use around 40k, but you can also adjust CONFIG_NRF_WIFI_SCAN_MAX_BSS_CNT if you want to limit the amount of returned SSID's.

Also, instead of using a fixed size for the net stack (CONFIG_NET_BUF_FIXED_DATA_SIZE=y), you can instead try the option CONFIG_NET_BUF_VARIABLE_DATA_SIZE, which will help you if you're running out of RAM.

Kind regards,

Håkon

RE: WiFi not able to connect due to MCUBOOT

Aarnav — Mon, 11 Aug 2025 13:53:07 GMT

Hey Hakon,

This is all I have wrt the logs. Let me know if you need any specific info.
Also I tried what you said and still facing the same error 😞

RE: WiFi not able to connect due to MCUBOOT

Håkon Alseth — Mon, 11 Aug 2025 13:36:52 GMT

Hi,

Can you please share your full log?

These should be present in your configuration to ensure that TFM logging is disabled:

https://github.com/NordicDeveloperAcademy/wifi-fund/blob/main/l5/l5_e1_sol/boards/nrf7002dk_nrf5340_cpuapp_ns.conf#L1-L3

Kind regards,

Håkon