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.

DM6446 building iUniversal Examples

Other Parts Discussed in Thread: DM3730

I have successfully gotten the Codec Engine and iUniversal examples to build in Linux.  I am now trying to debug the iUniversal Example in CCS 4.  I have followed the wiki and added Pkg.attrs.profile = "debug";  to my package.bld files.  I am still having trouble setting breakpoints in the iUniversal Example source files.  I searched the output of the make of the iUniversal examples and I am still seeing a -O2 in my build.  The Pkg.attrs.profile = "debug" caused a lot of the other build steps to change from -O2 to -g which is what I expected.  Can someone please tell me how the following is generated and how do I get the -O2 to -g in this part of the build? Thanks.

 

#
# clv5T package/cfg/remote_ti_platforms_evmDM6446_xv5T.c ...
/opt/arm-linux-gnueabi//bin/arm-linux-gnueabi-gcc -c -MD -MF package/cfg/remote_ti_platforms_evmDM6446_xv5T.ov5T.dep -x c  -fPIC -Wunused -march=armv5t -Dfar=   -Dxdc_cfg__header__='remote_ti_platforms_evmDM6446/package/cfg/remote_ti_platforms_evmDM6446_xv5T.h'  -Dxdc_target_name__=GCArmv5T -Dxdc_target_types__=gnu/targets/arm/std.h -Dxdc_bld__profile_release -Dxdc_bld__vers_1_0_4_2_4 -O2  -I. -I/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages -I/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages -I/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dsplink-1_61_03-prebuilt/packages -I/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/framework_components_2_23_01/packages -I/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/codec_engine_2_23_01/packages -I/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/xdais_6_23/packages -I/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dm6446_dvsdk_combos_2_05/packages -I/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/linuxutils_2_23_01/packages -I/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dmai_trunk/packages -I/packages -I/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/edma3_lld_1_05_00/packages -I/home/dmarsh/bios_5_33_02/packages -I/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/biosutils_1_01_00/packages -I/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages -I..  -o package/cfg/remote_ti_platforms_evmDM6446_xv5T.ov5T package/cfg/remote_ti_platforms_evmDM6446_xv5T.c
sed 's"^\"\(package/cfg/remote_ti_platforms_evmDM6446_xv5Tcfg.cmd\)\""\"/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages/ti/sdo/apps/fir/cfg/linux/remote_ti_platforms_evmDM6446/\1\""' package/cfg/remote_ti_platforms_evmDM6446_xv5T.xdl > linker.cmd
Compiling firtest.evmDM6446.ov5T from firtest.c..
/opt/arm-linux-gnueabi/bin/arm-linux-gnueabi-gcc  -Wall -g   -I/include  -c -march=armv5t -I"/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dsplink-1_61_03-prebuilt/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/framework_components_2_23_01/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/codec_engine_2_23_01/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/xdais_6_23/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dm6446_dvsdk_combos_2_05/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/linuxutils_2_23_01/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dmai_trunk/packages" -I"/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/edma3_lld_1_05_00/packages" -I"/home/dmarsh/bios_5_33_02/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/biosutils_1_01_00/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages" -I"/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages/ti/sdo/apps/fir/cfg/linux/remote_ti_platforms_evmDM6446/.."  -Dxdc_target_types__="gnu/targets/arm/std.h" -Dxdc_target_name__=GCArmv5T -Dxdc_cfg__header__="/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages/ti/sdo/apps/fir/cfg/linux/remote_ti_platforms_evmDM6446/package/cfg/remote_ti_platforms_evmDM6446_xv5T.h"  -I/include  -o firtest.evmDM6446.ov5T firtest.c
Compiling smain.evmDM6446.ov5T from smain.c..
/opt/arm-linux-gnueabi/bin/arm-linux-gnueabi-gcc  -Wall -g   -I/include  -c -march=armv5t -I"/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dsplink-1_61_03-prebuilt/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/framework_components_2_23_01/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/codec_engine_2_23_01/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/xdais_6_23/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dm6446_dvsdk_combos_2_05/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/linuxutils_2_23_01/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dmai_trunk/packages" -I"/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/edma3_lld_1_05_00/packages" -I"/home/dmarsh/bios_5_33_02/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/biosutils_1_01_00/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages" -I"/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages/ti/sdo/apps/fir/cfg/linux/remote_ti_platforms_evmDM6446/.."  -Dxdc_target_types__="gnu/targets/arm/std.h" -Dxdc_target_name__=GCArmv5T -Dxdc_cfg__header__="/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages/ti/sdo/apps/fir/cfg/linux/remote_ti_platforms_evmDM6446/package/cfg/remote_ti_platforms_evmDM6446_xv5T.h"  -I/include  -o smain.evmDM6446.ov5T smain.c
Compiling linux/main.evmDM6446.ov5T from linux/main.c..
/opt/arm-linux-gnueabi/bin/arm-linux-gnueabi-gcc  -Wall -g   -I/include  -c -march=armv5t -I"/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dsplink-1_61_03-prebuilt/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/framework_components_2_23_01/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/codec_engine_2_23_01/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/xdais_6_23/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dm6446_dvsdk_combos_2_05/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/linuxutils_2_23_01/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dmai_trunk/packages" -I"/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/edma3_lld_1_05_00/packages" -I"/home/dmarsh/bios_5_33_02/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/biosutils_1_01_00/packages" -I"/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages" -I"/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages/ti/sdo/apps/fir/cfg/linux/remote_ti_platforms_evmDM6446/.."  -Dxdc_target_types__="gnu/targets/arm/std.h" -Dxdc_target_name__=GCArmv5T -Dxdc_cfg__header__="/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages/ti/sdo/apps/fir/cfg/linux/remote_ti_platforms_evmDM6446/package/cfg/remote_ti_platforms_evmDM6446_xv5T.h"  -I/include  -o linux/main.evmDM6446.ov5T linux/main.c

