-
Notifications
You must be signed in to change notification settings - Fork 9
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
Error No such file or directory #17
Comments
It's possible that the Debian Raspberry Pi image doesn't have sysfs GPIO enabled by default. What do you get if you |
I wonder if this is the timing issue on export that has been noted elsewhere related to udev: rust-embedded/rust-sysfs-gpio#5. Can you run the command again with |
It seem that is
|
If I do It's Ok if I do
|
Ah, I see. I think you need to execute the |
If I do
I got information
but I have this error with
No error when I do
|
That second error does sound more similar to the aforementioned RPi issues and might be something we could put a workaround in for (in gpio-utils, not the library). |
Like @nastevens say in rust-sysfs-gpio Added warning about Raspberry Pi PR, do you think that is possible to use the retry crate to try a few times with a delay between each attempt? |
Yes, that sounds reasonable. Can you open a PR with this @LeMoussel? |
I'm newbie with Rust :) |
Permission denied error is due to the creation of symlink for each GPIO name/alias : For Raspberry PI, I don't see why these symlink are created. In gpio_export.rs, Line 28, If I replace Should be make PR for that? |
The symlink feature does have real value in many configurations. We could consider changing the deafult to not have a symlink root (see config.rs). |
Ok.
But there is always error. This is due to the fact that is not possible to create new symbolic link (like One solution would be to put no name in the configuration file |
Yeah, making the symlink root be in sysfs will not work and doesn't make sense. Using some other directory (e.g. /tmp) may work. |
Yep ! It's much better with
With this configuration
I got this result
I update |
On a raspberry PI 3/debian,
raspberrypi.toml
is in current directory.What does this error mean?
The text was updated successfully, but these errors were encountered: