wrong RSSI calculation
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
looks like a driver does some wrong calculation on RSSI value.
when having zeroed out offset 0x45 in eeprom (this was popular with xiaomi mini until http://nbd.name/mt76-lnagain.patch was made) i get RSSI value ~ -65dBm, if i keep original value (+2dBm) at 0x45 the RSSI is calculated in wrong direction showing ~69dBm while it should be closer to -60dBm
trying to compensate for this entering 2A to eeprom address 4A (chain0) works fine, but entering 2A to 4B (chain1) does not work. at first i patched both addresses but later found out it only works for chain0.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the driver’s RSSI calculation and the EEPROM handling for offsets 0x45, 0x4A, and 0x4B. Compare the chain0 and chain1 paths using the reported zeroed and +2 dBm values; done means both chains produce RSSI values in the expected direction and range.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100