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

Installing and building SYSLink for OMAPL137 in windows 7, Do I need Linux ?

kassem nabha
Prodigy 120 points
Other Parts Discussed in Thread: OMAP-L137, OMAPL138

WE are using Omap-L137 and trying to build a SYSLink example project using the examples provided.

WE are using CCS 5 .

After attempting to run the example project in the SYSlink installation directory to be more specific the fallowing one

SYSLink_install_dir\syslink_2_10_06_28\examples\archive\ti_platforms_evmOMAPL138_elf_linux\ex02_messageq\ex02_messageq

From reading the readme file located at SYSLink_install_dir\syslink_2_10_06_28\examples\archive

Few questions had come up:

How to install SYSLink using windows 7 operating system

How to configured and built SYSLink for the device/platform being used.

How to run "make syslink" from the top-level SysLink installation before buiding the examples.

How to pre-build slaveloader application

and then  Run "make samples-hlos" from the top-level 

SysLink installation before executing "make install" in each of the examples.

How to do all that in windows.

Do I have to use Linux to be able to set up a SYSlink  

Thank you for the help in advance 

Kassem

  • 0
    TI__Mastermind 22760 points

    Kassem,

    If you will be building Linux-based SysLink apps for the Arm9 then you should use a Linux host for building.  You can build only the SysLink rtos (DSP-side) libraries and examples on a Windows machine.  You would need to install SysLink, BIOS, Ipc, XDCtools, and your codegen tools on the windows machine.  After setting your DEVICE and the various install directories in the products.mak, you can then build the rtos side using gmake from the root of your syslink install:

        gmake syslink-rtos

        gmake samples-rtos

    If you want to build the SysLink Linux libraries and examples, you may try these instructions from the DVSDK download page (http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_4_00/latest/index_FDS.html) for setting up a virtual Ubuntu image:

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_4_00/latest/index_FDS.html

    On the other hand, you could also run BIOS on both the Arm9 and the DSP, and you wouldn't need SysLink at all.  Instead you could use Ipc for inter-processor communication.  You can start a CCS project for this by choosing one of the IPC and I/O Examples templates:

    In CCS, select File -> New -> Project

    Choose "Code Composer Studio" -> CCS Project

    Hit the "Next" button, and then you will see the list of project templates and examples, from which you can choose one of the IPC and I/O examples.

    I hope this helps.

    Best regards,

        Janet

  • 0 in reply to janet
    Prodigy 120 points

    Hi Janet,

    I have started to use the IPC and figure out how it works, but I still need to use the SYSLink.

    My main problem is Linux, which ill get around but how do I know what to fill in the products.make file

    more specifically:

    ######## For OMAPL1XX device ########
    else ifeq ("$(DEVICE)","OMAPL1XX")
    LINUXKERNEL =                               $(DEPOT)/_your_linux_kernel_install_
    CGT_ARM_INSTALL_DIR =             $(DEPOT)/_your_arm_code_gen_install_
    CGT_ARM_PREFIX =                         $(CGT_ARM_INSTALL_DIR)/bin/arm-none-linux-gnueabi-

    # If LOADER=ELF then below elf tools path is required else set C674 path
    ifeq ("$(LOADER)","ELF")
    CGT_C674_ELF_INSTALL_DIR= $(DEPOT)/_your_c674elf_code_gen_install_
    else
    CGT_C674_INSTALL_DIR= $(DEPOT)/_your_c674_code_gen_install_
    endif

     

    Thank you 

    Kassem 

  • 0 in reply to kassem nabha
    TI__Mastermind 22760 points

    Kassem,

    If you are using SysLink for a Linux based device, you will need to set LINUXKERNEL to the location of the Linux kernel that has been configured for your target system (eg, for the Arm9 on the OMAPL138).  Since you will need to build the syslink driver and libraries, you need to set the paths to the codegen tools to build them.  For example, in the products.mak file at the root of my SysLink installation, I have set:

    DEVICE = OMAPL1XX

    # Master core (GPP) OS type (choose one): Linux, Qnx, Bios, Android
    #
    GPPOS = Linux

    # SysLink HLOS driver options variable (choose one): 0 or 1
    #
    SYSLINK_BUILD_DEBUG=1
    SYSLINK_BUILD_OPTIMIZE=0
    SYSLINK_TRACE_ENABLE=1

    # Set SDK type when building for a TI SDK kit (choose one): EZSDK or NONE
    #
    SDK = NONE

    # Define root dir to install SysLink driver and samples for target file-system
    #
    EXEC_DIR = /tmp

    # Optional: choose one to override DEVICE-specific default: COFF, ELF
    #
    LOADER = ELF

    # Optional: recommended to install all dependent components in one folder.
    #
    DEPOT = _your_depot_folder_


    # Define the product variables for the device you will be using.
    #

    ...

    ######## For OMAPL1XX device ########
    else ifeq ("$(DEVICE)","OMAPL1XX")
    LINUXKERNEL             =  $(VENDORS)/kernel_org/arm/DaVinci-PSP-SDK-03.21.00.04/src/kernel/linux-03.21.00.04
    CGT_ARM_INSTALL_DIR     = $(VENDORS)/cs/arm/arm-2009q1-203
    CGT_ARM_PREFIX          = $(CGT_ARM_INSTALL_DIR)/bin/arm-none-linux-gnueabi-
    IPC_INSTALL_DIR         = $(TREES)/ipc/ipc-h32/exports/ipc_1_24_03_32
    BIOS_INSTALL_DIR        = $(TREES)/avalaprod/avalaprod-i46/exports/bios_6_33_05_46
    XDC_INSTALL_DIR         = $(TREES)/xdcprod/xdcprod-p53/product/Linux/xdctools_3_23_03_53

    # If LOADER=ELF then below elf tools path is required else set C674 path
    ifeq ("$(LOADER)","ELF")
    CGT_C674_ELF_INSTALL_DIR= $(VENDORS)/ti/c6x/7.2.2/Linux
    else
    CGT_C674_INSTALL_DIR= $(DEPOT)/_your_c674_code_gen_install_
    endif
    ######## End of device specific variables ########

    Then I run 'make' from the root of my SysLink installation to build the syslink.ko driver and the syslink libraries for both the Arm and the DSP.  This step needs to be done before building the SysLink examples.

    Best regards,

        Janet

  • 0 in reply to janet
    Prodigy 120 points

    Hello Janet,

    That was a great help thank you.

    One more question if you please.

    we are using OMAP L137, our first step in the project is to read a file from the sd card, do some processing and then store back on the sd card.

    Is this possible and if it is, what is the best approach: IPC , SYSLink or  DSPLink

    The next step of the project is to get an audio input, do some processing, and store the data or output the data 

    Again what would the best approach be.

    Thank you,

    Kassem.

  • 0 in reply to kassem nabha
    TI__Mastermind 22760 points

    Kassem,

    You may want to develop your application on the DSP only, at least to start with, especially, given that you don't have a Linux development environment.  Also, the OMAP L137 is an older device, and SysLink has not been validated on it.

    You can find software downloads for the DSP here:

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

    If you click on BIOS Platform Support Packages you will find a BIOS PSP for OMAPL13x that you can download, along with user's guide and release notes.  There is an MMCSD driver for the DSP, which depends on the EDMA3 low level driver, so you would need to download that too.  You can get that here.  So you should be able to read data from a file on the MMC card from the DSP, and write it back out.  You could also, initially, just read and write the data to a file on the host PC, before trying the MMC.

    You will need to use BIOS 5 (not 6), which you should have with your CCS installation.

    If you want to use both the Arm and the DSP you will need a Linux host.  You can download the Linux software here:

    http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_sb/S1SDKLNX/SDK_EA2OMAPL137LNX/index_FDS.html

    I believe this download will come with DspLink.  It will not come with SysLink.  So I would recommend that if you need to use both Arm and DSP, to use DspLink.  But whether you use Arm and DSP, or just DSP, really depends on what you're ultimately trying to do.

    Best regards,

        Janet

  • 0 in reply to janet
    Prodigy 120 points

    Hey Janet,

    First I want to thank you for your help.

    I have few more small questions for you, we originally started working on DSPLink but since we are working with code composer studio 5,

    it seams harder to get it working, because there is no examples related to DSPLink with CCS 5.

    Is DSPLink the same as SYSLink in terms that we have to use a Linux Host ?

    Regarding IPC is it out of the picture ?

    Thank you very much for you help.

    Kassem

  • 0 in reply to kassem nabha
    TI__Mastermind 22760 points

    Kassem,

    DSPLink and SysLink both assume you have a high-level OS (such as Linux, WinCE, QNX) running on the Arm, and BIOS running on the DSP.  SysLink is the newer version of DSPLink, and is used for BIOS 6 based systems, while DSPLink is BIOS 5 based.  If you have Linux running on the Arm, you will need a Linux based build host to run the Arm codegen tools.  If you want to have BIOS 6 running on both the Arm and the DSP and pass messages or stream data between the two processors, then IPC should be fine.

    Best regards,

        Janet