-
Notifications
You must be signed in to change notification settings - Fork 410
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
bad ISR initialisation #27
Comments
That is just a plain error on my part. The erroneous error is because of an incorrect check when the GPIO is unexported. The unexport itself will be fine. However a consequential error means the GPIO is still marked exported internally and the software will not set up a new ISR. The line if (err != sizeof(buf)) return PI_BAD_ISR_INIT; should be if (err != strlen(buf)) return PI_BAD_ISR_INIT; in the intGpioSetISRFunc function. I'll correct the software in the next release (probably before 27th Oct 15). |
Great, thanks. |
Implemented in V39. |
Thanks for fixing this. Everything looks a lot better now and the issue has been resolved. However, there is a new issue. Here's the output of the first run of the test program from the original post:
Here's the output of the second run:
As can be seen, everything isn't quite right yet. However, this is a different problem so I'll open a new issue for it. This problem can be solved by calling |
The goal of the program below is the following:
However,
gpioSetISRFunc(GPIO, EITHER_EDGE, 0, NULL)
, which I think should disable interrupts is returning -123 which meansbad ISR initialisation
.The output of the program is:
Am I doing something incorrectly?
Additional info:
The text was updated successfully, but these errors were encountered: