Part Number: BEAGLEBK
Tool/software: Linux
Hi,
There are no /dev/rpmsg_pru30 and /dev/rpmsg_pru31 devices as they used to be before and it is not possible to follow the examples in
http://processors.wiki.ti.com/index.php/RPMsg_Quick_Start_Guide
http://processors.wiki.ti.com/index.php/PRU_Training:_Hands-on_Labs
Reinserting the pru_rproc.ko module like below does not help.
root@am335x-evm:~# rmmod -f /lib/modules/4.9.59-ga75d8e9305/kernel/drivers/remoteproc/pru_rproc.ko
[ 141.469328] pru-rproc 4a338000.pru1: pru_rproc_remove: removing rproc 4a338000.pru1
[ 141.482132] remoteproc remoteproc2: releasing 4a338000.pru1
[ 141.503365] pru-rproc 4a334000.pru0: pru_rproc_remove: removing rproc 4a334000.pru0
[ 141.542891] remoteproc remoteproc1: releasing 4a334000.pru0
root@am335x-evm:~# insmod /lib/modules/4.9.59-ga75d8e9305/kernel/drivers/remoteproc/pru_rproc.ko
[ 190.143821] remoteproc remoteproc1: 4a334000.pru0 is available
[ 190.149989] pru-rproc 4a334000.pru0: PRU rproc node /ocp/pruss_soc_bus@4a326000/pruss@4a300000/pru@4a334000 probed successfully
[ 190.216124] remoteproc remoteproc2: 4a338000.pru1 is available
[ 190.237189] pru-rproc 4a338000.pru1: PRU rproc node /ocp/pruss_soc_bus@4a326000/pruss@4a300000/pru@4a338000 probed successfully
Has there been any substantial change in the way PRUs should be be accessed?
Best regards,
Adam
