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.

Linux/AM5728: ping_rpmsg example not working

Part Number: AM5728

Tool/software: Linux

Hi,

I am trying to get IPC between DSP1 running TI-RTOS (the latest) and A15 Core 0 running Linux (4.4.12), working. Upon using rpmsg to load the firmware onto the DSP core I get the following messages:

root@am57xx-evm:/sys/bus/platform/drivers/omap-rproc# echo 40800000.dsp > unbind
[ 2667.980791] omap_hwmod: mmu1_dsp1: _wait_target_disable failed
[ 2667.993804] omap_hwmod: mmu0_dsp1: _wait_target_disable failed
[ 2668.001615]  remoteproc2: stopped remote processor 40800000.dsp
[ 2668.007812]  remoteproc2: releasing 40800000.dsp
root@am57xx-evm:/sys/bus/platform/drivers/omap-rproc# echo 40800000.dsp > bind
[ 2674.257154] omap-rproc 40800000.dsp: assigned reserved memory node dsp1_cma@99000000
[ 2674.264986]  remoteproc2: 40800000.dsp is available
[ 2674.270816]  remoteproc2: Note: remoteproc is still under development and considered experimental.
[ 2674.279911]  remoteproc2: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
root@am57xx-evm:/sys/bus/platform/drivers/omap-rproc# [ 2674.299262]  remoteproc2: powering up 40800000.dsp
[ 2674.307658]  remoteproc2: Booting fw image dra7-dsp1-fw.xe66, size 4502200
[ 2674.321995] omap_hwmod: mmu0_dsp1: _wait_target_disable failed
[ 2674.327887] omap-iommu 40d01000.mmu: 40d01000.mmu: version 3.0
[ 2674.333819] omap-iommu 40d02000.mmu: 40d02000.mmu: version 3.0
[ 2674.348511]  remoteproc2: remote processor 40800000.dsp is now up
[ 2674.354986] virtio_rpmsg_bus virtio5: rpmsg host is online
[ 2674.360558]  remoteproc2: registered virtio5 (type 7)
[ 2721.291603] virtio_rpmsg_bus virtio5: creating channel rpmsg-proto addr 0x33

which seems correct.

But when I try to use the test ping_rpmsg application to communicate with the DSP core I get the following error message

root@am57xx-evm:/usr/bin# ping_rpmsg
Connecting to address 0x33 on vprocId 0
connect failed: Invalid argument (22)
root@am57xx-evm:/usr/bin# ping_rpmsg 100 4
Connecting to address 0x33 on vprocId 4
connect failed: Invalid argument (22)

After debugging I noticed that the call to 'connect' in ping_rpmsg.c' is failing.

Please can you let me know what I'm doing wrong?

Thanks very much.

Regards,

Shaunak