• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 554 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.

Original question:

RTOS/TDA2PXEVM: UART & Network logging problem

RTOS/TDA2PXEVM: SBL build fails

TG2718
Intellectual 1000 points
Part Number: TDA2PXEVM
Other Parts Discussed in Thread: SYSBIOS

Tool/software: TI-RTOS

I would like to try booting from the SD card as an alternative to loading code directly via CCS 8 using an XDS200 JTAG. From the vision_sdk\build directory, I executed the following commands, which appeared to build successfully (aside from the lack of UART output discussed in a related post):

Path=C:\ti\PROCESSOR_SDK_VISION_03_03_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;

gmake -s -j depend
gmake -s -j

Then I followed the instructions in the VisionSDK_UserGuide_TDA2xx.pdf section 3.5.3, and ran the command "gmake -s sbl". This resulted in numerous errors similar to the following:

c:\ti\PROCESSOR_SDK_VISION_03_03_00_00\vision_sdk\build>gmake -s sbl
# Compiling tda2px:a15_0:debug:csl_init: a15/src/csl_a15_init.asm
process_begin: CreateProcess(NULL, c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/cg_tools/windows/gcc-arm-none-eabi-4_9-2015q3/bin/arm-none-eabi-gcc -c -x assembler-with-cpp -DMAKEFILE_BUILD -Wimplicit -Wall -Wunused -Wunknown-pragmas -ffunction-sections -fdata-sections -c -mcpu=cortex-a15 -g -mfpu=neon -mfloat-abi=hard -mabi=aapcs -mapcs-frame -D__ARMv7 -Werror -D_DEBUG_=1 -DBUILD_A15_0 -DSOC_TDA2PX -Ic:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/cg_tools/windows/gcc-arm-none-eabi-4_9-2015q3/arm-none-eabi/include -I. -Ia15/src -Ia15 -Ic:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/drivers/pdk_01_09_00_17/packages -Ic:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/drivers/pdk_01_09_00_17/packages/ti/csl -Ic:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/drivers/pdk_01_09_00_17/packages/ti/csl -I/apps/apps_nonbam/inc -I/ -I/common -o c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_radar/ti/csl/arch/obj/tda2px/a15/debug/csl_a15_init.oa15fg a15/src/csl_a15_init.asm, ...) failed.
make (e=2): The system cannot find the file specified.
gmake[6]: *** [c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_radar/ti/csl/arch/obj/tda2px/a15/debug/csl_a15_init.oa15fg] Error 2
gmake[5]: *** [csl_init] Error 2
gmake[4]: *** [a15_0] Error 2

I'm not sure which file can not be found of the many paths listed above, or what should be done about it.

Thanks.

  • 0
    TI__Guru 55685 points
    Hi,

    It seems that GCC compiler path is not set correctly.
    Can you check path for GCC compiler in Rules.make and modify it accordingly.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Intellectual 1000 points
    Hi Rishabh,

    The gcc path must also be set in order for gmake -s -j depend or gmake -s -j to work, no? Those build OK.

    Makefile defines the sbl target as follows:
    sbl:
    $(MAKE) -C ./rtos/makerules -fbuild_pdk.mk sbl
    I added a diagnostic statement to build_pdk to determine the value of PDK_SBL_BUILD_OPTIONS
    $(info build_pdk.mk: PDK_SBL_BUILD_OPTIONS is $(PDK_SBL_BUILD_OPTIONS)). The values look reasonable to me:

    MAKERULEDIR=c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/drivers/pdk_01_09_00_17/packages/ti/build/makerules
    PDK_INSTALL_PATH=c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/drivers/pdk_01_09_00_17/packages
    TOOLCHAIN_PATH_GCC=c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/cg_tools/windows/gcc-arm-none-eabi-4_9-2015q3
    TOOLCHAIN_PATH_A15=c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/cg_tools/windows/gcc-arm-none-eabi-4_9-2015q3
    TOOLCHAIN_PATH_M4=c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/cg_tools/windows/ti-cgt-arm_16.9.2.LTS
    C6X_GEN_INSTALL_PATH=c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/cg_tools/windows/C6000_7.4.2
    TOOLCHAIN_PATH_EVE=c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/cg_tools/windows/arp32_1.0.7
    BIOS_INSTALL_PATH=c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/os_tools/bios_6_46_04_53
    XDC_INSTALL_PATH=c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/os_tools/windows/xdctools_3_32_01_22_core
    EDMA3LLD_BIOS6_INSTALLDIR=c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/drivers/edma3_lld_02_12_00_20
    RADARLINK_INSTALL_PATH=c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/radar/mmwave_dfp_01_00_00_01
    MSHIELD_DK_DIR=c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/mshield-dk_std_4_5_3
    utils_PATH=c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/ti_components/os_tools/windows/xdctools_3_32_01_22_core/bin
    INCLUDE_DUMMY_OSAL=no
    PACKAGE_VIP=yes
    INCLUDE_SYSBIOS=yes
    PACKAGE_VPE=no
    PACKAGE_CAL=no
    PACKAGE_ISS=no
    PACKAGE_DSS=yes
    EMIFMODE=SINGLE_EMIF_512MB
    SBL_CONFIG=disable_safety

    Please let me know if you see any problems with the above or have other ideas of what to check.

    Thanks.
  • 0 in reply to TG2718
    TI__Guru 55685 points
    Hi,

    Radar build does not include A15 and hence you did not face any issue when you built Vision SDK.
    You should follow section 2.1.2.1 A15 Compiler, Linker of VisionSDK_UserGuide_TDA2xx.pdf.

    Regards,
    Rishabh