Thanks guys, I'll keep an eye on the repository and grab a copy once things 
are finalised.

On Wednesday, 10 May 2017 15:29:22 UTC+1, RobertCNelson wrote:
>
> I just pushed another sync up: P8_31 was mising ecap. ;) 
>
>
> https://github.com/beagleboard/bb.org-overlays/commit/6197c268c1b875a2c066635413c9742b720762bc
>  
>
> I'm going to do a quick space -> tab conversion on cape-universal*.dts 
> as i need to also sync all the eqep options with 12 or so 
> univ-<board>-<enable>.dts 
>
> Regards, 
>
> On Wed, May 10, 2017 at 9:01 AM, Drew Fustini <[email protected] 
> <javascript:>> wrote: 
> > I actually ran into this too recently and have modified 
> > cape-universala-00A0.dts to enable pins P8_33 and P8_35 for eqep1: 
> > https://github.com/beagleboard/bb.org-overlays/pull/46 
> > 
> > Thanks 
> > Drew 
> > 
> > On May 10, 2017 7:29 AM, "Hugh Frater" <[email protected] <javascript:>> 
> wrote: 
> >> 
> >> Found it - cape-universal doesn't support eqep1, this was added to 
> >> cape-universalh 4 months ago but the code wasn't merged into 
> cape-universal. 
> >> I will look at doing this now. 
> >> 
> >> On Wednesday, 10 May 2017 10:20:56 UTC+1, Hugh Frater wrote: 
> >>> 
> >>> Anyone? 
> >>> 
> >>> On Thursday, 20 April 2017 15:01:07 UTC+1, Hugh Frater wrote: 
> >>>> 
> >>>> Following on from my earlier messages related to this, I am using 
> >>>> cape-universal now to setup and control the pins for my mechatronics 
> >>>> project. Pinmap constraints mean I need to use eQEP1 and eQEP2. eQEP2 
> on 
> >>>> P8_11, P8_12 and P8_16 is working, but I can't get config-pin to 
> setup eQEP1 
> >>>> on P8_31, P8_33 and P8_35. 
> >>>> 
> >>>> root@beaglebone:/dev# config-pin -l P8_31 
> >>>> default gpio gpio_pu gpio_pd uart qep 
> >>>> 
> >>>> You can see qep is a supported mode. 
> >>>> 
> >>>> root@beaglebone:/dev# config-pin P8_31 qep 
> >>>> bash: line 0: echo: write error: No such device 
> >>>> Cannot write pinmux file: 
> >>>> /sys/devices/platform/ocp/ocp:P8_31_pinmux/state 
> >>>> 
> >>>> And that is the error I get... 
> >>>> 
> >>>> Does anyone know what is going on here? This 2nd encoder input is the 
> >>>> last bit of the pinmux'ing puzzle I need to sort out, all the other 
> GPIO is 
> >>>> working nicely now. 
> >>>> 
> >>>> Thanks, Hugh 
> >>>> 
> >> -- 
> >> 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] <javascript:>. 
> >> To view this discussion on the web visit 
> >> 
> https://groups.google.com/d/msgid/beagleboard/2cbad167-27c6-44b0-aea2-e423cca25dd1%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 [email protected] <javascript:>. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/beagleboard/CAEf4M_D9ytOfzome-NbXGJ6oObebsBO8en_OcVW9XqiygqoVsw%40mail.gmail.com.
>  
>
> > 
> > For more options, visit https://groups.google.com/d/optout. 
>
>
>
> -- 
> 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/14a712d3-98de-42c9-8a4f-44f49c6856e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to