Good day,

By now you probably already found an answer/solution, but I had a similar 
problem with kernel 4.9.51 and maybe someone else needs the workaround.
It looks like now the firmware has to be loaded into the PRU's manually. 
http://processors.wiki.ti.com/index.php/PRU-ICSS_Remoteproc_and_RPMsg

echo 'am335x-pru0-fw' > /sys/class/remoteproc/remoteproc1/firmware 
echo 'am335x-pru1-fw' > /sys/class/remoteproc/remoteproc2/firmware 
echo 'start' > /sys/class/remoteproc/remoteproc1/state 
echo 'start' > /sys/class/remoteproc/remoteproc2/state 

After executing the above commands I would get the familiar dmesg output:

[  100.724488] remoteproc remoteproc1: powering up 4a334000.pru0
[  100.734584] remoteproc remoteproc1: Booting fw image am335x-pru0-fw, 
size 26416
[  100.748630] remoteproc remoteproc1: remote processor 4a334000.pru0 is 
now up
[  111.235625] remoteproc remoteproc2: powering up 4a338000.pru1
[  111.247976] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, 
size 72904
[  111.261356] ti-pruss 4a300000.pruss: configured system_events = 
0x00000000000c0000 intr_channels = 0x0000000a host_intr = 0x0000000a
[  111.285770] remoteproc remoteproc2: registered virtio0 (type 7)
[  111.300130] remoteproc remoteproc2: remote processor 4a338000.pru1 is 
now up
[  111.380517] virtio_rpmsg_bus virtio0: creating channel rpmsg-pru addr 
0x1f
[  111.388129] virtio_rpmsg_bus virtio0: rpmsg host is online
[  111.544072] rpmsg_pru virtio0.rpmsg-pru.-1.31: new rpmsg_pru device: 
/dev/rpmsg_pru31

Hope this helps,
Eryk



On Wednesday, July 12, 2017 at 5:55:14 AM UTC-4, Igor Jędrzejczak wrote:
>
> Have*

-- 
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/71600f91-be2a-476b-b2a2-7aeb9a97ec18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to