Will Spies created ticket #221

Ubuntu Core Snap failing to build RPI GPIO

Severin Hoffmann posted a comment on ticket #214

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

Oliver Maye created ticket #220

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

Patrick Mischke created ticket #219

Unable to run using archlinux armv8

Scott Alfter posted a comment on ticket #218

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?

Scott Alfter created ticket #218

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

Ken Brooks posted a comment on a wiki page

I tried the standard install command on my apple silicon macintosh. It didn't work because a header file called sys/epoll.h is missing from the system.A little research suggests that this header file belongs to Linux, not clear that it belongs to Macintosh. Here's the full output: % pip install RPi.GPIO Collecting RPi.GPIO Downloading RPi.GPIO-0.7.1.tar.gz (29 kB) Preparing metadata (setup.py) ... done Building wheels for collected packages: RPi.GPIO Building wheel for RPi.GPIO (setup.py) ... error...

James posted a comment on ticket #210

Will this be fixed and published for easier update?

dreamlayers posted a comment on ticket #210

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....

Avasam posted a comment on ticket #178

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

Daniel Robles created ticket #216

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

Matthew S Gerber posted a comment on ticket #210

Looks like /sys/class/gpio has been deprecated: https://www.thegoodpenguin.co.uk/blog/stop-using-sys-class-gpio-its-deprecated/ And now it's not present in the latest Ubuntu Server OS, which is what I'm running. Any plans to migrate away from /sys/class/gpio?

Matthew S Gerber posted a comment on ticket #210

I am getting the same error as above, using RPi.GPIO 0.7.1 and Python 3.11. Is there any fix or workaround?

Sam created ticket #215

Provide bindings for non-RPi development

Melissa LeBlanc-Williams posted a comment on ticket #214

Due to lack of response, we ended up refactoring and using libgpiod. Thanks.

Melissa LeBlanc-Williams posted a comment on ticket #214

More info. It wasn't installing at all previously, but now it installs. When I try running GPIO.setup() as a user I get: RuntimeError: No access to /dev/mem. Try running as root! If I run as root, I get: RuntimeError: Mmap of GPIO registers failed

Melissa LeBlanc-Williams created ticket #214

Plans to support Raspberry Pi 5

ChrisMartu posted a comment on a wiki page

Thank you Emmanuel

Kobra posted a comment on a wiki page

I just get that this cant be installed on my windows system even thought I just want to have it install so I can do coding on my windows system and known that it will work for my PI systems

Avasam posted a comment on ticket #178

Adding type stubs would help teach linting and type-checking tools about possible imports, symbols and class/methods definitions. See https://peps.python.org/pep-0561/#specification If the maintainer(s) of this project does not want to provide and maintain type-stubs, you can create your own package and distribute it on PyPI. Or request and/or add it to https://github.com/python/typeshed . This also relates to the following stub-request Pylance issue: https://github.com/microsoft/python-type-stu...

Matheus Tosta created ticket #213

Support pyproject.toml-based installation

Justin Lee Pulley posted a comment on ticket #212

I found a 2 year old post that says this library is not able to be compiled on windows.

Justin Lee Pulley modified a comment on ticket #212

Here is the screen cap of Visual C++ 14.) or greater installed

Justin Lee Pulley posted a comment on ticket #212

Justin Lee Pulley created ticket #212

pip install error on windows

Bug Menot created ticket #211

Unable to build with gcc 11 - Segmentation fault

msaimper posted a comment on ticket #210

Hello, I ended up migrating to gpiod, where things work out of the box. Best msaimper

msaimper created ticket #210

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

Walter A. Boring IV posted a comment on ticket #208

Just seems like a bad bug that I can't even watch for a change while only reading a pin that it causes failures elsewhere.

Ben Croston posted a comment on ticket #208

I would loop back pin 12 to another spare pin on your RPi using a 1k resistor and monitor that pin instead. It isn't possible to set up events for an output channel.

Walter A. Boring IV posted a comment on ticket #208

