The kernel is doing what a kernel does, manager of the resources!
Try this in a terminal:
config-pin -h
Here's an example usage:
config-pin P9.14 low_pd
That set header pin P9.14 to a GPIO direction output and set to LOW and
with pull-down resistor.
It works great!
Use this extremely useful
That's /boot/uEnv.txt, typo above.
On Sun, May 28, 2017 at 11:57 PM, William Hermans wrote:
> First, you disable universal IO, second, if you do not need hdmi, you
> disable hdmi video, and audio at boot. Through /boot.uEnv.txt. This will
> free up any pin that's not related
First, you disable universal IO, second, if you do not need hdmi, you
disable hdmi video, and audio at boot. Through /boot.uEnv.txt. This will
free up any pin that's not related to I2C-0, I2C-2, the eMMC, and possibly
a few others I'm not thinking of off the top of my head.
On Sun, May 28, 2017
Charles Steinkuehler says the new kernels use memory management to lock
access to the pinmux registers. This certainly matches the symptoms I am
getting. Hopefully, he can tell me how to use config-pin to set it up.
Jon
--
For more options, visit http://beagleboard.org/discuss
---
You
OK, GPIOs 45 to 47 are available and work. So, far, none of the other
GPIOs I've tried work, as they seem to be assigned to other mode
selections. The export and direction files don't seem to change the pinmux
setting.
Is there some utility that can change the pinmux assignment, so I can set
On Sunday, May 28, 2017 at 7:50:01 PM UTC-5, William Hermans wrote:
>
>
>
>
>
> What I'd do in your shoes is just use the sysfs gpio file structure to set
> your pins how needed. You do not technically need to load anything from a
> device tree file if all you're using is GPIO. Well any
Since I can't get the devicetree working on the 4.4.62 kernel, I'm trying
to set the GPIO pin configuration directly. I did this on the Beagle Board
a long time ago, and am trying to adapt that code.
So, I have this code :
int fd = open("/dev/mem", O_RDWR | O_SYNC);
volatile ulong