Quote:
Originally Posted by pmknkaek
My issue is that I don't know exactly how to interact with the GPIO on this particular device.
|
As previous written, if you use Linux then a lot of the hardware complexity will be abstracted.
The software differences between the RPi using Linux and the OrangePi using Linux is not that great.
The real problem is that there is a RPi (hobbyist) jargon that conflicts with Linux kernel (professional) jargon.
You need to be aware that Linux "gpio" has a specific meaning that does not mesh identically with how RPi users (and probably hobbyists in general) use the term "GPIO".
The Linux kernel makes a distinction between pins (of the SoC) and gpio.
A pin can be assigned for use by a peripheral device (through pin multiplexing during kernel initialization). That pin is then no longer a "gpio" (actually the pin never was a "gpio").
A pin that is not assigned to any peripheral device (after boot is complete) becomes a gpio. The pool of available gpios is a managed resource, i.e. a driver or program can acquire a gpio, and then releases it when done (just like a memory buffer).
So technically (or more accurately) "
interact with the GPIO" would mean input or output using simple digital (i.e. TTL) signal.
Connecting to the UARTs and SPI and TWI interfaces on the 40-pin header involves pinmuxing, and not "
GPIO".
Quote:
Originally Posted by pmknkaek
... as well as scour github for something that might work with this
|
Instead of "
github" learn how to use
Google.
There are resources out there if you bother to look.
Regards