• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 102 subscribers
  • Views 1730 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Sys/BIOS on Beagleboard

Valdez V.
Intellectual 635 points
Other Parts Discussed in Thread: OMAP3530

Hi Everybody,

I'd like to learn how to use DSP core on my Beagleboard with OMAP3530. It is possible to find in network some tutorials for DspLINK and I was almost decided to start with it. Additionally Beagleboard wiki site says that it is good choice and SysLINK is for OMAP4. But then I saw that SysLINK supports OMAP3530. Unfortunatelly I didn't found any description/tutorial how to prepare Linux system witch can use DSP core by SysLINK. Do you know some? Do you think it is harder or easier to start with SysLINK without experience with DspLINK? Or maybe after I read user guide, installation guide etc. you could help such a noob like me on this forum?

EDIT: Btw SysLINK is Sys/BIOS with Link, like it was explained here about DspLink?

Best regards,

Valdez

  • 0
    TI__Intellectual 2790 points

    Valdez:

       SysLink does support OMAP3530:  http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/syslink/2_20_00_14/exports/syslink_2_20_00_14/syslink_2_20_00_14_ReleaseNotes.html#Device_Support

       The question is: What kind of application are you going to build?

       If you want to create a certain type of video, speech, image or audio multimedia algorithm on the DSP, and want an ARM application to invoke it, you can use Codec Engine: http://processors.wiki.ti.com/index.php/Category:Codec_Engine 

       If you just want to run some arbitrary DSP code, and just need the ARM to DSP inter-processor communication, you could use SysLink: http://processors.wiki.ti.com/index.php/SysLink_Overview

      I would not use DSPLink, as that is an older product, no longer under development.
    Regards,
    - Gil
  • 0 in reply to GAnthony
    Intellectual 635 points

    Thanks GAnthony.

    Finally I have time to do something with it.

    I followed SysLink 2.20.02.20 Install Guide. I installed first:

    • XDCtools 3.23.03.53

    • SYS/BIOS 6.33.05.46

    • IPC 1.24.03.32

    • Linux GCC - CodeSourcery 2009q1-203

    • C6000 Code Generation Tools 7.2.2

    Could you help me with settings in products.mak file? I'm not sure about these.

    This is obvious:

    SYSLINK_INSTALL_DIR = $(CURDIR)
    DEVICE = OMAP3530
    GPPOS = Linux

    This I think I can leave default now at the beginning:

    SYSLINK_BUILD_DEBUG=1
    SYSLINK_BUILD_OPTIMIZE=0
    SYSLINK_TRACE_ENABLE=1
    SYSLINK_NOTIFYDRIVER=NOTIFYDRIVERSHM
    SYSLINK_TRANSPORT=TRANSPORTSHM

    I just want start simple provided examples so can I leave it:

    SDK = NONE ?

    That root dir is for files that I need to load on board? I have it now like this ( I created EXEC_DIR in syslink directory):

    EXEC_DIR = $(SYSLINK_INSTALL_DIR)/EXEC_DIR

    For loader format files I choosed ELF, because of notes in Install Guide:

    LOADER = ELF

    DEPOT is a directory where I have installed other components like mentioned above, useful for next variables setting? So I can set it like:

    DEPOT = /home/valdez/dsp/ ?

    And later in ######## For OMAP3530 device ######## section I set simply paths to all of that components? Not to bin subdirectories? Deeper path is only for crosstool prefix as we can see there?

    Cheers,

    Valdez

  • 0 in reply to Valdez V.
    TI__Expert 6860 points

    It look like you have everything setup correctly.  To build for the beagleboard, this is what is needed:

               DEVICE=OMAP3530
           GPPOS=Linux
           LOADER=ELF  /*Note this is the default */
           SDK=NONE
           SYSLINK_INSTALL_DIR=/home/user/syslink_x_xx_xx_xx \
           IPC_INSTALL_DIR=/home/user/ipc_x_xx_xx_xx \
           BIOS_INSTALL_DIR=/home/user/bios_x_xx_xx_xx \
           XDC_INSTALL_DIR=/home/user/xdctools_x_xx_xx_xx \
           LINUXKERNEL=/home/user/OMAP3530-LINUX-PSP-xx.xx.xx.xx/src/kernel/linux-xx.xx.xx.xx
           CGT_ARM_INSTALL_DIR=/home/user/arm/arm-xxxxqx-xxx
           CGT_ARM_PREFIX=/home/user/arm/arm-xxxxqx-xxx/bin/arm-none-linux-gnueabi-
           CGT_C64P_ELF_INSTALL_DIR=/home/user/c6x/x.x.x/

    The DEPOT variable is an convenient way to set some of the needed variable for some of the 
    dependent components (IPC, XDC, BIOS) assuming they are installed in a common root 
    directory.