• State Resolved
  • Locked Locked
  • Replies 30 replies
  • Answers 6 answers
  • Subscribers 98 subscribers
  • Views 3444 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.

RTOS/TDA2P-ACD: PDK build error for ipu1

Hrishikesh Rajurkar
Expert 1165 points

Part Number: TDA2P-ACD
Other Parts Discussed in Thread: SYSBIOS

Tool/software: TI-RTOS

Hello 

After following steps mentioned in another thread  https://e2e.ti.com/support/arm/automotive_processors/f/1021/p/672536/2475799#2475799 

# Invoking configuro...
generating interfaces for package vps_examples_displayDssLowLatency_configuro (b
ecause package/package_vps_examples_displayDssLowLatency_configuro.c is older th
an package.xdc) ...
configuring displayDssLowLatency.xem4 from package/cfg/displayDssLowLatency_pem4
.cfg ...
# !!! Current build BOARD is [tda2px-evm] !!!
# !!! Current build SOC is [tda2px] !!!
# !!! Current build CORE is [ipu1_0] !!!
generating custom ti.sysbios library makefile ...
Starting build of library sources ...
Build of libraries failed.
error: xdc.cfg.SourceDir: "C:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/os_
tools/windows/xdctools_3_32_01_22_core/packages/xdc/cfg/SourceDir.xs", line 209:
xdc.cfg.SourceDir : Build of generated source libraries failed: exit status = 2
:
"C:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/os_tools/bios_6_46_04_53/pack
ages/ti/sysbios/family/arm/m3/Hwi_asm.sv7M", ERROR! at line 1937339231:
[E1500]
file access error: failed to open "m3_Hwi_asm.obj" for writing

INTERNAL ERROR: c:\PROCESSOR_SDK_VISION_03_02_00_00\ti_components\cg_tools\windo
ws\ti-cgt-arm_16.9.1.LTS\bin\armasm.exe experienced a segmentation fault
while processing file C:/PROCESSOR_SDK_VISION_03_02_00_00/ti_c
omponents/os_tools/bios_6_46_04_53/packages/ti/sysbios/family/arm/m3/Hwi_asm.sv7
M line 1937339231

This is caused by a defect in the compiler itself. TI Customer
Support may be able to suggest a workaround to avoid this.

Upgrading to the newest version of the compiler may fix this problem.

Contact TI in the E2E support forums at http://e2e.ti.com under
"Development Tools", "TI C/C++ Compiler". See the link titled
"Submitting an issue". Include this ENTIRE error message and a
copy of the .pp file created when option --preproc_with_comment
(-ppc) is used.

gmake[1]: *** [m3_Hwi_asm.obj] Error 1
gmake: *** [c:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/drivers/pdk_01_08_
01_06/packages/ti/binary/vps_examples_displayDssLowLatency/obj/tda2px-evm/ipu1_0
/release/vps_examples_displayDssLowLatency_configuro/package/cfg/displayDssLowLa
tency_pem4.src/sysbios/sysbios.aem4] Error 2

