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.

Real time support for Syslink Notify

Hi,

I am working on th dm8148, using ti-SDK 5..04.00.11 .  Syslink 2.10.3.20

On the DSP side, I register a notify event in order to send to the ARM side a signal. I use that notify every 10ms. On the ARM side (Linux Embedded OS) I see these notifies signals by receiving them in a callback function and raise a GPIO. So, I can see the GPIO rises every 10ms but for some reason, sometime (like once in 5 minutes) the ARM misses a notify or two.    When I run some more processes on the ARM side, like ftp and etc. there are more misses of these notifies.  I want to give highest priority to the callback function of the receiving event, So I do it with the Round-Robin approach in the linux, tough I can't understand where this callback is running - kernel-space or user-space.

Did someone encountered a similar problem of real-time demand or know how can i fix this so the ARM won't miss one event notify?

  • Hi Liran,

    I am not very familiar with the syslink notify mechanism, but here are my thoughts.

    When you register the notify event, the event id can be prioritized, 0 (highest), 31 (lowets).

    http://processors.wiki.ti.com/index.php/SysLink_UserGuide

    The MessageQ also has priorities:

    {EZSDK}/component-sources/ipc_x_xx_xx_xx/IPC_Users_Guide.pdf, section 3.3.8 Message Priorities

    For thread priorities:

    {EZSDK}/component-sources/bios_x_xx_xx_xx/docs/Bios_User_Guide.pdf, section 3.2.4 Thread Priorities

    Also the below e2e thread might be in help:

    http://e2e.ti.com/support/embedded/linux/f/354/p/155497/581144.aspx#581144

    Regards,
    Pavel