Setting nrf700x-coex ble-WiFi brings error

RE: Setting nrf700x-coex ble-WiFi brings error

sguitton01 — Thu, 01 Feb 2024 10:11:19 GMT

Hi Simon, I think that's it, thank you,

Sylvian

RE: Setting nrf700x-coex ble-WiFi brings error

Simonr — Thu, 01 Feb 2024 08:46:44 GMT

Hi Sylvain

Okay, but I don't see that you've also done step 4 where you need to apply the same devicetree nodes to the network core as well as the application core. Can you please confirm you've done that as well?

Best regards,

Simon

RE: Setting nrf700x-coex ble-WiFi brings error

sguitton01 — Wed, 31 Jan 2024 13:41:50 GMT

Hi Simon,

Yes I am able to run the projects without this config though I added these config accroding to this:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/device_guides/wifi_coex.html#ug-radio-coex

Because as I will use WiFi and BLE I want tothem to be able to work at the same time and avoid interference, ...

Best regards,

Sylvain

RE: Setting nrf700x-coex ble-WiFi brings error

Simonr — Wed, 31 Jan 2024 12:06:25 GMT

I tried on my end and I'm also able to reproduce this by setting these configs on my end, so it must be related to the MPSL.

CONFIG_MPSL_CX=y

CONFIG_MPSL_CX_NRF700X=y

I've not been able to find out why, as the error reported refers to a "Broken Pipe" which I'm not able to find where would be. I have asked the developers that made the MPSL if they know why this could be and will get back to you when I hear something. Thank you for your patience.

By removing these configs you will be able to run the project as expected I think. Is there a specific reason you've set these configs in your coex project?

Best regards,

Simon

RE: Setting nrf700x-coex ble-WiFi brings error

sguitton01 — Tue, 30 Jan 2024 10:28:40 GMT

Hi Simon, you're right,
I switch to

//Add for BLE/Wifi Coexistence

