Dot11zynq - to support full range 16 Bit ADC I/Q data in the receive path. #9
Conversation
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
Tobias-DG3YEV
approved these changes
Apr 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
We are using 16 Bit I/Q data with zero bbgain in the rx_intf module. We went through the receive signal path and found the areas that were having problems with low and high signal levels. This limited dynamic range to about 45dB. This was increased to 69dB dynamic range of successful decoding of HT MCS0 packets. In our system, the ADC I/Q data ranges from fully saturated 0x7fff/0x8000 to about 4bits of noise at the low end.
Thought you may be interested in these changes.