demo/send_packet: env-gated 40 MHz RX + HT STBC/LDPC TX radiotap#105
Merged
Conversation
DEVOURER_BW=40 selects a 40 MHz monitor channel (CHANNEL_WIDTH_40, with DEVOURER_CHOFFSET for the secondary half) so the RX can receive HT40 frames; needed to validate the gr-ieee802-11 fork's HT40 transmit over the air. Also surface bw/stbc/ldpc/sgi on the <devourer-corrupt-any> DUMP_ALL line (matching <devourer-stream>) so a frame the chip decodes-but-fails-CRC can be inspected for its decoded PHY params. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The HT-MCS radiotap branch read bandwidth and short-GI but never STBC or FEC, so an HT frame tagged STBC/LDPC in radiotap silently transmitted as BCC SISO -- only the VHT branch honoured them. Read STBC (MCS known bit5 / flags bits5-6) and LDPC (known bit4 / flags bit4) here too, so WiFiDriverTxDemo with DEVOURER_TX_HT_MCS=1 + DEVOURER_TX_STBC=1 emits a real HT STBC / HT LDPC frame. Verified at the TX descriptor: fixed rate:128 (MGN_MCS0) stbc:1. Intended as a chip reference for the gr-ieee802-11 fork's modern TX. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two small, independent additions that let
WiFiDriverTxDemo/WiFiDriverDemoexercisemodern HT formats (used to validate an external userspace TX against the chip):
demo: env-gated 40 MHz RX (DEVOURER_BW=40) + the bw/stbc/ldpc/sgi PHY flagson the
<devourer-corrupt-any>DUMP_ALL line (matching<devourer-stream>), so anHT40 frame can be received and a decoded-but-CRC-failed frame inspected for its PHY
params.
send_packet: honour STBC and FEC=LDPC on the HT radiotap path. The HT-MCSradiotap branch read bandwidth/short-GI but never STBC or FEC, so an HT frame tagged
STBC/LDPC transmitted as plain BCC SISO — only the VHT branch honoured them. Reading
them here (with
DEVOURER_TX_HT_MCS=1) makesWiFiDriverTxDemoemit a real HT STBC /HT LDPC frame. Verified at the TX descriptor:
fixed rate:128 (MGN_MCS0) ... stbc:1.Builds clean (WiFiDriverDemo + WiFiDriverTxDemo).
🤖 Generated with Claude Code