Recent changes to tickets

Ubuntu Core Snap failing to build RPI GPIO

2025-02-27T21:13:25.653000Z

I am building Python 3.11 into an Ubuntu Core Snap(craft.yaml). This for use within Greengrass (also part of same Snap). Running on a Raspberry CM4. During pip install of RPi.GPIO==0.7.1 I get a failure from gcc linker:

2025-02-27T16:24:49.551Z [WARN] (Copier) com.thio.coredevice.thio_bp_lab: stderr. gcc -pthread -shared -L/root/parts/python/install/usr/lib -L/root/parts/python/install/usr/lib/aarch64-linux-gnu -L/root/parts/python/install/usr/lib -L/root/parts/python/install/usr/lib/aarch64-linux-gnu -DCONFIG64 -L/snap/aws-iot-greengrass-v2/x1 build/temp.linux-aarch64-cpython-311/source/cgpio.o build/temp.linux-aarch64-cpython-311/source/common.o build/temp.linux-aarch64-cpython-311/source/constants.o build/temp.linux-aarch64-cpython-311/source/cpuinfo.o build/temp.linux-aarch64-cpython-311/source/eventgpio.o build/temp.linux-aarch64-cpython-311/source/pygpio.o build/temp.linux-aarch64-cpython-311/source/pypwm.o build/temp.linux-aarch64-cpython-311/source/softpwm.o -o build/lib.linux-aarch64-cpython-311/RPi/GPIO.cpython-311-aarch64-linux-gnu.so. {scriptName=services.com.thio.coredevice.thiobplab.lifecycle.run.Script, serviceName=com.thio.coredevice.thiobplab, currentState=RUNNING}

###### 2025-02-27T16:24:49.551Z [WARN] (Copier) com.thio.coredevice.thiobplab: stderr. /snap/aws-iot-greengrass-v2/x1/usr/bin/ld: cannot find /usr/lib/aarch64-linux-gnu/libcnonshared.a. {scriptName=services.com.thio.coredevice.thiobplab.lifecycle.run.Script, serviceName=com.thio.coredevice.thiobplab, currentState=RUNNING}

