[nRF7002EK] Unable to read mac address

RE: [nRF7002EK] Unable to read mac address

Elfving — Wed, 19 Feb 2025 11:55:47 GMT

So when you do not have the EK shield connected to the DK, what results do you get then for QSPI and SPI?

Btw, I hear that your local RSM is trying to contact you. Please get in touch with him, as he might be able to help you further.

Regards,

Elfving

RE: [nRF7002EK] Unable to read mac address

Sagar.K — Mon, 17 Feb 2025 13:49:41 GMT

I tried connecting the nrf7002ek as mentioned in this article here. But still facing the above issue of qspi interface.

[quote userid="103347" url="~/f/nordic-q-a/118639/nrf7002ek-unable-to-read-mac-address/523067"]How are you enabling SPI and QSPI here? [/quote]

I am changing the SPI config to QSPI config in nrf7002ek shield configuration.

[quote userid="103347" url="~/f/nordic-q-a/118639/nrf7002ek-unable-to-read-mac-address/523067"]what do you get the same results when using the EK shield in the build?[/quote]

No. for ek shield it is working fine.

Thank you.

RE: [nRF7002EK] Unable to read mac address

Elfving — Fri, 14 Feb 2025 14:09:28 GMT

REGION.PROTECT0 = 0x50fa50fa is what I was expecting.

Looks to me like you are targeting the two different nRF7s when using the QSPI interface vs when using the SPI one. How are you enabling SPI and QSPI here? And what do you get the same results when using the EK shield in the build?

Regards,

ELfving

RE: [nRF7002EK] Unable to read mac address

Sagar.K — Wed, 12 Feb 2025 09:21:44 GMT

Getting below Reading for QSPI interface :

[00:00:00.337,829] <dbg> wifi_nrf_bus: qspi_wait_while_rpu_awake: RDSR1 = 0x6
[00:00:00.339,691] <inf> wifi_nrf: nrf_wifi_fmac_otp_mac_addr_get: MAC addr not programmed in OTP
[00:00:00.339,752] <err> wifi_nrf: nrf_wifi_get_mac_addr: Invalid MAC address: 00:00:00:00:00:00
[00:00:00.339,752] <err> wifi_nrf: nrf_wifi_if_start_zep: Failed to get MAC address
[00:00:00.339,843] <dbg> wifi_nrf_bus: qspi_deinit: TODO : qspi_deinit

uart:~$ wifi_radio_ficr_prog otp_read_params
OTP Region is unprogrammed - program to enable R/W

PRODTEST.FT.PROGVERSION = 0xff0300ff

PRODTEST.TRIM0 = 0xffffffff
PRODTEST.TRIM1 = 0x0009d40b
PRODTEST.TRIM2 = 0x0009d80b
PRODTEST.TRIM3 = 0xffffffff
PRODTEST.TRIM4 = 0xffffffff
PRODTEST.TRIM5 = 0xffffffff
PRODTEST.TRIM6 = 0xffffffff
PRODTEST.TRIM7 = 0xffffffff
PRODTEST.TRIM8 = 0xffffffff
PRODTEST.TRIM9 = 0xffffffff
PRODTEST.TRIM10 = 0xffffffff
PRODTEST.TRIM11 = 0xffffffff
PRODTEST.TRIM12 = 0xffffffff
PRODTEST.TRIM13 = 0xffffffff
PRODTEST.TRIM14 = 0xffffffff

INFO.PART = 0x00007002
INFO.VARIANT = 0x00423030

INFO.UUID0 = 0x433ffe78
INFO.UUID1 = 0x11edcb69
INFO.UUID2 = 0x2eb304cc
INFO.UUID3 = 0x258a4998

REGION.PROTECT0 = 0xffffffff
REGION.PROTECT1 = 0xffffffff
REGION.PROTECT2 = 0xffffffff
REGION.PROTECT3 = 0xffffffff


uart:~$ wifi_radio_ficr_prog otp_get_status
Checking OTP PROTECT Region......
OTP Region is unprogrammed - program to enable R/W

QSPI Keys are not programmed in OTP
MAC0 Address is programmed in OTP
MAC1 Address is programmed in OTP
CALIB_XO is programmed in OTP

Getting below Reading for SPI interface :

uart:~$ wifi_radio_ficr_prog otp_get_status
Checking OTP PROTECT Region......
OTP Region is open for R/W

QSPI Keys are not programmed in OTP
MAC0 Address is programmed in OTP
MAC1 Address is programmed in OTP
CALIB_XO is programmed in OTP

