+- PINE64 (https://forum.pine64.org)
+-- Forum: PINE A64(+) (https://forum.pine64.org/forumdisplay.php?fid=4)
+--- Forum: Pine A64 Hardware, Accessories and POT (https://forum.pine64.org/forumdisplay.php?fid=32)
+---- Forum: Pi2, Euler and Exp GPIO Ports (https://forum.pine64.org/forumdisplay.php?fid=34)
+---- Thread: RPi.GPIO python module for Pine A64/A64+ (/showthread.php?tid=723)
RE: RPi.GPIO python module for Pine A64/A64+ - jacobscarter - 06-19-2016
(06-19-2016, 07:56 AM)martinayotte Wrote: In my case, RPi.GPIO-PineA64 worked out of the box using "python setup.py install", nothing else to do.
Beware that pyA20 doesn't use the same pins for A64, so some GPIOs are working but some other won't or simply not defined.
Hmm okay. Maybe it's time to try a fresh OS. What kernel version are you running on the OS that RPi.GPIO for Pine is working on?
RE: RPi.GPIO python module for Pine A64/A64+ - martinayotte - 06-19-2016
Ubuntu with longsleep kernel.
RE: RPi.GPIO python module for Pine A64/A64+ - MarkHaysHarris777 - 06-20-2016
http://wiki.pine64.org/index.php/Main_Page#Debian_Linux_Jessie_with_Mate_GUI_Image_.5B20160508.5D_by_lenny.raposo_with_Longsleep_kernel
The lenny.raposo image (debian) with the Longsleep kernel works straight-away also... no problems.
RE: RPi.GPIO python module for Pine A64/A64+ - respawned - 06-20-2016
Thanks for the help.
After installing the GCC compiler everything worked.
I am using the OpenHAB image based on Ubuntu Linux Longsleep 20160415, which does not seem to work with the GPIO Python library out-of-box:
http://wiki.pine64.org/index.php/Pine_A64_Software_Release#openHAB_Image_base_on_Ubuntu_Linux_Longsleep_20160415_image
RE: RPi.GPIO python module for Pine A64/A64+ - greenleafthered - 07-09-2016
Thank you for this thread. Between this and some posts on using the GPIO on a Raspberry Pi I got what I was trying to do working without too much frustration.
RE: RPi.GPIO python module for Pine A64/A64+ - editor - 07-10-2016
I tried to use the RPi GPIO script with OpenOCD to connect it with an ARM STM32 microcontroller, however OpenOCD can't find it. It is a adapter interface for Pine A64 like the bcm2835gpio interface, right?
Screenshot of putty output:
.cfg file for OpenOCD:
RE: RPi.GPIO python module for Pine A64/A64+ - xalius - 07-10-2016
If that OpenOCD driver uses the GPIO hardware directly (looks like it since there is a base address define), it will be different on the Pine and you have to look at how to port the GPIO driver for the bcm2835 to the A64 since the registers are also different... I prefer FTDI based JTAG adapters that implement the electrical part in hardware...
RE: RPi.GPIO python module for Pine A64/A64+ - Wolfenstein - 08-09-2016
I use this code
Code:
import RPi.GPIO as GPIO
GPIO.setmode(GPIO.BOARD)
GPIO.setup(3, GPIO.IN)
while True:
print GPIO.input(3)http://imgur.com/a/HjjuE
and I get nothing but "0" in the console.
RE: RPi.GPIO python module for Pine A64/A64+ - MarkHaysHarris777 - 08-09-2016
You will need to provide an external pull-up resistor 4.7k to 3v3...
...that will give you '1' unless you ground the pin (on the pin side of the 4.7k resistor.
Or, you can define the input as having a pull-up and then the pull-up will be internal.
PS you can experiment with 'strong' or 'weak' pull-up resistors, anything from 1k to 10k, the higher the number, the weaker the pull-up.
PSS I too will experiment with pin(3) GPIO02 as input... on debian... will get back to you soon
RE: RPi.GPIO python module for Pine A64/A64+ - Wolfenstein - 08-09-2016
(08-09-2016, 02:30 PM)MarkHaysHarris777 Wrote: You will need to provide an external pull-up resistor 4.7k to 3v3...
...that will give you '1' unless you ground the pin (on the pin side of the 4.7k resistor.
Or, you can define the input as having a pull-up and then the pull-up will be internal.
PS you can experiment with 'strong' or 'weak' pull-up resistors, anything from 1k to 10k, the higher the number, the weaker the pull-up.
PSS I too will experiment with pin(3) GPIO02 as input... on debian... will get back to you soon
http://forum.pine64.org/showthread.php?tid=62&pid=17268#pid17268
(08-03-2016, 08:29 PM)MarkHaysHarris777 Wrote: hi Wolfenstein, when I code for a pull-up on an input pin ( I'm going to put a switch on it that pulls to ground ) then I leave it with the internal pull-up ( why use an additional component if not needed ).
Now you are confusing me.