2025-02-27T16:24:49.551Z [WARN] (Copier) com.thio.coredevice.thiobplab: stderr. collect2: error: ld returned 1 exit status. {scriptName=services.com.thio.coredevice.thiobplab.lifecycle.run.Script, serviceName=com.thio.coredevice.thiobplab, currentState=RUNNING}
2025-02-27T16:24:49.551Z [WARN] (Copier) com.thio.coredevice.thiobplab: stderr. error: command '/snap/aws-iot-greengrass-v2/x1/usr/bin/gcc' failed with exit code 1. {scriptName=services.com.thio.coredevice.thio*

The main error appears to be the linker cannot find the libc_nonshared.a. I have found this library under /snap/aws-iot-greengrass-v2/x1/usr/lib in the snap -- however even though I added this under the -L option (using CFLAGS) I still get an error from ld cannot find /usr/lib/libc_nonshared.a

Help?

#214 Plans to support Raspberry Pi 5

2025-01-13T18:24:51.168000Z

Please have a look at https://github.com/phylax2020/RPi.GPIO

remove_event_detect() may produce a memory access error - system exit

2024-12-13T15:41:38.655000Z

After ramping up and running a GPIO pin in input direction and using interrupts, the sutdown procedure terminates abruptly when calling move_event_detect() with nothing more than "Memory access error" ("Speicherzugriffsfehler") written on the console.

I suggests focussing on py_gpio.c#py_remove_event_detect() around line #760. It seems as if the callback memory structures are free'd (in line #767) way before actually muting the interrupt through a call of remove_edge_detect() (in line #777). If an interrupt happens to occur right in between, the remaining code may refer to memory, that is actually released, already.

Unable to run using archlinux armv8

2024-11-22T13:14:27.001000Z

I've tried using rpi.gpio on a Pi 3+ running archlinux armv8. Sadly, all I get is the error message

RuntimeError: This module can only be run on a Raspberry Pi!

I did not find any related issues here, though on the AUR page other people experienced the same issue: https://aur.archlinux.org/packages/python-rpi-gpio

#218 regression: can't import RPi.GPIO on RPi model B

2024-11-15T22:00:22.728000Z

Update: I upgraded from Bullseye to Bookworm (with this as a guide), and everything continued working as it should. Possible packaging problem by Raspberry Pi?

regression: can't import RPi.GPIO on RPi model B

2024-11-15T16:37:38.522000Z

I tried bringing up some software that was previously working on the original Raspberry Pi under the latest OS release and can no longer import RPi.GPIO:

Python 3.11.2 (main, Aug 26 2024, 07:20:54) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import RPi.GPIO as GPIO
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3/dist-packages/RPi/GPIO/__init__.py", line 927, in <module>
    RPI_INFO = _get_rpi_info()
               ^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/RPi/GPIO/__init__.py", line 428, in _get_rpi_info
    raise NotImplementedError(
NotImplementedError: This module does not understand old-style revision codes
>>> import RPi.GPIO
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3/dist-packages/RPi/GPIO/__init__.py", line 927, in <module>
    RPI_INFO = _get_rpi_info()
               ^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/RPi/GPIO/__init__.py", line 428, in _get_rpi_info
    raise NotImplementedError(
NotImplementedError: This module does not understand old-style revision codes
>>>

When I rolled the device back to Bullseye, I was able to import the module.

#210 RPi.GPIO 0.7.1 still acts on /sys/class/gpio/ ?

2024-05-11T16:05:32.437000Z

Will this be fixed and published for easier update?

#210 RPi.GPIO 0.7.1 still acts on /sys/class/gpio/ ?

2024-03-16T23:06:42.634000Z

It seems /sys/class/gpio is only used for edge detection. It only appears in event_gpio.c.

The immediate problem is that starting with kernel 6.5, BCM GPIO numbering in /sys/class/gpio doesn't start with 0 any more. It starts with 512 on my Raspberry Pi 2 B running Raspbian Bullseye with kernel 6.6.20+rpt-rpi-v7 but don't know if it is safe to hard code 512. Regardless of that, I created a quick fix which adds 512 to numbers when using /sys/class/gpio and increases size of buffers used for this. I'm using this with ha-rpi_gpio for Home Assistant, which now works. I am attaching a patch.

#178 linter problems

2024-03-13T16:56:33.485000Z

RPi.GPIO stubs are on typeshed as of https://github.com/python/typeshed/pull/11345

No access to /dev/mem, how to change to /dev/gpiomem

2024-01-25T16:10:54.723000Z

Hi, RPi.GPIO is usings /dev/mem on my raspberry, I only can use it with sudo, how can I switch it to /dev/gpiomem? I tried to change permission to 777 but it not work either
My environment info:

pi@ticketera:~/ticketera $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
pi@ticketera:~/ticketera $ uname -a
Linux ticketera 6.1.74-v7+ #1725 SMP Mon Jan 22 13:30:14 GMT 2024 armv7l GNU/Linux
pi@ticketera:~/ticketera $ sudo ls -l /dev/mem
crwxrwxrwx 1 root kmem 1, 1 Jan 25 09:18 /dev/mem
pi@ticketera:~/ticketera $ sudo ls -l /dev/gpiomem
crw------- 1 root root 241, 0 Jan 25 09:18 /dev/gpiomem
pi@ticketera:~/ticketera $ grep -i --color 'gpio' /etc/group
gpio:x:997:pi
pi@ticketera:~/ticketera $ grep -i --color 'kmem' /etc/group
kmem:x:15:pi

With pi user, I try to update to 0.7.1 because in 0.7.0 it didn't work either

pi@ticketera:~/ticketera $ python3 
Python 3.9.2 (default, Mar 12 2021, 04:06:34) 
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from RPi import GPIO
>>> GPIO.VERSION
'0.7.1'
>>> GPIO.setmode(GPIO.BOARD)
>>> GPIO.setup(5, GPIO.IN)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: No access to /dev/mem.  Try running as root!
>>>

With sudo

pi@ticketera:~/ticketera $ sudo python3 
Python 3.9.2 (default, Mar 12 2021, 04:06:34) 
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from RPi import GPIO
>>> GPIO.VERSION
'0.7.0'
>>> GPIO.setmode(GPIO.BOARD)
>>> GPIO.setup(5, GPIO.IN)
>>>