-
Notifications
You must be signed in to change notification settings - Fork 2.1k
cpu/nrf5x/nrfmin: fix isr termination #11395
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
Conversation
miri64
left a comment
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.
Seems obvious. But I still want to test. ACK on the rest though
|
Mh... I wasn't able to reproduce the issue, but during my testing I found the following problem: When I ping from two nodes simultaneously everything works fine, however when I then do the first command doesn't work anymore afterwards. I'll have a look if this is isolated to |
miri64
left a comment
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.
ACK
|
Please provide a backport to |
|
Backport provided in #11408 |
Contribution description
The nrfmin driver had a serious bug terminating the interrupt handler in case of an invalid CRC value.
Instead of closing with
cortexm_isr_end();it just returned, which resulted in unwanted behaviour.This PR fixes one error mentioned in #10878 and is based on the solution of @pystub
Testing procedure
Testing should at least involve receiving and then sending packets with a valid CRC. However, it is appreciated if a reviewer makes sure that the behaviour is also correct with invalid CRC.
Make sure to test it using nrfmin with
USEMODULE=nrfminon nrf5x boards.