• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 264 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.

t.LONGNAME, OMAP-L137

Flamingo
Expert 2290 points

Other Parts Discussed in Thread: OMAP-L137

I'm trying to build code engine examples on the demo version of MV5. The file user.bld in the codec engine examples directory sets t.LONGNAME to ...arm-none-linux-gnueabi-gcc, which does not exist in v5t-le/bin. I think I'm trying to build the correct target (standard Linux) for my Spectrum Digital OMAP-L137 EVM running the demo embedded Linux. Does anyone know what the LONGNAME should be for this configuration?

  • 0
    TI__Mastermind 37340 points

    apologies for the delayed response; to rebuild codec engine examples, simply follow the Building the examples: step-by-step instructions section in the following file

       /home/user/OMAPL137_arm_1_00_00_07/codec_engine_2_22/examples/build_instructions.html

    Below are some useful hints as you go thru the installations instructions above

    Hint 1. in user.bld file, set doBuild to false for uClibc, C64P, and PC.

          { doBuild: false, // build for uC Linux
              target:  "gnu.targets.UCArm9",

          "DSP":    [{doBuild: false, // DSP builds (DSP servers for dual-CPU platforms or full apps for DSP-only platforms)
                    target:  "ti.targets.C64P",

          "PC":     [{doBuild: false,  // build for PC Linux
                    target:  "gnu.targets.Linux86",

    Hint 2. in user.bld change the t.LONGNAME toward the end of the file to point to right tool-chain binary

         if (t.name == "GCArmv5T") {
             t.LONGNAME = "bin/arm_v5t_le-gcc";

    Hint 3. in xdcpaths.mk define the devices (not optional)for only the devices you wish to build (in this case OMAPl137)

        DEVICES := OMAPL137

    Hint 4. if using default installation directories the following paths should be set in your xdcpaths.mk

       CE_INSTALL_DIR        := /home/user/omapl1/OMAPL137_arm_1_00_00_07/codec_engine_2_22
       XDC_INSTALL_DIR       := /home/user/omapl1/OMAPL137_arm_1_00_00_07/xdctools_3_10_03
       BIOS_INSTALL_DIR      := /home/user/omapl1/OMAPL137_arm_1_00_00_07/bios_5_33_03

       # no need to specify the installation directories below if your CE installation
       # has cetools/ directory on top
       USE_CETOOLS_IF_EXISTS := 0
       XDAIS_INSTALL_DIR     := /home/user/omapl1/OMAPL137_arm_1_00_00_07/xdais_6_22_01
       DSPLINK_INSTALL_DIR   := /home/user/omapl1/OMAPL137_arm_1_00_00_07/dsplink-1_61-prebuilt
       CMEM_INSTALL_DIR      := /home/user/omapl1/OMAPL137_arm_1_00_00_07/linuxutils_2_22_01
       FC_INSTALL_DIR        := /home/user/omapl1/OMAPL137_arm_1_00_00_07/framework_components_2_22_01
       BIOSUTILS_INSTALL_DIR := /home/user/omapl1/OMAPL137_arm_1_00_00_07/biosutils_1_02_01

    Hint 5. in xdcpaths.mk fix the name of the tool-chain binary

        CC_V5T = bin/arm_v5t_le-gcc
        CGTARGET = gnu.targets.arm.GCArmv5T