compile EDMA but get error

shuanghe Zhu

Hi,

thank you first for concerning on my question.

I wangt to compile the EDMA lib myself follow the steps listed by the EDMA3_Driver_User_Guide.pdf, but got ERROR when i gamke them. My CCS version is 5.1.

I want to know why i get this error and how to solve the problem. Thank you !

Following is what i have input to and get from the Command line:

C:\Program Files\Texas Instruments\edma3_lld_02_11_03_02\packages>set ROOTDIR=C:

/PROGRA~1/TEXASI~1/edma3_lld_02_11_03_02

C:\Program Files\Texas Instruments\edma3_lld_02_11_03_02\packages>set PATH=C:/PR

OGRA~1/TEXASI~1/xdctools_3_22_04_46

C:\Program Files\Texas Instruments\edma3_lld_02_11_03_02\packages>gmake libs FOR

MAT=ELF

# Making generic/c674:debug:edma3_lld_rm

gmake -C C:/PROGRA~1/TEXASI~1\edma3_lld_02_11_03_02/packages/ti/sdo/edma3/rm PLA

TFORM=generic CORE=674 PROFILE_674=debug

gmake[1]: Entering directory `C:/PROGRA~1/TEXASI~1/edma3_lld_02_11_03_02/package

s/ti/sdo/edma3/rm'

# Compiling src/edma3resmgr.c to obj/generic/674/debug/edma3resmgr.oe674 ...

C:/PROGRA~1/TEXASI~1/C6000C~1.3/bin/cl6x -ppd=obj/generic/674/debug/.deps/edma3

resmgr.P -c -qq -pdsw225 -mv6740 --abi=elfabi -mo -eo.oe674 -ea.se674 --symdebu

g:dwarf -Dxdc_target_name__=C674 -Dxdc_bld__profile_debug -D_DEBUG_=1 -DGENER

IC -Dxdc_target_types__=ti/targets/elf/std.h -Dxdc_bld__vers_1_0_7_2_0_10271 -mi

10 -DGENERIC -DGENERIC -IC:/PROGRA~1/TEXASI~1/C6000C~1.3/include -I. -I../..

/../.. -Isrc -fr=obj/generic/674/debug -fs=obj/generic/674/debug -fc src/edma3re

smgr.c

process_begin: CreateProcess(NULL, C:/PROGRA~1/TEXASI~1/C6000C~1.3/bin/cl6x -ppd

=obj/generic/674/debug/.deps/edma3resmgr.P -c -qq -pdsw225 -mv6740 --abi=elfabi

-mo -eo.oe674 -ea.se674 --symdebug:dwarf -Dxdc_target_name__=C674 -Dxdc_bld__pro

file_debug -D_DEBUG_=1 -DGENERIC -Dxdc_target_types__=ti/targets/elf/std.h -Dxdc

_bld__vers_1_0_7_2_0_10271 -mi10 -DGENERIC -DGENERIC -IC:/PROGRA~1/TEXASI~1/C600

0C~1.3/include -I. -I../../../.. -Isrc -fr=obj/generic/674/debug -fs=obj/generic

/674/debug -fc src/edma3resmgr.c, ...) failed.

make (e=3): 系统找不到指定的路径。

gmake[1]: *** [obj/generic/674/debug/edma3resmgr.oe674] Error 3

gmake[1]: Leaving directory `C:/PROGRA~1/TEXASI~1/edma3_lld_02_11_03_02/packages

/ti/sdo/edma3/rm'

gmake: *** [edma3_lld_rm_generic] Error 2

And following is the context of the env.mk file:

# File: env.mk. This file contains all the paths and other ENV variables

# Module paths

# Directory where all internal software packages are located; typically

# those that are checked into version controlled repository. In this case all

# the OMX components and SDK/OMX demo.

INTERNAL_SW_ROOT = C:/PROGRA~1/TEXASI~1/edma3_lld_02_11_03_02

# Directory where all external (imported) software packages are located; typically

# those that are NOT checked into version controlled repository. In this case,

# compiler tool chains, BIOS, XDC, Syslink, IPC, FC, CE, drivers, codecs, etc.

EXTERNAL_SW_ROOT = C:/PROGRA~1/TEXASI~1

# Destination root directory.

