Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

Håkon Alseth — Thu, 27 Jun 2024 14:00:43 GMT

Hi,

Start with a stock bluetooth example (for instance peripheral_lbs), and see if this works.

I'm out of the office until August, so I suggest to create a new case if you still run into any issues.

Kind regards,

Håkon

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

wadn — Thu, 27 Jun 2024 11:00:16 GMT

Thank you for your patience with this issue. I have since tried to switch to bluetooth firmware on my board and ran into another issue. Since I am not sure if maybe these issues are connected I am posting this here:

I have also found another post which displays the same issues I had using WiFi.

Regards

wadn

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

Håkon Alseth — Tue, 25 Jun 2024 14:07:08 GMT

Hi,

There is something wrong with the pinout / setup of your custom board.

If you have done any modifications in your hardware, please revert these. I would recommend that you open up a separate case to review your hardware and layout.

Kind regards,

Håkon

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

wadn — Tue, 25 Jun 2024 12:16:37 GMT

I forgot to put something in the proj.conf file. Now I get this print:

But I am still not able to issue any commands.

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

Håkon Alseth — Tue, 25 Jun 2024 11:54:03 GMT

there should be either this boot print:

00> *** Booting nRF Connect SDK v3.5.99-ncs1-1 ***

or a "rtt" prompt:

00> rtt:~$ rtt:~$

Could you try disconnecting and reconnecting in the JLink RTT viewer? F3 for disconnect and F2 for connect.

Kind regards,

Håkon

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

wadn — Tue, 25 Jun 2024 09:28:41 GMT

No there are no prints:

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

Håkon Alseth — Tue, 25 Jun 2024 09:13:59 GMT

Hi,

Try setting:

CONFIG_LOG_BACKEND_RTT_BUFFER=0
CONFIG_SHELL_BACKEND_RTT_BUFFER=1

This will make the logs come up on the first terminal.

Is there any prints?

Kind regards,

Håkon

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

wadn — Tue, 25 Jun 2024 08:49:46 GMT

I cannot send the command that way, it automatically cuts off the last part

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

Håkon Alseth — Tue, 25 Jun 2024 08:38:48 GMT

Hi,

There should be prints in your RTT Viewer, and you should be able to issue commands. Please note that you may have to change this setting:

Kind regards,

Håkon

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

wadn — Tue, 25 Jun 2024 08:27:15 GMT

I'm not sure if I understand correctly, do I have to issue this command via the RTT viewer, or some terminal?

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

Håkon Alseth — Mon, 24 Jun 2024 12:40:21 GMT

This means that there's a hardware-wise setup issue.

Could you try to run the nrf/samples/wifi/radio_test and issue "wifi_radio_ficr_prog otp_read_params" ?

You need to switch the shell backend to rtt and disable uart:

# RTT backends
CONFIG_RTT_CONSOLE=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_SHELL_BACKEND_RTT=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_RTT_BUFFER=1
CONFIG_SEGGER_RTT_MODE_NO_BLOCK_SKIP=y

# UART backends
CONFIG_UART_CONSOLE=n
CONFIG_LOG_BACKEND_UART=n
CONFIG_SHELL_BACKEND_SERIAL=n

You will likely have to open up the nRF700x OTP area, as given in step 1 here:

https://docs.nordicsemi.com/bundle/nan_043/page/APP/nan_043/otp_programming.html

ie. issue only this line, then reboot afterwards before issuing any other commands (for instance writing the MAC address):

wifi_radio_ficr_prog otp_write_params 0x100 0x50FA50FA

PS: Do not lock the device unless you really want to do that.

Kind regards,

Håkon

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

wadn — Mon, 24 Jun 2024 11:04:52 GMT

This is what I got from the RTT Viewer:

00> [00:00:00.565,490] <err> wifi_nrf_bus: RDSR failed: -16
00> [00:00:00.565,551] <err> wifi_nrf: zep_shim_bus_qspi_dev_add: QSPI device init failed
00> [00:00:00.565,612] <err> wifi_nrf: nrf_wifi_bus_qspi_dev_add: nrf_wifi_osal_bus_qspi_dev_add failed
00> [00:00:00.565,673] <err> wifi_nrf: nrf_wifi_bal_dev_add: Bus dev_add failed
00> [00:00:00.565,734] <err> wifi_nrf: nrf_wifi_hal_dev_add: nrf_wifi_bal_dev_add failed
00> [00:00:00.565,826] <err> wifi_nrf: nrf_wifi_fmac_dev_add: nrf_wifi_hal_dev_add failed
00> [00:00:00.565,856] <err> wifi_nrf: nrf_wifi_fmac_dev_add_zep: nrf_wifi_fmac_dev_add failed
00> [00:00:00.565,856] <err> wifi_nrf: nrf_wifi_if_start_zep: nrf_wifi_fmac_dev_add_zep failed
00> *** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
00> [00:00:01.567,382] <inf> Lesson6_Exercise1: Connecting to Wi-Fi
00> [00:00:01.567,413] <err> Lesson6_Exercise1: Connecting to Wi-Fi failed, err: -134

