Am Donnerstag, 13. August 2020 18:16:55 UTC+2 schrieb Andrew Harres:
>
> debian@beaglebone:~$ groups
> debian adm kmem dialout cdrom floppy audio dip video plugdev users
> systemd-journal input bluetooth netdev cloud9ide xenomai weston-launch
> tisdk docker i2c iio spi admin remoteproc eqep pwm gpio
>
The system group pruio is missing. It gets created when installing the
libpruio-lkm.deb packege.
debian@beaglebone:~$ sudo chown root:gpio
> /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
>
> debian@beaglebone:~$ sudo chmod 664
> /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
>
> debian@beaglebone:~$ sudo ls -l
> /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
> -rw-rw-r-- 1 root gpio 0 Jan 1 1970
> /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
>
> debian@beaglebone:~$ cat
> /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
> cat: /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins: Permission
> denied
>
Obviously also the folder needs permissions. Here's the folder chain on my
system
dr-xr-xr-x 12 root root 0 Aug 13 19:40 sys
> rwxr-xr-x 10 root root 0 Aug 13 19:40 kernel
> drwx--x--x 41 root root 0 Jan 1 1970 debug
> drwxrwxr-x 2 root gpio 0 Jan 1 1970 44e10800.pinmux
>
Regarding ADC the example 1.py works now in python 2 and 3:
debian@beaglebone:~$ sudo python3 src/pruio_examples/1.py
> F940 EBD0 F4A0 88C0 58A0 9EB0 B6C0 F1E0
> F960 EE70 F510 C170 9600 91A0 9990 F200
> F950 EE10 F530 C630 A400 A0A0 A1D0 F1E0
> F970 EE30 F510 C680 A640 A470 A680 F1F0
> F990 EE10 F4E0 C680 A6B0 A5C0 A910 F200
> F990 EE30 F500 C660 A6B0 A630 AA10 F1E0
> F980 EE00 F4F0 C680 A660 A5D0 A980 F1C0
> F980 ED90 F4E0 C640 A590 A520 A8D0 F1D0
> F950 ED90 F510 C5F0 A520 A470 A7B0 F1B0
> F940 EDC0 F500 C5C0 A4F0 A420 A6B0 F1D0
> F960 EDA0 F4D0 C5C0 A4B0 A3B0 A630 F210
> F940 EDC0 F500 C5B0 A450 A370 A5C0 F1C0
> F940 EDF0 F4F0 C5D0 A4E0 A3C0 A5F0 F1B0
>
But you don't have pinmuxing feature yet.
1. Try to install libpruio-lkm.deb package (command groups should list
the system group pruio afterwards).
2. Make yourself a member in this group.
3. Fix the permissions in path
/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins.
4. Make uEnv.txt *NOT* loading the cape_universal stuff.
Then the AssertionError: pruio_new failed ('parsing kernel claims') should
disappear and all members of group pruio should have pinmuxing capability
from user space.
Regards
--
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/5dad1c89-3390-40cf-8bc9-00a728afde8bo%40googlegroups.com.
