Problems using nRF7002 with non-nRF MCU

RE: Problems using nRF7002 with non-nRF MCU

Marte Myrvold — Wed, 23 Oct 2024 09:56:57 GMT

Hi,

Thanks for the update. It is great to hear that it is working now!

Best regards,
Marte

RE: Problems using nRF7002 with non-nRF MCU

djgj — Tue, 22 Oct 2024 14:02:31 GMT

Hello Marte,
Apologies for the late reply. We were able to run nRF7002 in our actual board and we don't see this specific issue there. I assume there is some powering/wiring issue when i was working with devkits. Also i used latest changes in zephyr to test these again. So probably one or the other fixed the issue for us.

Regards,

djgj

RE: Problems using nRF7002 with non-nRF MCU

Marte Myrvold — Mon, 21 Oct 2024 07:50:05 GMT

Hi.

Have you been able to test with the new boards you received and collect logs?

Best regards,
Marte

RE: Problems using nRF7002 with non-nRF MCU

djgj — Mon, 23 Sep 2024 09:47:57 GMT

Hi Marte,
Thanks for the follow up.

Yes i am still experiencing issues on this. I was so far testing on devkits.
To rule out any setup issues I will test it on our actual boards which arrived last week.
I tried changing the clock speeds too but it didn't too much.

I will capture the logs accordingly and will keep you posted on it soon by today or tomorrow..

Regards,

djgj

RE: Problems using nRF7002 with non-nRF MCU

Marte Myrvold — Mon, 23 Sep 2024 08:58:53 GMT

Hi,

Are you still experiencing the issues in this ticket? If so, do you have an update on the questions in my previous reply?

Best regards,
Marte

RE: Problems using nRF7002 with non-nRF MCU

Marte Myrvold — Wed, 11 Sep 2024 12:50:40 GMT

Hi,

[quote user="djgj"]I will verify the SPI frequency and voltage values on BUCKEN, IOVDD, and VBAT and confirm on it soon.[/quote]

Do you have any updates on this?

What is the clock frequency of the host (RT595) that you are using? It seems to be pretty high. Can you clock it to 128 MHz, the same as the nRF5340, and collect the same logs as previously?

Best regards,
Marte

RE: Problems using nRF7002 with non-nRF MCU

Marte Myrvold — Fri, 06 Sep 2024 12:59:45 GMT

Hi,

I have not received a response yet but have asked for an update. I expect to hear something early next week.

Best regards,
Marte

RE: Problems using nRF7002 with non-nRF MCU

Marte Myrvold — Thu, 05 Sep 2024 08:33:00 GMT

Hi,

Thank you for providing additional debug information. I forwarded it internally and am waiting for a reply. If I have not heard anything by tomorrow, I will ask them for an update and get back to you.

Best regards,
Marte

RE: Problems using nRF7002 with non-nRF MCU

djgj — Mon, 02 Sep 2024 16:05:12 GMT

Hello Marte,
I have attached the salea logic analyser logs in this reply.
I have compared the init sequence of nRF7002 with nRF53 and RT595 devkits.

nRF7002 with RT595 EVK

nRF7002 with nRF5340 DK

* I do see some difference in the way init sequence is happening on RT500 compared to nRF53.
Do you think this can cause issue within that power cycle with nRF7002?

* Also once nRF7002 goes into error state what is the recommended to bring it back to proper state?
I noticed that once i use nRF7002 with nRF53 devkit and then switch to RT500 normally i don't see invalid addresses for sometime. But once the nRF7002 starts giving invalid address errors (for some reason like improper connections or init sequences) it continues on. I think there can be a link somewhere here.

I will verify the SPI frequency and voltage values on BUCKEN, IOVDD, and VBAT and confirm on it soon.

Additional Info/Question:

* I also added some log messages in the spi_if.c file to compare and see for any SPI errors between nRF53 and RT500.
https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/wifi/nrfwifi/src/qspi/src/spi_if.c#L29-L77

But however i don't see any of the bytes probed on nRF7002 SPI lines (via logic analyser) with those printed on spi_if driver logs

