Part Number:OMAP-L138
Tool/software: TI-RTOS
Hello, I am attempting to set up IPC between the ARM and C6740 cores of the OMAPL138. I am using the LCKDOMAPL138 development kit. Following the advice of this thread I've started by setting up a SYS/BIOS "Typical" setup project, then including the Ipc package trying to synchronize the cores, and then getting a primitive Notify even loop running before trying MessageQ. However, my current configuration leads to execution hang when I reach the Ipc_attach() calls in either processor, meaning synchronization never happens.
After some digging, it looked like the cause was a lack of shared region zero definition, however, even with a proper SharedRegion description in the SYS/BIOS config file, I'm still having the same issue.
What could be causing this hanging behavior in Ipc_attach()?
For reference, I am using CCS v7.4, SYSBIOS v6.52, IPC v3.47, XDCTools v3.50, and Processor SDK RTOS v4.03.
Also worthy of note is that function _mfence() appeared as an unresolved symbol when I plainly included the Ipc and MultiProc packages in the C6740-side project. This thread documents a similar scenario on the same versions of the libraries but was not concretely resolved. This document states that _mfence is not a supported implicitly-generated function for the C6740, so I figured a dummy definition would not break behavior. Is this assumption incorrect? I am wondering if this has something to do with my sync problem...
My application files are attached: arm_ipc for the ARM-side, and dsp_ipc for the C6740-side. I've commented-out the Notify behavior, since sync isn't working yet.
(Please visit the site to view this file)(Please visit the site to view this file)(Please visit the site to view this file)(Please visit the site to view this file)(Please visit the site to view this file)(Please visit the site to view this file)