Ah, apparently google notifications ceased working for me, and it half past whiskey:30, and . . .
Yeah Robert's got you covered. Cheers ;) On Sun, Dec 28, 2014 at 10:49 PM, William Hermans <[email protected]> wrote: > Heya Rick, > > First off let me say that I was exploring kernel 3.14.x myself in this > respect before the holidays, and got "sucked" into doing some remodeling > work for / with a friend who recently sold a house . . . > > Anyway, from what I see in your uEnv.txt file you're only loading an ADC > overlay, on top of the standard *bone-black dtb. Hence why your GPIO pins > are probably not working. However, since you did not say if your > *bone-black.dtb is modified or not . . . yeah, I could not say that 100% > for sure. > > So here is a post by Tom King ( and Panto - IRC nick ) from early on after > release. > > http://elinux.org/BeagleBone_and_the_3.8_Kernel > > There are some differences here now between 3.8.x, and 3.14.x. First of > all, of course we do not have capemgr in 3.14.x, and I *think* we can use > an #include statement in the main overlay to pull in additional overlays. I > am a bit fussy here myself, as before the holidays, this is where I > personally halted my own experiments. Anyway, Robert undoubtedly could > answer this question better than I, but if you look in the main board file > *.dtb you should find examples of #include commented out ( e.g. ##include > ). which should give you a hint. > > Combine that with the link ( informational purposes ) I gave above, and > you *should* be able to modify the main board file to #include a custom > overlay for the GPIO pins you need. > > *However, you seem to be using a 3.8.x kernel ?* > > cape_enable=capemgr.enable_partno=BB-ADC kind of denotes this but let us > say for example you had your pin configs all setup in a file named > *BB-GPIO.*, your enable line would look similar to . . . > > *cape_enable=capemgr.enable_partno=BB-ADC, BB-GPIO* > > Comma separated overlay files . . . > > Also, if you look very closely at the *.dtb files in the /boot/ directory, > you'll see files for various other hardware platforms such as *bone.dtb ( > beaglebone white ), and other hardware platforms that Robert supports with > / for his various build instructions. > > As for the rest of your questions, I would have to defer to someone else > more knowledgeable. Hopefully though the link I gave above would be able to > answer most / all of those questions. > > > On Sun, Dec 28, 2014 at 10:04 PM, Rick Mann <[email protected]> wrote: > >> >> > On Dec 28, 2014, at 19:56 , Robert Nelson <[email protected]> >> wrote: >> > >> > So the ADC is pretty straight forward, for example the proxy cape uses >> > 3 adc channels.. >> > >> > >> https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-bone-basic-proto-cape.dtsi >> > >> > So if you add that node (with the 2 adc channels you need) to: >> > >> > >> https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-boneblack.dts >> > >> > then it's just >> > >> > make >> > sudo make install >> > sudo reboot >> > >> > (this is with the 3.14-ti branch of dtb-rebuilder) >> > >> > The best gpio example is in the argus dtsi >> > >> > >> https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-bone-argus.dtsi >> >> Okay, that seemed to re-enable the ADC, but it killed my GPIOs (which >> were working, actually). I didn't yet try to add a node for the GPIOs. I >> have many questions: >> >> A) What does it mean for all those resulting .dtb files to be in the >> /boot/... directory? Do they all get loaded? Does only the main one >> ("am335x-boneblack")? >> >> B) In the Argus example, all the &ocp/..._pinmux statuses are set to >> "disabled." Wouldn't I want the pinmux to be enabled ("okay")? What does it >> mean to disable the pinmux? >> >> C) Can there be multiple &ocp, &am33xx_pinmux entries? >> >> D) There's a comment on >> https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-bone-argus.dtsi#L56 >> that says the gpio controllers appear to be numbered starting at 1, but >> then list gpio controllers numbered 0. >> >> E) What does "debug" and "shutdown" do? >> >> F) I'm going to add version of each of these ampersand-nodes, and a root >> node, just like the argus ones, replacing "argus_ups" with "podtique", and >> adjusting the pins to what I need. Is that the right approach? That will >> result in am335x-boneblack.dts having multiple root nodes, and multiple >> &ocp and &am335x-pinmux nodes. Eventually, this suggests making a separate >> .dtsi with all the stuff for my cape, and just including it into .dts, >> right? >> >> G) What should my uEnv.txt look like? It currently looks like this: >> http://pastebin.com/3fx5SDb9 >> >> Thanks! >> >> -- >> Rick Mann >> [email protected] >> >> >> -- >> 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]. >> 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]. For more options, visit https://groups.google.com/d/optout.
