Thank you Robert. In the long term I will certainly do as you suggest. Is there no way to "downgrade" or use an overlay for pin configuration that is in sync with my current (4.4.30) kernel version?
If that is not possible, will the 4.4.91 version you recommend support uio_pruss? I will have to review my notes, but my recollection is the remoteproc/uio driver debate was raging when I decided on this route, and it took some effort for me to figure out how to make it work. Finally, if I must move to 4.4.91, would you kindly state how I can accomplish this with all pinmux/helper/config/overlay items also being synced without disrupting uio_pruss? I presume this: cd /opt/scripts/tools/ git pull sudo ./update_kernel.sh sudo reboot will result in the latest kernel version (4.9.x??) which is not what I want... On Wednesday, December 20, 2017 at 1:33:46 PM UTC-8, ags wrote: > > I've been building a prototype using the uio_pruss driver and one "test" > pin (P9_27) which was easily allocated using config-pin. > I'm now trying to complete the prototype and need to enable a total of 8 > PRU pins (pr1_pru0_pru_r30_[0-7]). I am unable to enable most of these pins: > > debian@BBB:~$ uname -r > 4.4.30-ti-r64 > > debian@BBB:~$ config-pin -a p9_29 pruout > > P9_29 pinmux file not found! > > P9_29 overlay not found > > Loading cape-universala overlay > > bash: line 0: echo: write error: File exists > > Error loading device tree overlay file: cape-universala > > > After searching I found this: > https://github.com/cdsteinkuehler/beaglebone-universal-io/issues/43 > > recommending updating overlays ("things have changed")... > > So I went here: https://github.com/beagleboard/bb.org-overlays > > and did this: > > > debian@BBB:~$ sudo apt update ; sudo apt install bb-cape-overlays > > > debian@BBB:~$ apt show bb-cape-overlays > > Package: bb-cape-overlays > > Version: 4.4.20171215.0-0rcnee1~jessie+20171215 > > Maintainer: Robert Nelson <[email protected]> > > Installed-Size: 2,003 kB > > Depends: device-tree-compiler > > Priority: extra > > Section: misc > > Download-Size: 59.5 kB > > APT-Manual-Installed: yes > > APT-Sources: http://repos.rcn-ee.com/debian/ jessie/main armhf Packages > > Description: Device tree overlays for Beaglebone. > > Device tree overlays for Beaglebone /lib/firmware/ > > > But now have a new problem: > > > debian@BBB:~$ config-pin p9_29 pruout > > bash: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state: No such file or > directory > > Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state > > debian@BBBr0C0-1:~/node$ config-pin -a p9_29 pruout > > bash: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state: No such file or > directory > > Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state > > > I did read about moving away from kernel overlays to uBoot overlays here: > https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays > > but am no closer to a solution. I am now under time pressure and prefer to > make minimal changes to my system. Can anyone help with suggestions to work > around this? > -- 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/ef4d04f4-ec1d-4bca-81c2-1777e0d42338%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