Linking linux/remote_ti_platforms_evmDM6446_fir.xv5T from firtest.evmDM6446.ov5T smain.evmDM6446.ov5T linux/main.evmDM6446.ov5T cfg/linux/remote_ti_platforms_evmDM6446/linker.cmd..
/opt/arm-linux-gnueabi/bin/arm-linux-gnueabi-gcc  -lpthread -lm  -Wl,-Map,linux/remote_ti_platforms_evmDM6446_fir.xv5T.map -o linux/remote_ti_platforms_evmDM6446_fir.xv5T firtest.evmDM6446.ov5T smain.evmDM6446.ov5T linux/main.evmDM6446.ov5T cfg/linux/remote_ti_platforms_evmDM6446/linker.cmd
make[1]: Leaving directory `/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages/ti/sdo/apps/fir'
make -C packages/ti/sdo/apps/fir -f /home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/Makefile.app TARGET=linux/local_ti_platforms_evmDM6446 APP_NAME=fir
make[1]: Entering directory `/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages/ti/sdo/apps/fir'

======= Building linux/local_ti_platforms_evmDM6446 =======
Configuring application using linux/local_ti_platforms_evmDM6446.cfg

XDCPATH="^;/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dsplink-1_61_03-prebuilt/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/framework_components_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/codec_engine_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/xdais_6_23/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dm6446_dvsdk_combos_2_05/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/linuxutils_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dmai_trunk/packages;/packages;;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/edma3_lld_1_05_00/packages;/home/dmarsh/bios_5_33_02/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/biosutils_1_01_00/packages;" /home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/xs xdc.tools.configuro -o cfg/linux/local_ti_platforms_evmDM6446 -t gnu.targets.arm.GCArmv5T -p ti.platforms.evmDM6446 -b /home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/config.bld linux/local_ti_platforms_evmDM6446.cfg
#
# making package.mak (because of package.bld) ...
/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/tconf  -Dxdc.path="/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dsplink-1_61_03-prebuilt/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/framework_components_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/codec_engine_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/xdais_6_23/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dm6446_dvsdk_combos_2_05/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/linuxutils_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dmai_trunk/packages;/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/edma3_lld_1_05_00/packages;/home/dmarsh/bios_5_33_02/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/biosutils_1_01_00/packages;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages;.." -Dxdc.root=/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59 -Dxdc.hostOS=Linux -Dconfig.importPath=".;/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dsplink-1_61_03-prebuilt/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/framework_components_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/codec_engine_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/xdais_6_23/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dm6446_dvsdk_combos_2_05/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/linuxutils_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dmai_trunk/packages;/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/edma3_lld_1_05_00/packages;/home/dmarsh/bios_5_33_02/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/biosutils_1_01_00/packages;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages;..;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/etc" -Dxdc.bld.targets="" -DTOOLS=   /home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages/xdc/bld/bld.js ./config.bld package.bld package.mak
#
# generating interfaces for package local_ti_platforms_evmDM6446 (because package/package.xdc.inc is older than package.xdc) ...
/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/xs -Dxdc.path="/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dsplink-1_61_03-prebuilt/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/framework_components_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/codec_engine_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/xdais_6_23/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dm6446_dvsdk_combos_2_05/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/linuxutils_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dmai_trunk/packages;/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/edma3_lld_1_05_00/packages;/home/dmarsh/bios_5_33_02/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/biosutils_1_01_00/packages;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages;.." -Dxdc.root=/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59 -Dxdc.hostOS=Linux -Dconfig.importPath=".;/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dsplink-1_61_03-prebuilt/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/framework_components_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/codec_engine_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/xdais_6_23/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dm6446_dvsdk_combos_2_05/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/linuxutils_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dmai_trunk/packages;/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/edma3_lld_1_05_00/packages;/home/dmarsh/bios_5_33_02/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/biosutils_1_01_00/packages;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages;..;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/etc" -Dxdc.bld.targets="" -DTOOLS=  -f xdc/services/intern/cmd/build.xs  -m package/package.xdc.dep -i package/package.xdc.inc package.xdc
#
# configuring local_ti_platforms_evmDM6446.xv5T from package/cfg/local_ti_platforms_evmDM6446_xv5T.cfg ...
/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/xs -Dxdc.path="/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dsplink-1_61_03-prebuilt/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/framework_components_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/codec_engine_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/xdais_6_23/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dm6446_dvsdk_combos_2_05/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/linuxutils_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dmai_trunk/packages;/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/edma3_lld_1_05_00/packages;/home/dmarsh/bios_5_33_02/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/biosutils_1_01_00/packages;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages;.." -Dxdc.root=/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59 -Dxdc.hostOS=Linux -Dconfig.importPath=".;/home/dmarsh/projects/ip224sdk/myapps/iuniversal_examples/packages;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dsplink-1_61_03-prebuilt/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/framework_components_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/codec_engine_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/xdais_6_23/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dm6446_dvsdk_combos_2_05/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/linuxutils_2_23_01/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/dmai_trunk/packages;/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/edma3_lld_1_05_00/packages;/home/dmarsh/bios_5_33_02/packages;/home/dmarsh/projects/ip224sdk/proprietary/dvsdk_2_00_00/dvsdk_2_00_00_22/biosutils_1_01_00/packages;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/packages;..;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59;/home/dmarsh/projects/ip224sdk/proprietary/xdctools_3_15_01/xdctools_3_15_01_59/etc" -Dxdc.bld.targets="" -DTOOLS=   xdc.cfg local_ti_platforms_evmDM6446.xv5T package/cfg/local_ti_platforms_evmDM6446_xv5T.cfg package/cfg/local_ti_platforms_evmDM6446_xv5T
    will link with ti.sdo.ce.universal:lib/release/universal.av5T
    will link with ti.sdo.ce:lib/release/ce.av5T
    will link with ti.sdo.ce.alg:lib/release/Algorithm_noOS.av5T;lib/release/alg.av5T
    will link with ti.sdo.ce.ipc.linux:lib/release/ipc_linux.av5T
    will link with ti.sdo.ce.osal.linux:lib/release/osal_linux_470.av5T
    will link with ti.sdo.fc.acpy3:lib/release/acpy3.a470MV
    will link with ti.sdo.fc.memutils:lib/release/memutils.a470MV
    will link with ti.sdo.linuxutils.cmem:lib/cmem.a470MV
    will link with ti.sdo.fc.dman3:lib/release/dman3Cfg.a470MV
    will link with ti.sdo.ce.utils.xdm:lib/release/XdmUtils.av5T
    will link with ti.sdo.utils.trace:lib/release/gt.a470MV
    will link with ti.sdo.ce.node:lib/release/node.av5T
    will link with ti.sdo.algos.fir:lib/fir_ti.lv5T