uart:~$ wifi_radio_ficr_prog otp_read_params
OTP Region is open for R/W

PRODTEST.FT.PROGVERSION = 0xff0300ff

PRODTEST.TRIM0 = 0x0009040f
PRODTEST.TRIM1 = 0x0009d40b
PRODTEST.TRIM2 = 0x0009d80b
PRODTEST.TRIM3 = 0x000f040c
PRODTEST.TRIM4 = 0x000fd408
PRODTEST.TRIM5 = 0x000fd808
PRODTEST.TRIM6 = 0xffffffff
PRODTEST.TRIM7 = 0xffffffff
PRODTEST.TRIM8 = 0xffffffff
PRODTEST.TRIM9 = 0xffffffff
PRODTEST.TRIM10 = 0xffffffff
PRODTEST.TRIM11 = 0xffffffff
PRODTEST.TRIM12 = 0xffffffff
PRODTEST.TRIM13 = 0xffffffff
PRODTEST.TRIM14 = 0xffffffff

INFO.PART = 0x00007002
INFO.VARIANT = 0x00423030

INFO.UUID0 = 0x433ffe78
INFO.UUID1 = 0x11edcb69
INFO.UUID2 = 0x2eb304cc
INFO.UUID3 = 0x258a4998

REGION.PROTECT0 = 0x50fa50fa
REGION.PROTECT1 = 0x50fa50fa
REGION.PROTECT2 = 0x50fa50fa
REGION.PROTECT3 = 0x50fa50fa

MAC0.ADDRESS0 = 0x0036cef4
MAC0.ADDRESS1 = 0x00004950
MAC0.ADDRESS = f4:ce:36:00:50:49

MAC1.ADDRESS0 = 0x0036cef4
MAC1.ADDRESS1 = 0x00004a50
MAC1.ADDRESS = f4:ce:36:00:50:4a

CALIB.XO = 0x29
REGION_DEFAULTS = 0xfffffff1

Not sure why we are seeing this behaviour ? any insights.

RE: [nRF7002EK] Unable to read mac address

Elfving — Tue, 11 Feb 2025 14:04:30 GMT

[quote user="Sagar.K"]

So the issue is with the OTP memory which is present on nRF7002 module.

So if we replace the nRF7002 module present on nRF7002EK will it resolve the issue ?

[/quote]

Yes, that is correct. Though if you take an nRF7 from a reel to replace the one on the EK, then you would also have to write to the OTP of that and set a few values that comes pre-set on EKs and DKs. Could you try running this first?

wifi_radio_ficr_prog otp_get_status

Regards,
Elfving

RE: [nRF7002EK] Unable to read mac address

Sagar.K — Tue, 11 Feb 2025 07:03:20 GMT

Hello,

So the issue is with the OTP memory which is present on nRF7002 module.

So if we replace the nRF7002 module present on nRF7002EK will it resolve the issue ?

Thanks.

RE: [nRF7002EK] Unable to read mac address

Elfving — Mon, 10 Feb 2025 13:44:48 GMT

[quote user="Sagar.K"]

No, we are not using two nRF7s. We are just using the nRF5340DK and nRF7002EK, these two are interfaced over QSPI interface. We are using nrf7002dk_nrf5340_cpuapp board config for build purpose only as it has support for nRF7002 interfacing over QSPI by default. we didn't use the nRF7002EK as a shield argument because it is configured to use SPI interface for nRF7002.

[/quote]

I guess as long as it works it is fine. Though using the EK as a shield, and then connecting it like this is the recommended way when using QSPI.

[quote user="Sagar.K"]

Providing the output below :

[/quote]

Looks like there is something wrong with the OTP, like you show in the OP it is supposed to be 0x50FA50FA. I guess ESD could be the issue, as I don't see what else could have caused this.

Regards,

Elfving

RE: [nRF7002EK] Unable to read mac address

Sagar.K — Fri, 07 Feb 2025 11:29:10 GMT

[quote userid="103347" url="~/f/nordic-q-a/118639/nrf7002ek-unable-to-read-mac-address/521869"]While I am not sure that would work, why not rather use the nRF7002 on the nRF7002Dk? That one is connected over QSPI.[/quote]

we don't have an nRF7002DK as of now, so we are using the mentioned approach and it is working without any issues.

