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.

Codec engine 2.24 build error

Other Parts Discussed in Thread: OMAP3530

Hi,all

I downloaded the CE2.24 and build the source code under "codec_engine_2_24\packages\ti\sdo\ce\ipc\dsplink" following the Readme.txt , and when build it , errors below turn up:

E:\CE_WinCE\codec_engine_2_24\packages\ti\sdo\ce\ipc\dsplink>gmake
E:/CE_WinCE/xdctools_3_10_05_61/xdc XDCPATH="E:/CE_WinCE/codec_engine_2_24/examp
les;E:/CE_WinCE/codec_engine_2_24/cetools/packages;E:/CE_WinCE/codec_engine_2_24
/packages;E:/CE_WinCE/codec_engine_2_24/cetools/packages" all
making package.mak (because of package.bld) ...
config.bld: Running the version from Codec Engine Examples.
js: "E:/CE_WinCE/codec_engine_2_24/examples/ti/sdo/ce/examples/buildutils/Platfo
rms.xs", line 75: TypeError: Cannot call method "match" of undefined (E:/CE_WinC
E/codec_engine_2_24/examples/ti/sdo/ce/examples/buildutils/Platforms.xs#75)
    "E:/CE_WinCE/codec_engine_2_24/examples/config.bld", line 138
all files complete.

Would someone give me some help to fix it?

Thanks & Best Regards,

Stephen

  • Hi Stephen,

    You should not actually need to build the package, ti\sdo\ce\ipc\dpslink, in order to build the codec engine exampl programs. The

    readme.txt in this directory was set up for Linux builds, when porting DSPLink and codec engine to a new device . Is there a reason you wanted to

    build this package?

    Regards,

        Janet

  • HI, Janet,

    Thanks for you reply. In fact, I want to port the codec engine and dsplink to a new device which is not catalog now.

    How should I do if I port the codec engine and dsplink to a new device?

    Thanks

    Stephen

  • Hi Stephen,

    From your build errors, it looks like you're trying to build for Windows CE. Here is something you can try:

    Edit the makefile in codec_engine_2_24/packages/ti/sdo/ce/ipc/dsplink to set the environment variables (you may have already done that. For example, I have:

    XDC_INSTALL_DIR := C:/xdctools_3_10_05_61
    CE_INSTALL_DIR  := C:/mytools/codec_engine_2_24
    DSPLINK_REPO    := C:/mytools/dsplink_1_61_04
    USER_BLD        := C:/mytools/examples_2_24

    Now make the following changes to the makefile below the environment variables (changes are marked red):

    include $(USER_BLD)/xdcpaths.mak

    # No changes below this line
    XDC_PATH := $(USER_BLD);$(DSPLINK_REPO);$(CE_INSTALL_DIR)/packages;$(CE_INSTALL_DIR)/cetools/packages


    include $(USER_BLD)/buildutils/xdcrules.mak

    #all:
    #%::
    # $(XDC_INSTALL_DIR)/xdc XDCPATH="$(XDC_PATH)" $@
    #
    #  @(#) ti.sdo.ce.ipc.dsplink; 2, 0, 1,120; 6-3-2009 02:28:54; /db/atree/library/trees/ce/ce-n07x/src/
    #

    Then run gmake again. 

    Best regards,

        Janet

  • Hi, Janet,

    Thanks for your help. Yes, I work on WinCE.

    I following  your guide and the build is moving on, but another error(I thought it was) turns up:

    **** DRA44X

    Remark: module 'dsplink.gpp.Global' not found, this package will not be built.

    Then, when build is over ,I can not see any libs recreated under lib/release or lib/debug 

  • Hi Stephen,

    The error you are getting: Remark: module 'dsplink.gpp.Global' not found, occurs when dsplink has not been built properly. If you

    have built DSPLink according to one of the install guides (eg, InstallGuide_WinCE_OMAP3530.pdf),  you may also have to run the

    XDC command (although this may already be built into the DSPLink build process). You can do this by running the following commands:

    cd into the $(DSPLINK)/dsp directory and run:

    $ $(XDC_INSTALL_DIR)/xdc clean

    $ $(XDC_INSTALL_DIR)/xdc .interfaces

     

    cd into the $(DSPLINK)/gpp directory and run:

     

    $ $(XDC_INSTALL_DIR)/xdc clean

    $ $(XDC_INSTALL_DIR)/xdc .interfaces

     

    Regards,

        Janet

     

  • Hi, Janet, 

     Thanks for your help. I have fixed it, I set the DSPLINK_REPO path wrong , so ...

     

    By the way, if I want to port the CE to a new devices, what should I do? Can I rebuild codec_engine_2_24\packages\ti\sdo\ce ?

    Thanks 

    Stephen

  • Hi,Janet

    I am building the whole ce now, but when building the codec_engine_2_24\packages\ti\sdo\

    ce\osal\wince ,  the file Reg.h  is missing. I searched the file, but didn't find it. This file is included in file Reg_wince.c?

    Do you have this file in your ce ?

     

    Thanks 

    Stephen

  • Stephen,

    We are also facing the same issue when building the CE 2.24 downloaded from TI website for WinCE.

    Did you try building the Codec Engine OSAL with the reg.h commented? I feel that it only contains the API declarations.

    By the way, since you are building for DRA44x device, you need to update your DSPLINK configuration as well? Have you done that? We were able to build LINK 1.6104 for DM6446 on WinCE and test most of the sample apps.

     

     

  • Ravindra,

    Thanks for yr reply. I will have a try with the reg.h commented.

    As you know, the dsplink for DRA44x under wince is not supported now, so I am trying to modified the dsplink for DRA44x.

    Best Regards,

    Stephen Zhang

  • Stephen,

    If you are trying to build dsplink for DRA44x, why don't you change the platform type as JACINTO1 or JACINTO2. I believe the LINK 1.61.04 already supports the DRA44x platforms via these platform names.

    For CE 2.24, there is no build target called JACINTO and that becomes a problem. Are you trying to build only the ipc/dsplink folder or the complete ti.sdo.ce path.

    We are facing problems when we re-build the complete ti.sdo.ce path. Missing config.bld

    Regards

  • Ravindra,

    In fact, the JACINTO1 (DRA44X)and JACINTO2 are supported by dsplink 1.61.04 for PROS not WinCE, so I need to modify the dsplink, is that right?

    I am trying to rebuild the ti.sdo.ce, I am thinking that some packages under ti.sdo.ce may don't need to  be rebuild as some ones are for DSP usage.  I will check again the config.bld to give you a reply.

     

    Best Regards,

    Stephen