oops, https://github.com/wphermans/bb-info is the top most path . . .
On Sat, May 20, 2017 at 6:27 PM, William Hermans <yyrk...@gmail.com> wrote: > By the way these are my own preffered "pin mux mode" "spread sheet" PDF > files for working with various pins: https://github.com/wphermans/ > bb-info/blob/master/BeagleboneBlackP8HeaderPinMuxModes.pdf > > I do not recall who made these, but links in the PDF's themselves lead > back to who created them. Whom also derived the information in these files > from Derrek Molloy. > > So I do not claim the material at all. I just wanted a location that was > easy for me to find, and would never go away. My git seemed to be as good a > place as any, for me. > > On Sat, May 20, 2017 at 6:14 PM, William Hermans <yyrk...@gmail.com> > wrote: > >> Greg, >> >> You know what. If I were you, I would get a Beaglebone black or green, >> and make learning about it your favorite hobby. This way, you could >> experiment with various things, until you're happy with what you end up >> using. >> >> If memory is serving me correctly yes, you're using a blue. Yes, yes, but >> the hardware is largely the same, and most if not all the software will be >> exactly the same. >> >> So yes, buy a beaglebone, take it home, and start experimenting. Then I >> would probably not worry about HAVING to have hardware connected up with >> it. There is a lot you can do by experimenting with software only. How, and >> where to explore the GPIO subsystem. Which will then lead to being able to >> tell if you've configured your overlay file at boot correctly. etc, etc. >> >> On Sat, May 20, 2017 at 6:01 PM, Gerald Coley <gcol...@emprodesign.com> >> wrote: >> >>> I decided not to copy what was in the TRM into the SRM. That is why the >>> SRM is specific to the BBB. And the TRM gets updated failry often by TI. >>> >>> >>> >>> Gerald >>> >>> >>> >>> >>> >>> *From:* beagleboard@googlegroups.com [mailto:beagleboard@googlegrou >>> ps.com] *On Behalf Of *William Hermans >>> *Sent:* Saturday, May 20, 2017 8:00 PM >>> *To:* beagleboard@googlegroups.com >>> *Subject:* Re: [beagleboard] Re: Surefire PRU - Setup. >>> >>> >>> >>> System reference manual SRM, Technical reference manual TRM. >>> >>> >>> >>> On Sat, May 20, 2017 at 5:58 PM, William Hermans <yyrk...@gmail.com> >>> wrote: >>> >>> No, prior to uboot overlays, overlays were loaded from the initrd, at >>> best. Also we need to understand that the board file(also an overlay of >>> sorts - but required )is seperate from all this discussion. >>> >>> I do not understand why you would have "field people" playing around >>> with hardware overlays though. Once your hardware is finalized, it should >>> never change. Which is one small reason why I personally find Universal IO >>> unnecessary for my own purposes. >>> >>> The problem I've seen with explanations, and documentation on device >>> tree, is that no one explains it really well. Additionally, as a new player >>> into device tree overlays. Its not clear where to get information from. >>> See, you need to understand the pin-ctrl subsystem, gpio subsystem . . . >>> list goes one, and on . . .A lot of this information has to be found from >>> the Linux kernel source documentation.HOWEVER, you do not necessarily need >>> to memorize all of this. We ( programmers ) just need a reference that does >>> not goes on, and on for days about silly details we do not need to know to >>> get our jobs done. Nothing like this exists. >>> >>> Anyway, in order to learn, you need to "do". >>> >>> >>> >>> -- >>> 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. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/beagleboard/CALHSORrAaF4Z%2B%3DUZRq%2Bi_oMFRM_K88noC7y5D >>> %3D9MQAkeRUovrw%40mail.gmail.com >>> <https://groups.google.com/d/msgid/beagleboard/CALHSORrAaF4Z%2B%3DUZRq%2Bi_oMFRM_K88noC7y5D%3D9MQAkeRUovrw%40mail.gmail.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 beagleboard+unsubscr...@googlegroups.com. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/beagleboard/a67232f2a5a94c10abc16cc8ff83aa70%40winhexbeu >>> s11.winus.mail >>> <https://groups.google.com/d/msgid/beagleboard/a67232f2a5a94c10abc16cc8ff83aa70%40winhexbeus11.winus.mail?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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORo_%2B6M3PBu%3Dtgzjo-Tw40N5FMCL45sig%3DN6kgJPee-TkQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
