• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 237 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.

Ipc_control(STARTCALLBACK) to C674x fails on TI8168 device

Erkka
Prodigy 230 points

Hello,

Basically our problem same as this:

DSP hangs or Ipc_control(STARTCALLBACK) fails on TI81XX device
http://processors.wiki.ti.com/index.php/SysLink_FAQs#DSP_hangs_or_Ipc_control.28STARTCALLBACK.29_fails_on_TI81XX_device

We have a custom HW and a custom image.

SOC: DM8168
Linux version is: linux-2.6.37-psp04.00.02.14
U-boot version is: u-boot-2010.06-psp04.00.02.14
IPC version is: ipc_1_23_05_40
Syslink version is: syslink_2_00_03_82

If we run Syslink's frameq sample in our HW with our image (versions mentioned above) then the problem occurs and Ipc_control(STARTCALLBACK)
fails to the C674x.

If we run the same sample in our HW with the EZSDK 5_04_00_11 image it works ok.

What could be causing this problem?

Br,
Erkka

  • 0
    TI__Genius 12025 points

    Erkka,

    If you are still having trouble, please move this thread to Support Forums > Embedded Software > Multimedia Software Codecs. This is a hardware forum. If the issue is resolved, please make a closing post.

    By "image", do you mean software component versions or Linux uImage?

    The most common issue with compatibility is the memory map. The EZSDK's will often use a memory map which is not compatible with the SysLink examples. Although you indicate that the SysLink FrameQ sample does work with EZSDK 5.04.00.11 and not with your custom version, I would still suspect the memory map. What version of SysLink is the EZSDK using?

    ~Ramsey

  • 0 in reply to Ramsey
    Prodigy 230 points

    Hi Ramsey,

    I forgot to post here that the problem was solved. If someone else is troubled by the same problem then check the version of the Syslink. We were using too old version of the Syslink. Updating to the Syslink 2_00_4_83 or newer solved the problem.

    Thanks,

    Erkka