nrf_wifi: Add a testcase for nRF7120PDK

[krish2718]

Add a basic end-end test using Raw TX packet (tested on TLM) for nRF7120PDK.

[NordicBuilder]

The following west manifest projects have changed revision in this Pull Request:

Name	Old Revision	New Revision	Diff

✅ All manifest checks OK

Note: This message is automatically posted and updated by the Manifest GitHub Action.

[NordicBuilder]

CI Information

^{To view the history of this post, clich the 'edited' button above}
Build number: 6

Inputs:

Sources:

sdk-nrf: PR head: 7f71c28c5b2bc5b4e4f8bd93d724ef4a3537a5b0

more details

sdk-nrf:

PR head: 7f71c28c5b2bc5b4e4f8bd93d724ef4a3537a5b0
merge base: fd3639dbf31e806be13ba098759f140b56c90b94
target head (main): fd3639dbf31e806be13ba098759f140b56c90b94
Diff

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (10)

CODEOWNERS
boards
│  ├── nordic
│  │  ├── nrf7120pdk
│  │  │  │ nrf7120pdk_nrf7120_cpuapp.yaml
tests
│  ├── drivers
│  │  ├── nrf_wifi
│  │  │  ├── raw_tx_rx
│  │  │  │  ├── CMakeLists.txt
│  │  │  │  ├── Kconfig
│  │  │  │  ├── ipc.overlay
│  │  │  │  ├── overlay-nrf71-tlm.conf
│  │  │  │  ├── prj.conf
│  │  │  │  ├── src
│  │  │  │  │  │ main.c
│  │  │  │  ├── sysbuild.conf
│  │  │  │  │ testcase.yaml

Outputs:

Toolchain

Version: 1d2c5d0ab5
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:1d2c5d0ab5_8bf7ca4353

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

• ◻️ Toolchain - Skipped: existing toolchain is used
• ✅ Build twister
  • sdk-nrf test count: 7
• ✅ Integration tests

Disabled integration tests

• • desktop52_verification
  • doc-internal
  • test_ble_nrf_config
  • test-fw-nrfconnect-apps
  • test-fw-nrfconnect-ble_mesh
  • test-fw-nrfconnect-ble_samples
  • test-fw-nrfconnect-boot
  • test-fw-nrfconnect-chip
  • test-fw-nrfconnect-fem
  • test-fw-nrfconnect-nfc
  • test-fw-nrfconnect-nrf-iot_cloud
  • test-fw-nrfconnect-nrf-iot_libmodem-nrf
  • test-fw-nrfconnect-nrf-iot_mosh
  • test-fw-nrfconnect-nrf-iot_positioning
  • test-fw-nrfconnect-nrf-iot_samples
  • test-fw-nrfconnect-nrf-iot_serial_lte_modem
  • test-fw-nrfconnect-nrf-iot_thingy91
  • test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • test-fw-nrfconnect-nrf_crypto
  • test-fw-nrfconnect-proprietary_esb
  • test-fw-nrfconnect-ps
  • test-fw-nrfconnect-rpc
  • test-fw-nrfconnect-rs
  • test-fw-nrfconnect-tfm
  • test-fw-nrfconnect-thread
  • test-low-level
  • test-sdk-audio
  • test-sdk-dfu
  • test-sdk-find-my
  • test-sdk-mcuboot
  • test-sdk-pmic-samples
  • test-sdk-wifi
  • test-secdom-samples-public

Note: This message is automatically posted and updated by the CI

[github-actions]

You can find the documentation preview for this PR here.

[VivekUppunda]

I would have a transmit socket and a receive socket even though parallel calls for send/recv to a socket are possible when using threads. I will leave that to you. Also, possibly the socket has to have ETH_P_ALL protocol now.

[krish2718]

I would have a transmit socket and a receive socket even though parallel calls for send/recv to a socket are possible when using threads. I will leave that to you.

As the TX is controlled and interleaved with RX there is no contention (at least not in the current code), in future if we modify if to have concurrent accesses, we can add a mutex to the socket operations.

Also, possibly the socket has to have ETH_P_ALL protocol now.

Fixed locally will push during manifest update.