Create Account
Search
You are here: TDG Forum  >>  Texas Instruments SOMs and Development Kits  >>  OMAP35x, DM3730, AM3703 Torpedo SOM Development Kit  >>  Using the DM3730 DSP core with Mainstream Linux

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 24 Oct 2016 08:47 AM by  Adam Ford
Using the DM3730 DSP core with Mainstream Linux
 4 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Ryan Crowell
New Member
New Member
Posts:15


--
21 Oct 2016 08:19 AM

    We have been using the Torpedo+Wireless SOM for over a year now in custom designs.  In the last couple of weeks we've transitioned successfully over to using Buildroot with the mainstream Linux kernel code. 

    One thing that we haven't yet done that we'd like to explore is using the DSP core in the DM3730 to accelerate some of our proprietary algorithms.  Unfortunately, it seems that the readily available tools for developing and executing code on the DSP don't play well with the newer Linux kernels, so we're struggling to find a path forward.

    Can anybody recommend tools, tutorials, guides, etc. for learning how to develop code for the DSP core, getting that code to execute and communicating between the ARM and DSP processors?  Preferably something that works with newer Kernels and in (or alongside) the Buildroot system?

    For reference, we're currently using Buildroot-2016.02, and kernel 4.4.9, but would be happy to bump versions up to something newer if that helps any.

    Thank you so much for any pointers!

    Ryan
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    21 Oct 2016 08:47 AM
    The Build tools in our 2.4-4 BSP patched the DSP code slightly. A colleague of mine was able to get it working with the 3.19 kernel. We haven't yet done testing on the 4.4 Kernel and the DSP.

    As a starting point, you may wish pull down DSP code in the BSP 2.4-4 and run

    ./ltib -p -m prep

    This will extract the code and patch it. You can try it against the 4.4 kernel to see how it works.


    An alternative is to look at the meta-ti repository for Yocto. TI uses Yocto for their builds, and they have evidence of building the DSP stuff. I haven't tried the DSP, but I did try their Yocto build with our device tree. Unfortunately, it didn't boot our board, so I didn't pursue it further.

    However, if you want to look at their DPS patches, they have some posted:

    http://git.yoctoproject.o...16c879a66974df964dfe

    Additional DSP related tools are found: http://git.yoctoproject.o...16c879a66974df964dfe

    Consider it all untested by Logic PD, so use it at your own risk, but it appears as if TI is trying to keep them alive for their kits.

    adam

    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    21 Oct 2016 08:50 AM

    As a 3rd option, we do offer design and engineering services where we could work on developing patches to the DSP and related tools for using it with the 4.4.y kernel. I can have one of our account managers contact you if you'd like a quote.


    If you're going to use the 4.4. kernel, I would highly suggest that you use the latest version of 4.4.y. There was a USB fix applied which allowed the MUSB (OTG Controller) to function again, and another patch yesterday which addressed the dirtycow bug. See: http://dirtycow.ninja/

    All of those came out after our 4.4 Beta documentation was released. We'll be updating our documentation soon.

    adam
    Ryan Crowell
    New Member
    New Member
    Posts:15


    --
    24 Oct 2016 08:45 AM
    Thank you Adam,

    No need to go down the path of setting up a contract for custom work at this point, but perhaps in the future. Thanks for the suggestions. We'll look into the various possibilities you mention above.

    Ryan
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    24 Oct 2016 08:47 AM
    No problem. For what it's worth, it's on my list of things to do, but it's not high on the priority list yet. When I get some free time, I'll try working on it and as I get things working, I'll post them to our forum, so keep checking every so often.

    adam
    You are not authorized to post a reply.

    Forums Texas Instruments SOMs and Development Kits OMAP35x, DM3730, AM3703 Torpedo SOM Development Kit