PTT = push to talk. it raises one of the GPIO pins to high which is connected to my ham radio to key up the mic for transmit out RF. I'm trying to monitor direwolf when it raises the PTT GPIO pin There is also an RX GPIO Pin as well that I want to monitor at the same time Ultimately I'm trying to monitor when my ham radio does a TX and RX via the GPIO pins that direwolf uses.

Ben Croston posted a comment on ticket #208

Is the PTT an output from direwolf?

Walter A. Boring IV posted a comment on ticket #208

I'm trying to monitor the PTT being set high from python.

Ben Croston modified a comment on ticket #208

Rather than a software fix, would it not be easier in this case to connect your PTT to a second input pin as well and use that?

Ben Croston posted a comment on ticket #208

Rather than a software fix, would it not be easier in this case to connect your PTT to a second input pin and use that?

Walter A. Boring IV created ticket #208

Using add_event_detect() prevents other apps from using the GPIO pins.

Ben Croston modified ticket #207

Missing "Python.h"

David Rayna posted a comment on ticket #205

Within a single Python program, there should be little issue, but would other processes or external hardware always see bits tested and changed in the same order? I no longer have an issue of wrong GPIO changing among simultaneous C++ & Python programs since I corrected a C++ code mistake in using the special set & clear addresses in the gpio_map. I had seen some examples of C GPIO code using __sync_synchronize() so I was thinking there was a concern. CPU behavior or overhead in Python might assure...

Ben Croston modified ticket #205

Shouldn't __sync_synchronize() be used after writes and before IO reads ?

Ben Croston posted a comment on ticket #205

CPython effectively operates as a single thread (i.e. it uses the GIL) so this is unlikely to be a problem. Do you know of any issues that the lack of __sync_synchronize() causes?

Ben Croston modified ticket #200

Support Radxa Zero

Ben Croston posted a comment on ticket #200

The radxa zero is not a Raspberry Pi and uses a completely different SOC so it will never be supported by this library.

Ben Croston modified ticket #199

Installing package failed on PyCharm

Ben Croston posted a comment on ticket #199

RPi.GPIO is not designed to be compiled or run on Windows

Ben Croston modified ticket #206

Not running on a RPi! on Pi4B running AWS Greengrass

Wout posted a comment on ticket #202

Looking at the code, it can be 99% be resolved by a small modification to run_py_callbacks(unsigned int gpio) by moving the code inside the if (cb->gpio == gpio) branch outside the loop, this would allow the callback to modify the callback linked list without crashing the loop. This would leave still a tiny chance of the callback getting called during the initial setup of the callbacks, getting into a race condition if I'm right, but I haven't looked at how the threading is set up yet. So a lock...

Wout posted a comment on ticket #202

I've made the modifications to allow callbacks adding/removing callbacks, see attached files. I've moved performing the call backs to outside the loop, so the callback doesn't mess up the loop. Plus I've added a mutex so another thread cannot mess up the loop if the other thread is adding/removing callbacks. There's only one tiny risk during startup, since the polling thread is created/started when adding the first callback, in theory when that callback is called right away, it can add callbacks,...

Ben Croston posted a comment on ticket #207

This is part of Python itself, not RPi.GPIO. Have you got the Python development packages installed on your distro?

Ian Binnie created ticket #207

Missing "Python.h"

Eric Snyder posted a comment on ticket #206

Solved. Adding the user that greengrass runs as to the group gpio fixed the issue.

Eric Snyder posted a comment on ticket #206

I have learned a bit more. When I run commands in the cli as the greengrass user I get the errors. It definitely seems to be a hardware detection error that is happening but only when run a certain users.

Eric Snyder created ticket #206

Not running on a RPi! on Pi4B running AWS Greengrass

David Rayna created ticket #205

Shouldn't __sync_synchronize() be used after writes and before IO reads ?

Barney Stratford created ticket #204

Segfault when using callbacks

Mirza Kapetanovic created ticket #203

