I discovered that (at least in my ubuntu Linux arm 4.1.13-ti-r36) trying to load and unload overlays on the fly doesn't work. I did it many times, in the right way. But you should reboot your system at first and THEN try to load your overlay. Your changes at the pinmux should be visible now.
I don't know why one should reboot the system everytime. 2015-12-31 11:39 GMT+01:00 Bremenpl <breme...@gmail.com>: > Didnt know about this page, thabk you a lot :). > > On December 31, 2015 11:30:53 AM Davide Picchi <pave...@gmail.com> wrote: > >> And if you need some help I can suggest you to try the code generated in >> this page >> <http://kilobaser.com/blog/2014-07-28-beaglebone-black-devicetreeoverlay-generator#1gpiodto> >> . >> >> At least you have the chance to check, whether your code is right or not. >> You can simplify debugging of your code. >> >> Regards >> >> Am Mittwoch, 9. September 2015 18:41:21 UTC+2 schrieb bremenpl: >>> >>> Hello there, >>> I just got back to my BeagleBone Black and i have no idea why but I just >>> cannot change a pin configuration using overlay nor through export. This is >>> what I am trying to do: >>> >>> I want to set P8_29 and P8_31 Pins to inputs with a pullup (0x37). here >>> is my overlay: >>> >>> /dts-v1/; >>> /plugin/; >>> >>> /{ >>> compatible = "ti,beaglebone", "ti,beaglebone-black"; >>> part-number = "BB-AVRDUDE"; >>> version = "00A0"; >>> >>> fragment@0 { >>> target = <&am33xx_pinmux>; >>> >>> __overlay__ { >>> ebb_example: BB-AVRDUDE { >>> pinctrl-single,pins = < >>> 0x0E4 0x37 // P8_29, AVR #RST pin, Input Mode7 pullup >>> 0x0D8 0x37 // P8_31, AVR #HWB pin, Input Mode7 pullup >>> >>> /* INPUT GPIO(mode7) 0x27 pulldown, 0x37 pullup, >>> 0x?f no pullup/down */ >>> >; >>> }; >>> }; >>> }; >>> >>> fragment@1 { >>> target = <&ocp>; >>> __overlay__ { >>> gpio_helper { >>> compatible = "gpio-of-helper"; >>> status = "okay"; >>> pinctrl-names = "default"; >>> pinctrl-0 = <&ebb_example>; >>> }; >>> }; >>> }; >>> }; >>> >>> Then I load the DTS and see in the list (last). HDMI is disabled: >>> >>> 0: 54:PF--- >>> 1: 55:PF--- >>> 2: 56:PF--- >>> 3: 57:PF--- >>> 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G >>> 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI >>> 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN >>> 7: ff:P-O-L Override Board Name,00A0,Override Manuf,NEOSEC-TINYLCD22 >>> 8: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-KEYS >>> 9: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-SPI1-2CS >>> 10: ff:P-O-L Override Board Name,00A0,Override Manuf,am33xx_pwm >>> 11: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-COOLER >>> 12: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART5 >>> 13: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BUZZER >>> 14: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-W1 >>> *15: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-AVRDUDE* >>> >>> >>> Dmesg says it was OK: >>> >>> root@beaglebone:~# dmesg | grep BB-AVRDUDE >>> [ 151.732517] bone-capemgr bone_capemgr.9: part_number 'BB-AVRDUDE', >>> version 'N/A' >>> [ 151.732633] bone-capemgr bone_capemgr.9: slot #15: 'Override Board >>> Name,00A0,Override Manuf,BB-AVRDUDE' >>> [ 151.732729] bone-capemgr bone_capemgr.9: slot #15: Requesting part >>> number/version based 'BB-AVRDUDE-00A0.dtbo >>> [ 151.732744] bone-capemgr bone_capemgr.9: slot #15: Requesting >>> firmware 'BB-AVRDUDE-00A0.dtbo' for board-name 'Override Board Name', >>> version '00A0' >>> [ 151.736445] bone-capemgr bone_capemgr.9: slot #15: dtbo >>> 'BB-AVRDUDE-00A0.dtbo' loaded; converting to live tree >>> >>> >>> Then I check the pins and they remain as they were in default: >>> >>> root@beaglebone:~# cat $PINS | grep "pin 57" >>> pin 57 (44e108e4) 00000027 pinctrl-single >>> root@beaglebone:~# cat $PINS | grep "pin 54" >>> pin 54 (44e108d8) 0000002f pinctrl-single >>> >>> >>> Did I forget something? I really cant think of anything. I would really >>> apreciate all help here! >>> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "BeagleBoard" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/beagleboard/kL9YPe8NuPg/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> beagleboard+unsubscr...@googlegroups.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. > 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. For more options, visit https://groups.google.com/d/optout.
