[beagleboard] Re: More pimux woes
On Monday, 22 January 2018 17:42:03 UTC, lgil...@tethers.com wrote: > > Thanks!! Very helpful. One issue with just using the config-pin utility > is that it doesn't always give you access to all the configurations > possible for a peripheral (not pin), for instance, setting a pin to eqep > (qep), there are actually several modes of eqep. The dts file often > includes all these options. > > That is a very valid point and something I hadn't considered. I was working around this by using my pru code to configure the required peripheral registers directly, which now I look at it seems a terrible way to do it when I could use the dts file... -- 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/6f82ba09-c0de-4318-bc76-5e272dc0a8f4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: More pimux woes
Thanks!! Very helpful. One issue with just using the config-pin utility is that it doesn't always give you access to all the configurations possible for a peripheral (not pin), for instance, setting a pin to eqep (qep), there are actually several modes of eqep. The dts file often includes all these options. On Saturday, January 20, 2018 at 12:28:20 AM UTC-8, Hugh Frater wrote: > > You basically have 2 options regarding pinmuxing on a bb the > config-pin utility requires the universal cape to be loaded as the only > dtbo, you then use configure-pin to setup the pins you want. > > 2nd option, specify the overlays for the actual hardware you want to use, > e.g robotics cape, bone-eqep2 etc. You can’t load the specific overlays and > the universal cape together, they conflict, and you can’t use confit-pin > without the universal overlay being loaded. > > Personally, given I’m using a ton of pins for various things, I use the > universal overlay then have a script that runs from init.d to configure all > the pins at boot time. I preferred the convenience of using the config-pin > utility as apposed to writing my own device overlay for the pins I’m using. -- 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/8116d795-5b36-4db5-b705-e7b19fa2c8c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: More pimux woes
Robert, everything is working nicely at this end with the new version of bb-cape-overlays. Thanks -- 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/18053977-5aaa-41ad-86be-33c15d0936d6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: More pimux woes
You basically have 2 options regarding pinmuxing on a bb the config-pin utility requires the universal cape to be loaded as the only dtbo, you then use configure-pin to setup the pins you want. 2nd option, specify the overlays for the actual hardware you want to use, e.g robotics cape, bone-eqep2 etc. You can’t load the specific overlays and the universal cape together, they conflict, and you can’t use confit-pin without the universal overlay being loaded. Personally, given I’m using a ton of pins for various things, I use the universal overlay then have a script that runs from init.d to configure all the pins at boot time. I preferred the convenience of using the config-pin utility as apposed to writing my own device overlay for the pins I’m using. -- 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/30b0ebb2-991a-46ca-90c0-490cc04e288c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: More pimux woes
When I load a .dtbo though my uEnv.txt file (ie, uboot_overlay_addr4=/lib/firmware/bone_eqep2b-00A0.dtbo ) I no longer have access to config-pin's ability to set up ANY pins. Is there some sort of exclusiveness built into the system such that if .dtbos are found, then you cannot manually configure pins after boot with the config-pin utility? My system info: [root@beaglebone]> uname -a Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l GNU/Linux Thanks in advance! On Thursday, January 18, 2018 at 4:53:59 AM UTC-8, Hugh Frater wrote: > > I've been trying to get my test hardware back up and running after > corrupting node and bonescript, see my earlier post. > > I'm trying to get up and running with an 8.6 image as I couldn't get a 9.2 > image to provide pru_rproc support > > debian@beaglebone:~$ uname -r > 4.4.54-ti-r93 > > I'm trying to get the eqep support working on P8_31,33 & 35 (it was > working before) > > debian@beaglebone:~$ sudo config-pin -l P8_31 > default gpio gpio_pu gpio_pd uart qep > > Looks like qep is a supported mode... > > debian@beaglebone:~$ sudo config-pin P8_31 qep > [sudo] password for debian: > bash: line 0: echo: write error: No such device > Cannot write pinmux file: /sys/devices/platform/ocp/ocp:P8_31_pinmux/state > > Any idea what is causing the above error? The important bits from uEnv.txt > are: > > ##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled: > dtb=am335x-boneblack-overlay.dtb > > cmdline=coherent_pool=1M net.ifnames=0 quiet cape-universal=enable > > ##Example v4.1.x > #cape_disable=bone_capemgr.disable_partno= > cape_enable=bone_capemgr.enable_partno=cape-universala > > > > > > > > -- 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/246ca2a9-97a3-4f96-a78d-26bf03c64c98%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: More pimux woes
Thanks Robert, I won’t be back in front of my BBB till Monday now but I’ll be sure to test it first thing. -- 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/5b8146ee-3982-4472-b6eb-1883101442c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: More pimux woes
On Fri, Jan 19, 2018 at 2:25 PM, Robert Nelsonwrote: > On Fri, Jan 19, 2018 at 10:25 AM, Hugh Frater wrote: >> Top man, thanks for taking care of this. Let me know when it gets pushed up >> and i'll re-run apt update > > Okay all pushed out.. > > sudo apt update ; sudo apt upgrade bb-cape-overlays > > sudo reboot > > Please test it and let us know if those config-pin options work.. debian@test-bbb-4:~$ config-pin -q P9.42 P9_42 Mode: default Direction: in Value: 0 debian@test-bbb-4:~$ config-pin -l P9.42 default gpio gpio_pu gpio_pd gpio_input spi_cs spi_sclk uart pwm pru_ecap debian@test-bbb-4:~$ config-pin P9.42 pru_ecap debian@test-bbb-4:~$ config-pin -q P9.42 P9_42 Mode: pru_ecap 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/CAOCHtYhFpNbx86WAi0Gc%3DEKgopB9j6t6yng7hfaULfQmNdPNvQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: More pimux woes
On Fri, Jan 19, 2018 at 10:25 AM, Hugh Fraterwrote: > Top man, thanks for taking care of this. Let me know when it gets pushed up > and i'll re-run apt update Okay all pushed out.. sudo apt update ; sudo apt upgrade bb-cape-overlays sudo reboot Please test it and let us know if those config-pin options work.. 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/CAOCHtYiD%2BCUBAD_DRU1qdiFtCxzqbnOJfUMG8o-prj7BeJzFCg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: More pimux woes
Top man, thanks for taking care of this. Let me know when it gets pushed up and i'll re-run apt update On Friday, 19 January 2018 16:17:21 UTC, RobertCNelson wrote: > > On Fri, Jan 19, 2018 at 5:45 AM, Hugh Frater> wrote: > >>> > >> Running: > >> > >> sudo apt update ; sudo apt install bb-cape-overlays > >> > >> Has fixed the eqep errors and the clash between p9_26 and p8_24 that I > was > >> seeing - however, pru_ecap has now gone as a mode for p9_42 - > argggh > > > > > > I see from the most recent commit that this has been added back again as > a > > mux option Robert, any idea when it will be pushed up and available > through > > apt update? > > Hi Hugh, > > Yeah after your message yesterday, i went thru the overlays and > regenerated with *.dts/pinmux.. > > I'll have a full update for the kernel/config-pin/etc shortly > > (plus gpio_input option will be available).. > > 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/8047deb5-a5b3-42bc-b550-e38fb34ad843%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: More pimux woes
On Fri, Jan 19, 2018 at 5:45 AM, Hugh Fraterwrote: >>> >> Running: >> >> sudo apt update ; sudo apt install bb-cape-overlays >> >> Has fixed the eqep errors and the clash between p9_26 and p8_24 that I was >> seeing - however, pru_ecap has now gone as a mode for p9_42 - argggh > > > I see from the most recent commit that this has been added back again as a > mux option Robert, any idea when it will be pushed up and available through > apt update? Hi Hugh, Yeah after your message yesterday, i went thru the overlays and regenerated with *.dts/pinmux.. I'll have a full update for the kernel/config-pin/etc shortly (plus gpio_input option will be available).. 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/CAOCHtYg0umVu10RBtTjM0fu49W4ZX%3DcOw0OT%3D-2ZQOLsWn%2BnFA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: More pimux woes
> > >> Running: > > sudo apt update ; sudo apt install bb-cape-overlays > > Has fixed the eqep errors and the clash between p9_26 and p8_24 that I was > seeing - however, pru_ecap has now gone as a mode for p9_42 - argggh > I see from the most recent commit that this has been added back again as a mux option Robert, any idea when it will be pushed up and available through apt update? -- 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/e8fc5f86-3620-4968-94fa-dd8b1615059b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: More pimux woes
On Thursday, 18 January 2018 12:53:59 UTC, Hugh Frater wrote: > > I've been trying to get my test hardware back up and running after > corrupting node and bonescript, see my earlier post. > > I'm trying to get up and running with an 8.6 image as I couldn't get a 9.2 > image to provide pru_rproc support > > debian@beaglebone:~$ uname -r > 4.4.54-ti-r93 > > I'm trying to get the eqep support working on P8_31,33 & 35 (it was > working before) > > debian@beaglebone:~$ sudo config-pin -l P8_31 > default gpio gpio_pu gpio_pd uart qep > > Looks like qep is a supported mode... > > debian@beaglebone:~$ sudo config-pin P8_31 qep > [sudo] password for debian: > bash: line 0: echo: write error: No such device > Cannot write pinmux file: /sys/devices/platform/ocp/ocp:P8_31_pinmux/state > > Any idea what is causing the above error? The important bits from uEnv.txt > are: > > ##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled: > dtb=am335x-boneblack-overlay.dtb > > cmdline=coherent_pool=1M net.ifnames=0 quiet cape-universal=enable > > ##Example v4.1.x > #cape_disable=bone_capemgr.disable_partno= > cape_enable=bone_capemgr.enable_partno=cape-universala > > > Running: sudo apt update ; sudo apt install bb-cape-overlays Has fixed the eqep errors and the clash between p9_26 and p8_24 that I was seeing - however, pru_ecap has now gone as a mode for p9_42 - argggh -- 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/b83d1ac0-721a-4dd7-a546-e6fa05f8014c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.