• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 295 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Syslink notify does not work

sunny li
Prodigy 90 points

Hi all,

I run ICS in TI814EVM , the syslink can work, but I port the syslink.ko ti814x_hdvpss_1G.xem3 to jellybean and use the same kernel, there is error on notify_send_event failed! status = 0xfffffff0.

First the kenel and the syslink I rebuilt. and  If I change "init" in root directory  that built in ICS, syslink can work. So I am confused.

  • 0
    TI__Intellectual 2785 points

    Hi,

          To begin with Notify feature is supported both in Linux kernel & in Syslink.

          The firmware ti814x_hdvpss_1G.xem3 tested only with the Notify feature in Linux kernel.

          I am suspecting the interface differences which could cause this issue. (Ensure the notify address is same as per the ti814x_hdvpss_1G.xem3 requirement.

          In the above case you need to enable the notify feature in kernel and disable this in Syslink.

          If notify enabled in both also could cause issues.

    Thanks & Regards
    Velan

  • 0 in reply to Velan
    Prodigy 90 points

    Hi Velan,

    Thanks for your reply, I port the syslink and firmware to JellyBean a new version of android OS, but use the same linux kernel, they are worked in the android ICS,

    When JellyBean run init.rc at "slave_loader" the errors appear . If I take ICS "init" bin instead of JellyBean "init" to run init.rc ,the error will disappear.

    I also confuse about DSP syslink , I check the Notify error on kernel/drivers/DSP/syslink/...  so the codes are for DSP syslnk, Why  I run the M3 core leading DSP error?

  • 0 in reply to sunny li
    TI__Intellectual 2785 points

    Hi,

        In this trace, The notify is only sent between A8 and M3, so it is comming due to M3 is hung or there is no proper negotiation for this.

        It is just legacy that the directory is named as /DSP/syslink, now this is the generic code that it has notify for all cores. It is the same port of syslink notify module, so error codes might match with syslink->notify and kernel->notify.

        I am not familiar with the Android, So i can not comment on init & init.rc from Android.

    Thanks & Regards

    Velan