Hi,
I'm running latest debian image 'Linux beaglebone 4.9.82-ti-r102 #1 SMP PREEMPT Thu Feb 22 01:16:12 UTC 2018 armv7l GNU/Linux' on a BBB rev A5C.
I modified /boot/uEnv.txt to include:
- uboot_overlay_addr4=/lib/firmware/BB-UART4-00A0.dtbo
- uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-9-TI-00A0.dtbo
UART4 is working fine.
I have big troubles running GPIO Toggle example on pru (tested on pru0).
First of all:
I compiled the example onboard and I managed to get the binary .out file.
kernel does not seem to boot the firmware that I copied in '/lib/firmware/am335x-pru0-fw'
Looking at dmesg I have:
[ 28.341503] ti-pruss 4a300000.pruss: creating PRU cores and other child platform devices
[ 28.468932] remoteproc remoteproc1: 4a334000.pru0 is available
[ 28.469056] pru-rproc 4a334000.pru0: PRU rproc node /ocp/pruss_soc_bus@4a326000/pruss@4a300000/pru@4a334000 probed successfully
[ 28.508772] remoteproc remoteproc2: 4a338000.pru1 is available
[ 28.508896] pru-rproc 4a338000.pru1: PRU rproc node /ocp/pruss_soc_bus@4a326000/pruss@4a300000/pru@4a338000 probed successfully
and anything about 'Booting...'
Also I have:
lsmod | grep pru
pruss_soc_bus 4788 0
pru_rproc 14966 0
pruss_intc 9092 1 pru_rproc
pruss 10889 1 pru_rproc
Second:
I tried to config pin P9.29 to prout according to 0x0F toggle on R30 and I get:
debian@beaglebone:~$ config-pin P9.29 pruout
P9_29 pinmux file not found!
sudo: no askpass program specified, try setting SUDO_ASKPASS
Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_29_pinmux/state
Third:
The only effect of commenting out BB-UART4-00A0 is that most of the GPIO return to be exported as they were by default in vanilla installation.
pru firmware still does not get booted.
I'm stuck at this problem.
Please give me some advice.
Thanks in advance
Best regards
Filippo