• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 98 subscribers
  • Views 1000 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.

PROCESSOR-SDK-DRA8X-TDA4X: SDK Coordination between RTOS and Linux Builds

Scott Bonomi
Prodigy 70 points

Part Number: PROCESSOR-SDK-DRA8X-TDA4X

I do not yet have a successful build of the complete package for a TDA4 system. 

I started with the Vision Apps Users Guide page and it implied more instructions on screen than I saw. 

It was not quite obvious that after I ran the install.bin executable that I would then need to run the sdk-install.sh script. I would think that one would invoke the other and only one iteration would be required. 

However the issue remains that the RTOS_Auto package and the processor Linux j7 evm package do not know where each other is. 

this is giving me errors out of the make program, some of which were corrected by setting TI_RTOS_PATH and then adding a symbolic link to point from the RTOS install path to the subdirectory under packages/ti/build to point to a Rules.make file that seem to be expected in a directory named processor_sdk_rtos_j7_6_01_01_12  

It may or may not be the correct Rules.make, file. 

I am currently stuck with a message that says recipe for target 'ti-ipc-linux-config' failed: in that it could not execute a cd to a directory of the named target. 

It is quite possible that all the issues will cure themselves if there is a "correct" set of directories to install into. 

At this time, if have the PSDKLA (Linux applications side) in my home directory  ~/ti-processor-sdk-Linux-automotive(…) 

And I have the PSDKRA (rtos auto package)e under ~/ti_tools/psdk_rtos_auto_j7(…) 

A little direction would be appreciated. 

Regards,

 - - Scott 

  • 0
    TI__Mastermind 42515 points

    Hi Scott,

    can you show (or attach as a file if it is too long) the whole build log when you get the error?

    Regards,

    Yordan

  • 0 in reply to Yordan Kamenov
    Prodigy 70 points

    I am attaching multiple files. CoordinationError.txt  reflects executing "make ti-ipc" from the PSDKLA directory. This exhibits the specific recipe failure described above. 

    The File CoordinationRTOS.txt is from executing a "make all" from the vision_apps directory under PDSKRA.

    The File FullBuildFromClean.txt is a much larger result of executing a "make clean" which is not shown followed by a "make all" capturing both stdout and stderr into the file.

    Both of the short files also include stderr. 

    Fullscreen CoordinationRTOS.txt Download 
    SHELL=/bin/sh