[quote userid="103347" url="~/f/nordic-q-a/118639/nrf7002ek-unable-to-read-mac-address/521869"]Can you give me the output when trying to read the OTP, not write to it?[/quote]

Providing the output below :

uart:~$ wifi_radio_ficr_prog otp_read_params
OTP Region is in invalid state

PRODTEST.FT.PROGVERSION = 0xff0300ff

PRODTEST.TRIM0 = 0x090d0009
PRODTEST.TRIM1 = 0x0009d40b
PRODTEST.TRIM2 = 0x0009d80b
PRODTEST.TRIM3 = 0x040c0904
PRODTEST.TRIM4 = 0xd40809d4
PRODTEST.TRIM5 = 0xd80809d8
PRODTEST.TRIM6 = 0xffffffff
PRODTEST.TRIM7 = 0xffffffff
PRODTEST.TRIM8 = 0xffffffff
PRODTEST.TRIM9 = 0xffffffff
PRODTEST.TRIM10 = 0xffffffff
PRODTEST.TRIM11 = 0xffffffff
PRODTEST.TRIM12 = 0xffffffff
PRODTEST.TRIM13 = 0xffffffff
PRODTEST.TRIM14 = 0xffffffff

INFO.PART = 0x00007002
INFO.VARIANT = 0x00423030

INFO.UUID0 = 0x78f4e38f
INFO.UUID1 = 0x11edcb69
INFO.UUID2 = 0x2eb304cc
INFO.UUID3 = 0x258a4998

REGION.PROTECT0 = 0x50099550
REGION.PROTECT1 = 0x50099550
REGION.PROTECT2 = 0x50099550
REGION.PROTECT3 = 0x50099550

MAC0.ADDRESS0 = 0xe30d60e3
MAC0.ADDRESS1 = 0x00004950
MAC0.ADDRESS = e3:60:0d:e3:50:49

MAC1.ADDRESS0 = 0xe30d60e3
MAC1.ADDRESS1 = 0x00004a50
MAC1.ADDRESS = e3:60:0d:e3:50:4a

CALIB.XO = 0x29
REGION_DEFAULTS = 0xfffffff1

Thank you.

RE: [nRF7002EK] Unable to read mac address

Elfving — Fri, 07 Feb 2025 08:45:41 GMT

[quote user="Sagar.K"]is it possible that an ESD charge might create this type of issue ?[/quote]

I have never heard of that happening atleast.

[quote user="Sagar.K"]

[/quote]

While I am not sure that would work, why not rather use the nRF7002 on the nRF7002Dk? That one is connected over QSPI.

[quote user="Sagar.K"]

Hope this will clear the confusion. Now, coming to the main question. Is there a way to recover from this state ?

[/quote]

Can you give me the output when trying to read the OTP, not write to it?

Regards,

Elfving

RE: [nRF7002EK] Unable to read mac address

Sagar.K — Thu, 06 Feb 2025 13:32:40 GMT

Hello Elfving

[quote userid="103347" url="~/f/nordic-q-a/118639/nrf7002ek-unable-to-read-mac-address/521719"]But I am also a bit confused as to how you ran into this issue if the EK module used to run well. Did you try writing to the OTP? [/quote]

No. We didn't try writing to the OTP memory When it was working. We are also not quite sure, why we ran into this issue. is it possible that an ESD charge might create this type of issue ?

[quote userid="103347" url="~/f/nordic-q-a/118639/nrf7002ek-unable-to-read-mac-address/521719"]Any reason why you are using the two nRF7s?[/quote]

Hope this will clear the confusion. Now, coming to the main question. Is there a way to recover from this state ?

Thank you.

RE: [nRF7002EK] Unable to read mac address

Elfving — Thu, 06 Feb 2025 12:40:22 GMT

Hi Sagar,

[quote user=""]

So, is there a way we can replace only the OTP memory on the nRF7002EK, as it will be a suitable alternative for us rather than replacing the while module. If yes, can you please suggest a part no of the module.

[/quote]

I might be misunderstanding you here, but the OTP memory is not another IC on the nRF7002EK - it is in the nRF7002.

But I am also a bit confused as to how you ran into this issue if the EK module used to run well. Did you try writing to the OTP? The OTP should be already written to on the EKs, there is no need to write to it again.

Another thing that could add to the confusion here is that you are running an nRF7002EK along with an nRF7002DK. That should be possible of course, though I guess it might be possible that you are using the nRF7 on the DK instead of on the EK without you being aware of it. Any reason why you are using the two nRF7s?

Regards,

Elfving