Thanks! I don't intend to use any "real" capes, just a proto cape to make it easier to solder wires to it. I might add some voltage regulators, etc. But for testing the ADC, it's enough to stick the wires off a potentiometer into the pin sockets.
Someday, I want to make a proper cape with audio output and amplifier capable of driving small speakers, but for now I just need to get to where I can read the ADC. I've got a neat project idea that's stalled until then, and I need to finish it by the end of the year. (The remaining issue I have has to do with audio glitces, no idea how to track that down, and I haven't found any helpful forum online.) Do you think libpruio will be able to work with your changes? > On Dec 11, 2014, at 15:08 , William Hermans <[email protected]> wrote: > > Rick, i'm going through the whole process my self right now. For the first > time. I'm confident I'll be able to get all the info you need so you should > be able to step by step copy paste setup. > > However, what I am not sure of is exactly what all is enabled as this point > in time cape wise. ADC, I2C, UARTs, PWM, etc. But I can experiment some, and > show you how to experiment too in the process, As an aside, I have no > circuitry or physical capes to test much, but I should be able to provide > enough information for you to learn how to do this on your own ( beaglebone > side ). Then if you have physical circuitry on hand, you should be golden. > > Right now, im dding the console image to an sdcard, next step is booting it > up, and upgrading to 3.14.x via APT. My notes thus far as very verbose, so > should show others who are unfamiliar with the process of experimentation how > it is done. At least how I do it. > > On Thu, Dec 11, 2014 at 3:46 PM, Rick Mann <[email protected]> wrote: > > > On Dec 10, 2014, at 05:49 , Robert Nelson <[email protected]> wrote: > > > > On Wed, Dec 10, 2014 at 2:41 AM, Rick Mann <[email protected]> wrote: > >> What's the current way to access the analog input ADC values? Everything I > >> find online refers to capemanager, which apparently no longer exists. At > >> least, there's no capemgr under /sys in my Debian/3.14.22 system. > > > > > > http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Custom_dtb > > > > See this example: > > > > https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-bone-basic-proto-cape.dtsi#L12 > > > > Location of the analog outpus are the same in userspace as in 3.8 > > Thanks for this, Robert. I've been poking at it since yesterday, and I'm not > at all sure I understand what I need to do. I built the dtbs from your repo. > Is it enough to copy the am335x-boneblack.dtb (its .dts includes the proto > cape example .dtsi), and update uEnv.txt to point to that? > > -- > 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. -- 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.