/ {

nrf_radio_coex: nrf7002-coex {

status = "okay";

compatible = "nordic,nrf700x-coex";

req-gpios = <&gpio0 28 (GPIO_ACTIVE_HIGH)>;

status0-gpios = <&gpio0 30 (GPIO_ACTIVE_HIGH)>;

grant-gpios = <&gpio0 24 (GPIO_ACTIVE_HIGH | GPIO_PULL_UP)>;

};

and the boot up errors are gone.
Though I still have the NRF RPC error and the Interface 1 error.
Do you know why?

OK
[00:00:00.517,791] <inf> fs_nvs: 2 Sectors of 4096 bytes
[00:00:00.517,822] <inf> fs_nvs: alloc wra: 0, fb8
[00:00:00.517,822] <inf> fs_nvs: data wra: 0, e4
*** Booting nRF Connect SDK v2.5.0 ***
[00:00:00.620,635] <err> nrf_rpc_ipc: IPC endpoint bond timeout
[00:00:00.620,666] <err> NRF_RPC: Failed to initialize transport, err: -32
[00:00:01.620,758] <err> NRF_RPC: Not all groups are ready to use.
[00:00:01.620,819] <inf> net_config: Initializing network
[00:00:01.620,849] <inf> net_config: Waiting interface 1 (0x200017d0) to be up...
OK
OK
OK
OK
FAIL
OK
OK
[00:00:31.621,978] <inf> net_config: IPv4 address: 192.165.100.150
[00:00:31.622,070] <inf> net_config: Running dhcpv4 client...
[00:00:31.622,406] <err> net_config: Timeout while waiting network interface
[00:00:31.622,406] <err> net_config: Network initialization failed (-115)

Sylvain

RE: Setting nrf700x-coex ble-WiFi brings error

Simonr — Tue, 30 Jan 2024 09:08:09 GMT

On your side the interface seems to time out waiting because the network is down (error -115). I just checked the pin config of your overlay, and it seems you might have mixed up the configs here, as P0.24 should be the COEX_GRANT in HW, not P0.25, and P0.28 should be the COEX_REQ pin. Also, the status pin you're using is by default used for QSPI with the nRF7002, so that's likely what you're having trouble with. I'm sorry I missed that initially.

Best regards,

Simon

RE: Setting nrf700x-coex ble-WiFi brings error

sguitton01 — Mon, 29 Jan 2024 09:30:55 GMT

Hi Simon,

I did try the coex example and here's the logs (it seems to boot like it should)

nRF Connect SDK v2.5.0 ***
[00:00:00.420,288] <OK
inf> net_config: Initializing network
[00:00:00.420,288] <inf> net_config: Waiting interface 1 (0x20001b40) to be up...
[00:00:00.420,410] <inf> net_config: IPv4 address: 192.168.1.99
[00:00:00.420,471] <inf> net_config: Running dhcpv4 client...
[00:00:00.420,623] <inf> coex: Starting nrf7002dk_nrf5340_cpuapp with CPU frequency: 128 MHz
[00:00:01.420,684] <inf> coex: test_wlan = 1 and test_ble = 1

[00:00:01.420,715] <inf> wifi_nrf: GPIO P1.10 set to 0

[00:00:01.433,593] <inf> coex: Connection requested
[00:00:01.433,593] <inf> coex: Waiting for Wi-Fi Connection
[00:00:31.433,685] <err> coex: Timeout waiting for Wi-Fi Connection -> -11

One thing that change is that on my side the "Waiting interface 1 (0x20001b40) to be up..." is always timing out, do you have an idea why?

Best regards,

Sylvain

RE: Setting nrf700x-coex ble-WiFi brings error

Simonr — Mon, 29 Jan 2024 08:19:06 GMT

Hmm, this look perfectly fine to me. How are you powering the DK on your end exactly? And could you try using one of our Wi-Fi sample projects just to make sure if this isn't an issue with the changes you made to the coex sample.

Best regards,

Simon

RE: Setting nrf700x-coex ble-WiFi brings error

sguitton01 — Thu, 25 Jan 2024 13:39:39 GMT

HI Simon,

Here's the picture:

Thank you,

Sylvain

RE: Setting nrf700x-coex ble-WiFi brings error

Simonr — Wed, 24 Jan 2024 12:31:11 GMT

Hi Sylvain

With that version of the DK NCS 2.5.0 should by default build for that chip revision, so that shouldn't be the issue. Can you send a (high-res) picture of your DK, and some information on how you're posing it and what the switches on the DK is set to?

The error messages you get is telling you that you're not able to communicate correctly with the nRF7002 chip for some reason, so I just want to see that the DK seems to be correctly set up.

Best regards,

Simon

RE: Setting nrf700x-coex ble-WiFi brings error

sguitton01 — Tue, 23 Jan 2024 14:49:24 GMT

Hi Simon,

I tried to power off with the switch but it did not solved it.
I am using the PCA10143 (1.0.2), the symbol CONFIG_NRF700X_REV_A is unknown so I can't set it.

Thank you,

Sylvain

RE: Setting nrf700x-coex ble-WiFi brings error

Simonr — Tue, 23 Jan 2024 11:52:04 GMT

Hmm, that's strange. Does it also occur if you power the DK off and on with the power switch? I've seen this been a fix in the past at least. What revision of the nRF7002 DK are you using? You can try setting CONFIG_NRF700X_REV_A=n in your prj.conf file if it isn't already (I think it should be by default).

Best regards,

Simon

RE: Setting nrf700x-coex ble-WiFi brings error

sguitton01 — Mon, 22 Jan 2024 10:42:15 GMT

Hi Simon,

Yes the DK has the P22-P23 headers has jumpers.

I just followed the OTP memory programming section, heres the logs:

uart:~$ wifi_radio_ficr_prog otp_write_params 0x100 0x50FA50FA
OTP Region is open for R/W

Finished Writing OTP params
[00:00:27.209,320] <inf> otp_prog: Written REGION_PROTECT0 (0x100) : 0x50fa50fa

[00:00:27.209,350] <inf> otp_prog: Written REGION_PROTECT1 (0x104) : 0x50fa50fa

[00:00:27.209,350] <inf> otp_prog: Written REGION_PROTECT2 (0x108) : 0x50fa50fa

[00:00:27.209,381] <inf> otp_prog: Written REGION_PROTECT3 (0x10c) : 0x50fa50fa

uart:~$

*** Booting nRF Connect SDK v2.5.0 ***
uart:~$ wifi_radio_ficr_prog otp_read_params
OTP Region is open for R/W

PRODTEST.FT.PROGVERSION = 0xff0200ff

PRODTEST.TRIM0 = 0x0099040b
PRODTEST.TRIM1 = 0x0099d407
PRODTEST.TRIM2 = 0x0099d807
PRODTEST.TRIM3 = 0x009f040c
PRODTEST.TRIM4 = 0x009fd408
PRODTEST.TRIM5 = 0x009fd808
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 = 0xc468fd02
INFO.UUID1 = 0x11ed7d66
INFO.UUID2 = 0x75a701cc
INFO.UUID3 = 0x02f0c3ce

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

MAC0.ADDRESS0 = 0x0036cef4
MAC0.ADDRESS1 = 0x0000dc17
MAC0.ADDRESS = f4:ce:36:00:17:dc

MAC1.ADDRESS0 = 0x0036cef4
MAC1.ADDRESS1 = 0x0000dd17
MAC1.ADDRESS = f4:ce:36:00:17:dd

CALIB.XO = 0x29
REGION_DEFAULTS = 0xfffffff1

uart:~$ wifi_radio_ficr_prog otp_write_params 0x100 0x00000000
OTP Region is open for R/W

Finished Writing OTP params
[00:02:47.825,988] <inf> otp_prog: Written REGION_PROTECT0 (0x100) : 0x0000

[00:02:47.826,019] <inf> otp_prog: Written REGION_PROTECT1 (0x104) : 0x0000

[00:02:47.826,019] <inf> otp_prog: Written REGION_PROTECT2 (0x108) : 0x0000

[00:02:47.826,049] <inf> otp_prog: Written REGION_PROTECT3 (0x10c) : 0x0000

And if after I go back to my code I still have the issue:

nrf_wifi_fw_load: nrf_wifi_fmac_fw_load failed
[00:00:11.287,322] <err> wifi_nrf: nrf_wifi_hal_fw_chk_boot: Boot_sig check failed for RPU(0), Expected: 0x5A5A5A5A, Actual: 0x88888888

[00:00:11.287,414] <err> wifi_nrf: nrf_wifi_fmac_fw_load: LMAC ROM boot check failed

[00:00:11.291,809] <err> wifi_nrf: nrf_wifi_fmac_dev_add_zep: nrf_wifi_fw_load failed

[00:00:11.291,809] <err> wifi_nrf: nrf_wifi_if_init_zep: nrf_wifi_fmac_dev_add_zep failed

[00:00:11.292,449] <err> wifi_nrf: nrf_wifi_if_start_zep: Invalid MAC address: <unknown>

[00:00:11.299,713] <inf> fs_nvs: 2 Sectors of 4096 bytes
[00:00:11.299,743] <inf> fs_nvs: alloc wra: 0, fe8
[00:00:11.299,743] <inf> fs_nvs: data wra: 0, 0
*** Booting nRF Connect SDK v2.5.0 ***
[00:00:11.402,343] <err> nrf_rpc_ipc: IPC endpoint bond timeout
[00:00:11.402,374] <err> NRF_RPC: Failed to initialize transport, err: -32
[00:00:12.402,496] <err> NRF_RPC: Not all groups are ready to use.
[00:00:12.402,557] <inf> net_config: Initializing network
[00:00:12.402,587] <inf> net_config: Waiting interface 1 (0x200017d0) to be up...
[00:00:42.403,594] <inf> net_config: IPv4 address: 192.165.100.150
[00:00:42.403,656] <inf> net_config: Running dhcpv4 client...
[00:00:42.403,991] <err> net_config: Timeout while waiting network interface
[00:00:42.404,022] <err> net_config: Network initialization failed (-115)
[00:00:42.405,090] <inf> ble_module: State: STATE_INIT
[00:00:42.406,219] <inf> ui_module: Registrated Button 0
[00:00:42.406,250] <inf> wifi_module: State: STATE_INIT
[00:00:42.406,921] <err> net_sock: invalid access on sock 536960896 by thread 0x20001c48
[00:00:42.406,982] <inf> wifi_module: State: STATE_RUNNING
[00:00:42.420,837] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:42.420,898] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:42.420,928] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 197.47763 Build 2370639017
[00:00:42.506,500] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:42.506,530] <inf> ble_module: Wi-Fi provisioning service starts successfully.

[00:00:42.507,751] <inf> bt_hci_core: Identity: D8:02:D1:80:10:C0 (random)
[00:00:42.507,781] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x2102, manufacturer 0x0059
[00:00:42.507,812] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x2102
[00:00:42.529,327] <inf> ble_module: settings_load() return code 0
[00:00:42.535,522] <inf> ui_module: ble_status_msg processed by CALLBACK ble_channel_cb: ble_central_status = 1

[00:00:42.535,522] <inf> ui_module: ble_status_msg processed by CALLBACK ble_channel_cb: ble_peripheral_status = 1

[00:00:42.535,583] <inf> ble_module: State: STATE_RUNNING

Best regards,

Sylvain

RE: Setting nrf700x-coex ble-WiFi brings error

Simonr — Mon, 15 Jan 2024 12:15:36 GMT

First thing's first, can you make sure P22 and P23 headers on the DK has jumpers on them, as this has been the issue when seeing this in the past.

Another common issue that will result in logs like this is if you haven't enabled the read/write access for the OTP memory locations in your nRF7002, please follow the OTP memory programming section of our Device Commissioning and Characterization application note available here to write a MAC address and set the OTP memory to protected state afterwards before usage.

Best regards,

Simon