After reading lots of stuff I have what I thought might work.
Segments from my .dts
exclusive-use =
"p9.25"; /* R30[7] */
fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
mygpio: pinmux_mygpio{
pinctrl-single,pins = <
0x1AC 0x25 /* P9.25 mode 5 pulldown output */
>;
};
};
};
If I do nothing in my pru code this pin is always high even after I reboot
the bbb.
I tried
CLR R30.T7
and the pin still remained high.
Is there something else I need to do.
On Tuesday, October 7, 2014 4:00:44 AM UTC-7, Charles Steinkuehler wrote:
>
> On 10/7/2014 12:39 AM, Ray Madigan wrote:
> >
> > I am currently using pru0 simply because it is before pru1. Is there a
> > drawback to using pru1 over pru0.
>
> The two PRU cores are identical, other than the external pins they are
> tied to for direct I/O. Choose the PRU core to use based on the pins
> you want, or if you're not using direct I/O it doesn't matter which core
> you choose.
>
> --
> Charles Steinkuehler
> cha...@steinkuehler.net <javascript:>
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