Update download files to the latest version

Wout created ticket #202

Make adding and removing event handlers (add_event_detect and remove_event_detect) thread safe.

Ben Croston modified ticket #176

Misidentifying board type

Ben Croston posted a comment on ticket #176

Fixed in 0.7.1

Ben Croston modified ticket #171

"Not running on a RPi" message from GPIO.setup(id, GPIO.IN) on new RPi4B

Ben Croston posted a comment on ticket #171

Fixed in 0.7.1

Ben Croston modified ticket #194

compilation warning on python 3.9 and gcc 10

Ben Croston posted a comment on ticket #194

Fixed in 0.7.1

Ben Croston modified ticket #198

Compilation Fails with Python 3.9

Ben Croston posted a comment on ticket #198

Fixed in 0.7.1

Ben Croston modified ticket #198

Compilation Fails with Python 3.9

Ben Croston posted a comment on ticket #198

Fixed in 0.7.1

Ben Croston modified ticket #191

64bit This module can only be run on a Raspberry Pi!

Ben Croston posted a comment on ticket #191

Fixed in 0.7.1

Ben Croston modified ticket #190

/proc/cpuinfo identification needs updates for RPi 4

Ben Croston posted a comment on ticket #190

Fixed in 0.7.1

Ben Croston committed [f8d556]

Release 0.7.1

Ben Croston committed [be8e4d]

Added tag 0.7.1 for changeset f8d556afd9b0

Dave Hocker posted a comment on ticket #198

This problem is caused by a change to the GCC 10 default options. I came across it while migrating my RaspberryPi's from Buster to the newly released Raspberry Pi OS BullsEye. Originally, the default was -fcommon but it has been changed to -fno-common. You can work around the problem by setting the CFLAGS environment variable. For example: export CFLAGS=-fcommon Alternatively, this problem can be fixed in source by changing setup.py as follows: setup(name = 'RPi.GPIO', version = '0.7.0', author =...

George Harker posted a comment on ticket #198

Agreed, would be great to promote this to a non alpha status as it was a bit freaky after dist-upgrade to fine rpi.GPIO wouldn't install, worked around with a pin to the alpha version, but would be great for folks to not have to do that.

Peter Hansen created ticket #201

Setting up an output should not always disable pulls

Owen Carter posted a comment on ticket #198

November now; Bullseye is released, with python 3.9 as default.. https://forums.raspberrypi.com/viewtopic.php?t=323289 Getting a non-alpha release out asap could be a good idea.

Kjeld Flarup posted a comment on ticket #190

I use Raspberry Pi OS https://www.raspberrypi.com/software/ Funny, I found that python 2 runs, but not python3

Juerg Haefliger posted a comment on ticket #190

Repo of what distro? Also, the upstream kernel is deprecating GPIO control via sysfs, so you might want to look into alternate Python solutions. This is the new world: https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/

Kjeld Flarup posted a comment on ticket #190

When will this reach an official repository. And where can I download the patch?

Max touch created ticket #200

Support Radxa Zero

Nicola created ticket #199

Installing package failed on PyCharm

the_redburn posted a comment on ticket #176

Could you paste the output of tail -n 4 /proc/cpuinfo | grep -v ^Serial ?

the_redburn posted a comment on ticket #171

I can confirm that it's fixed in 0.7.1a4 with Hardware : BCM2711 Revision : c03114 Model : Raspberry Pi 4 Model B Rev 1.4 It wasn't working with 0.7.0

Ness modified a comment on a wiki page

Your Programm runs only once. Try it within a while loop: import time import RPi.GPIO as GPIO GPIO.setwarnings(False) GPIO.setmode(GPIO.BCM) GPIO.setup(17, GPIO.OUT) GPIO.setup(27, GPIO.OUT) GPIO.setup(22, GPIO.OUT) GPIO.setup(16, GPIO.OUT) while True: GPIO.output(16, GPIO.HIGH) GPIO.output(17, GPIO.HIGH) GPIO.output(27, GPIO.HIGH) GPIO.output(22, GPIO.HIGH) time.sleep(2) GPIO.output(17, GPIO.LOW) GPIO.output(27, GPIO.LOW) GPIO.output(22, GPIO.LOW) time.sleep(2) GPIO.cleanup() https://www.tutori...