# - specify the directory where you want to place the object, archive/library,

# binary and other generated files in a different location than source tree

# - or leave it blank to place then in the same tree as the source

#DEST_ROOT = E:/DS

# 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).

UTILS_INSTALL_DIR = C:/PROGRA~1/TEXASI~1/xdctools_3_22_04_46

# Set path separator, etc based on the OS

ifeq ($(OS),Windows_NT)

PATH_SEPARATOR = ;

UTILSPATH = $(UTILS_INSTALL_DIR)/bin/

else

# else, assume it is linux

PATH_SEPARATOR = :

endif

# BIOS

bios_PATH = $(EXTERNAL_SW_ROOT)/bios_6_32_04_49

bios_INCLUDE = $(bios_PATH)/packages

# XDC

xdc_PATH = $(EXTERNAL_SW_ROOT)/xdctools_3_22_03_41

xdc_INCLUDE = $(xdc_PATH)/packages

# EDMA3 LLD

edma3_lld_PATH = $(INTERNAL_SW_ROOT)

include $(edma3_lld_PATH)/packages/component.mk

# Tools paths

# Cortex-M3

CODEGEN_PATH_M3 = $(EXTERNAL_SW_ROOT)/TMS470~1.0

# Cortex-A8

CODEGEN_PATH_A8 = $(EXTERNAL_SW_ROOT)/TMS470~1.0

# ARM-9

CODEGEN_PATH_ARM9 = $(EXTERNAL_SW_ROOT)/TMS470~1.0

# DSP - Since same toolchain does not support COFF and ELF, there are two entries

# This would go away when one version supports both formats

CODEGEN_PATH_DSP = $(EXTERNAL_SW_ROOT)/C6000C~1.3

CODEGEN_PATH_DSPELF = $(EXTERNAL_SW_ROOT)/C6000C~1.3

# Commands commonly used within the make files

RM = $(UTILSPATH)rm

RMDIR = $(UTILSPATH)rm -rf

MKDIR = $(UTILSPATH)mkdir

ECHO = @$(UTILSPATH)echo

# MAKE = $(UTILSPATH)make

EGREP = $(UTILSPATH)egrep

CP = $(UTILSPATH)cp

# This is to avoid using full blown cygwin - chmod is really needed only linux

ifeq ($(OS),Windows_NT)

CHMOD = @echo

else

CHMOD = $(UTILSPATH)chmod

endif

# XDC specific ENV variables

# XDC Config.bld file (required for configuro) ; Derives from top-level omx_PATH

CONFIG_BLD_XDC_674 = $(edma3_lld_PATH)/packages/_config.bld

CONFIG_BLD_XDC_64p = $(edma3_lld_PATH)/packages/_config.bld

CONFIG_BLD_XDC_64t = $(edma3_lld_PATH)/packages/_config.bld

CONFIG_BLD_XDC_a8 = $(edma3_lld_PATH)/packages/_config.bld

CONFIG_BLD_XDC_arm9 = $(edma3_lld_PATH)/packages/_config.bld

CONFIG_BLD_XDC_66 = $(edma3_lld_PATH)/packages/_config.bld

CONFIG_BLD_XDC_m3 = $(edma3_lld_PATH)/packages/_config.bld

XDCPATH = $(bios_PATH)/packages;$(xdc_PATH)/packages;$(edma3_lld_PATH)/packages;

export XDCPATH

XDCROOT = $(xdc_PATH)

XDCTOOLS = $(xdc_PATH)

export XDCROOT

export XDCTOOLS

TMS470_CGTOOLS = $(CODEGEN_PATH_M3)

CGTOOLS = $(CODEGEN_PATH_DSP)

CGTOOLS_ELF = $(CODEGEN_PATH_DSPELF)

export TMS470CGTOOLPATH

CODESOURCERYCGTOOLS = $(CODEGEN_PATH_A8)

export CODESOURCERYCGTOOLS

PATH += $(PATH_SEPARATOR)$(xdc_PATH)$(PATH_SEPARATOR)$(CODEGEN_PATH_M3)/bin

export PATH

# Nothing beyond this point

over 13 years ago

0 Prasad Konnur over 13 years ago

TI__Expert 6065 points

Hi,

Please make sure the paths mentioned in the env.mk are proper.

