• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Digital Signal Processors (DSP) » DaVinci™ Video Processors » DM64x DaVinci Video Processor Forum » Where to Obtain Latest Tool Releases?
Share
DaVinci™ Video Processors
  • Forums
  • Announcements
Options
  • Subscribe via RSS

Where to Obtain Latest Tool Releases?

Where to Obtain Latest Tool Releases?

This question is not answered
HyperGalaxy
Posted by HyperGalaxy
on Oct 22 2008 14:34 PM
Intellectual650 points

Where can I obtain the lastest version of the following:

 

* BIOSutils

* the latest version DSPlink

* the latest version of the Code Generation tools

 

Have a great day!

 

Take care,

Darwin

BIOSutils DSPlink Code Generation Tools
Report Abuse
  • Reply
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
All Replies
  • BrandonAzbell
    Posted by BrandonAzbell
    on Oct 22 2008 14:53 PM
    Guru54850 points

    Assuming a license of Code Composer Studio is available to you, you can use the Update Advisor in the Help->Update Advisor->Check for Updates.

    Brandon

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Bernie Thompson TI
    Posted by Bernie Thompson TI
    on Oct 22 2008 15:00 PM
    Mastermind41680 points

    In the context of Davinci devices I would typically suggest using the tool versions that are associated with the particular DVSDK you are using, which can be obtained through www.ti.com/davinciregistration, using varying tool versions could conflict with each other and may cause problems.

    For the actual latest versions, the wiki article here has a link to download the latest version of BIOS Link, following through that link on the left of the download page there is a link to get to where you can download BIOS and additional target tools, and the wiki article here has a link to download the lastest version of the code generation tools.

    DaVinci BIOS download
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • HyperGalaxy
    Posted by HyperGalaxy
    on Oct 22 2008 15:48 PM
    Intellectual650 points

    Thanks, Bernie. However, the issue with using the DVEVM update site is that it does not seem to have all of the needed tools, at least that seemed to be my impression when I was trying to get everything installed (perhaps that is not the case, though). There do seem to be compatibility issues with using the latest versions of the tools that I could find, though, as you stated.

     

    I upgraded to MV Linux 5.0 and downloaded and installed the latest versions (that I could find) of the various T.I. tools. However, now I am getting an error that indicates that my XDC path might not be correct:


    Making all in subdirectory encodedecode...
    make[2]: Entering directory `/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/encodedecode'
    XDCPATH="/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/dm6446_dvsdk_combos_1_35/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/dsplink_1_51/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdais_6_20/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/linuxutils_2_20/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/framework_components_2_20_01/packages" /home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/xs xdc.tools.configuro -c /opt/montavista/pro/devkit/arm/v5t_le -o encodedecode_config -t gnu.targets.MVArm9 \
            -p ti.platforms.evmDM6446 encodedecode.cfg
    making package.mak (because of package.bld) ...
    generating interfaces for package encodedecode_config (because package/package.xdc.inc is older than package.xdc) ...
    configuring encodedecode.x470MV from package/cfg/encodedecode_x470MV.cfg ...
    js: "/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages/xdc/cfg/Main.xs", line 200: xdc.services.global.XDCException: xdc.PACKAGE_NOT_FOUND: can't locate the package 'dsplink.gpp' along the path: '/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/dm6446_dvsdk_combos_1_35/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/dsplink_1_51/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdais_6_20/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/linuxutils_2_20/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/framework_components_2_20_01/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages;..;'. Ensure that the package path is set correctly.
        "/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages/xdc/cfg/Main.xs", line 174
        "/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages/xdc/cfg/Main.xs", line 154
        "/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages/xdc/xs.js", line 125
    gmake: *** [package/cfg/encodedecode_x470MV.c] Error 1


    However, I think that this might have something to do with the latest version of DSP Link. (The new version now has two directories and no installation instructions.)

     

    Have a great day!

     

    Take care,

    Darwin

    BIOSutils DSP/BIOS Link XDC DSP/BIOS Code Generation Tools Linux Utils
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • BrandonAzbell
    Posted by BrandonAzbell
    on Oct 22 2008 19:22 PM
    Guru54850 points

    HyperGalaxy,

    What version of DSP/BIOS Link have you downloaded and attempted to use in the above DVSDK v1.30.01.41?

    I believe you will need to build dsplink prior to building the DVSDK, although I am speaking only from memory.  The Rules.make in the DVSDK directory will point to the DSP/BIOS Link directory, but I don't think it goes into that directory and builds like some of the other components.
    DSPLINK has its own configuration that needs to take place to identify what services are to be implemented, etc.

    Brandon

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • HyperGalaxy
    Posted by HyperGalaxy
    on Oct 23 2008 16:22 PM
    Intellectual650 points

    Brandon,

     

    Thanks, much, for your reply. That is potentially valuable information (especially given the fact that DSPlink does not seem to have any installation instructions).

     

    I was trying to use DSP/BIOS Link version 1.51, but now I am about to try falling back to version 1.40-05p1 (the version that came with the DVSDK version 1.30.01.41).

     

    Have a great day!

     

    Take care,

    Darwin

    DSP/BIOS Link
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • BrandonAzbell
    Posted by BrandonAzbell
    on Oct 24 2008 23:17 PM
    Guru54850 points

    In trying to model your development environment, I also discovered that using DSP/BIOS Link v1.51 was not convenient with the DVSDK v1.30.01.41.  I discovered that you needed to also upgrade Codec Engine as well.

    There is a Codec Engine v2.10.02 that you can download and use with DVSDK v1.30.01.41.  This particulare Codec Engine version comes with a bundled version of DSP/BIOS Link v1.50.  Once I pointed the Rules.make to this newer Codec Engine and the DSP/BIOS Link to the following, the build environment completed without error.

    Rules.make file
    ------------------
    CE_INSTALL_DIR=$(PROJECTDIR)/codec_engine_2_10_02
    LINK_INSTAL_DIR=$(CE_INSTALL_DIR)/cetools
    ------------------

    I use an environment variable in my projects called $PROJECTDIR to help make the entire work area portable.  In my case, $PROJECTDIR=<where I installed the dvsdk_1_30_01_41> directory.

    Brandon

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Brad Griffis
    Posted by Brad Griffis
    on Oct 27 2008 11:20 AM
    Guru57330 points

    Codec Engine 2.21 will add support for MVPro 5.0.  It will be available in 2-3 weeks and will include other important components such as CMEM, Framework Components, and DSP/BIOS Link.  All of those components will have been validated on MVPro 5.0.  I recommend that at the bare minimum you wait for that release.  Depending on your needs you might want to consider waiting for DVSDK 2.0 which will be built upon those components.  It will give you a fully integrated codec environment and will likely be the best "user experience" in terms of getting things working quickly.  The only downside is that DVSDK 2.0 will not be released until mid 1Q09.

    Brad

    ---------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    --------------------------------------------------------------------------------------------------------- 

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Brad Griffis
    Posted by Brad Griffis
    on Oct 27 2008 11:59 AM
    Guru57330 points

    Details on the versions of Link, Framework Components, CMEM are given here:

    http://wiki.davincidsp.com/index.php?title=Codec_Engine_Roadmap

    ---------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    --------------------------------------------------------------------------------------------------------- 

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • HyperGalaxy
    Posted by HyperGalaxy
    on Nov 03 2008 19:11 PM
    Intellectual650 points

    Brandon,

     

    Where did you find the Codec Engine V2.10.02? (I can only find V2.10.01...)

     

    Have a great day!

     

    Take care,

    Darwin

    codec engine
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • HyperGalaxy
    Posted by HyperGalaxy
    on Nov 03 2008 19:47 PM
    Intellectual650 points

    Brandon,

     

    I am still getting errors when trying to build the codecs:

     

    Making all in subdirectory encodedecode...
    make[2]: Entering directory `/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/encodedecode'
    XDCPATH="/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/dm6446_dvsdk_combos_1_35/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/cetools/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdais_6_20/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/linuxutils_2_20/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/framework_components_2_20_01/packages" /home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/xs xdc.tools.configuro -c /opt/montavista/pro/devkit/arm/v5t_le -o encodedecode_config -t gnu.targets.MVArm9 \
            -p ti.platforms.evmDM6446 encodedecode.cfg
    making package.mak (because of package.bld) ...
    generating interfaces for package encodedecode_config (because package/package.xdc.inc is older than package.xdc) ...
    configuring encodedecode.x470MV from package/cfg/encodedecode_x470MV.cfg ...
    ti.sdo.ce.utils.trace.close() ...
    ti.sdo.ce.utils.trace.validate() ...
        will link with ti.sdo.ce.utils.trace:lib/TraceUtil.av5T
        will link with ti.sdo.ce.bioslog:lib/bioslog.av5T
        will link with ti.sdo.ce.video:lib/video.av5T
        will link with ti.sdo.ce:lib/ce.av5T
        will link with ti.sdo.ce.alg:lib/Algorithm_noOS.av5T;lib/alg.av5T
        will link with ti.sdo.ce.ipc.dsplink:lib/ipc_dsplink_6446.av5T
    js: "/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages/xdc/cfg/Main.xs", line 25: XDC runtime error: can't find the library 'lib/ipc_dsplink_6446.av5T' specified by package ti.sdo.ce.ipc.dsplink. It wasn't found along the path '/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/dm6446_dvsdk_combos_1_35/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/cetools/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdais_6_20/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/linuxutils_2_20/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/framework_components_2_20_01/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages;/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages;..;'.
        "/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages/xdc/cfg/Main.xs", line 163
        "/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages/xdc/xs.js", line 125
    gmake: *** [package/cfg/encodedecode_x470MV.c] Error 1
    gmake: *** Deleting file `package/cfg/encodedecode_x470MV.c'
    gmake: *** [package/cfg/encodedecode_x470MV.c] Deleting file `package/cfg/encodedecode_x470MV.xdl'
    gmake: *** [package/cfg/encodedecode_x470MV.c] Deleting file `package/cfg/encodedecode_x470MV.h'
    /opt/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc -Wall -Dti_sdo_ce_osal_Memory_USEDEPRECATEDAPIS=1 -I/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/utils/include -I/home/darwin/projects/LightSpeed/ti-davinci_evm-arm_v5t_le_MV5/linux-2.6.18_pro500/include -c -g -D__DEBUG  -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/dm6446_dvsdk_combos_1_35/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/cetools/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdais_6_20/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/linuxutils_2_20/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/framework_components_2_20_01/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages" -I".."   -Dxdc_target_types__="gnu/targets/std.h" -Dxdc_target_name__=MVArm9 -Dxdc_cfg__header__="/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/encodedecode/encodedecode_config/package/cfg/encodedecode_x470MV.h" -o debug/capture.o capture.c
    capture.c: In function ‘captureThrFxn’:
    capture.c:362: warning: pointer targets in passing argument 2 of ‘initCaptureDevice’ differ in signedness
    /opt/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc -Wall -Dti_sdo_ce_osal_Memory_USEDEPRECATEDAPIS=1 -I/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/utils/include -I/home/darwin/projects/LightSpeed/ti-davinci_evm-arm_v5t_le_MV5/linux-2.6.18_pro500/include -c -g -D__DEBUG  -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/dm6446_dvsdk_combos_1_35/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/cetools/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdais_6_20/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/linuxutils_2_20/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/framework_components_2_20_01/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages" -I".."   -Dxdc_target_types__="gnu/targets/std.h" -Dxdc_target_name__=MVArm9 -Dxdc_cfg__header__="/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/encodedecode/encodedecode_config/package/cfg/encodedecode_x470MV.h" -o debug/ctrl.o ctrl.c
    /opt/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc -Wall -Dti_sdo_ce_osal_Memory_USEDEPRECATEDAPIS=1 -I/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/utils/include -I/home/darwin/projects/LightSpeed/ti-davinci_evm-arm_v5t_le_MV5/linux-2.6.18_pro500/include -c -g -D__DEBUG  -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/dm6446_dvsdk_combos_1_35/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/cetools/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdais_6_20/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/linuxutils_2_20/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/framework_components_2_20_01/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages" -I".."   -Dxdc_target_types__="gnu/targets/std.h" -Dxdc_target_name__=MVArm9 -Dxdc_cfg__header__="/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/encodedecode/encodedecode_config/package/cfg/encodedecode_x470MV.h" -o debug/display.o display.c
    /opt/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc -Wall -Dti_sdo_ce_osal_Memory_USEDEPRECATEDAPIS=1 -I/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/utils/include -I/home/darwin/projects/LightSpeed/ti-davinci_evm-arm_v5t_le_MV5/linux-2.6.18_pro500/include -c -g -D__DEBUG  -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/dm6446_dvsdk_combos_1_35/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/cetools/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdais_6_20/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/linuxutils_2_20/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/framework_components_2_20_01/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages" -I".."   -Dxdc_target_types__="gnu/targets/std.h" -Dxdc_target_name__=MVArm9 -Dxdc_cfg__header__="/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/encodedecode/encodedecode_config/package/cfg/encodedecode_x470MV.h" -o debug/main.o main.c
    main.c: In function ‘main’:
    main.c:523: warning: missing sentinel in function call
    /opt/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc -Wall -Dti_sdo_ce_osal_Memory_USEDEPRECATEDAPIS=1 -I/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/utils/include -I/home/darwin/projects/LightSpeed/ti-davinci_evm-arm_v5t_le_MV5/linux-2.6.18_pro500/include -c -g -D__DEBUG  -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/dm6446_dvsdk_combos_1_35/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/cetools/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdais_6_20/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/linuxutils_2_20/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/framework_components_2_20_01/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages" -I".."   -Dxdc_target_types__="gnu/targets/std.h" -Dxdc_target_name__=MVArm9 -Dxdc_cfg__header__="/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/encodedecode/encodedecode_config/package/cfg/encodedecode_x470MV.h" -o debug/ui.o ui.c
    /opt/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc -Wall -Dti_sdo_ce_osal_Memory_USEDEPRECATEDAPIS=1 -I/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/utils/include -I/home/darwin/projects/LightSpeed/ti-davinci_evm-arm_v5t_le_MV5/linux-2.6.18_pro500/include -c -g -D__DEBUG  -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/dm6446_dvsdk_combos_1_35/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/codec_engine_2_20_01/cetools/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdais_6_20/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/linuxutils_2_20/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/framework_components_2_20_01/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages" -I"/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages" -I".."   -Dxdc_target_types__="gnu/targets/std.h" -Dxdc_target_name__=MVArm9 -Dxdc_cfg__header__="/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/encodedecode/encodedecode_config/package/cfg/encodedecode_x470MV.h" -o debug/video.o video.c
    /opt/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc -lfreetype -lpng -ljpeg -lpthread -o debug/encodedecoded debug/capture.o debug/ctrl.o debug/display.o debug/main.o debug/ui.o debug/video.o encodedecode_config/linker.cmd /home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/utils/lib/simplewidgetd.a /home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/utils/lib/msp430libd.a /home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/utils/lib/rszcopyd.a /home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/utils/lib/smoothd.a
    arm_v5t_le-gcc: encodedecode_config/linker.cmd: No such file or directory
    make[2]: *** [debug/encodedecoded] Error 1
    make[2]: Leaving directory `/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446/encodedecode'
    make[1]: *** [encodedecode] Error 2
    make[1]: Leaving directory `/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/demos/dm6446'
    make: *** [demos/dm6446] Error 2

     

    Do you have any idea what could be wrong with my setup? Also, can you please send me your Rules.make and xdcpaths.mak files?

     

    Have a great day!

     

    Take care,

    Darwin

     

     

    DVSDK codec engine DSP/BIOS Link XDAIS XDC Code Generation Tools
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Juan Gonzales
    Posted by Juan Gonzales
    on Nov 03 2008 19:54 PM
    Mastermind33935 points

    you can get v.2.10.02 thru Update Advisor assuming you have CCS License; let me know if you need further help with this.

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Juan Gonzales
    Posted by Juan Gonzales
    on Nov 03 2008 20:03 PM
    Mastermind33935 points

    May I ask where you got the codec(s) from? FYI, they do not come as part of DVSDK. 

    The error suggests there is a missing liker.cmd file; I am wondering if you have all the files necessary to perform the build.

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Brad Griffis
    Posted by Brad Griffis
    on Nov 03 2008 21:28 PM
    Guru57330 points

    error

    ti.sdo.ce.utils.trace.validate() ...
        will link with ti.sdo.ce.utils.trace:lib/TraceUtil.av5T
        will link with ti.sdo.ce.bioslog:lib/bioslog.av5T
        will link with ti.sdo.ce.video:lib/video.av5T
        will link with ti.sdo.ce:lib/ce.av5T
        will link with ti.sdo.ce.alg:lib/Algorithm_noOS.av5T;lib/alg.av5T
        will link with ti.sdo.ce.ipc.dsplink:lib/ipc_dsplink_6446.av5T
    js: "/home/darwin/projects/LightSpeed/dvsdk_1_30_01_41/xdctools_3_10_02/packages/xdc/cfg/Main.xs", line 25: XDC runtime error: can't find the library 'lib/ipc_dsplink_6446.av5T'

    From the files above it would appear that you're using one of the new versions of XDCtools and taking advantage of the new GCArmv5T target.  It appears that the getLibs function that is part of that RTSC package was written before GCArmv5T and so it is incorrectly generating the filenames.  The "proper" solution is for that package (in this case codec engine) to update its getLibs function.  That has actually been done in CE 2.20 and later.  So for you to use that specific version the easiest thing you can do would be to use the MVArm9 target instead of the GCArmv5T target.  Is that a possibility?  There is another workaround, but I don't remember the syntax off the top of my head.

    Brad

    ---------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    --------------------------------------------------------------------------------------------------------- 

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Juan Gonzales
    Posted by Juan Gonzales
    on Nov 03 2008 23:47 PM
    Mastermind33935 points

    Brad,

    I totally missed this error; it is a good thing you were more awake than I.

    Normally you should look at the codec release notes (all codec(s) should be accompanied by a set of release notes) and use the version of codec engine (and other software components) listed in the release notes.  This will save you many head-aches.

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • HyperGalaxy
    Posted by HyperGalaxy
    on Nov 04 2008 18:43 PM
    Intellectual650 points

    I am using V1.30.01-41 of the DVSDK. I assumed that this does have the codecs, since the default Rules.mak file sets the CODEC_INSTALL_DIR variable to $(DVSDK_INSTALL_DIR)/dm6446_dvsdk_combos_1_35, and that directory exists and has the packages/ti/sdo/codecs subdirectory which contains various codecs...

     

    If I need additional codecs, where do I obtain them?

     

    Have a great day!

     

    Take care,

    Darwin

    DVSDK
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
12345»
TI E2E™ Community
  • Support Forums
  • Blogs
  • Videos
  • Groups
  • Site Support & Feedback
  • Settings
TI E2E™ Community Groups
  • TI University Program
  • Make the Switch
  • Microcontroller Projects
  • Motor Drive & Control
Other Communities
  • Deyisupport
  • Designsomething.org
  • beagleboard.org
  • TI on Element 14
  • TI on TechXchangeSM
Other Technical & Support Resources
  • WEBENCH® Design Center
  • Product Information Centers
  • Technical Documents
  • TI Design Network
  • TI Technical Articles
  • TI Training

All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
embedded processors, along with software, tools and the industry’s largest sales/support staff.

© Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
Trademarks | Privacy Policy | Terms of Use