The data compared here is from nRF7002 driver itself which does some checking/sending a message every 10 seconds after just initialization (no other wifi commands issued and I did not add anything code for this here except those log messages on spim_xfer_rx/tx functions)

Technically it is just writing and reading to same nRF7002 registers every 10 seconds. But the bytes seen in SPI lines are different every time. This behavior is seen on both RT500 and nRF5340 setup too. I would like know how to debug these message bytes so that i can know what kind of SPI error could be happening?

Regarding Host setup:

We are using NXP MIMXRT595-EVK as our Host MCU board and nRF7002 EK.
We are using devkits to verify this Wi-Fi interfacing path with nRF7002EK.

I was not able to use the full Arduino shield interface on RT595 EVK board since
their "arduino_spi" interface was not available out of the box for using on RT500

Instead, I connected nRF7002 EK pins partially to "Arduino" and "HS_SPI_1" pins on the RT595 EVK board.
(reference chapter 9 https://www.farnell.com/datasheets/3209290.pdf)

NRF7002 EK	RT5959 EVK
V5V	J29 - pin 5
GND	J29 - pin 6
VIO	J29 - pin 4
HOST_IRQ	J27 - pin 8
BUCK_EN	J27 - pin 2
IOVDD_EN	J27 - pin 1
SS	HS_SPI_1 - JP26 - pin 1
MOSI	HS_SPI_1 - JP26 - pin 2
MISO	HS_SPI_1 - JP26 - pin 3
CLK	HS_SPI_1 - JP26 - pin 4

And on the software side we are using latest zephyr containing Nordic updates on nRF7002.
App: https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/net/wifi

I made a small change on nrf7002ek.overlay to be able to use setup without too much custom changes.

Thanks,

djgj

RE: Problems using nRF7002 with non-nRF MCU

Marte Myrvold — Mon, 02 Sep 2024 09:40:46 GMT

Hi,

The team has suggested some things you can do to debug the issue.

Measure the SPI clock while running the SPI at 2MHz or 1MHz to validate the frequency.
Measure the BUCKEN, IOVDD, and VBAT supplied to the nRF70.
Probe IOVDD and BUCKEN with an oscilloscope during boot to check the power sequencing.

The power-up sequencing requirements are as follows:

Supply VBAT/BUCKVBAT/BUCKVBATS/AFEVBAT
Wait ≥ 6 ms
Assert BUCKEN
Wait ≥ 1 ms
Supply IOVDD

You can read more about this in supply sequencing requirements.

Please share the results of these tests.

It would also be helpful if you could share the hardware schematics of your host interface.

Best regards,
Marte

RE: Problems using nRF7002 with non-nRF MCU

Marte Myrvold — Fri, 30 Aug 2024 12:59:16 GMT

Hi,

I have forwarded this internally and will get back to you early next week.

Best regards,
Marte

RE: Problems using nRF7002 with non-nRF MCU

djgj — Wed, 28 Aug 2024 08:29:27 GMT

Hi Marte,

Issue about wake up is better when i disable CONFIG_NRF_WIFI_LOW_POWER. However i still see those invalid memory addresses most often along with other issues like timeouts. Overall the connection/interface is not stable enough to do any networking task.

I tried to debug by connecting logic analyzer to SPI lines. However i do not know what each bytes represent to check anything meaningful.

Are these memory addresses transferred via SPI line to host? i could not see them in my logs?
Could you help me debug this issue and to what to look for in those analyzer logs?

How to prove it is an issue on either host MCU side or nRF7002? on the host side we have also verified that SPI lines are working and stable. Only in combination with nRF7002 we face this issue.

Regards,

djgj

RE: Problems using nRF7002 with non-nRF MCU

Marte Myrvold — Wed, 28 Aug 2024 07:10:44 GMT

Hi,

Can you try disabling low power mode to debug the issue? You can do this by setting CONFIG_NRF_WIFI_LOW_POWER in prj.conf or adding it as a flag when building (-- -DCONFIG_NRF_WIFI_LOW_POWER=n).

Best regards,
Marte

RE: Problems using nRF7002 with non-nRF MCU

djgj — Tue, 27 Aug 2024 15:51:26 GMT

Thank you Marte,

I also noticed that when i leave the setup for more than 5 minutes and try wifi scan command again. then nrf7002 kind of goes to off/low power mode and it does not wake up.

Is this also known issue? should i disable/enable something?

Regards,

djgj

RE: Problems using nRF7002 with non-nRF MCU

Marte Myrvold — Tue, 27 Aug 2024 09:26:29 GMT

Hi,

Thank you for clarifying and providing the files. I have forwarded it internally and will get back to you by the end of the week.

Best regards,
Marte

RE: Problems using nRF7002 with non-nRF MCU

djgj — Mon, 26 Aug 2024 11:00:15 GMT

Hi Marte,

Thank you for the response.
I will try to debug from SPI transfer corruption aspect.
I currently running at 8 MHZ, however i tried at 1, 2 MHz too without much success.

I meant with 50% failing is during single boot itself. if i issue the `wifi scan` shell command, it passes around 50% time roughly. but i do keep seeing these invalid addresses always.

I have also attached the requested files.

devzone.nordicsemi.com/.../1856.logs.zip

regards,

djgj

RE: Problems using nRF7002 with non-nRF MCU

Marte Myrvold — Mon, 26 Aug 2024 07:35:20 GMT

Hi,

The Wi-Fi team does not believe the issue is relevant to https://github.com/nrfconnect/sdk-nrfxlib/blame/main/nrf_wifi/hw_if/hal/src/hal_interrupt.c#L437.

The Invalid memory addresses from the logs seem to be random addresses, which would suggest SPI read corruption. This could indicate SPI connection issues.

What SPI frequency are you using? Would it be possible to try with lower SPI frequencies, such as 2 MHz or even 1 MHz?

Please also specify what you mean by the commands failing 50% of the time. Do the commands both succeed and fail during a single boot or do they succeed during some boots and fail during other boots?

Please also provide logs during the boot, as well as .config and zephyr.dts from the build folder.

Best regards,
Marte

RE: Problems using nRF7002 with non-nRF MCU

Marte Myrvold — Fri, 23 Aug 2024 12:25:17 GMT

Hi,

I have forwarded this issue internally and will get back to you early next week.

Best regards,
Marte

RE: Problems using nRF7002 with non-nRF MCU

djgj — Thu, 22 Aug 2024 08:15:56 GMT

Hello,
I didn't see this issue when i tried the same sample with nRF5340 DK and nRF7002 EK.

do you know on what conditions this might be triggered?
https://github.com/nrfconnect/sdk-nrfxlib/blame/main/nrf_wifi/hw_if/hal/src/hal_interrupt.c#L437

What connection should i ensure so that nRF7002 does not give wrong addresses?

Regards,
djgj

RE: Problems using nRF7002 with non-nRF MCU

Marte Myrvold — Wed, 21 Aug 2024 13:54:32 GMT

Hi,

Do you have a Nordic DK that you can use as the host MCU to verify whether the issue is caused by using a non-nRF MCU as the host or by an issue with the nRF7002 drivers in upstream Zephyr?

Best regards,
Marte

RE: Problems using nRF7002 with non-nRF MCU

djgj — Wed, 21 Aug 2024 08:58:05 GMT

Hi Runar,

We are using RT500 MCU (NXP) as our host MCU. I connected our host MCU with nRF7002 EK via SPI connection.

I am running the basic WiFi shell application on zephyr:

https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/net/wifi

All other configs are same as used with nRF5340 except the SPI interface part.

While debugging i also noticed this comment which can be related to my issue.
https://github.com/nrfconnect/sdk-nrfxlib/blame/main/nrf_wifi/hw_if/hal/src/hal_interrupt.c#L437

Do you know what this is about and how to mitigate this?

kindly let me know if you need more details.

Regards,

djgj

RE: Problems using nRF7002 with non-nRF MCU

runsiv — Wed, 21 Aug 2024 07:48:49 GMT

Hi Djgj

Could you give a bit more information regarding your system? As we can't test for all devices, the test level will be lower on non Nordic hosts. Due to this, there might be compatibility issues with helper libraries, such as the download library.

Regards

Runar