Do yourself a favor. Dump Angstrom which is not supported anymore and go
with a newer stock debian image.
People here dont support Angstrom here. It was horrable to begin with.

On 3/18/2017 11:45 PM, 'woody stanford' via BeagleBoard wrote:
>
> Ok, here where I'm at (and I do apologize about the jokes...forgot I
> was on an email server...sorry).
>
> I looked at the various Github solutions and not too impressed with
> them. (Please don't be offended, I'm just saying...to me)
>
> Here is my question to those guys that have done this before. Let me
> bounce this logic off of you and where I am wrong PLEASE feel free to
> correct me. I've just been thinking about it
>
> I have a BBBW Rev C (I think) running stock Angstrom. I go to the
> uEnv.txt file, I make the directory read/write (anyone remember how to
> do this...I'm serious...chmod?) and then I add the overlays starting
> with the lowest one first (so like universela or universeln) then I
> add overlays (like BB_UART) until I'm left with the particular
> configuration I need. Is THIS a correct procedure (or am I like
> totally misunderstanding this approach)?
>
> Then at boot up, it should be configured, right? No BS, just someone
> that has done this before and has put in the time to think about how
> they actually did it.
>
> Thoughts, or is this approach totally cracked?
>
> On Thursday, March 9, 2017 at 5:17:59 AM UTC-7, woody stanford wrote:
>
>     OK, I want to get to the bottom of this whole GPIO issue on the
>     BBB, so I'm opening up this thread as a "documenter" whereby which
>     I can take notes based on my research into how you consistently,
>     stably and SOLIDLY programatically access the GPIO pins on a BBB.
>     I've already done a lot of the footwork so I'm not entirely
>     unknowledgeable, but I want to get to the heart of this issue and
>     solve the mental block people have with this. A private hope.
>
>     Either way, probably a good mess of processed links, articles and
>     information where you can start.
>
> -- 
> 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 [email protected]
> <mailto:[email protected]>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/53822ae9-ef4e-4a9d-8e0c-c77cb4548b86%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/53822ae9-ef4e-4a9d-8e0c-c77cb4548b86%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/bad91179-2e5e-5545-5801-77baa3488602%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to