Like bios_PATH, xdc_PATH, CODEGEN_PATH_DSP/M3 are valid.

I can see that the xdc version used to set PATH variable in cmd prompt and xdc_PATH in env.mk are different.

Regards,
Prasad

0 shuanghe Zhu over 13 years ago in reply to Prasad Konnur

Prodigy 30 points

Hi,

Thank you very much for your work and solution, it's very useful and i have recorrected the paths mentioned in the env.mk, and now the error "cannot found the ptah (找不到指定路径)" have been solved, and i have compile the rm folder, but got a new error:

(command line:)

C:\Program Files\Texas Instruments\edma3_lld_02_11_03_02\packages>set ROOTDIR=C:/PROGRA~1/TEXASI~1/edma3_lld_02_11_03_02

C:\Program Files\Texas Instruments\edma3_lld_02_11_03_02\packages>set PATH=C:/PR\OGRA~1/TEXASI~1/xdctools_3_22_04_46

C:\Program Files\Texas Instruments\edma3_lld_02_11_03_02\packages>gmake libs FOR

MAT=ELF

...................

# Making generic/arm9:release:edma3_lld_rm
gmake -C C:/PROGRA~1/TEXASI~1/edma3_lld_02_11_03_02/packages/ti/sdo/edma3/rm PLA
TFORM=generic CORE=arm9 PROFILE_arm9=release
gmake[1]: Entering directory `C:/PROGRA~1/TEXASI~1/edma3_lld_02_11_03_02/package
s/ti/sdo/edma3/rm'
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory `C:/PROGRA~1/TEXASI~1/edma3_lld_02_11_03_02/packages
/ti/sdo/edma3/rm'
# Making c674:debug:edma3_lld_drv
gmake -C C:/PROGRA~1/TEXASI~1/edma3_lld_02_11_03_02/packages/ti/sdo/edma3/drv PL
ATFORM=ti816x-evm PROFILE_c6xdsp=debug
gmake[1]: Entering directory `C:/PROGRA~1/TEXASI~1/edma3_lld_02_11_03_02/package
s/ti/sdo/edma3/drv'
gmake[1]: *** No rule to make target `C:\Program', needed by `obj/674/debug/edma
3_drv_adv.oe674'. Stop.
gmake[1]: Leaving directory `C:/PROGRA~1/TEXASI~1/edma3_lld_02_11_03_02/packages
/ti/sdo/edma3/drv'
gmake: *** [edma3_lld_ti816x-evm_674_libs_drv] Error 2

I have view the makefile and the makerules file, but don't know how to solve this problem, my ccs version is CCS5.1, and the edma version is : edma3_lld_02_11_03_02,

there are two xdc version ,one is xdctools_3_22_04_46, and the other is xdctools_3_20_08_88, i have test both them ,but the result is the same,

I want to know how to find the error' source? thank you !

Regards

Following is the context of env.mk file:

# File: env.mk. This file contains all the paths and other ENV variables

#
# Module paths
#

# Directory where all internal software packages are located; typically
# those that are checked into version controlled repository. In this case all
# the OMX components and SDK/OMX demo.
INTERNAL_SW_ROOT = C:/PROGRA~1/TEXASI~1/edma3_lld_02_11_03_02

# Directory where all external (imported) software packages are located; typically
# those that are NOT checked into version controlled repository. In this case,
# compiler tool chains, BIOS, XDC, Syslink, IPC, FC, CE, drivers, codecs, etc.
EXTERNAL_SW_ROOT = C:/PROGRA~1/TEXASI~1

# Destination root directory.
#   - specify the directory where you want to place the object, archive/library,
#     binary and other generated files in a different location than source tree
#   - or leave it blank to place then in the same tree as the source
#DEST_ROOT = E:/DS

# 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).
UTILS_INSTALL_DIR = C:/PROGRA~1/TEXASI~1/xdctools_3_22_04_46

# Set path separator, etc based on the OS
ifeq ($(OS),Windows_NT)
PATH_SEPARATOR = ;
UTILSPATH = $(UTILS_INSTALL_DIR)/bin/
else
# else, assume it is linux
PATH_SEPARATOR = :
endif

# BIOS
bios_PATH = $(EXTERNAL_SW_ROOT)/bios_6_32_05_54
bios_INCLUDE = $(bios_PATH)/packages

# XDC
xdc_PATH = $(EXTERNAL_SW_ROOT)/xdctools_3_22_04_46
xdc_INCLUDE = $(xdc_PATH)/packages

# EDMA3 LLD
edma3_lld_PATH = $(INTERNAL_SW_ROOT)
include $(edma3_lld_PATH)/packages/component.mk

#
# Tools paths
#
# Cortex-M3
CODEGEN_PATH_M3 = C:\ti\ccsv5\tools\compiler\tms470

# Cortex-A8
CODEGEN_PATH_A8 = C:\ti\ccsv5\tools\compiler\tms470

# ARM-9
CODEGEN_PATH_ARM9 = C:\ti\ccsv5\tools\compiler\tms470

# DSP - Since same toolchain does not support COFF and ELF, there are two entries
# This would go away when one version supports both formats
CODEGEN_PATH_DSP = C:\ti\ccsv5\tools\compiler\c6000
CODEGEN_PATH_DSPELF = C:\ti\ccsv5\tools\compiler\c6000

# Commands commonly used within the make files

RM = $(UTILSPATH)rm
RMDIR = $(UTILSPATH)rm -rf
MKDIR = $(UTILSPATH)mkdir
ECHO = @$(UTILSPATH)echo
# MAKE = $(UTILSPATH)make
EGREP = $(UTILSPATH)egrep
CP = $(UTILSPATH)cp

# This is to avoid using full blown cygwin - chmod is really needed only linux
ifeq ($(OS),Windows_NT)
CHMOD = @echo
else
CHMOD = $(UTILSPATH)chmod
endif

#
# XDC specific ENV variables
#

# XDC Config.bld file (required for configuro) ; Derives from top-level omx_PATH
CONFIG_BLD_XDC_674 = $(edma3_lld_PATH)/packages/_config.bld
CONFIG_BLD_XDC_64p = $(edma3_lld_PATH)/packages/_config.bld
CONFIG_BLD_XDC_64t = $(edma3_lld_PATH)/packages/_config.bld
CONFIG_BLD_XDC_a8 = $(edma3_lld_PATH)/packages/_config.bld
CONFIG_BLD_XDC_arm9 = $(edma3_lld_PATH)/packages/_config.bld
CONFIG_BLD_XDC_66 = $(edma3_lld_PATH)/packages/_config.bld
CONFIG_BLD_XDC_m3 = $(edma3_lld_PATH)/packages/_config.bld

XDCPATH = $(bios_PATH)/packages;$(xdc_PATH)/packages;$(edma3_lld_PATH)/packages;
export XDCPATH

XDCROOT = $(xdc_PATH)
XDCTOOLS = $(xdc_PATH)
export XDCROOT
export XDCTOOLS

TMS470_CGTOOLS = $(CODEGEN_PATH_M3)
CGTOOLS = $(CODEGEN_PATH_DSP)
CGTOOLS_ELF = $(CODEGEN_PATH_DSPELF)
export TMS470CGTOOLPATH

CODESOURCERYCGTOOLS = $(CODEGEN_PATH_A8)
export CODESOURCERYCGTOOLS

PATH += $(PATH_SEPARATOR)$(xdc_PATH)$(PATH_SEPARATOR)$(CODEGEN_PATH_M3)/bin
export PATH

# Nothing beyond this point

0 shuanghe Zhu over 13 years ago in reply to Prasad Konnur

Prodigy 30 points

Hi,

I have found the reason of the problem which i asked for help just now, it's my own false, i have modifed a src file, and it have some error, now i have compile the edma lib, thank you very much for your help!

Regards,

Prasad

0 user4818971 over 8 years ago in reply to shuanghe Zhu

Prodigy 20 points

After you compile it ,you get a lib?in which directory?

0 Kenia Guinto over 8 years ago in reply to user4818971

TI__Expert 7250 points

Hi,
We generally discourage posting a new question to an old closed thread because the person who answered before may no longer be available, and also it will allow whomever is currently assigned to monitor the forum to respond to you more quickly. For these reasons, I suggest you start a new thread with your question and reference this thread.

Thank you

Processors

Processors forum

compile EDMA but get error