> On Aug 3, 2017, at 2:32 PM, Mark A. Yoder <mark.a.yo...@gmail.com> wrote: > > It looks like when the Blue comes out of the box, running a current image > it's all set up to run the Robotics stuff. You can access the ADCs, servos, > etc. through the robot interface. > > When I teach my Embedded Linux class I would also like my students to access > the ADCs, PWM, etc in the Linux way. > > How do I configure the Blue to boot up in "Embedded Linux" mode rather than > "Robot Linux" mode?
If we get the integration right, IMO, we'll boot up so that we can use the Linux userspace interfaces and the libroboticscape interfaces. The libroboticscape setup should do whatever is needed to disable Linux kernel drivers at runtime in order to enable its userspace accesses. Turn on the ADC kernel drivers and look how libroboticscape fails. Then, report that as a bug. > > --Mark > > >> On Wednesday, August 2, 2017 at 11:15:40 AM UTC-4, Mark A. Yoder wrote: >> It sounds like I can either have a Blue that boots as a robot, or boots as >> an embedded processor, but not both at the same time. >> I need to see what it would take to remove the ADC from the robots control. >> >> --Mark >> >>> On Tuesday, August 1, 2017 at 4:57:09 PM UTC-4, Hugh Briggs wrote: >>> I have lived on BBB + Robotics Cape in James' world for some time. While I >>> haven't done this with a Blue, I suspect what I did can work there too. I >>> did do his installation (for a Rev C BBB and a Rev D Robotics Cape). With >>> Robert's help I put the Capemgr back in the DTs and added the capemgr >>> partno boot line for BB-ADC. This seems to be a workable combination of >>> the two worlds. My premise is that I don't try to do both at once. That >>> is, I don't run any of the rc_* apps or services while trying to read the >>> ADCs from /sys/bus/iio. So far it seems to work for me. >>> Hugh >>> >>>> On Monday, July 31, 2017 at 11:44:09 AM UTC-7, Mark A. Yoder wrote: >>>> Yup, this is the Blue. >>>> In there short term is there an easy way to turn off the robotics stuff >>>> and get easy access to the analog in? >>>> >>>> In the long term, what will it take to convert James' robot stuff to >>>> libiio? I might take a shot at it if it isn't too hard. >>>> >>>> --Mark >>>> >>>>> On Friday, July 28, 2017 at 5:56:30 PM UTC-4, RobertCNelson wrote: >>>>> On Fri, Jul 28, 2017 at 4:40 PM, Mark A. Yoder <mark.a...@gmail.com> >>>>> wrote: >>>>> > How do I read AIN on the latest images? I don't know where to find it >>>>> > in >>>>> > /sys/ >>>>> >>>>> Hi Mark, >>>>> >>>>> This is with the Blue right? >>>>> >>>>> James' got the ADC tied up in mmap for the Robotic's cape library.. >>>>> >>>>> https://github.com/StrawsonDesign/Robotics_Cape_Installer/blob/master/libraries/mmap/rc_mmap_gpio_adc.c >>>>> >>>>> >>>>> We need to convert his library to use libiio, then we can just enable >>>>> the ADC's as an iio device and share usage with the library.. >>>>> >>>>> https://analogdevicesinc.github.io/libiio/ >>>>> >>>>> Regards, >>>>> >>>>> -- >>>>> Robert Nelson >>>>> https://rcn-ee.com/ > > -- > 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/4499e97d-fa44-42a1-a033-fe75ce95c4e9%40googlegroups.com. > 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/F2C0A1E5-41EB-4E40-9431-A933D69ECAD7%40gmail.com. For more options, visit https://groups.google.com/d/optout.
