RPi.GPIO python module for Pine A64/A64+

[MarkHaysHarris777]

Yes, that's the one. So far I've just used it to blink LED's. This is my first attempt at trying to work with I2C. I wonder if there's some sample code that I could look at somewhere.

Your first attempts at i2c will be frustrating ( usually is ).

... first step is to place the device on your system, and then see if the i2c tools can see it;  does it show up and is its address what you expect?

[martinayotte]

Since I'm running Armbian, I'm using /dev/i2c-1 instead of /dev/twi1.
But here is some code I'm using to make some LEDs flashing on an MCP23017 :

Code:

#!/usr/bin/env python

import sys, time
from RPi import I2C as i2c

i2c.init("/dev/i2c-1")
i2c.open(0x20)
i2c.write([0x00, 0x00])
i2c.write([0x01, 0x00])
while True:
    i2c.write([0x12, 0x0F])
    i2c.write([0x13, 0x0F])
    time.sleep(0.15)
    i2c.write([0x12, 0xF0])
    i2c.write([0x13, 0xF0])
    time.sleep(0.15)

[psychedup]

Since I'm running Armbian, I'm using /dev/i2c-1 instead of /dev/twi1.
But here is some code I'm using to make some LEDs flashing on an MCP23017 :

Code:

#!/usr/bin/env python

import sys, time
from RPi import I2C as i2c

i2c.init("/dev/i2c-1")
i2c.open(0x20)
i2c.write([0x00, 0x00])
i2c.write([0x01, 0x00])
while True:
    i2c.write([0x12, 0x0F])
    i2c.write([0x13, 0x0F])
    time.sleep(0.15)
    i2c.write([0x12, 0xF0])
    i2c.write([0x13, 0xF0])
    time.sleep(0.15)

Thanks, I found the problem thanks to your example. I was trying to open "/dev/twi1" which didn't exist. It's /dev/i2c-1. For some reason when I run i2cdetect or i2cdump they want me to use twi1 as an alias to /dev/i2c-1 so I got them mixed up.

Now it is reading from the device. I just have to figure out what to do with the results

Thanks for your help.

[islas.f]

Hello, I have an error when I include RPi.GPIO in my python script which includes a GUI. Error says
"cannot access to /dev/mem/" I read running as root this error is solved but if I run my script as root from the shell I get the next error "cannot connect to X server". I have read and try many options but none has work. Could you give some guidance?

[martinayotte]

you can change permission on /dev/mem by doing "sudo chmod a+rw /dev/mem", and then you application should be able to access it.

[islas.f]

you can change permission on /dev/mem by doing "sudo chmod a+rw /dev/mem", and then you application should be able to access it.

It doesn't work for me, still the same error. Any other idea? ... Thanks

[www139]

I just ported RPi.GPIO python module for Pine A64/A64+.
You can download the package from https://github.com/swkim01/RPi.GPIO-PineA64.
Thank to joey for gpio pin information.
However, the event detect function was not operated yet.
I guess the kernel's gpio driver has to be modified to enable gpio interrupts.

Will this work with the Rock64?

[i69fstop]

I just ported RPi.GPIO python module for Pine A64/A64+.
You can download the package from https://github.com/swkim01/RPi.GPIO-PineA64.
Thank to joey for gpio pin information.
However, the event detect function was not operated yet.
I guess the kernel's gpio driver has to be modified to enable gpio interrupts.

Will this work with the Rock64?

@www139, I don't think it will work, would love some community expert to port this for Rock64.

[psychedup]

I got a Nokia 5110 LCD module from Sparkfun (here), wired it up to my pineA64+ and was able to use this library to make it work over SPI (happy to share how I did it if anybody's interested).

It works just fine, but everytime I call SPI.write(), besides writing to the device it also dumps the values to the console. This was nice for debugging, but is there a way to make it quieter?

Thanks,
Chris

[xalius]

Are you using spidev?