TARGET_MAKEFILES=applibs/srv_bowl_lut_gen_applib/concerto.mak applibs/srv_calibration_applib/concerto.mak applibs/test/concerto.mak apps/basic_demos/app_c7x_kernel/c7x/concerto.mak apps/basic_demos/app_c7x_kernel/concerto.mak apps/basic_demos/app_dof/concerto.mak apps/basic_demos/app_linux_arm_ipc/concerto.mak apps/basic_demos/app_linux_arm_mem/concerto.mak apps/basic_demos/app_linux_arm_opengl_mosaic/concerto.mak apps/basic_demos/app_linux_arm_remote_log/concerto.mak apps/basic_demos/app_multi_cam/concerto.mak apps/basic_demos/app_single_cam/concerto.mak apps/basic_demos/app_stereo/concerto.mak apps/basic_demos/app_test_framework/concerto.mak apps/basic_demos/app_tirtos/common/concerto.mak apps/basic_demos/app_tirtos/tirtos_linux/c66x_1/concerto.mak apps/basic_demos/app_tirtos/tirtos_linux/c66x_2/concerto.mak apps/basic_demos/app_tirtos/tirtos_linux/c7x_1/concerto.mak apps/basic_demos/app_tirtos/tirtos_linux/mcu2_0/concerto.mak apps/basic_demos/app_tirtos/tirtos_linux/mcu2_1/concerto.mak apps/basic_demos/app_tirtos/tirtos_linux/mpu1/concerto.mak apps/basic_demos/app_vx_conformance/concerto.mak apps/basic_demos/app_vx_tutorial/concerto.mak apps/cockpit_demos/app_tirtos_linux/concerto.mak apps/dl_demos/app_tidl/concerto.mak apps/dl_demos/app_tidl_avp/concerto.mak apps/dl_demos/app_tidl_avp2/concerto.mak apps/dl_demos/app_visual_localization/concerto.mak apps/ptk_demos/app_common/concerto.mak apps/ptk_demos/app_dof_sfm_fisheye/concerto.mak apps/ptk_demos/app_ldc/concerto.mak apps/ptk_demos/app_ldc_dof/concerto.mak apps/ptk_demos/app_lidar_ogmap/concerto.mak apps/ptk_demos/app_radar_gtrack/concerto.mak apps/ptk_demos/app_sfm_fisheye/concerto.mak apps/ptk_demos/app_surround_radar_ogmap/concerto.mak apps/ptk_demos/app_valet_parking/concerto.mak apps/ptk_demos/applibs/fused_ogmap_applib/concerto.mak apps/ptk_demos/applibs/lidar_ogmap_applib/concerto.mak apps/ptk_demos/applibs/ps_mapping_applib/concerto.mak apps/ptk_demos/applibs/radar_gtrack_applib/concerto.mak apps/ptk_demos/applibs/surround_radar_ogmap_applib/concerto.mak apps/ptk_demos/applibs/surround_sfm_ogmap_applib/concerto.mak apps/srv_demos/app_srv_calibration/concerto.mak apps/srv_demos/app_srv_camera/concerto.mak apps/srv_demos/app_srv_fileio/concerto.mak kernels/common/target/concerto.mak kernels/img_proc/arm/concerto.mak kernels/img_proc/c66/concerto.mak kernels/img_proc/host/concerto.mak kernels/lidar/arm/concerto.mak kernels/lidar/host/concerto.mak kernels/park_assist/host/concerto.mak kernels/park_assist/target/concerto.mak kernels/park_assist/test/concerto.mak kernels/sample/a72/concerto.mak kernels/sample/host/concerto.mak kernels/srv/c66/concerto.mak kernels/srv/gpu/3dsrv/Tools/concerto.mak kernels/srv/gpu/3dsrv/concerto.mak kernels/srv/gpu/concerto.mak kernels/srv/host/concerto.mak kernels/srv/test/concerto.mak kernels/stereo/arm/concerto.mak kernels/stereo/c7x/concerto.mak kernels/stereo/host/concerto.mak utils/console_io/src/concerto.mak utils/draw2d/src/concerto.mak utils/dss/src/concerto.mak utils/grpx/src/concerto.mak utils/hwa/src/concerto.mak utils/ipc/src/concerto.mak utils/iss/src/concerto.mak utils/mem/src/concerto.mak utils/misc/src/concerto.mak utils/mmc_sd/src/concerto.mak utils/opengl/src/a72/concerto.mak utils/opengl/src/pc/concerto.mak utils/perf_stats/src/concerto.mak utils/remote_service/src/concerto.mak utils/sciclient/src/concerto.mak utils/sensors/src/concerto.mak utils/udma/src/concerto.mak
file TIARMCGT_ROOT=$(PSDK_PATH)/ti-cgt-arm_18.12.1.LTS
file GCC_SYSBIOS_ARM_ROOT=$(PSDK_PATH)/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-elf
file CGT6X_ROOT=$(PSDK_PATH)/ti-cgt-c6000_8.3.2
file CGT7X_ROOT=$(PSDK_PATH)/ti-cgt-c7000_1.2.0.STS
undefined GCC_WINDOWS_ROOT=
file GCC_LINUX_ROOT=/usr/
#######################################################################
TARGET_COMBO=J7:SYSBIOS:R5F:3:debug:TIARMCGT
HOST_ROOT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps
HOST_COMPILER=TIARMCGT
HOST_PLATFORM=PC
HOST_OS=LINUX
HOST_CPU=x86_64
HOST_ARCH=64
HOST_FAMILY=x86_64
HOST_NUM_CORES=4
TARGET_OS=SYSBIOS
TARGET_CPU=R5F
TARGET_ARCH=32
TARGET_FAMILY=ARM
TARGET_NUM_CORES=3
TARGET_PLATFORM=J7
TARGET_BUILD=debug
TARGET_OUT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/R5F/SYSBIOS/debug
TARGET_DOC=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/R5F/SYSBIOS/debug/docs
BUILD_DEFS =  CUSTOM_KERNEL_PATH BUILD_TUTORIAL BUILD_CONFORMANCE_TEST
J7_SYSBIOS_R5F_3_debug_TIARMCGT_DEFS = SYSBIOS J7 R5F="R5F" TARGET_NUM_CORES=3 TARGET_ARCH=32 ARCH_32 ARM TARGET_BUILD=2
J7_SYSBIOS_R5F_3_debug_TIARMCGT_LDIRS = 
SCM_ROOT=
SCM_VERSION=
#######################################################################
TARGET_COMBO=J7:SYSBIOS:A72:1:debug:GCC_SYSBIOS_ARM
HOST_ROOT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps
HOST_COMPILER=GCC_SYSBIOS_ARM
HOST_PLATFORM=PC
HOST_OS=LINUX
HOST_CPU=x86_64
HOST_ARCH=64
HOST_FAMILY=x86_64
HOST_NUM_CORES=4
TARGET_OS=SYSBIOS
TARGET_CPU=A72
TARGET_ARCH=64
TARGET_FAMILY=ARM
TARGET_NUM_CORES=1
TARGET_PLATFORM=J7
TARGET_BUILD=debug
TARGET_OUT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/A72/SYSBIOS/debug
TARGET_DOC=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/A72/SYSBIOS/debug/docs
BUILD_DEFS =  CUSTOM_KERNEL_PATH BUILD_TUTORIAL BUILD_CONFORMANCE_TEST
J7_SYSBIOS_A72_1_debug_GCC_SYSBIOS_ARM_DEFS = SYSBIOS J7 A72="A72" TARGET_NUM_CORES=1 TARGET_ARCH=64 ARCH_64 ARM TARGET_BUILD=2
J7_SYSBIOS_A72_1_debug_GCC_SYSBIOS_ARM_LDIRS = 
SCM_ROOT=
SCM_VERSION=
#######################################################################
TARGET_COMBO=J7:SYSBIOS:C66:2:debug:CGT6X
HOST_ROOT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps
HOST_COMPILER=CGT6X
HOST_PLATFORM=PC
HOST_OS=LINUX
HOST_CPU=x86_64
HOST_ARCH=64
HOST_FAMILY=x86_64
HOST_NUM_CORES=4
TARGET_OS=SYSBIOS
TARGET_CPU=C66
TARGET_ARCH=32
TARGET_FAMILY=DSP
TARGET_NUM_CORES=2
TARGET_PLATFORM=J7
TARGET_BUILD=debug
TARGET_OUT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/C66/SYSBIOS/debug
TARGET_DOC=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/C66/SYSBIOS/debug/docs
BUILD_DEFS =  CUSTOM_KERNEL_PATH BUILD_TUTORIAL BUILD_CONFORMANCE_TEST
J7_SYSBIOS_C66_2_debug_CGT6X_DEFS = SYSBIOS J7 C66="C66" TARGET_NUM_CORES=2 TARGET_ARCH=32 ARCH_32 DSP TARGET_BUILD=2
J7_SYSBIOS_C66_2_debug_CGT6X_LDIRS = 
SCM_ROOT=
SCM_VERSION=
#######################################################################
TARGET_COMBO=J7:SYSBIOS:C71:1:debug:CGT7X
HOST_ROOT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps
HOST_COMPILER=CGT7X
HOST_PLATFORM=PC
HOST_OS=LINUX
HOST_CPU=x86_64
HOST_ARCH=64
HOST_FAMILY=x86_64
HOST_NUM_CORES=4
TARGET_OS=SYSBIOS
TARGET_CPU=C71
TARGET_ARCH=64
TARGET_FAMILY=DSP
TARGET_NUM_CORES=1
TARGET_PLATFORM=J7
TARGET_BUILD=debug
TARGET_OUT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/C71/SYSBIOS/debug
TARGET_DOC=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/C71/SYSBIOS/debug/docs
BUILD_DEFS =  CUSTOM_KERNEL_PATH BUILD_TUTORIAL BUILD_CONFORMANCE_TEST
J7_SYSBIOS_C71_1_debug_CGT7X_DEFS = SYSBIOS J7 C71="C71" TARGET_NUM_CORES=1 TARGET_ARCH=64 ARCH_64 DSP TARGET_BUILD=2
J7_SYSBIOS_C71_1_debug_CGT7X_LDIRS = 
SCM_ROOT=
SCM_VERSION=
#######################################################################
TARGET_COMBO=J7:LINUX:A72:1:debug:GCC_LINUX_ARM
HOST_ROOT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps
HOST_COMPILER=GCC_LINUX_ARM
HOST_PLATFORM=PC
HOST_OS=LINUX
HOST_CPU=x86_64
HOST_ARCH=64
HOST_FAMILY=x86_64
HOST_NUM_CORES=4
TARGET_OS=LINUX
TARGET_CPU=A72
TARGET_ARCH=64
TARGET_FAMILY=ARM
TARGET_NUM_CORES=1
TARGET_PLATFORM=J7
TARGET_BUILD=debug
TARGET_OUT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/A72/LINUX/debug
TARGET_DOC=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/A72/LINUX/debug/docs
BUILD_DEFS =  CUSTOM_KERNEL_PATH BUILD_TUTORIAL BUILD_CONFORMANCE_TEST
J7_LINUX_A72_1_debug_GCC_LINUX_ARM_DEFS = LINUX J7 A72="A72" TARGET_NUM_CORES=1 TARGET_ARCH=64 ARCH_64 ARM TARGET_BUILD=2
J7_LINUX_A72_1_debug_GCC_LINUX_ARM_LDIRS = 
SCM_ROOT=
SCM_VERSION=
#######################################################################
TARGET_COMBO=J7:SYSBIOS:R5F:3:release:TIARMCGT
HOST_ROOT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps
HOST_COMPILER=TIARMCGT
HOST_PLATFORM=PC
HOST_OS=LINUX
HOST_CPU=x86_64
HOST_ARCH=64
HOST_FAMILY=x86_64
HOST_NUM_CORES=4
TARGET_OS=SYSBIOS
TARGET_CPU=R5F
TARGET_ARCH=32
TARGET_FAMILY=ARM
TARGET_NUM_CORES=3
TARGET_PLATFORM=J7
TARGET_BUILD=release
TARGET_OUT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/R5F/SYSBIOS/release
TARGET_DOC=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/R5F/SYSBIOS/release/docs
BUILD_DEFS =  CUSTOM_KERNEL_PATH BUILD_TUTORIAL BUILD_CONFORMANCE_TEST
J7_SYSBIOS_R5F_3_release_TIARMCGT_DEFS = SYSBIOS J7 R5F="R5F" TARGET_NUM_CORES=3 TARGET_ARCH=32 ARCH_32 ARM TARGET_BUILD=1
J7_SYSBIOS_R5F_3_release_TIARMCGT_LDIRS = 
SCM_ROOT=
SCM_VERSION=
#######################################################################
TARGET_COMBO=J7:SYSBIOS:A72:1:release:GCC_SYSBIOS_ARM
HOST_ROOT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps
HOST_COMPILER=GCC_SYSBIOS_ARM
HOST_PLATFORM=PC
HOST_OS=LINUX
HOST_CPU=x86_64
HOST_ARCH=64
HOST_FAMILY=x86_64
HOST_NUM_CORES=4
TARGET_OS=SYSBIOS
TARGET_CPU=A72
TARGET_ARCH=64
TARGET_FAMILY=ARM
TARGET_NUM_CORES=1
TARGET_PLATFORM=J7
TARGET_BUILD=release
TARGET_OUT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/A72/SYSBIOS/release
TARGET_DOC=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/A72/SYSBIOS/release/docs
BUILD_DEFS =  CUSTOM_KERNEL_PATH BUILD_TUTORIAL BUILD_CONFORMANCE_TEST
J7_SYSBIOS_A72_1_release_GCC_SYSBIOS_ARM_DEFS = SYSBIOS J7 A72="A72" TARGET_NUM_CORES=1 TARGET_ARCH=64 ARCH_64 ARM TARGET_BUILD=1
J7_SYSBIOS_A72_1_release_GCC_SYSBIOS_ARM_LDIRS = 
SCM_ROOT=
SCM_VERSION=
#######################################################################
TARGET_COMBO=J7:SYSBIOS:C66:2:release:CGT6X
HOST_ROOT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps
HOST_COMPILER=CGT6X
HOST_PLATFORM=PC
HOST_OS=LINUX
HOST_CPU=x86_64
HOST_ARCH=64
HOST_FAMILY=x86_64
HOST_NUM_CORES=4
TARGET_OS=SYSBIOS
TARGET_CPU=C66
TARGET_ARCH=32
TARGET_FAMILY=DSP
TARGET_NUM_CORES=2
TARGET_PLATFORM=J7
TARGET_BUILD=release
TARGET_OUT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/C66/SYSBIOS/release
TARGET_DOC=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/C66/SYSBIOS/release/docs
BUILD_DEFS =  CUSTOM_KERNEL_PATH BUILD_TUTORIAL BUILD_CONFORMANCE_TEST
J7_SYSBIOS_C66_2_release_CGT6X_DEFS = SYSBIOS J7 C66="C66" TARGET_NUM_CORES=2 TARGET_ARCH=32 ARCH_32 DSP TARGET_BUILD=1
J7_SYSBIOS_C66_2_release_CGT6X_LDIRS = 
SCM_ROOT=
SCM_VERSION=
#######################################################################
TARGET_COMBO=J7:SYSBIOS:C71:1:release:CGT7X
HOST_ROOT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps
HOST_COMPILER=CGT7X
HOST_PLATFORM=PC
HOST_OS=LINUX
HOST_CPU=x86_64
HOST_ARCH=64
HOST_FAMILY=x86_64
HOST_NUM_CORES=4
TARGET_OS=SYSBIOS
TARGET_CPU=C71
TARGET_ARCH=64
TARGET_FAMILY=DSP
TARGET_NUM_CORES=1
TARGET_PLATFORM=J7
TARGET_BUILD=release
TARGET_OUT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/C71/SYSBIOS/release
TARGET_DOC=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/C71/SYSBIOS/release/docs
BUILD_DEFS =  CUSTOM_KERNEL_PATH BUILD_TUTORIAL BUILD_CONFORMANCE_TEST
J7_SYSBIOS_C71_1_release_CGT7X_DEFS = SYSBIOS J7 C71="C71" TARGET_NUM_CORES=1 TARGET_ARCH=64 ARCH_64 DSP TARGET_BUILD=1
J7_SYSBIOS_C71_1_release_CGT7X_LDIRS = 
SCM_ROOT=
SCM_VERSION=
#######################################################################
TARGET_COMBO=J7:LINUX:A72:1:release:GCC_LINUX_ARM
HOST_ROOT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps
HOST_COMPILER=GCC_LINUX_ARM
HOST_PLATFORM=PC
HOST_OS=LINUX
HOST_CPU=x86_64
HOST_ARCH=64
HOST_FAMILY=x86_64
HOST_NUM_CORES=4
TARGET_OS=LINUX
TARGET_CPU=A72
TARGET_ARCH=64
TARGET_FAMILY=ARM
TARGET_NUM_CORES=1
TARGET_PLATFORM=J7
TARGET_BUILD=release
TARGET_OUT=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/A72/LINUX/release
TARGET_DOC=/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/A72/LINUX/release/docs
BUILD_DEFS =  CUSTOM_KERNEL_PATH BUILD_TUTORIAL BUILD_CONFORMANCE_TEST
J7_LINUX_A72_1_release_GCC_LINUX_ARM_DEFS = LINUX J7 A72="A72" TARGET_NUM_CORES=1 TARGET_ARCH=64 ARCH_64 ARM TARGET_BUILD=1
J7_LINUX_A72_1_release_GCC_LINUX_ARM_LDIRS = 
SCM_ROOT=
SCM_VERSION=
Building app_tirtos_common_mcu2_1.lib as static library
Running xdc configuro for apps.basic_demos.app_tirtos.tirtos_linux.mcu2_0
Linking /home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/R5F/SYSBIOS/debug/vx_app_tirtos_linux_mcu2_0.out
Building vx_app_tirtos_linux_mcu2_0.out as static library
Running xdc configuro for apps.basic_demos.app_tirtos.tirtos_linux.mcu2_1
Linking /home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/R5F/SYSBIOS/debug/vx_app_tirtos_linux_mcu2_1.out
Building vx_app_tirtos_linux_mcu2_1.out as static library
Required system library lib_remote_device.lib
Required system library lib_remote_device_display.lib
Running xdc configuro for apps.cockpit_demos.app_tirtos_linux
Linking /home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/R5F/SYSBIOS/debug/cockpit_app_cockpit_can_params_demo.out
Building cockpit_app_cockpit_can_params_demo.out as static library
Building vx_kernels_common.lib as static library
Building vx_target_kernels_img_proc_r5f.lib as static library
Building vx_kernels_lidar.lib as static library
Building vx_target_kernels_stereo_arm.lib as static library
Building app_utils_console_io.lib as static library
Building app_utils_dss.lib as static library
Building app_utils_hwa.lib as static library
Building app_utils_ipc.lib as static library
Building app_utils_iss.lib as static library
Building app_utils_mem.lib as static library
Building app_utils_misc.lib as static library
Building app_utils_perf_stats.lib as static library
Building app_utils_remote_service.lib as static library
Building app_utils_sciclient.lib as static library
Building app_utils_sensors.lib as static library
Building app_utils_udma.lib as static library
[GCC] Compiling C99 app_mem_linux_ion.c
/bin/sh: 1: /home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu/bin/aarch64-linux-gnu-gcc: not found
concerto/finale.mak:304: recipe for target '/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/A72/LINUX/debug/module/utils.mem.src/app_mem_linux_ion.o' failed
make: *** [/home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/vision_apps/out/J7/A72/LINUX/debug/module/utils.mem.src/app_mem_linux_ion.o] Error 127
    Fullscreen CoordinationError.txt Download 
    =====================================
Building the Linux Kernel DTBs
=====================================
make -C /home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47 ARCH=arm64 CROSS_COMPILE=/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/aarch64-linux-gnu- tisdk_j7-evm_defconfig
make[1]: Entering directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
#
# configuration written to .config
#
make[1]: Leaving directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Entering directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
scripts/kconfig/conf  --syncconfig Kconfig
make[1]: Leaving directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Entering directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Leaving directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Entering directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Leaving directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Entering directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Leaving directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Entering directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Leaving directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Entering directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Leaving directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Entering directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Leaving directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Entering directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make[1]: Leaving directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
=================================
Building the Linux Kernel
=================================
make -C /home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47 ARCH=arm64 CROSS_COMPILE=/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/aarch64-linux-gnu- tisdk_j7-evm_defconfig
make[1]: Entering directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
#
# configuration written to .config
#
make[1]: Leaving directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make -j 4 -C /home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47 ARCH=arm64 CROSS_COMPILE=/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/aarch64-linux-gnu-  Image
make[1]: Entering directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
scripts/kconfig/conf  --syncconfig Kconfig
  CALL    scripts/checksyscalls.sh
  CHK     include/generated/compile.h
  GZIP    kernel/config_data.gz
make[1]: Leaving directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
make -j 4 -C /home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47 ARCH=arm64 CROSS_COMPILE=/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/aarch64-linux-gnu- modules
make[1]: Entering directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
  CALL    scripts/checksyscalls.sh
  Building modules, stage 2.
  MODPOST 716 modules
