-
Notifications
You must be signed in to change notification settings - Fork 63
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
Read expected payload size of GPIO packet #304
Read expected payload size of GPIO packet #304
Conversation
Hi @IAmNickNack |
Could you clarify If you mean I2C via non-socket GPIO, then no. Even prior to making this change I have been unable to get non-socket GPIO working on my local setup. Startup fails on my v4 device with If this is what you mean. I can persevere. |
Hi @IAmNickNack the PI_INIT_FAILED error you get is most probably because you are not running it as root. Can you try again with root? |
Running as root appears to make no difference. I will have to try a simpler test case than the application I'm currently working on to see if I can find out what's going on. Filesystem permissions appear to be correct. I would expect both root and the user account to behave the same in this case anyway:
|
A-ha! This could be useful information to others, as I've seen this error mentioned in a number of posts: Non-socket GPIO doesn't work when I did still need to be running as root for this to work though. So, in response to your original question @eitch, yes. I have tested this code change with a normal, non-socket i2c connection and have satisfied myself that it is good. Please feel free to suggest a more rigorous and definitive testing strategy to me if you like however. Thanks |
Hi @IAmNickNack thanks for your work! I have merged your PR. Happy to see it works! |
Thanks @eitch. Hopefully somebody with an active serial or SPI project can add appropriate support for the equivalent operations to the |
This PR addresses issue #303 and could possibly be expanded to cover SPI and serial data too.