seems to be something wrong with the QSPI connection if I understand correctly.

Regards

wadn

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

Håkon Alseth — Mon, 24 Jun 2024 09:05:17 GMT

Hi,

Can you please use JLink RTT for log output and share what is printed?

Add this to your prj.conf and use JLink RTT Viewer to see the traces after flashing:

# RTT backends
CONFIG_RTT_CONSOLE=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_SEGGER_RTT_MODE_NO_BLOCK_SKIP=y

# UART backends
CONFIG_UART_CONSOLE=n
CONFIG_LOG_BACKEND_UART=n

Kind regards,

Håkon

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

wadn — Fri, 21 Jun 2024 07:16:14 GMT

Hi Håkon

Sorry for the late response, I assembled a second board aswell as resoldered the nRF5340 on the first one. Now on both of them BUCKEN and IOVDD_EN are set and the timing seems to be good aswell:

VBAT in blue is enabled more than 6ms before BUCKEN in purple and after a little more than 1ms IOVDD is enabled.

Still when I run my code I get error -134 on the net_mgmt function.

Regards

wadn

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

Håkon Alseth — Thu, 20 Jun 2024 10:46:11 GMT

Hi,

Q1: Can you scope your pins using a logic analyzer to see how the boot-up sequence is applied?

And please share how it looks from reset

Q2: Can you try with a stock sample, like wifi/scan or wifi/sta to see if they behave the same?

Q3: Can you try with another of your custom boards, to see if the issue is local to one board or if this is a generic problem on all boards that you've manufacturered?

Kind regards,

Håkon

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

wadn — Thu, 20 Jun 2024 09:25:34 GMT

Hi Håkon

When i change the pin in the devicetree from high active to low active I get a signal, which means the connection should be fine. This would then mean the MCU is not setting the pin active for some reason.

Regards

wadn

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

Håkon Alseth — Wed, 19 Jun 2024 13:44:25 GMT

Hi wadn,

[quote user="wadn"]This is the squencing according to the datasheet of the 7002. When I measure my control signals (BUCKEN and IOVDD_EN) they are both low. Do I have to set those manually or should they be set automatically at startup? I thought they are set automatically because in the devicetree they are defined as qspi signals and not output pins.[/quote]

This indicates that there's a mechanical issue with your design. These should be set high.

Kind regards,

Håkon

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

wadn — Wed, 19 Jun 2024 13:13:25 GMT

Thanks for the tip, unfortunately I only have the one board that I am working with. I had another look at all the connections between the 5340 and the 7002 and I think you are right that it does not boot up correctly.

This is the squencing according to the datasheet of the 7002. When I measure my control signals (BUCKEN and IOVDD_EN) they are both low. Do I have to set those manually or should they be set automatically at startup? I thought they are set automatically because in the devicetree they are defined as qspi signals and not output pins.

Regards

wadn

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

Håkon Alseth — Wed, 19 Jun 2024 09:03:57 GMT

Hi,

My guess is that you're having issues booting up the nRF700x properly.

If you have more than one custom board, I would recommend that you test those as well, to see if they exhibit the same behavior.

Has your custom design been reviewed by us previously? If not, could you open up a private ticket and request a review (gerber files / altium files + schematic) ?

Kind regards,

Håkon

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

wadn — Wed, 19 Jun 2024 06:58:43 GMT

Thanks for the reply,

Unfortunately I am not able to output any logs because I dont have a UART interface. The error code I was able to catch through the debugger
The connections are not all the same, since I needed P0.28 for analog inputs. These are the connections that differ: REQ -> P0.29 (instead of P0.28), STATUS1 -> P1.08 (instead of P0.29). The vdd7002 label you mention is connected to a load switch which enables the VBAT voltage. However, right now I am bypassing the load swich so that the nRF7002 is permanently supplied. That is why this label is commented out.
I have tried running the WiFI fundamentals course Lesson 2 exercise 2 code (without the shell part) since that does exactly what I need, but I get the same error. I was using the same overlay file as attached in the first post.

Regards

wadn

RE: Error -134 when trying to connect to WiFi using net_mgmt with static credentials on custom board

Håkon Alseth — Tue, 18 Jun 2024 14:24:47 GMT

Hi,

[quote user=""]I am working on a WiFi application using a custom board equipped with both the nRF5340 aswell as the nRF7002. When requesting a WiFi connection using the net_mgmt function and static credentials I get the errorcode -134 (ENOTSUP).[/quote]

Q1: Could you share the full log from boot-up?

Q2: Do you have the exact same connections as the nRF7002-DK?

Your "vdd7002" label in DT seems to indicate that you're using P0.10 to power up the nRF7002?

Q3: Does a stock samples/wifi/sta or scan work as intended on your custom board?

Kind regards,

Håkon