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.

TDA4VM: Enable remote service receive task on A72

Part Number: TDA4VM

Hi TI,

I am currently investigating on sending data from MCU2_0 (R5F) to MPU1_0 (A72) using remote_service API from vision_apps. I am using PSDK RTOS/Linux in version 08.00.

The remote_service example provided by TI (running vx_app_arm_ipc.out on MPU1_0 and vx_app_rtos_linux_mcu2_0.out on MCU2_0) shows how to transfer data from MPU1_0->MCU2_0 (and other remote cores). In order to get a communication also in reverse direction, the define

 

Fullscreen
1
#define APP_ENABLE_REMOTE_SERVICE_RECEIVE_TASK
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

in app_remote_service_linux.c looked very suspicous. So I uncommented it and rebuilt the corresponding app for MPU1_0. However, now I am getting the following error, when executing the new app:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
IPC: mcu2_0 : rpmsg local endpt is 1025
[ 1761.244101] rpmsg_chrdev virtio5.rpmsg_chrdev.-1.21: idr_alloc failed: -28
IPC: mcu2_1 : rpmsg local endpt is 1024
IPC: c6x_1 : rpmsg local endpt is 1024
[ 1761.251452] rpmsg rpmsg78: failed to open rpmsg-char-3-1609
IPC: c6x_2 : rpmsg local endpt is 1024
IPC: c7x_1 : rpmsg local endpt is 1024
IPC: Init ... Done !!!
REMOTE_SERVICE: Init ... !!!
DEBUG: appRemoteServiceInit.
failed to open eptdev /dev/rpmsg78
REMOTE_SERVICE: ERROR: Count not start Remote Server
REMOTE_SERVICE: Init ... Done !!!
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

I am using a default linux kernel, as well as a default target filesystem. Can you please help me understand, why I get this error?

Thanks for your help and best regards,

Felix

  • Hi TI,

    I registered a new service in vx_app_rtos_linux_mcu2_0.out. It seems, that this is the root cause of the previous mentioned error. Removing this Service from app_init() call solves this issue. Maybe there was some misconfiguring when registering this service...

    Best regards,

    Felix