RPi.GPIO python module for Pine A64/A64+

[jacobscarter]

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?

[martinayotte]

Ubuntu with longsleep kernel.

[MarkHaysHarris777]

http://wiki.pine64.org/index.php/Main_Pa...eep_kernel

The lenny.raposo image (debian) with the Longsleep kernel works straight-away also... no problems.

[respawned]

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_A6...0415_image

[greenleafthered]

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.

[editor]

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:
   

[xalius]

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

[Wolfenstein]

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)

I have this setup
http://imgur.com/a/HjjuE
and I get nothing but "0" in the console.

[MarkHaysHarris777]

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

[Wolfenstein]

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?t...8#pid17268

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.