rm -f package/cfg/local_ti_platforms_evmDM6446_xv5T.ov5T
#

  • Is the IUNIVERSAL alg you're trying to debug on the DSP-side or ARM-side?  The logs look like both a 'remote' and 'local' app are being built, so it's unclear what to look at.

    Also, there's only one -O2 in the logs above - are there missing parts of these build logs that have more -O2's you don't expect?

    Chris

  • I am trying to debug the the DSP-side.  You are correct,  I am bulding by a remote and local application just for testing purposes.  I just cut out one section of the build with the -O2.  I was trying to determine where this option was getting set and maybe it doesn't have anything to do with the package.bld file.  I attached the entire output.

     

    0488.output.txt

  • That build log looks ok.  When building the fir alg, I see -g being thrown.

    The only times I see -O2 is when building the ARM-side, cfg-generated package/cfg/<really-long-name>.c.  That file typically only contains generated structs, variables, etc that you don't need to step through anyway.  (To build _that_ file with -g as well, you can set "-r debug" when running configuro on your ARM-side .cfg script - http://rtsc.eclipse.org/docs-tip/Command_-_xdc.tools.configuro).

    You might sanity check that the generated linker command file used when building your server (in your server's package/cfg/fir_unitserver_evmdm6446_x64P.xdl file) contains the full path to the fir library you just built (if it doesn't, perhaps you're pulling in an older library from somewhere else?).

    You might also sanity check that you're copying the built server next to your application executable.

    Also, since you're debugging the DSP from an ARM-side app, note that you shouldn't connect to the DSP and set breakpoints until after the ARM has returned from Engine_open(), since the DSP isn't loaded until that point.  Some other hints/details are here:

        http://processors.wiki.ti.com/index.php/Debugging_the_DSP_side_of_a_CE_application_using_CCS

    Chris

  • dmarsh10 wrote the following post at Tue, Jul 13 2010 2:35 PM:

    I have successfully gotten the Codec Engine and iUniversal examples to build in Linux.  I am now trying to debug the iUniversal Example in CCS 4.  I have followed the wiki and added Pkg.attrs.profile = "debug";

    -----  Question  ----

    What is the address to the wiki link that dmarsh10 mentioned above?

    I want to build the IUNIVERSAL FIR example to run on the DM3730 EVM but I am new to building the IUNIVERSAL and the Linux environment. Could someone help me get started with the step by step instruction?

    [6/26/12] OK, no one replied to my question above so I try to build the IUNIVERAL - FIR example but I get this error -- Please help

    user@ubuntu:~/labs/lab08b_audio_video/app$ make debug install

    Building 'debug' profile by calling: make -f makefile_profile.mak PROFILE=debug

    4. ----- Starting Configuro for app_cfg.cfg (note, this may take a minute)
    js: "/home/user/labs/lab08b_audio_video/app/app_cfg.cfg", line 31: XDCException: xdc.PACKAGE_NOT_FOUND: /home/user/ti-dvsdk_omap3530-evm_4_00_00_17/codec-engine_2_25_05_16/examples/ti/sdo/algos/fir/ce/package.xdc found along the package path, but no schema file was found. Ensure that the package 'ti.sdo.algos.fir.ce' is completely built.
    "./package/cfg/app_cfg_xv5T.cfg", line 474
    "./package/cfg/app_cfg_xv5T.cfg", line 429
    gmake: *** [package/cfg/app_cfg_xv5T.c] Error 1
    gmake: *** [package/cfg/app_cfg_xv5T.c] Deleting file `package/cfg/app_cfg_xv5T.xdl'
    gmake: *** [package/cfg/app_cfg_xv5T.c] Deleting file `package/cfg/app_cfg_xv5T.h'
    js: "/home/user/ti-dvsdk_omap3530-evm_4_00_00_17/xdctools_3_16_03_36/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
    Done building 'debug' for /home/user/labs/lab08b_audio_video/app

    ****  Question  ***

    >Ensure that the package 'ti.sdo.algos.fir.ce' is completely built.

    How do I built the IUNIVERSAL example package so I can use it?

    ------- below are my built environment please tell me what I have done wrong  ----

    1. As the baseline, I used Lab08 from the OMAP/DaVinci/Sitara System Integration using Linux which I already had it working.

    2. I added the IUNIVERSAL example ~/ti package under this directory:

       user@ubuntu:~/ti-dvsdk_omap3530-evm_4_00_00_17/codec-engine_2_25_05_16/examples$

    3. I confirmed that my "setpaths.mak" contains the correct codec engine

      SDK_INSTALL_DIR=$(HOME)/ti-dvsdk_omap3530-evm_4_00_00_17

      CE_INSTALL_DIR=$(SDK_INSTALL_DIR)/codec-engine_2_25_05_16

    4. I confirmed the XDCPATH in my "makefile_profile.mak"

    export XDCPATH := $(LAB_DIR);$(LAB_DIR)/../myDisplay/packages;$(DMAI_INSTALL_DIR)/packages;$(CE_INSTALL_DIR)/packages;$(CE_INSTALL_DIR)/examples;$(XDAIS_INSTALL_DIR)/packages;$(DSPLINK_INSTALL_DIR);$(CMEM_INSTALL_DIR)/packages;$(BIOS_INSTALL_DIR)/packages;$(BIOSUTILS_INSTALL_DIR)/packages;$(LPM_INSTALL_DIR)/packages;$(FC_INSTALL_DIR)/packages;$(XDCROOT)/packages

    5. I added the package to my "app_cfg.cfg"

    /*
    * ======== FIR remote.cfg ========
    */

    /* set up OSAL */
    var osalGlobal = xdc.useModule('ti.sdo.ce.osal.Global');
    osalGlobal.runtimeEnv = osalGlobal.DSPLINK_LINUX;
    osalGlobal.armDspLinkConfig = osalGlobal.DEFAULT_ARMDSPLINKCONFIG;

    /* get various codec modules; i.e., implementation of codecs */
    var FIR = xdc.useModule('ti.sdo.algos.fir.ce.FIR');
    FIR.alg.codeSection = "DDR2";

    /*
    * ======== Engine Configuration ========
    */
    var Engine = xdc.useModule('ti.sdo.ce.Engine');
    var myEngine = Engine.createFromServer(
    "firEngine",
    "./fir_unitserver_evm3530.x64P",
    "ti.sdo.servers.fir_unitserver_evm3530"
    );

    6. I added the path to my "main.c" then call the function in my execution

    #include <ti/sdo/apps/fir/firtest.h>

    . . .

    FIRTEST_main(myGetQuitFunction, FALSE, "firEngine");

    Regards,

    Sy

  • It's hard for me to figure out exactly what is going wrong here. I'm not sure if something is not built correctly or not, though it's more likely that it's a path problem.

    My first suggestion would be to NOT use Lab08 as a basis for what it sounds like you're trying to accomplish. Lab08 is our multi-threaded example that only utilizes the ARM to control audio and video threads. These threads only get data from the audio and video driver input channels, then put the data back to the output drivers. We didn't utilize any algorithms at this point in the workshop.

    It wasn't until Lab09 that we started using algorithms (i.e. codecs) of any kind. Thus, Lab08 (and earlier) don't make use of the Codec Engine framework - it just wasn't needed, yet.

    Labs 9 & 10 only used ARM-side (also known as "local") algorithms. That doesn't sound like what you're trying to do.

    If you're trying to use an algorithm that shipped with the DVSDK, then I suggest you example Lab11a. We used a DSP codec that shipped with the DVSDK in this example.

    Lab 12 was an example of integrating a 3rd party algorithm into your own DSP Server.

    Lab 13a provides an example of building your own IUNIVERSAL DSP algorithm and testing it within CCS.

    Lab 13b takes your newly developed and tested algorithm and and has you port it over to Linux and run it from an ARM-side program. Essentially, we're repeating Lab 12, but this time we're using our own IUNIVERSAL algorithm.

    To summarize, I'm guessing you would be better off using either Lab11 or Lab13, depending upon what you're actually trying to build.

    Scott

  • Scott,

    Thank you for your help.  I had this working months ago with your help and the code example from TTO as the baseline to build the project. I finally get around to update this post.  Keep up the great work of the TTO training material.

    Regards,
    Sy