nRF7002 WIFI performance based on the nrf7002 PDK

[paul zhang]

Hi:

     We want to test the nrf7002 WIFI performance based on the nrf7002 PDK.Do we have relevant test firmware?

     We noticed that the sdk document of V2.1.2 has a description of the radio test,  but the SDK of V2.1.2 does not contain the source code of the radio_test example. this path contains only shell examples. Have you updated the sdk version to support this function. Or whether to update the hex firmware for us to test.

[Raoul]

Hi Paul,

You can find the radio_test sample documentation and source code in the new NCS v.2.2.0, which released on GitHub a few hours ago. It will show up in the Toolchain Manager soon!

From what I can see, this sample wasn't present yet in v2.1.2.

Best regards,

Raoul

[paul zhang]

We encountered some problems when compiling and running.

This is compiling log,Does this mean the code is lost?

-- Found assembler: D:/Work/NCS/toolchains/v2.2.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
CMake Warning at D:/Work/NCS/v2.2.0/zephyr/CMakeLists.txt:824 (message):
  No SOURCES given to Zephyr library: drivers__wifi

  Excluding target from build.

This is the run log：

[00:00:00.393,920] <inf> wifi_nrf: QSPI freq = 24 MHz

[00:00:00.393,951] <inf> wifi_nrf: QSPI latency = 1

[00:00:00.447,723] <inf> wifi_nrf: wifi_nrf_fmac_fw_load: LMAC patches loaded

uart:~$
uart:~$ *** Booting Zephyr OS build v3.2.99-ncs1 ***
[00:00:10.579,895] <err> wifi_nrf: wifi_nrf_hal_fw_chk_boot: Boot_sig check failed for RPU(0), Expected: 0x5A5A5A5A, Actual: 0x16

[00:00:10.579,956] <err> wifi_nrf: wifi_nrf_fmac_fw_load: LMAC ROM boot check failed

[00:00:10.579,986] <err> wifi_nrf: wifi_nrf_fmac_dev_add_zep: wifi_nrf_fmac_fw_load failed

[00:00:10.579,986] <err> wifi_nrf: wifi_nrf_drv_main_zep: wifi_nrf_fmac_dev_add_zep failed

[paul zhang]

Did you test the example of shell or radio_test,I can't run these examples on nRF7002-PDK.

The 7002 build code is N7002QFAAAA.

The 5340 build code is N5340QKAAD02042AA

PCA10143 version is 0.2.1 2022.36

this is  uart log when we run shell example in the SDK V2.2.0:

uart:~$ *** Booting Zephyr OS build v3.2.99-ncs1 ***
Starting nrf7002dk_nrf5340_cpuapp with CPU frequency: 128 MHz
[00:00:10.489,349] <err> wifi_nrf: wifi_nrf_hal_fw_chk_boot: Boot_sig check failed for RPU(0), Expected: 0x5A5A5A5A, Actual: 0x0

[00:00:10.489,410] <err> wifi_nrf: wifi_nrf_fmac_fw_load: LMAC ROM boot check failed

[00:00:10.489,440] <err> wifi_nrf: wifi_nrf_fmac_dev_add_zep: wifi_nrf_fmac_fw_load failed

[00:00:10.489,471] <err> wifi_nrf: wifi_nrf_drv_main_zep: wifi_nrf_fmac_dev_add_zep failed

[00:00:10.489,685] <err> wifi_nrf: wifi_nrf_if_init: vif_ctx_zep is NULL

[00:00:10.494,232] <inf> net_config: Initializing network
[00:00:10.494,293] <inf> net_config: IPv4 address: 192.165.100.150
[00:00:10.494,323] <inf> net_config: Running dhcpv4 client...
[00:00:10.500,274] <inf> wpa_supp: start_wpa_supplicant: 192 Starting wpa_supplicant thread with debug level: 3

[00:00:10.500,396] <inf> wpa_supp: Successfully initialized wpa_supplicant
[00:00:10.500,427] <inf> wpa_supp: iface_cb: iface wlan0 ifindex 1 00:00:00:00:00:00
[00:00:10.500,457] <inf> wpa_supp: Using interface wlan0

[00:00:10.500,488] <inf> wpa_supp: Initializing interface 0: wlan0

[00:00:10.500,549] <err> wpa_supp: wpa_drv_zep_init: Interface wlan0 not found

[00:00:10.500,610] <err> wpa_supp: wlan0: Failed to initialize driver interface
[00:00:10.500,671] <inf> wpa_supp: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
[00:00:10.500,793] <inf> wpa_supp: wpa_supplicant_main: exitcode -1
[00:00:10.594,268] <inf> net_config: IPv6 address: 2001:db8::1

[Raoul]

Hi Paul,

It seems that your last two replies are related to the same issue, of the WiFi device driver not being found.

I am out of office and don't currently have access to nRF7002 hardware, so another colleague will take a look at your case and get back to you soon.

Thanks for your patience.

Best regards,

Raoul

[panypan]

Hi Raoul,

Is there any update on this issue?

This samples of shell has no problem when running in sdk v2.1.2, but it has this issue when running in sdk v2.2.0. I has this issue too.

Best regards,

Pany