Upgrading dm6437_demo to run with xdm 1.x

Gunjan,

Thanks for the answer - but as you may see in the attached log, I have been using CE 1.20 to stay with h264 decoder rev.1.10. After your comment I changed it to 2_10_02.

Based on http://wiki.davincidsp.com/index.php/Codec_Engine_Roadmap this should be ok when you run CE 2.10 the following are the dependencies:

1. DSP Link 1.50                (irrelevant for 6437)
2. DSP/BIOS 5.32.01             (I am using 32.04)
   
3. C6x Codegen tools 6.0.16     (I am using 6.0.18)
   
4. Framework Components 2.10    (same)
   
5. XDAIS 6.10                   (I am using 6.24.01)
   
6. CMEM 2.10                    (irrelevant)
   
7. XDC Tools 3.00.06            (I am using 3.05)
   
8. GCC 3.4 toolchain (MVPro 4)  (irrelevant)

Even with CE 2_10_02 and XDC tools 3.05 it can not find suffix. What I have expected to see are compilation errors because of differences to the structures used in accessing a codec in xdm0.9 vs. xdm1.x. Yet, it seems the xs.js in Configuro can not build a proper model.

Any suggestions??

Ja

Gunjan,

tried and failed - i.e., it was not a good pick.

js: "C:/Program Files/Texas Instruments/xdctools_3_10_05_61/include/utils.tci", line 748: xdc.services.global.XDCException: xdc.PACKAGE_NOT_FOUND: can't locate the package 'ti.bios' along the path:

'C:/dvsdk_2_00_00_00/xdctools_3_10_05_61;

C:/dvsdk_2_00_00_00/xdctools_3_10_05_61/packages;

C:/dvsdk_2_00_00_00/dm6437_demo_1_30_00/examples/common/evmDM6437;

C:/PROGRA~1/TEXASI~1/XDCTOO~1/packages;..;'. Ensure that the package path is set correctly.

please also notice that in spite adding a path at the end - it did not show up in the search path used to build. Any suggestions??

thanks,

ja

Gunjan,

I took care of correct setup of environmental variables by scripting the WinXP

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

set ENV_VARIABLE=BIOSDVSDK_INSTALL_DIR
set ENV_VAR_VALUE="C:\dvsdk_2_00_00_00"
setx %ENV_VARIABLE% %ENV_VAR_VALUE% -m
echo %ENV_VARIABLE% = %ENV_VAR_VALUE%


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

set ENV_VARIABLE=BIOS_INSTALL_DIR
set ENV_VAR_VALUE="C:\CCStudio_v3.3\bios_5_32_04"
setx %ENV_VARIABLE% %ENV_VAR_VALUE% -m
echo %ENV_VARIABLE% = %ENV_VAR_VALUE%

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

set ENV_VARIABLE=BIOSUTILS_INSTALL_DIR
set ENV_VAR_VALUE="%BIOSDVSDK_INSTALL_DIR%\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="%BIOSDVSDK_INSTALL_DIR%\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="%BIOSDVSDK_INSTALL_DIR%\pspdrivers_1_00_02_00\packages"
setx %ENV_VARIABLE% %ENV_VAR_VALUE% -m
echo %ENV_VARIABLE% = %ENV_VAR_VALUE%

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

set ENV_VARIABLE=NDK_INSTALL_DIR
set ENV_VAR_VALUE="%BIOSDVSDK_INSTALL_DIR%\ndk_1_92_00_22_eval"
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%\xdctools_3_10_05_61"
echo %ENV_VARIABLE% = %ENV_VAR_VALUE%
setx %ENV_VARIABLE% %ENV_VAR_VALUE% -m

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

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

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

I also save the project, closed, exit, and then restart to make sure that all has propagated to the system correctly.

Next, I run the configuration step where it failed. So all search scripts are not ready and I can not even configure it for manual build.

Any additional hints?

Thanks,

ja

Gunjan,

I have tried your suggestion and some other configurations but they were not successful. After reviewing some of the literature about XDC I would like to check whether direct execution of xs make sense - I have tried this idea but it not generated expected results. I believe however that it may be a move in the right direction.

In order to update an app I have to add packages with new release of software. These changes should be reflected in xdcpaths_evmDM6437.dat and I have added/modified all necessary lines there.When I have tried to see the file dependencies it showed few files with unresolved paths (yet they all have been properly defined in .dat file).

So to update the paths one should perhaps run configuro as prescribed on p. 2-16 of XDC Consumer User Guide (SPRUEX4A). So I tried:

>xs xdc.tools.configuro -t ti.targets.c64 -p ti.platforms.sim6xxx -c C:/CCStudio_v3.3/C6000/cgtools C:/dvsdk_2_00_00_00/dm6437_demo_1_30_00/dm6437_demo.cfg

It complained about directory name, filename or volume label sysntax error. I rechecked if the names are correct and they are correct.

Next, I have tried graphical repoman tool and could not see the way to update the paths for the project to correctly build the app. In assence I am trying to update dvsdk_2_00 for 6437 (TI did not do it so I am trying to get it done...).

Is using the xs (either in repoman or configuro) a right way to update the paths? and if it so how this can be done?

thx

ja

Gunjan,

To complete the discussion on this topic. It  seems that the mechnism in which Configuro gets data from (in this case) xdcpaths_evmDM6437.dat is broken.

I was able to bypass this problem by getting placing paths (one by one) in XDCPATH environmental variable.

Thanks,

Ja

I'm glad you were able to get it to work !

Gunjan.