• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 100 subscribers
  • Views 659 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PRU remoteproc support

Vaibhav Bansal
Prodigy 10 points

Hello TI,

I am trying to get remoteproc driver runnung on 3.14 kernel.

I have successfully installed the SDK and PRU addon support. While compiling the kernel modules drivers/virtio/virtio.ko and virtio_ring.ko are not getting compiled. These files are simply missing and hence remoteproc probe is failing

[   15.619594] pru-rproc 4a334000.pru0: sysevt-to-ch[16] -> 1
[   15.619605] pru-rproc 4a334000.pru0: skip intr mapping for chnl 0
[   15.619617] pru-rproc 4a334000.pru0: chnl-to-host[1] -> 1
[   15.619627] pru-rproc 4a334000.pru0: skip intr mapping for chnl 2
[   15.619636] pru-rproc 4a334000.pru0: skip intr mapping for chnl 3
[   15.619646] pru-rproc 4a334000.pru0: skip intr mapping for chnl 4
[   15.619655] pru-rproc 4a334000.pru0: skip intr mapping for chnl 5
[   15.619664] pru-rproc 4a334000.pru0: skip intr mapping for chnl 6
[   15.619674] pru-rproc 4a334000.pru0: skip intr mapping for chnl 7
[   15.619683] pru-rproc 4a334000.pru0: skip intr mapping for chnl 8
[   15.619693] pru-rproc 4a334000.pru0: skip intr mapping for chnl 9
[   15.619708] pruss-rproc 4a300000.pruss: SYSEV16 -> CH1 (CMR4 0x00000001)
[   15.619720] pruss-rproc 4a300000.pruss: CH1 -> HOST1 (HMR0 0x00000100)
[   15.619733] pruss-rproc 4a300000.pruss: configured system_events = 0x0000000000010000 intr_channels = 0x00000002 host_intr = 0x00000002
[   15.619745]  remoteproc1: starting PRU0: entry-point = 0x2d
[   15.619754]  remoteproc1: remote processor 4a334000.pru0 is now up
[   15.645432]  remoteproc1: kicking vqid 0 on PRU0

probe hangs here . Not able to rmmod since it says pruss_remoteproc is still in use

  • 0
    TI__Guru**** 393215 points

    Hi,

    I will ask a PRU expert to look at this.

  • 0
    TI__Genius 10440 points

    Vaibhav,

    We need to update the steps for lab 4 on our wiki to reflect the fact that virtio.ko, virtio_ring.ko, and remoteproc.ko are all built in to the 3.14 kernel. In order to load and run the firmwares into the PRU's you should only need:

    insmod virtio_rpmsg_bus.ko

    insmod pruss_remoteproc.ko

    Due to the pruss_remoteproc module getting used by some other components under the hood we need to force the remove:

    rmmod -f pruss_remoteproc.ko

    From your output above it looks as though the load was successful. What makes you think that the probe is failing?

    Jason Reeder