cpu/nrf52: fix RSSI calculation in nrf802154_radio#20839
Merged
benpicco merged 1 commit intoRIOT-OS:masterfrom Sep 6, 2024
Merged
cpu/nrf52: fix RSSI calculation in nrf802154_radio#20839benpicco merged 1 commit intoRIOT-OS:masterfrom
benpicco merged 1 commit intoRIOT-OS:masterfrom
Conversation
Contributor
|
What's the drawback of always setting |
Contributor
Author
I don't really see the necessity if we can deduce it from LQI anyways and I would expect it to be a minor overhead in hardware which we could avoid. But that feeling would certainly need some benchmarking to be backed up or falsified. I'm not opposed to going that route instead. |
Contributor
|
I have tested the PR on two nrf802154 and can confirm that it works as intended. |
benpicco
approved these changes
Sep 6, 2024
Contributor
Author
|
Thanks for your support both of you! |
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
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.
Contribution description
As detailed in #20803, The calculation of RSSI based on the hardware-provided LQI value on
masteris wrong. The documentation states thatwithout further detailing the applied mapping.
Reusing the RSSI measurement functionality, I was able to find out the (reverse) mapping with the diff below.
Testing procedure
Apply the following diff enabling automatic RSSI measurement during packet reception:
Flash and send some packets from a different node:
The RSSI value (given in
dBm) calculated from the (hardware-provided) LQI value (calc) closely matches the reported RSSI value (real).Alternatives considered
We could use the normal RSSI measurement approach as in the diff above to get the actual RSSI value. But since calculating RSSI back from LQI seems to work fine, I'd propose to skip that (potential) overhead.
Issues/PRs references
Fixes #20803