Haha, excellent progress, it sounds like. My app reads ADCs (and eventually some GPIO), and outputs sound. I will also like to output PWM to control some LEDs. Right now I'm reading the ADCs using open/read calls, which is fine (I only need to read them at 10 Hz; they're knobs for a human to turn). I hope I can write to an fs-based PWM node to establish a PWM.
> On Dec 11, 2014, at 22:39 , William Hermans <[email protected]> wrote: > > Nodejs is really good if you need a web server for an appliance like > situation. I use C too for various things, but when I need the information > displayed or something configurable over a network, Nodejs is how I prefer to > do that. > > Anyway, I'm not a Javascript salesman so . . . By default after using APT to > install linux-image-3.14.26-ti-r39 and glossing over Charles' git > instructions. I can see that universal io is there, but config-pin is not. > Still, there are ways around this, and assuming I'm not missing something. > you can use the sysfs to change the state of these pins. Which means, if > you're using C, it would only take a simple setup section in your code to get > everything you want and that is available setup correctly. That is really > nifty. > > As to using pruiio, I'm not 100% positive, but it seems so long as you have > the dtb file, you could *potentially* > > • drop the file into /boot/dtbs/3.14.26-ti-r39/ > • De compile am335x-boneblack.dtb > • Add an #include statement for the pruiio file > • Recompile am335x-boneblack.dtb > • rename / copy the fie into /boot/dtbs/3.14.26-ti-r39/ > • modify dtb=<your_new_dtb_file_here> in /boot/uEnv.txt > • reboot. > Of course I have not tested this yet, so I can not say 100% either way until > I test it myself. Someone else however( Robert ) would probably have a good > idea on if this would work or not. > > Anyway, I'm entertaining myself here exploring / experimenting . . . so it's > all good. > > " . . . At least they're not playing <dramatic pause > computer games . . ." > Name that quote ;) > > > On Thu, Dec 11, 2014 at 6:07 PM, Rick Mann <[email protected]> wrote: > Yeah, I don't use bonescript or node.js, either. It's all C++ for me. > > I downgraded to the 3.8 kernel (didn't even know you could just do that) > using apt-get. Not only am I able to access the ADC via the old information > available online, I can also play back audio without the buffer-underrun > glitches I was experiencing with 3.14. I'm very appreciative that you're > taking the lead on getting the ADC to work with the later kernel, but until I > can fix the audio problem with it, I'm going to stick with 3.8. > > > > On Dec 11, 2014, at 15:48 , William Hermans <[email protected]> wrote: > > > > Technically anything that is accessible from sysfs should be accessible via > > Nodejs. I dont know what all Jason does with bonescript, I shy away from it > > as its just another abstraction layer I personally do not need. I use > > "stock" Nodejs, and have not done much with it yet, but am able to execute > > a binary that queries a USB thermometer, and spit that information out to a > > local network webpage via socket.io. > > > > On Thu, Dec 11, 2014 at 4:25 PM, Rick Mann <[email protected]> wrote: > > > > > On Dec 11, 2014, at 15:08 , William Hermans <[email protected]> wrote: > > > > > > what I am not sure of is exactly what all is enabled as this point in > > > time cape wise. ADC, I2C, UARTs, PWM, etc. > > > > Is it possible to test these things from bonescript? It seems like it's > > able to enable these things, but I don't really understand how it all fits > > together. I know of at least one reference online that uses the bonescript > > repo as the authoritative source for device descriptions. > > -- > > 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. > > > -- > 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.
