ERROR: wifi_mgmt_ext: Connection request failed, reason 8

RE: ERROR: wifi_mgmt_ext: Connection request failed, reason 8

Marte Myrvold — Fri, 03 Jan 2025 13:26:12 GMT

Hi,

Can you share how you disconnect and try to connect again?

You mention bringing down the Wi-Fi interface, are you bringing it up again before trying to connect?

Best regards,
Marte

RE: ERROR: wifi_mgmt_ext: Connection request failed, reason 8

Sagar.K — Thu, 19 Dec 2024 10:46:02 GMT

Hello Marte Myrvold,

we are able to make a connection with the router when the device boots up. But, after that we disconnect and bring down the wifi interface, after this if we try to connect to network then we are facing the same error mentioned in the ticket. Can you please suggest a way to troubleshoot this issue.

Thanks.

RE: ERROR: wifi_mgmt_ext: Connection request failed, reason 8

Sagar.K — Fri, 06 Dec 2024 07:39:23 GMT

So, we solved the issue, it turns out that our configuration has CONFIG_POSIX_MAX_FDS=12 which we think is not enough for WiFi+AWS IoT+DNS, we increased this value to 20 and now its working fine.

Thanks.

RE: ERROR: wifi_mgmt_ext: Connection request failed, reason 8

Sagar.K — Fri, 06 Dec 2024 05:27:56 GMT

Yes, we deleted the build directory of v2.5.2 when we built the project for v2.7.0.

We were able to pinpoint the issue to a prj.conf option CONFIG_DNS_RESOLVER.

When this option is enabled we get the above error, and when this option is disabled the wifi works as expected and is able to make a connection to the router.

So, is there any other config options that we might need to enable for dns resolver to work with wifi ?

Thanks.

RE: ERROR: wifi_mgmt_ext: Connection request failed, reason 8

Marte Myrvold — Wed, 04 Dec 2024 14:08:29 GMT

Hi,

Good to hear that you were able to get the sample to work on your custom board.

Did you delete the build directory in your project after migrating from v2.5.2 to v2.7.0? Sometimes, things can be cached even when doing a pristine build, so I would recommend deleting the build directory completely when making changes to devicetree or migrating between SDK versions.

If you want to, you can upload your project so I can investigate it to figure out why it is failing when the STA sample works.

Best regards,
Marte

RE: ERROR: wifi_mgmt_ext: Connection request failed, reason 8

Sagar.K — Wed, 04 Dec 2024 10:38:17 GMT

Ok, so we tested the out of the box sample code for sta and we were able to connect to the router. But still, even though the qspi pins and code is same its not working with our custom board.

RE: ERROR: wifi_mgmt_ext: Connection request failed, reason 8

Sagar.K — Wed, 04 Dec 2024 05:26:02 GMT

We integrated the sample code as it is in our project for testing purpose, and verified that all config option from the sample code is present in our project.

We are getting these logs from bootup.

--- 4 messages dropped ---
[00:00:00.025,360] <dbg> net_mgmt: net_mgmt_event_init: (main): Net MGMT initialized: queue of 5 entries, stack size of 4400
[00:00:00.025,634] <dbg> net_mgmt: net_mgmt_add_event_callback: (main): Adding event callback 0x20016844
[00:00:00.025,665] <dbg> net_mgmt: net_mgmt_add_event_callback: (main): Adding event callback 0x20016830
[00:00:00.026,580] <dbg> wifi_nrf_bus: rpu_gpio_config: GPIO configuration done...

[00:00:00.028,778] <dbg> wifi_nrf_bus: rpu_pwron: Bucken = 0, IOVDD = 0
[00:00:00.028,930] <dbg> wifi_nrf_bus: qspi_nrfx_configure: RDSR 42 QE 1 need 1: no-change
[00:00:00.029,052] <dbg> wifi_nrf_bus: rpu_wrsr2: Written 0x1 to WRSR2
[00:00:00.029,144] <dbg> wifi_nrf_bus: qspi_RDSR2: RDSR2 = 0x1
[00:00:00.029,296] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x0
[00:00:00.029,327] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x0
[00:00:00.030,487] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x0
[00:00:00.030,517] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x0
[00:00:00.031,677] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x0
[00:00:00.034,057] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x2
[00:00:00.034,179] <dbg> wifi_nrf_bus: rpu_clks_on: RPU Clocks ON...
[00:00:00.067,535] <dbg> wifi_nrf_bus: rpu_irq_config: Finished Interrupt config

