Hi,
had a working environment with PRU 0, eqep some GPIO and HDMI.
Then I was trying to get analog inputs.
update / upgrade was recommended to solve that.
Analog input is working now … but the encoder is no longer working.
Encoder is connected on P8_11 and P8_12.
Problem:
root@beaglebone:/home/peter# config-pin -l P8_11
default gpio gpio_pu gpio_pd gpio_input qep pruout
root@beaglebone:/home/peter# config-pin -q P8_11
P8_11 Mode: default Direction: in Value: 1
root@beaglebone:/home/peter# config-pin P8_11 qep
/usr/local/bin/config-pin: 1489: echo: echo: I/O error
Cannot write pinmux file: /sys/devices/platform/ocp/ocp:P8_11_pinmux/state
ls -als /sys/devices/platform/ocp/ocp:P8_11_pinmux/state
0 -rw-rw-r-- 1 root gpio 4096 Sep 25 14:41 /sys/devices/platform/ocp/ocp:P8_11_pinmux/state
oot@beaglebone:/home/peter# /opt/scripts/tools/version.sh
git:/opt/scripts/:[b39ec679648a6be8f25f48bd1c9784c1fc5a0c46]
eeprom:[A335BNLTEIA02046SBB22866]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-04-06]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-00002-g07d5700e21]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0.bb.org-overlays]
UBOOT: Loaded Overlay:[BB-ADC-00A0.bb.org-overlays]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0.bb.org-overlays]
UBOOT: Loaded Overlay:[BB-NHDMI-TDA998x-00A0]
kernel:[4.19.94-ti-r64]
nodejs:[v10.24.0]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[disable_uboot_overlay_audio=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
uboot_overlay_options:[dtb_overlay=/lib/firmware/BB-ADC-00A0.dtbo]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade ]
pkg:[bb-cape-overlays]:[4.14.20210821.0-0~buster+20210821]
pkg:[bb-wl18xx-firmware]:[1.20210922.1-0~buster+20210922]
pkg:[kmod]:[26-1]
pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~buster+20200716]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~buster+20200305]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c gpio pwm eqep remoteproc admin spi iio docker tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet]
dmesg | grep remote
[ 68.234647] remoteproc remoteproc0: wkup_m3 is available
[ 68.457828] remoteproc remoteproc0: powering up wkup_m3
[ 68.457861] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217148
[ 68.458152] remoteproc remoteproc0: remote processor wkup_m3 is now up
[ 70.814996] remoteproc remoteproc1: 4a334000.pru is available
[ 70.830770] remoteproc remoteproc2: 4a338000.pru is available
[ 1307.768038] remoteproc remoteproc1: powering up 4a334000.pru
[ 1307.770814] remoteproc remoteproc1: Booting fw image pru_modulator-pru0-fw, size 64480
[ 1307.770887] remoteproc remoteproc1: remote processor 4a334000.pru is now up
dmesg | grep pru
[ 70.814996] remoteproc remoteproc1: 4a334000.pru is available
[ 70.815193] pru-rproc 4a334000.pru: PRU rproc node pru@4a334000 probed successfully
[ 70.830770] remoteproc remoteproc2: 4a338000.pru is available
[ 70.830976] pru-rproc 4a338000.pru: PRU rproc node pru@4a338000 probed successfully
[ 1307.768038] remoteproc remoteproc1: powering up 4a334000.pru
[ 1307.770814] remoteproc remoteproc1: Booting fw image pru_modulator-pru0-fw, size 64480
[ 1307.770887] remoteproc remoteproc1: remote processor 4a334000.pru is now up
dmesg | grep pinctrl-single
[ 0.981409] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
[ 0.994785] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 002: ID 1a86:e5e3 QinHeng Electronics
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END
I did search for hints and possible solutions, but most what I found was from 2014 and before.
Think the driver is missing … for my understanding eqep is part of the kernel, isn’t it?
Need help and good ideas where to search … remember, it worked fine up to the moment I update/upgrade.
Peter