WiFi not able to connect due to MCUBOOT

[Aarnav]

Hello,

I am working on a custom board with my own custom project/application. I have recently done porting from ncs v2.7.0 to v3.0.2

- I was able to initialise the wifi driver and get it connected to the given credentials(ssid and password) with Mcuboot for application core in ncs v2.7.0.
- I was able to initialise the wifi driver and get it connected to the given credentials(ssid and password) without enabling Mcuboot in ncs v3.0.2 after porting.

*** But After enabling MCUBOOT for either just app core or for both app & net core, it is not able to connect to the given credentials after driver initialisation being successful. I have followed nordic dev academy for developing my application code. 

Here's the error message from the app core due to which the connection is not happening: 

<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)

I am already late in terms of delivering the product as a department and we need to do make this work ASAP so a sooner reply would be highly appreciated! Refer to the attachments if needed.

Feel free to ask any doubts/questions. Thankyou.

21551.prj.conf1680.nrf5340dk_nrf5340_cpuapp_ns.overlay


 

[Håkon Alseth]

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

[Aarnav]

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

[Håkon Alseth]

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

[Aarnav]

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.

[Håkon Alseth]

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

[Aarnav]

The folder you asked includes the folllowing files:
0652.mcuboot.conf5432.mcuboot.overlay

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

[Håkon Alseth]

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

[Aarnav]

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"?
0066.mcuboot.zip