• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 304 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.

Proper use of cfg files -- error during configuring project.x64P

jacek maitan
Intellectual 415 points
Other Parts Discussed in Thread: CCSTUDIO

I am reconfiguring my dvsdk to include new packages. In the process all cfg must be rebuilt by configuro.ccs. I am using xdctools_3_16_02_32 and xdc_3_05. In the process of building interfaces the following is an error:

 

making package.mak (because of package.bld) ...
generating interfaces for package xdcconfig (because package/package_xdcconfig.c is older than package.xdc) ...
configuring av_udp_decoder.x64P from package/cfg/av_udp_decoder_x64P.cfg ...
js: "./package/cfg/av_udp_decoder_x64P.cfg", line 721: XDCException: xdc.PACKAGE_NOT_FOUND: can't locate the package 'ti.bios' along the path: 'C:/dvsdk_1_11_00_00/xdc_3_05;C:/dvsdk_1_11_00_00;C:/dvsdk_1_11_00_00/examples/common/evmDM6437;C:/PROGRA~1/TEXASI~1/xdctools_3_16_02_32/packages;..;'. Ensure that the package path is set correctly.
gmake.exe: *** [package/cfg/av_udp_decoder_x64P.c] Error 1
Warning: directory "C:/dvsdk_1_11_00_00/xdc_3_05" on package path has a "packages" subdirectory - did you mean this instead?
js: "C:/Program Files/Texas Instruments/xdctools_3_16_02_32/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro.ccs: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.

Warning is correct. There is a mistake in the path:

instead of "C:/dvsdk_1_11_00_00/xdc_3_05/package" it indeed should be C:/dvsdk_1_11_00_00/xdc_3_05/packages" where can I find the offending line?

 

Thanks for recommendations

 

Ja


  • 0
    Intellectual 415 points

    Here are additional info:

    • CCS and Win configuration has been checked by compiling and building a Client project that comes with h264 rev.2.00 package.
    • The following are environmental variables:
      • BIOS_INSTALL_DIR                   C:/CCStudio_v3.3/bios_5_32_04
      • BIOSDVSDK_INSTALL_DIR       C:\dvsdk_1_11_00_00
      • BIOSUTILS_INSTALL_DIR          C:\dvsdk_1_11_00_00\biosutils_1_00_02
      • BSL_EVMDM6437_INSTALLDIR C:\CCStudio_v3.3\boards\evmdm6437_v2
      • CE_INSTALL_DIR                      C:/dvdsdk_1_11_00_00/codec_engine_2_23_01
      • PSP_INCLUDE_SOC_PATH       DM6437
      • PSP_INSTALL_DIR                    C:\dvsdk_1_11_00_00\pspdrivers_1_10_00\packages
      • XDCPATH         %BIOSDVSDK_INSTALL_DIR%\xdc_3_05;%BIOSDVSDK_INSTALL_DIR%\xdc_3_05\packages
      • XDCROOT                                %BIOSDVSDK_INSTALL_DIR%\xdc_3_05

    What I am looking for is a clarification where can ichange the choice from Package to Packages so the configuration app has a proper choice of the path.

    Thanks for suggestions,

     

    ja

     

  • 0 in reply to jacek maitan
    TI__Expert 4510 points

    Can you try adding  %BIOS_INSTALL_DIR%\packages to XDCPATH and see if it helps?

     

    Also, for software related questions, I would suggest putting it on Embedded Software forum - Digital Media Processor forum is primarily for hardware support. There are 4 different sub-forums under Embedded Software - Linux, WinCE, codecs, DSPBIOS. In DM6437 case, this will fall under DSPBIOS sub-forum.  Thanks.

  • 0 in reply to Prateek Bansal
    Intellectual 415 points

    Prateek,

     

    Yes. I have installed all environmental variables as they have been described in the attached docs. I am using a script to assure that there is minimum typing error:


    set ENV_VARIABLE=BIOS_INSTALL_DIR
    set ENV_VAR_VALUE="C:/CCStudio_v3.3/bios_5_31_08"

    setx %ENV_VARIABLE% %ENV_VAR_VALUE% -m
    echo %ENV_VARIABLE% = %ENV_VAR_VALUE%

    ECHO **********************************

    set ENV_VARIABLE=BIOSUTILS_INSTALL_DIR
    set ENV_VAR_VALUE="C:\dvsdk_1_11_00_00\biosutils_1_00_02"
    setx %ENV_VARIABLE% %ENV_VAR_VALUE% -m
    echo %ENV_VARIABLE% = %ENV_VAR_VALUE%

    ECHO **********************************

    set ENV_VARIABLE=BSL_EVMDM6437_INSTALLDIR
    set ENV_VAR_VALUE="C:\CCStudio_v3.3\boards\evmdm6437_v2"
    setx %ENV_VARIABLE% %ENV_VAR_VALUE% -m
    echo %ENV_VARIABLE% = %ENV_VAR_VALUE%

    ECHO **********************************

    set ENV_VARIABLE=CE_INSTALL_DIR
    set ENV_VAR_VALUE="C:/dvdsdk_1_11_00_00/codec_engine_1_20_02"
    setx %ENV_VARIABLE% %ENV_VAR_VALUE% -m
    echo %ENV_VARIABLE% = %ENV_VAR_VALUE%

    ECHO **********************************

    set ENV_VARIABLE=PSP_INCLUDE_SOC_PATH
    set ENV_VAR_VALUE=DM6437
    setx %ENV_VARIABLE% %ENV_VAR_VALUE% -m
    echo %ENV_VARIABLE% = %ENV_VAR_VALUE%

    ECHO **********************************

    set ENV_VARIABLE=PSP_INSTALL_DIR
    set ENV_VAR_VALUE="C:\dvsdk_1_11_00_00\pspdrivers_1_10_00\packages"
    setx %ENV_VARIABLE% %ENV_VAR_VALUE% -m
    echo %ENV_VARIABLE% = %ENV_VAR_VALUE%

    ECHO **********************************

    set ENV_VARIABLE=XDCROOT
    set ENV_VAR_VALUE="%BIOSDVSDK_INSTALL_DIR%\xdc_2_95_02"
    setx %ENV_VARIABLE% %ENV_VAR_VALUE% -m
    echo %ENV_VARIABLE% = %ENV_VAR_VALUE%

    ECHO **********************************

    set ENV_VARIABLE=XDCPATH
    set ENV_VAR_VALUE="%BIOSDVSDK_INSTALL_DIR%\xdc_2_95_02;%BIOSDVSDK_INSTALL_DIR%\xdc_2_95_02\packages"
    setx %ENV_VARIABLE% %ENV_VAR_VALUE% -m
    echo %ENV_VARIABLE% = %ENV_VAR_VALUE%

    ECHO **********************************

     

    perhaps slashes "/" vs "\" make difference ...

     

    thkx,

     

    ja