-
Notifications
You must be signed in to change notification settings - Fork 616
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
GPIO Interrupt problem on CM3 #1121
Comments
@nascs Is this something you would be aware of? |
I tried to start an ISR in c code too and I found out that before starting the ISR, function |
I didn't know about this. Maybe the test missed it. |
Hi @ModnyCo-Navid , Can you show me your sample code so I can reproduce the problem and see how to fix it? |
This is my sample code to test the pin read function before and after interrupt configuration. `
} And this is the output of this code. As you can see, when I configure the interrupt, the GPIO read function always returns |
Hi @ModnyCo-Navid, Maybe your code needs to be improved, here's an example you can try, on my side it's possible to trigger to the interrupt handle function. |
|
I can get the interrupt trigger and it works fine. There is no problem with the interrupt trigger. |
I have reproduced this problem, and now found that there may be a problem with the parameters returned by the thread when it is created by pthread_create. |
I built the library on Debian Bullseye OS on a Radxa CM3 board, and everything goes well but when I tried to set an interrupt on any GPIO using
mraa-monitor
, the pin value always returns -1. I tried to run the command using sudo, but the result was the same.The text was updated successfully, but these errors were encountered: