I repeated this process for P8.14, and it works fine. This is just to let others who may not be aware that you can use 1-wire on any gpio pin that is not already in use by the system. Again, double check the pins in the schematic, to make sure they're not being used by somethign like HDMI( which you can disable hdmi audio and video if you do not need it. ), or i2c-0 / i2c-2, emmc, sdcard, etc. But again you have to of course change the overlay to reflect the pin you need to use.
*william@beaglebone:~$* diff ./dev/bb.org-overlays/src/arm/BB-W1-P8.14-00A0.dts ./dev/bb.org-overlays/src/arm/BB-W1-P9.12-00A0.dts 1c1,2 < /* --- > > /* 4c5 < * Virtual cape for onewire on connector pin P8.14 --- > * Virtual cape for onewire on connector pin P9.12 21c22 < part-number = "BB-W1-P8.14"; --- > part-number = "BB-W1-P9.12"; 27c28 < "P8.14"; --- > "P9.12"; 35c36 < BONE_P8_14 0x37 --- > BONE_P9_12 0x37 51c52 < gpios = <&gpio0 26 GPIO_ACTIVE_HIGH>; --- > gpios = <&gpio1 28 GPIO_ACTIVE_HIGH>; On Sat, Dec 3, 2016 at 3:11 PM, William Hermans <yyrk...@gmail.com> wrote: > @ Sebastian > > Ah I forgot to mention loading capes from /boot/uEnv.txt. So . . . > > *william@beaglebone:~$* cat /boot/uEnv.txt |grep cape > #cmdline=coherent_pool=1M quiet cape_universal=enable > video=HDMI-A-1:1024x768@60e > #cape_disable=capemgr.disable_partno= > #cape_enable=capemgr.enable_partno= > #cape_disable=bone_capemgr.disable_partno= > > cape_enable=capemgr.enable_partno=<overlay_name> is the way to go. You > can assign multiple cape overlays with this feature, but I do not remember > if they are space, or comma separated. I'm thinking comma separated, but > may be wrong. > > That's the first step. > > The second step would be to . . . > > Copy all your required overlays into /lib/firmware, which you've probably > already done. > > *william@beaglebone:~$* cd /opt/scripts/ > *william@beaglebone:/opt/scripts$* git pull > *william@beaglebone:/opt/scripts$* cd tools/developers/ > *william@beaglebone:/opt/scripts/tools/developers$* sudo > ./update_initrd.sh > > What this does, is notes what's in uEnv.txt in the way of enabled capes, > then which overlays you have in /lib/firmware, and "injects" these overlays > into the initramfs. This is important, and if not done, your overlays will > not load at boot using this method. But the upside is that once done, this > will load your overlays at boot faster than any other method. Near > instantly at boot, 1-2 seconds tops. > > Anyway, this method is fairly easy, and is actually the best way to go. > > -- 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/CALHSORoxQyVm4q56JLaCWZYhncAHEm7u_7Hoq-nZCj5V3pFaXA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
