I'm missing a "Big Picture" idea here. Let's see if I can ask with right questions.
How can I tell with device tree file my Bone is booting with? Where can I find it's source? How do I compile and install it? Right now I'm trying to get a st7735 SPI-based LCD display working again on my Black. This[1] used to work, but the make no longer works. What do I need to do so this: config-pin -a P9_30 spi # Data out config-pin -a P9_31 spi # Clock will work? First I want it to work on the Black, then on the Blue. --Mark [1] https://github.com/MarkAYoder/BeagleBoard-exercises/blob/master/displays/st7735/install.sh On Saturday, August 5, 2017 at 12:16:29 PM UTC-4, Hugh Briggs wrote: > > I found Jason's hint to be a bit short on explanations, so here is what > Robert Nelson led me through. It is was I reported that I did with a BBB + > Robotic Cape but didn't know if it would work with a Blue. I take Jason's > answer to be yes it will work with a Blue. > On July 11 Robert wrote in my earlier email stream titled "where is > capemgr?" > > It's not a service file, it's the device tree binary: > > > https://github.com/RobertCNelson/dtb-rebuilder/blob/4.4-ti/src/arm/am335x-boneblack-roboticscape.dts#L19 > > > Change: > > #include "am335x-bone-common-no-capemgr.dtsi" > > to: > > #include "am335x-bone-common.dtsi" > > He also led me through how to compile it and boot it, etc. I won't try to > repeat that here from memory. > Then do the usual capemgr boot line directive with partno=BB-ADC > > I still believe that this configuration can live with the rc_* apps and > services, as long as you only use one at a time. > Turns out we haven't been hearing from James (the rc_* creator) on this > because he is way way way out of the county for the summer. > Clark > > > > On Thursday, August 3, 2017 at 9:25:18 PM UTC-7, Jason Kridner wrote: >> >> >> >> On Aug 3, 2017, at 4:57 PM, Mark A. Yoder <[email protected]> wrote: >> >> Sounds like a good idea. How do I turn on the ADC drivers? >> >> >> >> https://github.com/RobertCNelson/dtb-rebuilder/blob/4.4-ti/src/arm/am335x-boneblack-custom.dts#L56 >> >> >> --Mark >> >> On Thursday, August 3, 2017 at 2:45:44 PM UTC-4, Jason Kridner wrote: >>> >>> >>> >>> On Aug 3, 2017, at 2:32 PM, Mark A. Yoder <[email protected]> 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 <[email protected]> >>>>>>> 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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beagleboard/4499e97d-fa44-42a1-a033-fe75ce95c4e9%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/beagleboard/4499e97d-fa44-42a1-a033-fe75ce95c4e9%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> 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]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/df730860-d5e5-4aad-8968-20a5e4188b50%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beagleboard/df730860-d5e5-4aad-8968-20a5e4188b50%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/ba829155-a6c9-44ae-9ee6-b1ae72755f8b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
