-
Notifications
You must be signed in to change notification settings - Fork 68
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 Access Denied #44
Comments
CB1 uses a custom IO arrangement, check my post here: #14 (comment) Just take a |
Hi thanks for the feedback I tried both the PC pins directly and the SOPine Gpio Alternate. Still getting a permission denied error. What version of the CB1 OS are you running? 2022-10-02 19:28:36,195 [gpio.py:_request_gpio()] - Unable to init gpiochip0:gpio74. Make sure the gpio is not in use by another program or exported by sysfs. |
I'm using latest Klipper image of CB1 OS, the V2.2.0. I just tried and I have the same problem. I think that it's just a permission problem. Tried with the solution in this post but it didn't work: Arksine/moonraker#249 (comment) |
Okay so you used the PC pins in klipper? Damn this is a good work around but it still has the downside of not being able to turn the printer on and off :'( |
Hmmm tried Power GPIO permission denied #249 and now the error looks different: |
Assuming that you used the Klipper image, so you had the linux MCU host already install or you did it by yourself, you must have:
Just checked and it corresponds: GPIO78 -> GPIO17_PC14 -> PIN n.11 You can try to set it only in your |
You can't use |
I just found the solution. Add the following lines in your
Create a new udev rule as
The solution I posted was using the "gpio" group, that does not exist in our CB1 image. |
Okay so this and this in combination with this seem to be allowing me to add |
If you don't get any error, it should work. Remember that |
Lovely I'm also getting around 1.8V output on high. |
You already tried more pins than me! The "disappointment" is that people have been asking Biqu/BTT for the GPIO pinout since weeks/months. |
Yeah my little list atleast references the current m8p pinout, weird that 75 aka gpio23 gives a error 16 device busy |
Now I just hope I can use this list on the radxa zero, having the same pinout issue there. |
You can run In my case |
That's supposed to be gpio8 according to there m8p pinout. This manual is useless. Well I have 8 functioning pins which is more than enough for my purposes. Thanks again for the help |
Hi all,
I wanted to use GPIOs for controling 3D printer relay. And it is finaly fixed by these steps.
Thanks @Michelinu next and add Reboot |
Moonraker is currently not able to access the gpio pins.
[gpio.py:_request_gpio()] - Unable to init gpiochip0:gpio6. Make sure the gpio is not in use by another program or exported by sysfs.
Traceback (most recent call last):
File "/home/biqu/moonraker/moonraker/components/gpio.py", line 84, in _request_gpio
chip = self._get_gpio_chip(pin_params['chip_id'])
File "/home/biqu/moonraker/moonraker/components/gpio.py", line 40, in _get_gpio_chip
chip = self.gpiod.Chip(chip_name, self.gpiod.Chip.OPEN_BY_NAME)
PermissionError: [Errno 13] Permission denied
2022-10-02 13:02:25,273 [moonraker.py:add_warning()] - Failed to load power device [power light_strip_2 ]
Error parsing option (pin) from section [power light_strip_2 ]
The text was updated successfully, but these errors were encountered: