Forums

Hi,

Are you sure that you are using 5.04.00.011 ? Because we haven't seen this issue at our end.This issue was present in previous release of 5.04.00.11 and fixed in this release. Please re-verify.

Regards,

Vijayvithal

Hello Vijayvithal,

We are using the latest release, installed from ezsdk_dm816x-evm_5_04_00_11_setuplinux (MD5: 010d245ced03a9c43989ed0b0c49af9b). The rest of the development platform is 32-bit Ubuntu 10.04, bash shell (as required by EZSDK) and CodeSourcery 2009q1-203.

Ivan,

        This can be further debugged by individually playing with the components "make rpe_clean, make rpe and make rpe_instal", this can be done only after all the dependent components are built (like after make components)

        I also do not understand why all others can install, but not omx, gstomx and ipe. Mostly i suspect it is a local modification at your side, we have not observed this issue with 5.04.00.11.

Thanks & Regards,
Velan

Ok, we modified the main Makefile and excluded problematic components like this:

components_linux: linux cmem osal syslink_hlos syslink_driver sgx-driver omx gstomx media-controller-utils rpe_linux
we changed to
components_linux: linux cmem osal syslink sgx-driver media-controller-utils

components_dsp: syslink_rtos edma3lld rpe_dsp
we changed to
components_dsp: edma3lld

components_install: linux_install syslink_install cmem_install sgx-driver_install omx_install gstomx_install media-controller-utils_install rpe_install
we changed to
components_install: linux_install syslink_install cmem_install sgx-driver_install media-controller-utils_install

apps: u-boot matrix psp-examples omtb
we changed to
apps: u-boot matrix psp-examples

apps_install: u-boot_install matrix_install psp-examples_install omtb_install
we changed to
apps_install: u-boot_install matrix_install psp-examples_install

And with these modifications, we invoked

make clean
make all
make install

and it finishes fine.

Then, we invoked

make syslink_clean
make syslink
make syslink_install

just to be sure, since syslink is required for dsp components.

Then, we built the excluded components separatly:

rpe_clean
rpe
rpe_install

omx_clean
omx
omx_install

gstomx_clean
gstomx
gstomx_install

omtb_clean
omtb
omtb_install

This way, everything builds and installs fine!

However, we reverted the changes in the main Makefile so rpe, omx, gstomx and omtb are there back again. Then we invoked:

make clean
make all
make install

and at the "install" step, it gives us the same old error again:

...
install lib/sys_top/bin/ti816x-evm/sys_top_a8host_debug.xv5T /home/ivan/ezsdk_q7/build/ti8168_q7/usr/bin/sys_top

install src/linux/ti816x-evm/*.sh /home/ivan/ezsdk_q7/build/ti8168_q7/usr/share/ti/ti-media-controller-utils

make[1]: Leaving directory `/home/ivan/ezsdk_q7/board-support/media-controller-utils_2_05_00_17'

for i in `find board-support/prebuilt-images -name "*.xem3" -or -name "*.xe674"`; do \
        install $i /home/ivan/ezsdk_q7/build/ti8168_q7/usr/share/ti/ti-media-controller-utils/ ; \
    done

make -C /home/ivan/ezsdk_q7/component-sources/rpe_1_00_00_05 ROOTDIR=/home/ivan/ezsdk_q7/component-sources/rpe_1_00_00_05 EXTERNAL_SW_ROOT=/home/ivan/ezsdk_q7/component-sources INTERNAL_SW_ROOT=/home/ivan/ezsdk_q7/component-sources/rpe_1_00_00_05/src bios_PATH=/home/ivan/ezsdk_q7/component-sources/bios_6_33_02_31 xdais_PATH=/home/ivan/ezsdk_q7/component-sources/xdais_7_22_00_03 linuxutils_PATH=/home/ivan/ezsdk_q7/component-sources/linuxutils_3_22_00_02 aaclcdec_PATH=/home/ivan/ezsdk_q7/component-sources/c674x-aaclcdec_01_41_00_00_elf ipc_PATH=/home/ivan/ezsdk_q7/component-sources/ipc_1_24_02_27 syslink_PATH=/home/ivan/ezsdk_q7/component-sources/syslink_2_10_03_20 xdc_PATH=/home/ivan/ezsdk_q7/component-sources/xdctools_3_23_01_43 uia_PATH=/home/ivan/ezsdk_q7/component-sources/uia_1_00_03_25 mcutils_PATH=/home/ivan/ezsdk_q7/board-support/media-controller-utils_2_05_00_17 lindevkit_PATH=/home/ivan/ezsdk_q7/linux-devkit/arm-none-linux-gnueabi/usr PLATFORM=ti816x-evm CODEGEN_PATH_A8=/home/ivan/CodeSourcery/Sourcery_G++_Lite CROSS_COMPILE=arm-none-linux-gnueabi- TOOLCHAIN_LONGNAME=arm-none-linux-gnueabi CODEGEN_PATH_DSPELF=/home/ivan/ezsdk_q7/dsp-devkit/cgt6x_7_3_1 install prefix=/home/ivan/ezsdk_q7/build/ti8168_q7/usr

make[1]: Entering directory `/home/ivan/ezsdk_q7/component-sources/rpe_1_00_00_05'

install: cannot stat `lib/dm81xx/bin/ti816x-evm/*': No such file or directory

make[1]: *** [install] Error 1

make[1]: Leaving directory `/home/ivan/ezsdk_q7/component-sources/rpe_1_00_00_05'

make: *** [rpe_install] Error 2

So the question is, why the components build fine separatly and failed to build in the main Makefile?

Ivan,

       I only suspect that the Build directory and EXEC_DIR is not being maintained correclty.

       With original EZSDK the EXEC_DIR points to target fs, but the above build trace shows it is differetn (prefix=/home/ivan/ezsdk_q7/build/ti8168_q7/usr) (ie. prefix=$(EXEC_DIR)/usr

Ivan Todorovic

install: cannot stat `lib/dm81xx/bin/ti816x-evm/*': No such file or directory

      The files lib/dm81xx/bin/ti816x-evm/* is under /home/ivan/ezsdk_q7/component-sources/rpe_1_00_00_05 after make rpe or make all, something like outfiles are going to some other directory which install can not pick.

     We verified that this issue do not occur with the release.

Thanks & Regards,

Velan

Hello Velan,

All our changes related to Make procedure are these:

1. We introduced two new variables which should be set in shell before invoking the main Makefile. EZSDK_Q7_GIT should point to EZSDK install directory (in our case, /home/ivan/ezsdk_q7) and EZSDK_Q7_TOOLCHAIN should point to CodeSourcery directory (in our case, /home/ivan/CodeSourcery/Sourcery_G++_Lite)

2. In main Rules.make, we set EZSDK_INSTALL_DIR=${EZSDK_Q7_GIT} and CSTOOL_DIR=${EZSDK_Q7_TOOLCHAIN}, and also retargeted EXEC_DIR=${EZSDK_Q7_GIT}/build/ti8168_q7, which serves as our targetfs directory.

And those are all the changes. Everything else is intact.

I'm currently investigating this further in components' Makefiles, but if you have any idea how these modifications can cause this trouble, any advice will be appreciated.

Best regards,
Ivan

We applied our changes to new EZSDK 5.05 and those make install errors dissapeared, good job! :)