-
Notifications
You must be signed in to change notification settings - Fork 2k
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
drivers/at86rf215: switch example config to use EXT3 on same54-xpro #19912
Conversation
This avoids the conflict of using the same IRQ line (EXTI07) as the PHY
1408eb0
to
05bf944
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes make sense.
I also compared the new pins assignment against SAME54-XPRO user manual.
Looks like this is all good.
bors merge |
19912: drivers/at86rf215: switch example config to use EXT3 on same54-xpro r=dylad a=benpicco Co-authored-by: Benjamin Valentin <[email protected]>
Build failed: |
bors merge |
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Contribution description
Attaching the
at86rf215
reference module to asame54-xpro
(via EXT1) stops working after 2a255ff configured the PHY IRQ pin to produce interrupts.This is because both the PHY IRQ (PD12) as well as the
at86rf215
IRQ (PB07) map to EXI7.Whatever of the two pins gets configured last wins.
Testing procedure
Attach the REB215-XPRO module to EXT3 on
same54-xpro
.Frame reception should now work again even if
sam0_eth
is in use.Issues/PRs references
fixes #19911