js: "C:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/os_tools/windows/xdctools
_3_32_01_22_core/packages/xdc/cfg/Main.xs", line 160: Error: Configuration faile
d!
xdctools_3_32_01_22_core\gmake.exe: *** [package/cfg/displayDssLowLatency_pem4.x
dl] Error 1
xdctools_3_32_01_22_core\gmake.exe: *** Deleting file `package/cfg/displayDssLow
Latency_pem4.xdl'
xdctools_3_32_01_22_core\gmake.exe: *** [package/cfg/displayDssLowLatency_pem4.x
dl] Deleting file `package/cfg/displayDssLowLatency_pem4.h'
xdctools_3_32_01_22_core\gmake.exe: *** [package/cfg/displayDssLowLatency_pem4.x
dl] Deleting file `package/cfg/displayDssLowLatency_pem4.c'
js: "C:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/os_tools/windows/xdctools
_3_32_01_22_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configur
o: configuration failed due to earlier errors (status = 2); 'c:/PROCESSOR_SDK_VI
SION_03_02_00_00/ti_components/drivers/pdk_01_08_01_06/packages/ti/binary/vps_ex
amples_displayDssLowLatency/obj/tda2px-evm/ipu1_0/release/vps_examples_displayDs
sLowLatency_configuro/linker_mod.cmd' deleted.
gmake[2]: *** [c:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/drivers/pdk_01_
08_01_06/packages/ti/binary/vps_examples_displayDssLowLatency/obj/tda2px-evm/ipu
1_0/release/vps_examples_displayDssLowLatency_configuro/package/cfg/displayDssLo
wLatency_pem4.c] Error 1
gmake[1]: *** [vps_examples_displayDssLowLatency] Error 2
gmake: *** [all] Error 2

regards

Hrishikesh

  • 0
    TI__Guru 55685 points

    Hi Hrishikesh,

    Can you please specify the build command that you are trying? I will try the same here.

    Regards,
    Rishabh

  • 0 in reply to Rishabh Garg
    Expert 1165 points
    Hi Risabh
    I tried to build by using the command gmake -s all BOARD=tda2px-evm CORE=ipu1_0
    when i changed core with ipu1_1,a15_0, c66x, arp_1, arp_2, I did not get any error.
    regards
    Hrishikesh
  • 0 in reply to Hrishikesh Rajurkar
    TI__Guru 55685 points
    Hi Hrishikesh,

    The build is working for me.
    Can you share your Rules.make so that I can cross check if any differences are there.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Expert 1165 points

    Hi Rishabh

    Please find attached rules.make (renamed as rules.txt) herein

    regards

    Hrishikesh

    Fullscreen Rules - Copy.txt Download 
    #
# Copyright (c) 2013-2017, Texas Instruments Incorporated
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
#
# *  Redistributions of source code must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
# *  Redistributions in binary form must reproduce the above copyright
#    notice, this list of conditions and the following disclaimer in the
#    documentation and/or other materials provided with the distribution.
#
# *  Neither the name of Texas Instruments Incorporated nor the names of
#    its contributors may be used to endorse or promote products derived
#    from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
# AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
# THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
# PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
# CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
# EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
# EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#

#Default build environment, windows or linux
ifeq ($(OS),)
  #if nothing is defined, default to linux
  OS ?= windows
endif

#Default BUILD_OS_TYPE (tirtos/baremetal)
BUILD_OS_TYPE ?= tirtos

# Default board
# Supported values: tda2xx-evm, am572x-evm, evmDRA72x, evmDRA75x, tda3xx-evm, tda3xx-rvp, evmDRA78x,
#                   tda2px-evm,
#                   tda3xx-evm-radar, tda2xx-evm-radar, tda3xx-ar12-booster,
#                   tda3xx-ar12-alps, tda3xx-ar12-rvp,
#                   am572x-idk am571x-evm,  evmAM572x, idkAM571x, idkAM572x
#                   evmK2H, evmK2K, evmK2E, evmK2L, evmK2G, evmC6678, evmC6657,
#                   evmAM335x, icev2AM335x, iceAMIC110, skAM335x, bbbAM335x,
#                   evmAM437x idkAM437x skAM437x evmOMAPL137 lcdkOMAPL138
#
BOARD ?= tda2px-evm
SOC ?= tda2px

#Below applicable only for TDA devices
mmwavelink_version := mmwave_dfp_00_09_01_06

ifeq ($(OS),Windows_NT)
#Paths for windows machine
  TOOLCHAIN_PATH_GCC ?= c:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/cg_tools/windows/gcc-arm-none-eabi-4_9-2015q3
  TOOLCHAIN_PATH_TI_CGT ?= c:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/cg_tools/windows/ti-cgt-arm_16.9.1.LTS
  C6X_GEN_INSTALL_PATH ?= c:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/cg_tools/windows/C6000_7.4.2
  TOOLCHAIN_PATH_EVE ?= c:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/cg_tools/windows/arp32_1.0.7
  PDK_INSTALL_PATH ?= c:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/drivers/pdk_01_08_01_06/packages
  BIOS_INSTALL_PATH ?= c:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/os_tools/bios_6_46_04_53
  XDC_INSTALL_PATH ?= c:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/os_tools/windows/xdctools_3_32_01_22_core
  EDMA3LLD_BIOS6_INSTALLDIR ?= c:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/drivers/edma3_lld_02_12_00_20
  #Required only for TDA RADAR build
  radarLink_PATH := C:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/radar/$(mmwavelink_version)
  #Required only for TDA Secure build
  MSHIELD_DK_DIR ?= c:/ti/mshield-dk_std_4_5_3
  #Required only for library size output generation
  CG_XML_BIN_INSTALL_PATH ?= c:/ti/cg_xml_2_41_00/bin
  #Not used for TDA device build
  CL_PRU_INSTALL_PATH ?= c:/ti/ti-cgt-pru_2.1.4
  NDK_INSTALL_PATH ?=  C:/PROCESSOR_SDK_VISION_03_02_00_00/ti_components/networking/ndk_2_24_02_31
# Utilities directory. This is required only if the build machine is Windows.
#   - specify the installation directory of utility which supports POSIX commands
#     (eg: Cygwin installation or MSYS installation).
# This could be in CCS install directory as in c:/ti/ccsv7/utils/cygwin or
# the XDC install bin folder $(XDC_INSTALL_PATH)/bin
  utils_PATH ?= c:/ti/ccsv6/utils/cygwin
  export utils_PATH
else
#Paths for linux machine
  TOOLCHAIN_PATH_GCC ?= /opt/tools/gcc-arm-none-eabi-4_9-2015q3
  TOOLCHAIN_PATH_TI_CGT ?= /opt/tools/cgtools/ti-cgt-arm_16.9.1.LTS
  C6X_GEN_INSTALL_PATH ?= /opt/tools/cgtools/C6000_7.4.2
  TOOLCHAIN_PATH_EVE ?= /opt/tools/cgtools/arp32_1.0.7
  PDK_INSTALL_PATH ?= /opt/ti/pdk_01_08_01_06/packages
  BIOS_INSTALL_PATH ?= /opt/tools/bios6/bios_6_46_04_53
  XDC_INSTALL_PATH ?= /opt/tools/xdc/xdctools_3_32_01_22_core
  EDMA3LLD_BIOS6_INSTALLDIR ?= /opt/tools/edma3/edma3_lld_02_12_00_20
  #Required only for TDA RADAR build
  radarLink_PATH := /opt/ti/$(mmwavelink_version)
  #Required only for TDA Secure build
  MSHIELD_DK_DIR ?= /opt/tools/mshield-dk_std_4_5_3
  #Required only for library size output generation
  CG_XML_BIN_INSTALL_PATH ?= /opt/ti/cg_xml_2_41_00/bin
  #Not used for TDA device build
  CL_PRU_INSTALL_PATH ?= /opt/ti-cgt-pru_2.1.4
  NDK_INSTALL_PATH ?= /opt/tools/ndk/ndk_2_24_03_35
endif

TOOLCHAIN_PATH_A8 ?= $(TOOLCHAIN_PATH_GCC)
TOOLCHAIN_PATH_A9 ?= $(TOOLCHAIN_PATH_GCC)
TOOLCHAIN_PATH_ARM9 ?= $(TOOLCHAIN_PATH_TI_CGT)
TOOLCHAIN_PATH_Arm9 ?= $(TOOLCHAIN_PATH_ARM9)
TOOLCHAIN_PATH_A15 ?= $(TOOLCHAIN_PATH_GCC)
TOOLCHAIN_PATH_M4 ?= $(TOOLCHAIN_PATH_TI_CGT)

ifeq ($(SOC),$(filter $(SOC), am335x))
  FPULIB_PATH ?= $(TOOLCHAIN_PATH_A8)/lib/gcc/arm-none-eabi/4.9.3/fpu
else ifeq  ($(SOC),$(filter $(SOC), am437x))
  FPULIB_PATH ?= $(TOOLCHAIN_PATH_A9)/lib/gcc/arm-none-eabi/4.9.3/fpu
else
  FPULIB_PATH ?= $(TOOLCHAIN_PATH_A15)/lib/gcc/arm-none-eabi/4.9.3/fpu
endif

# Default to m4 build depending on BOARD selected!!
ifeq ($(BOARD),$(filter $(BOARD), evmAM572x idkAM572x idkAM571x ))
  CORE ?= a15_0
endif
CORE ?= ipu1_0

# Default Build Profile
# Supported Values: debug | release
BUILD_PROFILE ?= release

# Set Core Build Profile depending on BUILD_PROFILE value
BUILD_PROFILE_$(CORE) ?= $(BUILD_PROFILE)

# Default PACKAGE_SELECT build flag
# Supported values: all, vps-hal-only, vps-vip-only, vps-vpe-only, vps-dss-only, vps-vip-dss, vps-vip-vpe
PACKAGE_SELECT ?= all

TREAT_WARNINGS_AS_ERROR ?= yes

# Disable recursive building of example dependencies
DISABLE_RECURSE_DEPS ?= no

# Default C++ build flag, yes or no
CPLUSPLUS_BUILD ?= no

#use <module>_PATH variable as makefile internally expects PATH variable this way for external component path
pdk_PATH := $(PDK_INSTALL_PATH)
bios_PATH := $(BIOS_INSTALL_PATH)
xdc_PATH := $(XDC_INSTALL_PATH)
edma3_lld_PATH := $(EDMA3LLD_BIOS6_INSTALLDIR)
ndk_PATH := $(NDK_INSTALL_PATH)
TI_SECURE_DEV_PKG := $(MSHIELD_DK_DIR)

ROOTDIR := $(pdk_PATH)
XDCPATH =
ifeq ($(BUILD_OS_TYPE),tirtos)
  XDCPATH = $(bios_PATH)/packages;$(xdc_PATH)/packages;$(edma3_lld_PATH)/packages;$(ndk_PATH)/packages;$(pdk_PATH);
endif

#Default SECTTI SIZE INFORMATION
SECTTI_SIZE_INFO ?= no

#Default SECTTI tool
SECTTI ?= $(CG_XML_BIN_INSTALL_PATH)/sectti

# Individual component path, needed to build a component in a different location
# as that of PDK
PDK_CSL_ROOT_PATH ?= $(pdk_PATH)
PDK_CSL_COMP_PATH = $(PDK_CSL_ROOT_PATH)/ti/csl
export PDK_CSL_COMP_PATH
PDK_PM_ROOT_PATH ?= $(pdk_PATH)
PDK_PM_COMP_PATH = $(PDK_PM_ROOT_PATH)/ti/drv/pm
export PDK_PM_COMP_PATH
PDK_OSAL_ROOT_PATH ?= $(pdk_PATH)
PDK_OSAL_COMP_PATH = $(PDK_OSAL_ROOT_PATH)/ti/osal
export PDK_OSAL_COMP_PATH
PDK_I2C_ROOT_PATH ?= $(pdk_PATH)
PDK_I2C_COMP_PATH = $(PDK_I2C_ROOT_PATH)/ti/drv/i2c
export PDK_I2C_COMP_PATH
PDK_VPS_ROOT_PATH ?= $(pdk_PATH)
PDK_VPS_COMP_PATH = $(PDK_VPS_ROOT_PATH)/ti/drv/vps
export PDK_VPS_COMP_PATH
PDK_GPIO_ROOT_PATH ?= $(pdk_PATH)
PDK_GPIO_COMP_PATH = $(PDK_GPIO_ROOT_PATH)/ti/drv/gpio
export PDK_GPIO_COMP_PATH
PDK_FATFS_ROOT_PATH ?= $(pdk_PATH)
PDK_FATFS_COMP_PATH = $(PDK_FATFS_ROOT_PATH)/ti/fs/fatfs
export PDK_FATFS_COMP_PATH
PDK_MMCSD_ROOT_PATH ?= $(pdk_PATH)
PDK_MMCSD_COMP_PATH = $(PDK_MMCSD_ROOT_PATH)/ti/drv/mmcsd
export PDK_MMCSD_COMP_PATH
PDK_PCIE_ROOT_PATH ?= $(pdk_PATH)
PDK_PCIE_COMP_PATH = $(PDK_PCIE_ROOT_PATH)/ti/drv/pcie
export PDK_PCIE_COMP_PATH
PDK_USB_ROOT_PATH ?= $(pdk_PATH)
PDK_USB_COMP_PATH = $(PDK_USB_ROOT_PATH)/ti/drv/usb
export PDK_USB_COMP_PATH
PDK_MCASP_ROOT_PATH ?= $(pdk_PATH)
PDK_MCASP_COMP_PATH = $(PDK_MCASP_ROOT_PATH)/ti/drv/mcasp
export PDK_MCASP_COMP_PATH
PDK_PROFILING_ROOT_PATH ?= $(pdk_PATH)
PDK_PROFILING_COMP_PATH = $(PDK_PROFILING_ROOT_PATH)/ti/utils/profiling
export PDK_PROFILING_COMP_PATH
PDK_PRUSS_ROOT_PATH ?= $(pdk_PATH)
PDK_PRUSS_COMP_PATH = $(PDK_PRUSS_ROOT_PATH)/ti/drv/pruss
export PDK_PRUSS_COMP_PATH
PDK_NIMU_ROOT_PATH ?= $(pdk_PATH)
PDK_NIMU_COMP_PATH = $(PDK_NIMU_ROOT_PATH)/ti/transport/ndk/nimu
export PDK_NIMU_COMP_PATH
PDK_NIMU_ICSS_ROOT_PATH ?= $(pdk_PATH)
PDK_NIMU_ICSS_COMP_PATH = $(PDK_NIMU_ICSS_ROOT_PATH)/ti/transport/ndk/nimu_icss
export PDK_NIMU_ICSS_COMP_PATH
PDK_ICSS_EMAC_ROOT_PATH ?= $(pdk_PATH)
PDK_ICSS_EMAC_COMP_PATH = $(PDK_ICSS_EMAC_ROOT_PATH)/ti/drv/icss_emac
export PDK_ICSS_EMAC_COMP_PATH
PDK_EMAC_ROOT_PATH ?= $(pdk_PATH)
PDK_EMAC_COMP_PATH = $(PDK_EMAC_ROOT_PATH)/ti/drv/emac
export PDK_EMAC_COMP_PATH
PDK_UART_ROOT_PATH ?= $(pdk_PATH)
PDK_UART_COMP_PATH = $(PDK_UART_ROOT_PATH)/ti/drv/uart
export PDK_UART_COMP_PATH
PDK_SPI_ROOT_PATH ?= $(pdk_PATH)
PDK_SPI_COMP_PATH = $(PDK_SPI_ROOT_PATH)/ti/drv/spi
export PDK_SPI_COMP_PATH
PDK_BOARD_ROOT_PATH ?= $(pdk_PATH)
PDK_BOARD_COMP_PATH = $(PDK_BOARD_ROOT_PATH)/ti/board
export PDK_BOARD_COMP_PATH
PDK_GPMC_ROOT_PATH ?= $(pdk_PATH)
PDK_GPMC_COMP_PATH = $(PDK_GPMC_ROOT_PATH)/ti/drv/gpmc
export PDK_GPMC_COMP_PATH
PDK_AUDK2G_ROOT_PATH ?= $(pdk_PATH)
PDK_AUDK2G_COMP_PATH = $(PDK_AUDK2G_ROOT_PATH)/ti/addon/audk2g
export PDK_AUDK2G_COMP_PATH
PDK_SBL_ROOT_PATH ?= $(pdk_PATH)
PDK_SBL_COMP_PATH = $(PDK_SBL_ROOT_PATH)/ti/boot/sbl
export PDK_SBL_COMP_PATH
PDK_SBL_AUTO_ROOT_PATH ?= $(pdk_PATH)
PDK_SBL_AUTO_COMP_PATH = $(PDK_SBL_AUTO_ROOT_PATH)/ti/boot/sbl_auto
export PDK_SBL_AUTO_COMP_PATH
PDK_CMB_ROOT_PATH ?= $(pdk_PATH)
PDK_CMB_COMP_PATH = $(PDK_CMB_ROOT_PATH)/ti/addon/cmb
export PDK_CMB_COMP_PATH
PDK_BOARD_IND_ROOT_PATH ?= $(pdk_PATH)
PDK_BOARD_IND_COMP_PATH = $(PDK_BOARD_IND_ROOT_PATH)/ti/addon/board_ind
export PDK_BOARD_IND_COMP_PATH

#Below applicable only for TDA devices
PDK_DIAG_ROOT_PATH ?= $(pdk_PATH)
PDK_DIAG_COMP_PATH = $(PDK_DIAG_ROOT_PATH)/ti/diag
export PDK_DIAG_COMP_PATH
PDK_FIREWALL_L3L4_ROOT_PATH ?= $(pdk_PATH)
PDK_FIREWALL_L3L4_COMP_PATH = $(PDK_FIREWALL_L3L4_ROOT_PATH)/ti/drv/fw_l3l4
export PDK_FIREWALL_L3L4_COMP_PATH
PDK_IPCLITE_ROOT_PATH ?= $(pdk_PATH)
PDK_IPCLITE_COMP_PATH = $(PDK_IPCLITE_ROOT_PATH)/ti/drv/ipc_lite
export PDK_IPCLITE_COMP_PATH
PDK_TDA3X_SECURITY_ROOT_PATH ?= $(pdk_PATH)
PDK_TDA3X_SECURITY_COMP_PATH = $(PDK_TDA3X_SECURITY_ROOT_PATH)/ti/boot/sbl_auto/security
export PDK_TDA3X_SECURITY_COMP_PATH

#Below applicable only for TDA devices for backward compatibility;not applicable for PRSDK
PDK_NORFLASH_ROOT_PATH ?= $(pdk_PATH)
PDK_NORFLASH_COMP_PATH = $(PDK_NORFLASH_ROOT_PATH)/ti/boot/sbl_auto/norflash
export PDK_NORFLASH_COMP_PATH
PDK_QSPIFLASH_ROOT_PATH ?= $(pdk_PATH)
PDK_QSPIFLASH_COMP_PATH = $(PDK_QSPIFLASH_ROOT_PATH)/ti/boot/sbl_auto/qspiflash
export PDK_QSPIFLASH_COMP_PATH
PDK_STW_LLD_ROOT_PATH ?= $(pdk_PATH)
PDK_STW_LLD_COMP_PATH = $(PDK_STW_LLD_ROOT_PATH)/ti/drv/stw_lld
export PDK_STW_LLD_COMP_PATH
PDK_BSP_LLD_ROOT_PATH ?= $(pdk_PATH)
PDK_BSP_LLD_COMP_PATH = $(PDK_BSP_LLD_ROOT_PATH)/ti/drv/bsp_lld
export PDK_BSP_LLD_COMP_PATH

export OS
export BUILD_OS_TYPE
export BOARD
export SOC
export CORE
export BUILD_PROFILE
export BUILD_PROFILE_$(CORE)
export TOOLCHAIN_PATH_A15
export TOOLCHAIN_PATH_A8
export TOOLCHAIN_PATH_A9
export TOOLCHAIN_PATH_ARM9
export TOOLCHAIN_PATH_Arm9
export TOOLCHAIN_PATH_M4
export TOOLCHAIN_PATH_EVE
export FPULIB_PATH
export C6X_GEN_INSTALL_PATH
export CL_PRU_INSTALL_PATH
export PDK_INSTALL_PATH
export bios_PATH
export xdc_PATH
export pdk_PATH
export edma3_lld_PATH
export ndk_PATH
export ROOTDIR
export XDCPATH
export PACKAGE_SELECT
export TREAT_WARNINGS_AS_ERROR
export DISABLE_RECURSE_DEPS
export CPLUSPLUS_BUILD
export mmwavelink_version
export radarLink_PATH
export MSHIELD_DK_DIR
export TI_SECURE_DEV_PKG
export SECTTI_SIZE_INFO
export SECTTI

ifeq ($(MAKERULEDIR), )
#Makerule path not defined, define this and assume relative path from ROOTDIR
  MAKERULEDIR := $(ROOTDIR)/ti/build/makerules
  export MAKERULEDIR
endif

include $(MAKERULEDIR)/build_config.mk
include $(MAKERULEDIR)/platform.mk
include $(MAKERULEDIR)/env.mk

  • 0 in reply to Hrishikesh Rajurkar
    TI__Guru 55685 points
    Hi Hrishikesh,

    Due to some oversight this build was done using gmake from 6.1.1.
    Can you please try the same at your end once. CCS download link: processors.wiki.ti.com/.../Download_CCS
    We will be making a new release in around two weeks. We will enable Windows build using CCSv7 gmake in the new release.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Expert 1165 points
    Hi Rishabh,
    I suppose we use the gmake at path C:\PROCESSOR_SDK_VISION_03_02_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core
    and not from the CCS.
    regards
    Hrishikesh
  • 0 in reply to Hrishikesh Rajurkar
    TI__Guru 55685 points
    Hi Hrishikesh,

    For building PDK we use gmake from the CCS cygwin. Can you try using cygwin from CCSv7 and let me know if you see any issue.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Expert 1165 points
    Hi Risabh,
    I tried after downloading ccs7.3 from the link you had provided and changed the line utils_PATH ?= c:/ti/ccsv7/utils/cygwin in rules.make file.
    But still same error remains. I have tested on another pc (Abhay's pc) it shows the same error.
    regards
    Hrishikesh
  • 0 in reply to Hrishikesh Rajurkar
    TI__Guru 55685 points
    Hi Hrisikesh,

    As I mentioned in my previous posts we had built using ccsv6. I told ccsv7 in case you have the same.
    Can you confirm if the build fails with ccsv6 also. My colleague has tried this on his machine using ccsv6 and the build passes.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Expert 1165 points
    Hi Rishabh,
    Initial build was with ccsv6 only, after that I had downloaded and tested with ccsv7 which is also resulting in same error.
    Do we need to do any other settings ?
    regards
    Hrishikesh
  • 0 in reply to Hrishikesh Rajurkar
    TI__Guru 55685 points
    Hi Hrishikesh,

    In your previous post you had mentioned that you are using gmake from XDC.
    My question is whether you tried using CCS6 gmake?
    You can invoke by giving path like c:/ti/ccsv6/utils/cygwin/gmake.exe -s all CORE=ipu1_0 BOARD=tda2px-evm.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Expert 1165 points
    Hi Rishabh,
    Sorry for confusion, I have tried to build using CCS6/CCS7 gmake only. (the path mentioned in Rules.make in line utils_PATH ?= c:/ti/ccsv7/utils/cygwin ). I was under impression that pdk drivers are being build using xdc from PROCESSOR_SDK_VISION_03_02_00_00 till I looked at this line.
    regards
    Hrishikesh
  • 0 in reply to Rishabh Garg
    Genius 4105 points

    Hi Rishabh,

    We have used CCS7 gmake and compiled PDK using command "gmake -s all BOARD=tda2px-evm CORE=ipu1_0".

    We are still getting error which in this case is different from the previous one.

    Screenshot is attached for your reference.

    Regards,

    Abhay

  • 0 in reply to Abhay Sorte
    TI__Guru 55685 points
    Hi Abhay,

    This seems very weird to me. It might be a permissions issue.
    Can you check if you have all permissions on XDC tools.
    You can also try reinstalling XDC tools.
    If that also doesn't work try this build on a linux machine.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    TI__Guru 55685 points
    Hi Abhay,

    Can you please provide an update on this issue. Thanks.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Genius 4105 points
    Hi Rishabh,

    This issue is not fixed yet.
    We have not installed XDC tools separately, we are using XDC tool available in "ti_components\os_tools\windows\xdctools_3_32_01_22_core".
    And currently we cannot switch to Linux machine.
    Can you let us know where exactly do we need to set the permissions for XDC tool.

    Regards,
    Abhay
  • 0 in reply to Abhay Sorte
    TI__Guru 55685 points
    Hi Abhay,

    You should ensure that you have full permissions on this folder. This option is there in Properties -> Security tab in Windows 10.
    Sometimes the permissions are messed up even though if it shows full permissions. So you should first remove and then add all permissions.
    I didn't suggest you to switch to linux. Suggestion was to check if the same build issue is there on linux.
    When we try the build here we don't see any issue on both windows and linux.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    TI__Guru 55685 points
    Hi Abhay,

    Were you able to make progress? If yes please mark this thread as resolved. If not then let us know what you are observing.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Genius 4105 points

    Hi Rishabh,

    I have raised the issue for full permissions on the XDC tools with our IT person as we don't have Admin rights.

    So I will update the status today.

    Regards,

    Abhay

  • 0 in reply to Abhay Sorte
    Genius 4105 points
    Hi Rishabh,

    With full permissions on the xdc tools as well as ti_components folder, we still get the same error.
    We are getting the same error the screenshot of which was shared with you earlier.

    Regards,
    Abhay
  • 0 in reply to Abhay Sorte
    TI__Guru 55685 points
    Hi Abhay,

    Did you try to build on linux?

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Genius 4105 points
    Hi Rishabh,

    Yes we were able to build it on linux successfully with "make -s all CORE=ipu1_0 BOARD=tda2px-evm".

    Regards,
    Abhay
  • 0 in reply to Abhay Sorte
    TI__Guru 55685 points
    Hi Abhay,

    Thanks for the confirmation.
    For us the build is working both on windows and linux.
    Can you try it on some other windows machine?

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Genius 4105 points
    Hi Rishabh,

    We have tried on Window 7 and Window 10 PC. We got same error on both.
    Will try again after re-booting the machine.

    Regards,
    Abhay
  • 0 in reply to Abhay Sorte
    TI__Guru 55685 points
    Hi Abhay,

    Can you compare the PATH variable in Windows with Linux and analyze the difference.
    There might be something that is missing in Windows.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    TI__Guru 55685 points
    Hi Abhay,

    I have an update on this issue. This issue might be due to windows path limitation: support.microsoft.com/.../830473
    Can you rename "PROCESSOR_SDK_VISION_03_02_00_00" folder to "vsdk" and then try the build.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Genius 4105 points

    Hi Rishabh,

    We will try this and let you know.

    Regards,
    Abhay

  • 0 in reply to Abhay Sorte
    TI__Guru 55685 points
    Hi Abhay,

    Is this issue resolved?

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Genius 4105 points
    Hi Rishabh,

    Yes this issue is resolved. We are now able to build pdk drivers on Windows as well.
    We changed the name of directory from "PROCESSOR_SDK_VISION_03_02_00_00" to "psdk_3_2" as you suggested and the build was successful.
    Thank you for your support .

    Regards,
    Abhay
  • 0 in reply to Abhay Sorte
    TI__Guru 55685 points
    Hi Abhay,

    Great! Thanks for the confirmation.
    Kindly mark the post that solved your query as "This resolved my issue".
    Feel free to post any follow up questions by posting a reply or by creating a new thread.

    Regards,
    Rishabh