Ness modified a comment on a wiki page

Your Programm runs only once. Try it within a while loop: import time import RPi.GPIO as GPIO GPIO.setwarnings(False) GPIO.setmode(GPIO.BCM) GPIO.setup(17, GPIO.OUT) GPIO.setup(27, GPIO.OUT) GPIO.setup(22, GPIO.OUT) GPIO.setup(16, GPIO.OUT) while True: GPIO.output(16, GPIO.HIGH) GPIO.output(17, GPIO.HIGH) GPIO.output(27, GPIO.HIGH) GPIO.output(22, GPIO.HIGH) time.sleep(2) GPIO.output(17, GPIO.LOW) GPIO.output(27, GPIO.LOW) GPIO.output(22, GPIO.LOW) time.sleep(2) GPIO.cleanup()

Ness posted a comment on a wiki page

Your Programm runs only once. Try it within a while loop: import time import RPi.GPIO as GPIO GPIO.setwarnings(False) GPIO.setmode(GPIO.BCM) GPIO.setup(17, GPIO.OUT) GPIO.setup(27, GPIO.OUT) GPIO.setup(22, GPIO.OUT) GPIO.setup(16, GPIO.OUT) while True: GPIO.output(16, GPIO.HIGH) GPIO.output(17, GPIO.HIGH) GPIO.output(27, GPIO.HIGH) GPIO.output(22, GPIO.HIGH) time.sleep(2) GPIO.output(17, GPIO.LOW) GPIO.output(27, GPIO.LOW) GPIO.output(22, GPIO.LOW) time.sleep(2) GPIO.cleanup()

Baris Can Yalcin posted a comment on a wiki page

I am having some troubles for signalizing of Raspberry Pi digital pins. Let me explain the problem The thing I was trying to do make a single pin constantly open, and ON-OFF other pins Lets say, GPIO.OUT 16 will constantly be open, meanwhile, the PIN 17, 27 and 22 will be open and close in a sequence import time import RPi.GPIO as GPIO GPIO.setwarnings(False) GPIO.setmode(GPIO.BCM) GPIO.setup(17, GPIO.OUT) GPIO.setup(27, GPIO.OUT) GPIO.setup(22, GPIO.OUT) GPIO.setup(16, GPIO.OUT) GPIO.output(16,...

Christian Krausse modified a comment on ticket #198

Solution found via https://pypi.org/project/RPi.GPIO/0.7.1a4/ Change Log :0.7.1a3 Fix PyEval_InitThreads deprecation warning for Python 3.9 (issue 188) Installing latest Version worked: pip3 install RPi.GPIO==0.7.1a4 --- could be closed ---

Christian Krausse posted a comment on ticket #198

Solution found via https://pypi.org/project/RPi.GPIO/0.7.1a4/ Change Log :0.7.1a3 Fix PyEval_InitThreads deprecation warning for Python 3.9 (issue 188) Installing latest Version worked: pip3 install RPi.GPIO==0.7.1a4

Christian Krausse created ticket #198

Compilation Fails with Python 3.9

Anthony Smith created ticket #197

Callback Function - Strange Behaviour

Shamkin Roman Alexandrovich modified a comment on ticket #161

Ben thanks, that all right!

Shamkin Roman Alexandrovich modified a comment on ticket #161

Ben thanks, that all right, but for new relises ArchlinuxArm-arch64 I made one thing before your installation tips: export CFLAGS="-fcommon" reason here: https://gcc.gnu.org/gcc-10/porting_to.html and then: sudo apt install mercurial $ pip3 install --upgrade hg+http://hg.code.sf.net/p/raspberry-gpio-python/code#egg=RPi.GPIO