make[1]: Leaving directory '/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47'
=================================
Configuring IPC
=================================
. /home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/linux-devkit/environment-setup; \
cd /home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/ipc_3_47_01_00; \
./configure ${CONFIGURE_FLAGS} \
	CC=${TOOLCHAIN_PREFIX}gcc \
	--prefix=/usr \
	PLATFORM= \
	KERNEL_INSTALL_DIR=/home/sbonomi/ti-processor-sdk-linux-automotive-j7-evm-06_01_01_02/board-support/linux-4.19.73+gitAUTOINC+0cabba2b47-g0cabba2b47
/bin/sh: 2: cd: can't cd to /home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/ipc_3_47_01_00
/bin/sh: 3: ./configure: not found
Makefile:318: recipe for target 'ti-ipc-linux-config' failed
make: *** [ti-ipc-linux-config] Error 127

  • 0 in reply to Scott Bonomi
    TI__Mastermind 42515 points

    Hi Scott,

    sorry for the delay, I have pinged SDK experts to help with the issue.

    Regards,

    Yordan

  • 0 in reply to Yordan Kamenov
    TI__Expert 8165 points

    Hi Scott,

    Thanks for providing the logs. As I understand, since you have followed the Vision Apps User Guide, you want to build the RTOS Automotive package. I see you are doing "make sdk" in your first log file. But the build stopped as you don't have the linux cross compiler installed (looks like):

    /bin/sh: 1: /home/sbonomi/ti_tools/psdk_rtos_auto_j7_06_01_01_12/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu/bin/aarch64-linux-gnu-gcc: not found

    This should have been installed when you run the setup_psdk_rtos_auto.sh script as mentioned in the UserGuide->Build and Run->Build Environment Setup : Step 4. You should run this script without fail to install all the dependencies. 

    Also, I want to understand why are you building the PSDKLA for working with PSDKRA. You can use the pre-built filesystem and boot binaries from PSDKLA as mentioned in the Step 2 of the aforementioned section. The ipc error you see is because the ipc folder LA is looking for is different than what you have. I need to refer the PSDKLA user guide to see what could have gone wrong there.

    Let me know if you missed an instruction or overlooked a step in the UserGuide. The error in first log is most definitely because of the missing compiler.

  • 0 in reply to Anand Mahadevan SS
    Prodigy 70 points

    Scott Bonomi <scott.bonomi@metawave.co>
    1:22 PM (24 minutes ago)
    to TI
    Anand -
    I find the referenced aarch64-linuz-gnu-gcc executable in the pdskla subdirectory tree linux-devkit/sysroots/x86_64-arago-linux/usr/bin 
    I also find the file name in the targetfs and targetNFS trees in the appropriate SDKs.  
    There must be something missing in the instructions for the network proxy. When I look at Ubuntu setup, they are using port 8080 instead of port 80 for http:
    I am getting Err:1 http://us.archive.ubuntu.com/ubuntu/dists/bionic/InRelease   Could not resolve 'webproxy.ext.ti.com' four times as well as messages number 2-4 and after reading the package lists it says Failed to Fetch  on four packages which are all related to the bionic package family.  However there are no missing packages, just a few that have not been updated recently.  It would be extremely useful to know why proxies are needed and what tools require that interface and for what period or duration. 
    ARE THE WEBPROXY URL NAMES SUPPOSED TO END WITH .COM OR .NET?  NSLOOKUP CAN RESOLVE THE NAME WITH .NET 
     This Machine is pingable at 80.74.142.135, however does not seem to be connecting as a "webproxy" on port 80 or 8080. as I am getting connection times out error messages instead of failed to resolve, 
    The log shows checking on  glm, glew and pip accomplished prior to terminating the psdk_auto_rtos.sh shell script. 
    Yes, I tried to build the linux SDK, because if it worked without error it would imply that I had a successful installation. After 35 years I have learned that building an example before introducing local errors is a good way to identify issues. 
    I would think that loading the RTOS (PSDKRA) would have loaded the correct cross compiler. 
  • 0 in reply to Scott Bonomi
    Prodigy 70 points

    I agree that the issue is the compiler not getting installed in the correct location, I am trying to figure out how to resolve that issue. 

    If I set the proxy controls exactly as written, I get a DNS failure to resolve the host name to a TI site.    e2e.ti.com resolves to somewhere in edgekey.net with a redirection machine in the middle. 

    But the Vision Apps Users Guide Step 3 has me stopped cold.

      

    It apparently claims to be correct for Ubuntu 18.04  and I am using 18.04.4 LTS on an Intel XEON not a pure x86.  I cannot see that as an issue,  

    Unfortunately, the setup_psdk_rtos.sh  script appears to run to completion despite having early failures. Failures which are fatal to later work ought to be a bit more visible.

    Perhaps an instruction that would validate the webproxy settings would be sufficient.  

     

  • 0 in reply to Scott Bonomi
    Prodigy 70 points

    After clearing ALL the WEBPROXY residue off my computer and manually executing the wget steps from the setup shell script, I untarred the packages and seem to have a complete build. 

    Build Environment STEP THREE NEEDS TO BE MARKED OPTIONAL 

    I do not know why my system failed to properly download and unpack the compiler tar files. I will suggest that the amount of text from the unpack step ought to be exactly the same from system to system as the unpack is relative to cwd.  So saving the output into a file, and them comparing file size seems like a reasonable approach to verifying correct installation. 

    I would also suggest a  flag to the setup script to install anyway whether the directory is there or not. an incomplete directory prevents a correction