• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 536 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.

DSPLINK for OMAP2430

Matthew Weber
Prodigy 110 points

Other Parts Discussed in Thread: OMAP3530

Looking to do a Linux integration with DSPLink on a OMAP2430 SDP board and then port to target hardware.  Is there a unoffical or older release of DSPLink that supports that chip?

 

  • 0
    TI__Genius 17205 points

    The latest DSP Link releases support OMAP2530, per their release notes.

    http://software-dl.ti.com/dsps/dsps_public_sw/DSPLink/index.html

    I don't know specifics, but my understanding is that, at least for the HW dependencies DSP Link has, the OMAP2430 and OMAP2530 devices are "close enough" that you could start with 2530, and there may not be much porting necessary.

    Chris

  • 0 in reply to Chris Ring
    Prodigy 110 points

    Thanks!

    I was able to get the DSP samples built and got a start on the GPP.  Currently the issues I'm seeing are related to the IO_ADDRESS macro mapping.   From what I can tell there were some changes made in the latest kernels that don't support what this macro is looking for while building the dsplinkk.ko.  Here's the error I get.  I'm trying to understand the changes I'll have to do to get a 2.6.36 kernel working with DSPLINK.

    [PMGR                ] ------- TARGET ---------------- DEBUG --------------
    Generating dsplinkk.o...
    Post processing kernel module dsplinkk...
    ERROR: "IO_ADDRESS" [/home/user/Desktop/dsplink/gpp/BUILD/PMGR/BIN/DEBUG/dsplinkk.ko] undefined!
    make[2]: *** [dsplinkk.o.deb] Error 1
    make[1]: *** [trgdeb] Error 2

  • 0 in reply to Matthew Weber
    TI__Expert 4930 points

    Matthew

    Which version of DSPLink are you on?

    In 1.65.00.03 available at http://software-dl.ti.com/dsps/dsps_public_sw/DSPLink/index.html

    In this release, only OMAP3530 is verified with newer kernels. In the platform files for OMAP3530 you will see code snippets for replacing IO_ADDRESS with ioremap in the function OMAP3530_phyShmemInit and  iounmap in OMAP3530_phyShmemExit. Reference at   $(DSPLINK)/gpp/src/arch/OMAP3530/shmem/Linux/omap3530_phy_shmem.c

    Please use above file as reference for the changes for OMAP2530 at $(DSPLINK)/gpp/src/arch/OMAP2530/shmem/Linux/omap2530_phy_shmem.c

    Another change that you will require is that the ioctl call is no longer present in the newer kernels. See attached a file for the changes to replace ioctl by unlocked_ioctl. The location for the updated file is $(DSPLINK)/gpp/src/pmgr/Linux/2.6.18/drv_pmgr.c

    Please do the above changes, rebuild DSPLink and try.

    Deepali

  • 0 in reply to Deepali Uppal
    Prodigy 110 points

    I'm currently using 1.63.

    I was able to get it to build by recreating the IO_ADDRESS and also commenting out the ioctl, but haven't tested it on hardware yet, so I'm guessing there's a good chance I'll have further issues.  I'll take a look at replacing/updating those calls and then give it a try.

    Thanks for the info and quick response!

     

  • 0 in reply to Matthew Weber
    Prodigy 110 points

    Do you happen to know the mmu mapping size for the PRCM?  I'm assuming the mailbox and general control will match the omap3530?

        halObject->generalCtrlBase = (Uint32)ioremap(GENERAL_CONTROL_BASE, SZ_4K) ;
        halObject->mailboxBase     = (Uint32)ioremap(MAILBOX_BASE, SZ_4K) ;
        halObject->prcmBase        = (Uint32)ioremap(PRCM_BASE, SZ_8K?????) ;