Activity for Ben Croston
-
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.
-
Is the PTT an output from direwolf?
-
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?
-
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?
-
Missing "Python.h"
-
Shouldn't __sync_synchronize() be used after writes and before IO reads ?
-
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?
-
Support Radxa Zero
-
The radxa zero is not a Raspberry Pi and uses a completely different SOC so it will never be supported by this library.
-
Installing package failed on PyCharm
-
RPi.GPIO is not designed to be compiled or run on Windows
-
Not running on a RPi! on Pi4B running AWS Greengrass
-
This is part of Python itself, not RPi.GPIO. Have you got the Python development packages installed on your distro?
-
Misidentifying board type
-
Fixed in 0.7.1
-
"Not running on a RPi" message from GPIO.setup(id, GPIO.IN) on new RPi4B
-
Fixed in 0.7.1
-
compilation warning on python 3.9 and gcc 10
-
Fixed in 0.7.1
-
Compilation Fails with Python 3.9
-
Fixed in 0.7.1
-
Compilation Fails with Python 3.9
-
Fixed in 0.7.1
-
64bit This module can only be run on a Raspberry Pi!
-
Fixed in 0.7.1
-
/proc/cpuinfo identification needs updates for RPi 4
-
Fixed in 0.7.1
-
Release 0.7.1
-
Added tag 0.7.1 for changeset f8d556afd9b0
-
Unable to install via pip on Arch Linux ARM (Raspberry Pi 4)
-
This should be fixed in the latest alpha version. To install: pip install --pre RPi.GPIO
-
"Not running on a RPi" message from GPIO.setup(id, GPIO.IN) on new RPi4B
-
I've changed the board detection method in 0.7.1a4. Does it work now?
-
64bit This module can only be run on a Raspberry Pi!
-
Fixed i n 0.7.1a4
-
Better RPi board + peri_addr detection (issue 190 / 191)
-
/proc/cpuinfo identification needs updates for RPi 4
-
Fixed in 0.7.1a4
-
Added to 0.7.1a4
-
Add support for Pi 4B 8GB, Pi 400 and CM4
-
Deprecattion warning when building with Python 3.9
-
Fixed in 0.7.1a3
-
Fix PyEval_InitThreads deprecation warning for Python 3.9 (issue 188)
-
Compilation error on gcc-10
-
Fixed in 0.7.1a2. To install and test: $ pip3 install --upgrade --pre RPi.GPIO
-
Fix build using GCC 10 (issue 187)
-
- Fix docstrings to not include licence
-
A few questions: what user is your script running as? is RPi.GPIO installed for that user? What version of Python are you using? is RPi.GPIO installed for that version of Python?
-
Does it work with other pins? Does it work after rebooting?
-
Does it work with other pins?
-
What is the result of: import RPi.GPIO as GPIO print(GPIO.VERSION)
-
What is the result of: import RPi.GPIO as GPIO print(GPIO.VERSION
-
Installation fails with python 3.8.5 in archlinux
-
This seems to be the same problem as #187 - making as a duplicate.
-
Deprecattion warning when building with Python 3.9
-
Have reproduced the problem using Raspbian Buster and gcc-10.1.0.
-
Compilation error on gcc-10
-
Unable to import module, update cpuinfo?
-
Support 64bit systems
-
Duplicate of issue #161.
-
docker support
-
Which distro are you using? Is it 64 bit?
-
Also: $ hexdump /proc/device-tree/system/linux,revision
-
What do you get when you: $ cat /proc/device-tree/system/linux,revision
-
What version of RPi.GPIO are you using?
-
Sounds like you may have a borderline power problem with your circuit using close to what a GPIO pin or power supply can handle. Using too much current for GPIO can starve the SOC of power causing reboots.
-
Sounds like you may have a borderline power problem with your circuit using close to what a GPIO pin can handle. Using too much current for GPIO can starve the SOC of power causing reboots.
-
Make raspberrypi-sys-mods a dependency of Raspbian Buster packages
-
aarch64: Add kernel detection support
-
In release 0.7.0
-
This module can only be run on a Raspberry Pi!
-
In release 0.7.0
-
failing to mmap() causes segfault due to wrong cast
-
In release 0.7.0
-
Pullups not working on Pi 4
-
In release 0.7.0
-
Release 0.7.0
-
Added tag 0.7.0 for changeset b51ae5efb17b
-
Fixed pull up/down for Pi4 (issue 168) - 0.7.0a2
-
Alpha release is now available for testing: pip3 install --upgrade --pre rpi.gpio
-
Alpha release is not available for testing: pip3 install --upgrade --pre rpi.gpio
-
Detect Pi 4B in RPI_INFO
-
Hopefully I'll get my hands on a Pi4 tomorrow to test and make a release. Thanks for the patch!
-
I've changed the if condition in the code. Does it still need iomem=relaxed? You can get the development version to test it: $ sudo apt install mercurial $ sudo pip3 install hg+http://hg.code.sf.net/p/raspberry-gpio-python/code#egg=RPi.GPIO
-
Fix checking mmap return value in c_gpio.c (issue 166)
-
The patch has been included and modified because it broke the detection of early boards. Could you please test the latest development copy on aarch64 and confirm that it works. The commands to install it will be something along the lines of: $ sudo apt install mercurial $ pip3 install --upgrade hg+http://hg.code.sf.net/p/raspberry-gpio-python/code#egg=RPi.GPIO
-
The patch has been included and modified because it broke the detection of early boards. Could you please test the latest development copy on aarch64 and confirm that it works. The commands to install it will be something along the lines of: $ sudo apt install mercurial $ pip3 install --upgrade hg+http://hg.code.sf.net/p/raspberry-gpio-python/code#egg=RPi.GPIO
-
Fix board detection for aarch64 (issues 161 / 165)
-
- Tested and working on Raspbian Buster / Python 3.8.0a1
-
Release 0.6.5
-
Added tag 0.6.5 for changeset a61764b2ba4b
-
Don't export GPIO to /sys/class/gpio if it already exists
-
reuse pwm objects
-
Fix several warnings in C extensions
-
Software PWM stopped working after hundreds start/stop cycles
-
soft pwm make memory leak, add pthread_detach() to pwm_start() may fix it.
-
Switching between PWM and plain fails
-
Release 0.6.4
-
Added tag 0.6.4 for changeset 5a09630ab01b
1 >
