-
Notifications
You must be signed in to change notification settings - Fork 2.1k
drivers/sx126x: improve hardware detection #21905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
maribu
wants to merge
1
commit into
RIOT-OS:master
Choose a base branch
from
maribu:drivers/sx126x/fix-hardware-detection
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
drivers/sx126x: improve hardware detection #21905
maribu
wants to merge
1
commit into
RIOT-OS:master
from
maribu:drivers/sx126x/fix-hardware-detection
+31
−16
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
49a1ac5 to
aaaae2c
Compare
aaaae2c to
a8aaafc
Compare
Member
Author
- split out the detection logic into a static helper function
- replace a forgotten debug `printf()` with `DEBUG()`
- add a `LOG_ERROR()` to when no device is detect to ease diagnosis of
a failing SPI bus / incorrect wiring / broken chip
- use a bullet-proof test:
- First set the modulation type to LoRa
- Then get the modulation type and expect it to be LoRa
Even if the reset of the devices fails (e.g. because the reset signal
is not connected) and the modulation would be different from LoRa, this
now should reliably detect the chip.
a8aaafc to
fba614b
Compare
Member
Author
|
I updated the PR to no longer try three times. After the power sequencing code of the cursed board was fixed, the board was less cursed and the chips reliably come up on the first try. I don't have a reason to believe that there is a benefit in retrying the detection, hence I removed this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area: drivers
Area: Device drivers
Area: LoRa
Area: LoRa radio support
CI: ready for build
If set, CI server will compile all applications for all available boards for the labeled PR
Type: bug
The issue reports a bug / The PR fixes a bug (including spelling errors)
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
printf()withDEBUG()LOG_ERROR()to when no device is detect to ease diagnosis of a failing SPI bus / incorrect wiring / broken chipEven if the reset of the devices fails (e.g. because the reset signal
is not connected) and the modulation would be different from LoRa, this
now should reliably detect the chip.
Testing procedure
This should 100% detect when hardware is present, and 99.99% detect when hardware is not present.
Issues/PRs references
None