On Thursday, September 12, 2019, 5:43:13 AM EDT, Richard Miller
<9f...@hamnavoe.com> wrote:
> > Do you also need the man pages for i2c and
> > spi, or did I send those the first time around?
>
> If you sent them, they must have gone astray ... if you can
> supply a new copy, I'll add them to the
> Do you also need the man pages for i2c and
> spi, or did I send those the first time around?
If you sent them, they must have gone astray ... if you can
supply a new copy, I'll add them to the image too. Thanks!
On Tuesday, September 10, 2019, 12:21:32 PM EDT, Richard Miller
<9f...@hamnavoe.com> wrote:
> Thanks Brian, I'll add your man page to the 9pi image for the
> next update.
You're welcome. Do you also need the man pages for i2c and
spi, or did I send those the first time around?
Thanks,
BLS
Thanks Brian, I'll add your man page to the 9pi image for the
next update.
On Tuesday, September 10, 2019, 10:27:08 AM EDT, Олег Бахарев
wrote:
> Need man page for this.
My bad. I thought I had sent man pages along with the
code. I've included the man page for it at the bottom of
this message.
> Can you get some example for reading/writing GPIO ?
I've also included
Need man page for this.
Can you get some example for reading/writing GPIO ?
сб, 7 сент. 2019 г., 16:46 Richard Miller <9f...@hamnavoe.com>:
> > How to get access to RPi 2 GPIO ?
>
> bind -a '#G' /dev
>
> Reading from /dev/gpio gives a 16-character big-endian hex string
> with current values of
> How to get access to RPi 2 GPIO ?
bind -a '#G' /dev
Reading from /dev/gpio gives a 16-character big-endian hex string
with current values of gpios 63-0.
Writing commands like 'function 17 out' and 'set 17 1' to /dev/gpio
will change functions and outputs.
Sorry there doesn't seem to be a man
How to get access to RPi 2 GPIO ?
