chsh-sk-ncs-tc-wifi-throughput

Runs automated UDP throughput benchmarks on nRF54LM20DK with nRF7002EB2 using zperf and iperf.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/chshzh/claude --skill chsh-sk-ncs-tc-wifi-throughput-chshzh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chsh-sk-ncs-tc-wifi-throughput
Source: https://github.com/chshzh/claude/tree/main/skills/chsh-sk-ncs-tc-wifi-throughput
Command: npx skills add https://github.com/chshzh/claude --skill chsh-sk-ncs-tc-wifi-throughput-chshzh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyserial, and includes scripts (resource) components.

What problem does it solve? Manually benchmarking Wi-Fi throughput on nRF devices across multiple bands, directions, and bus interfaces is slow and error-prone. This Skill automates the full WCS-121 test suite, comparing sQSPI@32MHz vs SPI@8MHz performance and producing consistent, repeatable results ready for Jira reporting. ## Core Features & Use Cases - Automated UDP TX/RX Benchmarks: Drives zperf on the nRF side and iperf v2 on the Mac side across 2.4 GHz and 5 GHz bands with warmup and 3 measured runs per direction. - Bus Interface Comparison: Tests two flashed devices (sQSPI@32MHz and SPI@8MHz shields) and interprets results against known baselines from WCS-78. - Jira Result Reporting: Guides updating the WCS-121 results table via the Atlassian MCP with run values and total test time. - Use Case: An engineer debugging low sQSPI throughput flashes both boards, runs the script per device, and gets TX/RX Mbps values per band in about 6-7 minutes each, then pastes them into Jira. ## Quick Start Ask Claude to run the Wi-Fi throughput test on the sQSPI device at /dev/tty.usbmodem0010518696873 while keeping iperf -s -u running in a separate terminal.

Frequently Asked Questions about chsh-sk-ncs-tc-wifi-throughput

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a Wi-Fi throughput test on nRF54LM20DK with zperf?

Flash the board with the zperf and high-performance overlays, then run the run_throughput_test.py script with the serial port and device label. Keep iperf -s -u running on the Mac for TX measurements; results print to stdout and save to /tmp/results_<label>.json.

How to compare sQSPI vs SPI throughput on nRF7002EB2?

Flash one device with the nrf7002eb2_mspi shield (sQSPI@32MHz) and another with nrf7002eb2 (SPI@8MHz), then run the test script once per device. Compare the TX/RX Mbps values against the SPI@8MHz baseline of roughly 4.6-4.9 Mbps from WCS-78.

What prerequisites are needed before running the zperf throughput script?

Both devices must be flashed, UART ports free, the Wi-Fi router reachable on both SSIDs, the Mac on wired Ethernet at 192.168.92.178, and iperf -s -u running in a separate terminal. A config.json with SSID, password, and Mac IP must exist.

Why does the throughput script hang with no output?

Python stdout buffering hides output until the script exits. Always invoke it with python3 -u for unbuffered output, and confirm no other serial terminal is holding the UART port open.

Why does zperf UDP upload fail with error -1?

The iperf server is not running on the Mac. Start iperf -s -u in a separate terminal before running the script; the script reuses an existing server or starts its own if none is found.

What causes low sQSPI throughput with xfer timeout cmd=0xeb?

The FLPR VPR sQSPI read deadline is missed at 32 MHz, which is a known issue documented in WCS-121. The skill's result interpretation table flags sQSPI values around 0.4-0.8 Mbps versus SPI's 4.3-5.1 Mbps as this failure mode.