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.
Part Number: PROCESSOR-SDK-DRA8X-TDA4X
Hi,
We are implementing IPC between Linux running on cortex A72 and Classic AUTOSAR stack(RTOS) running on MCU cortex R5F0.
Following are the two issues we are facing.
1. No Entry in /dev:
We are using CddIpc provied in RTOS psdk in following folder.
"psdk_rtos_auto_j7_06_02_00_21\mcusw\mcal_drv\mcal\CddIpc".
we have referred echo test example to implement the resource table and following is the initialization sequence we are following for IPC in R5F.
load resource table -> wait for linux ready--if (linux ready)--> Cdd_IpcInit -> Cdd_IpcAnnounce (msg: "rpmsg_chrdev").
Binary of R5F core is booted through SD card using SPL boot. Based on our understanding from pdk document section 8.5 "Developing IPC Applications" for every announced service, it creates a userspace /dev entry for each remote rpmsg_chrdev service.
we couldn't find any entry after announcing. But some times we observed in main uart we could see following message and in /dev "rpmsg_ctr11" is created, when we sent first IPC message by calling "Cdd_IpcSendMsg".
"virtio_rpmsg_bus virtio3: creating channel rpmsg_chrdev addr 0xd".
2. No Read/Write file operation:
As mentioned in query 1, some times "rpmsg_ctr11" is getting created. once it is created we are executing the application developed based on the pdk document section 8.5.10.2. "Writing IPC Applications on Linux".
In application, till opening the "/dev/rpmsg_ctrl11" is successful. But write and read operations are not working .
we are using linux sdk of version 06_02_00 and RTOS sdk of version 06_02_00_21.
Please provide solution for these issues.
Thanks®ards,
Mallikarjun
rpmsg_chrdev
Hi,
We removed "CddIpc" and we implemented ipc application using IPC driver.
Still Device is not created in Linux after announcement from rtos.
Please provide support in this issue.
Regards,
Mallikarjun
Hi,
Issue is resolved after setting sharable attribute for DDR memory in startup.
Regards,
Mallikarjun