• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 431 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.

Linux/DM3730: Communicate to C64x+ on DM3730 with kernel 4.4.x

Kevin Farley
Prodigy 20 points
Part Number: DM3730
Other Parts Discussed in Thread: OMAP3530

Tool/software: Linux

I am currently investigating enabling the DSP module (TMS320C64x+) on this DM3730 device (specifically the torpedo zoom).

We have kernel 4.4.24 running on there (not flexible on that point) and need to enable the dsp module to offload some arithmetic work etc.

I found information regarding the DSPLink and DSPBridge; however, both seem to have halted support pre-kernel 4.x

So I am currently investigating SysLink, but I want to confirm that this is the correct path and that syslink can bridge dsp-arm comms on kernel 4.x.

Any help would be appreciated.

  • 0
    TI__Guru 65405 points
    Hi Kevin,

    Linux kernel 4.x.xx is not officially supported on DM3730 by TI.
    You can find some resources for pre-kernel 4.x at:
    processors.wiki.ti.com/.../SysLink_UserGuide
    processors.wiki.ti.com/.../SysLink_MigrationGuide

    Regards,
    Tsvetolin Shulev
  • 0 in reply to Cvetolin Shulev-XID
    Prodigy 20 points

    Thank you for your reply.

    I have been made aware that there is no "official" support for kernel 4.x for the DM3730. I have also come across those wiki links and that is why I am posting here.

    So what I really need to know is if SysLink is a driver / set of modules which can run on a Linux kernel 4.x?

    I have attempted to compile it myself but ran into a number of issues during compilation. And at some point the issue became a compilation error where it was looking for a file in my kernel source which did not exist 

    "omap3530_hal_mmu_defs.h:52:24: fatal error: plat/iommu.h: No such file or directory 

    #include <plat/iommu.h>"

    That compilation error leads me to believe my kernel version may be incompatible or incomplete; however, if SysLink is viable for kernel 4.x I could potentially find a working example and figure out what exactly it needs.

    I was unable to find such information in the wiki pages and was hoping a response here could clear that up.