On Tue, May 16, 2017 at 7:41 PM, <[email protected]> wrote: > I've been a C and assembly programmer since the 80's, but all of this with > dtc is still pure greek to me. > I'm assuming the original intent was to install the latest git version of > the dtc compiler, though I'm not sure what implications the sed command > has, so I'd defer to you or the OP's opinions. >
Well device tree overlay source files are not C, or assembly either. Although, you can use C syntax highlighting in your text editor of choice to make your life easier. I tend to view overlay source files more as something like xml, or some form of a markup language. Understanding the source files though just takes time, and knowledge of how pin-muxing, and several hardware aspect on this platform works. How, I learned how the source files work, was to take one of the Universal IO overlay source files, and deleted everything in it except the main structure, and a single pin. At this point, you see all the different modes a pin can function as, and things become a bit clearer. It also helps to understand the hardware that you're trying to configure. Some of the simpler overlay source files such as for RTC, or 1-wire. Studying these should help one understand some things too. Such as how to load a driver from an overlay file, or how to configure an I2C device bus address from an overlay file. In the end it just takes time. -- 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/CALHSORrjJt67g5Y-g3zNJC0cOk76Uf%2BvjWZ2yLQpCqRw8Ub2Gw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