[00:00:00.067,657] <dbg> wifi_nrf_bus: rpu_wrsr2: Written 0x1 to WRSR2
[00:00:00.067,749] <dbg> wifi_nrf_bus: qspi_RDSR2: RDSR2 = 0x1
[00:00:00.067,840] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x6
[00:00:00.067,840] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x6
[00:00:00.069,030] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x6
[00:00:00.069,030] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x6
[00:00:00.079,589] <dbg> wifi_nrf_bus: rpu_wrsr2: Written 0x1 to WRSR2
[00:00:00.079,681] <dbg> wifi_nrf_bus: qspi_RDSR2: RDSR2 = 0x1
[00:00:00.079,803] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x6
[00:00:00.079,803] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x6
[00:00:00.080,993] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x6
[00:00:00.081,024] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x6
[00:00:00.199,157] <dbg> wifi_nrf_bus: rpu_wrsr2: Written 0x1 to WRSR2
[00:00:00.199,249] <dbg> wifi_nrf_bus: qspi_RDSR2: RDSR2 = 0x1
[00:00:00.199,340] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x6
[00:00:00.199,371] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x6
[00:00:00.200,531] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x6
[00:00:00.200,561] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x6
*** Booting My Application v1.1.15-lte-da6981f16cef ***
*** Using nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
[00:00:00.281,555] <dbg> net_mgmt: net_mgmt_add_event_callback: (main): Adding event callback 0x200149b0
[00:00:00.281,616] <dbg> net_mgmt: net_mgmt_del_event_callback: (main): Deleting event callback 0x200149b0
[00:00:00.282,440] <wrn> usb_device: USB device support already enabled
[00:00:00.283,233] <dbg> wifi_nrf_bus: rpu_wrsr2: Written 0x1 to WRSR2
[00:00:00.283,294] <dbg> wifi_nrf_bus: qspi_RDSR2: RDSR2 = 0x1
[00:00:00.283,386] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x0
[00:00:00.283,386] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x0
[00:00:00.284,576] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x0
[00:00:00.284,576] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x0
[00:00:00.285,736] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x0
[00:00:00.285,766] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x0
[00:00:00.286,895] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x0
[00:00:00.286,926] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x0
[00:00:00.288,055] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x2
[00:00:00.288,085] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x2
[00:00:00.289,215] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x2
[00:00:00.289,245] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x2
[00:00:00.290,069] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x2
[00:00:00.290,100] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x2
[00:00:00.291,076] <dbg> wifi_nrf_bus: qspi_RDSR1: RDSR1 = 0x6
[00:00:00.291,107] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x6
[00:00:00.300,201] <dbg> net_mgmt: net_mgmt_add_event_callback: (wpa_supplicant_wq): Adding event callback 0x20015abc
[00:00:29.039,672] <dbg> net_mgmt: net_mgmt_add_event_callback: (main): Adding event callback 0x20013880
[00:00:29.039,703] <dbg> net_mgmt: net_mgmt_add_event_callback: (main): Adding event callback 0x2001386c
[00:00:29.039,855] <wrn> date_time: getaddrinfo, error: -11
[00:00:29.039,978] <wrn> date_time: getaddrinfo, error: -11
[00:00:29.039,978] <wrn> date_time: Did not get time from any NTP server
[00:00:29.040,008] <inf> network: DATE_TIME_NOT_OBTAINED

[00:00:29.089,996] <err> wifi_mgmt_ext: Connection request failed

[00:00:29.090,026] <inf> apt_wifi: Connection Requested
[00:00:29.090,057] <inf> apt_wifi: -----------------Device MAC address is:00:18:07:00:fc:9d and type is:3-------------------------------

We have used these config options for enabling the logging.

CONFIG_NET_MGMT_EVENT_LOG_LEVEL_DBG=y
CONFIG_WIFI_CREDENTIALS_LOG_LEVEL_DBG=y
CONFIG_WIFI_MGMT_EXT_LOG_LEVEL_DBG=y
CONFIG_NET_L2_WIFI_MGMT_LOG_LEVEL_DBG=y
CONFIG_WIFI_NRF700X_BUS_LOG_LEVEL_DBG=y

RE: ERROR: wifi_mgmt_ext: Connection request failed, reason 8

Marte Myrvold — Tue, 03 Dec 2024 09:13:18 GMT

Hi,

Are you using the sample code out of the box in v2.7.0, or have you made any changes to it?

Error -8 means ENOEXEC. In this case, it suggests that there was a problem executing the Wi-Fi connection request. Since you are using a module and custom board, it could be an issue there.

Please upload the full log from the start of the application. You can upload it using Insert > Code or as a text or log file using Insert > Image/video/file.

Best regards,
Marte

RE: ERROR: wifi_mgmt_ext: Connection request failed, reason 8

Sagar.K — Tue, 03 Dec 2024 04:56:51 GMT

Yes, we are using the same WIFI_CREDENTIALS Kconfig options and our code is same as the sample code provided here ~/ncs/v2.7.0/nrf/samples/wifi/sta.

We are still unsure about what the error code -8 actually means, can you please explain what should we derive from that ?

RE: ERROR: wifi_mgmt_ext: Connection request failed, reason 8

Marte Myrvold — Mon, 02 Dec 2024 13:41:30 GMT

Hi,

Are you setting the credentials using the WIFI_CREDENTIALS Kconfig options?

CONFIG_WIFI_CREDENTIALS=y
CONFIG_WIFI_CREDENTIALS_STATIC=y
CONFIG_WIFI_CREDENTIALS_STATIC_SSID="Myssid"
CONFIG_WIFI_CREDENTIALS_STATIC_PASSWORD="Mypassword"

Can you share the full code where you connect to the network?

Best regards,
Marte