Hi, The Error message "xdc.loadPackage: can't find package 'dsplink.dsp" looks like the DSP Link Path is not included in the XDC_PATH variable. Can you add the following code at the last line of file xdcpaths.mak (located at codec_engine_2_20_00_15\examples)
XDC_PATH := $(DSPLINK_INSTALL_DIR)/packages;$(XDC_PATH) Regards Ansari -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, June 12, 2009 11:30 AM To: [email protected] Subject: Davinci-linux-open-source Digest, Vol 42, Issue 76 Send Davinci-linux-open-source mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Davinci-linux-open-source digest..." Today's Topics: 1. RE: DaVinci git update: v2.6.30 + dm365 + da830 (Paulraj, Sandeep) 2. Re: [PATCH v4 3/4] ARM: DaVinci: ASoC: Add mcasp support for DM646x (Denys Dmytriyenko) 3. Re: CMEM usage in no codec oriented application (Gopal Sukumar) 4. RE: DaVinci git update: v2.6.30 + dm365 + da830 (Rajashekhara, Sudhakar) 5. Example code servers": Error: xdc.loadPackage: can't find package 'dsplink.dsp' (Sandeep YEDIRE) ---------------------------------------------------------------------- Message: 1 Date: Thu, 11 Jun 2009 19:52:39 -0500 From: "Paulraj, Sandeep" <[email protected]> Subject: RE: DaVinci git update: v2.6.30 + dm365 + da830 To: Kevin Hilman <[email protected]>, "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" Kevin, If you look at the Kconfig , I do not see ARCH_DAVINCI_DMx being selected for DM365. Shouldn't that be the case? Thanks, Sandeep > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf > Of Kevin Hilman > Sent: Thursday, June 11, 2009 4:27 PM > To: [email protected] > Subject: DaVinci git update: v2.6.30 + dm365 + da830 > > Hello, > > DaVinci git has been update to v2.6.30 as well as the merging of basic > support for dm365 and da830. > > Kevin > > _______________________________________________ > Davinci-linux-open-source mailing list > [email protected] > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ------------------------------ Message: 2 Date: Thu, 11 Jun 2009 21:31:07 -0400 From: Denys Dmytriyenko <[email protected]> Subject: Re: [PATCH v4 3/4] ARM: DaVinci: ASoC: Add mcasp support for DM646x To: Chaithrika U S <[email protected]> Cc: [email protected], Pavel Kiryukhin <[email protected]>, [email protected], Naresh Medisetty <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii Chaithrika, On Fri, Jun 05, 2009 at 06:28:40AM -0400, Chaithrika U S wrote: > Adds driver support for the two instances of McASP on TI's DM646x. In patch #3 you removed struct evm_snd_platform_data: > -struct evm_snd_platform_data { > - int tx_dma_ch; > - int rx_dma_ch; > -}; That structure is still used in sound/soc/davinci/davinci-evm.c, until you fix it by patch #4: > -static struct evm_snd_platform_data dm335evm_snd_data = { > - .tx_dma_ch = DAVINCI_DMA_ASP1_TX, > - .rx_dma_ch = DAVINCI_DMA_ASP1_RX, That would break git-bisect... -- Denys ------------------------------ Message: 3 Date: Fri, 12 Jun 2009 10:17:49 +0530 From: Gopal Sukumar <[email protected]> Subject: Re: CMEM usage in no codec oriented application To: "Tivy, Robert" <[email protected]> Cc: davinci-linux-open-source <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" That's right! He has done this and it seems it is working fine for him. Regards, Gopal Sukumar. Tivy, Robert wrote: The CMEM module does not need to be loaded for the application link stage. If you get "undefined reference to CMEM_init" then that just means that you're not correctly referencing cmem.a in your link. Regards, - Rob ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Gopal Sukumar Sent: Thursday, June 11, 2009 1:54 AM To: Ondrej Pindroch Cc: davinci-linux-open-source Subject: Re: CMEM usage in no codec oriented application Hi Ondrej, This means linking cmem to your app has failed. Ensure that you have loaded the cmem module. Thanks, Gopal Sukumar. Ondrej Pindroch wrote: Hi How can I use CMEM and all it's API. In my application. I need to get one buffer with size almost 10MB, which will be continous in virtual and physical memory space. I have tried link cmem.a to my project but it told me "undefined reference to CMEM_init" and so on. Thanks for your answer Ondrej Pindroch SoftHard Technology ltd. ________________________________ _______________________________________________ Davinci-linux-open-source mailing list [email protected]<mailto:[email protected]> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ________________________________ http://www.mindtree.com/email/disclaimer.html ________________________________ http://www.mindtree.com/email/disclaimer.html -------------- next part -------------- An HTML attachment was scrubbed... URL: http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20090612/030405d7/attachment-0001.htm ------------------------------ Message: 4 Date: Fri, 12 Jun 2009 10:48:17 +0530 From: "Rajashekhara, Sudhakar" <[email protected]> Subject: RE: DaVinci git update: v2.6.30 + dm365 + da830 To: "'Kevin Hilman'" <[email protected]>, <[email protected]> Message-ID: <00b901c9eb1d$31857aa0$94906f...@[email protected]> Content-Type: text/plain; charset="us-ascii" On Fri, Jun 12, 2009 at 01:56:38, Kevin Hilman wrote: > Hello, > > DaVinci git has been update to v2.6.30 as well as the merging of basic support for dm365 and da830. > I tried booting this kernel on DA830 using da830_omapl137_defconfig but booting hangs at: ... Load Address: c0008000 Entry Point: c0008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... The http://linux.omap.com/pipermail/davinci-linux-open-source/2009-April/012557. html patch from Mark Greer solves this issue. Regards, Sudhakar ------------------------------ Message: 5 Date: Fri, 12 Jun 2009 11:29:20 +0530 (IST) From: Sandeep YEDIRE <[email protected]> Subject: Example code servers": Error: xdc.loadPackage: can't find package 'dsplink.dsp' To: [email protected] Cc: Sandeep Yedire <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Skipped content of type multipart/alternative-------------- next part -------------- # # ======== xdcpaths.mak ======== # definition of XDC paths and commands # # This makefile constructs the "search path" for the XDC tools where it finds # numerous components and packages needed to build Codec Engine examples and # programs. # # USER NOTE: # 1) you must specify various <component>_INSTALL_DIRs directores below to # reflect your installation, where <component> is CE for Codec Engine, # BIOS for DSP/BIOS, etc. # 2) you can remove some of the devices from the "DEVICES" list and/or remove # some of the types of binaries from the "PROGRAMS" list to reduce # the build time (and possibly avoid checking for presence of a component # you don't need) # # # # (Optional) Remove from this list the devices you're not interested in building DEVICES := DM6446 ## DM355 DM6437 DM648 #Removed from list_Jun 10, 2009, Sandeep. # (Optional) Remove from the list the types of programs you're not intersted in # building: # APP_CLIENT -- Arm client for codecs running on the DSP, on dual-CPU systems # DSP_SERVER -- DSP server with the codecs, running on the DSP, on dual-CPUs # APP_LOCAL -- Client+codecs in a single program, whether Arm only or DSP only PROGRAMS :=APP_CLIENT DSP_SERVER #APP_LOCAL # (Mandatory) Specify where various components are installed. # What you need depends on what device(s) you're building for, what type(s) of # programs you are building for, and whether your Codec Engine distribution # is a "big" one that contains all the minor components in its "cetools" # directory. The legend: # CE - Codec Engine (needed for Arm and for DSP) # XDC - XDC tools (Arm and DSP) # BIOS - DSP/BIOS (DSP only) # XDAIS - XDAIS header files (Arm and DSP) # FC - Framework components, various resource managers (ARM and DSP) # CMEM - Continuous memory manager (Arm only) # DSPLINK - Arm<->DSP communication software (Arm + DSP) # # you can ommit directory specifications for the components you think you don't # need (will be warned if you do, based on your DEVICES + PROGRAMS selection # above). CE_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/codec_engine_2_00_01 XDC_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/xdc_3_00_02 BIOS_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/bios_5_31_08 # no need to specify the installation directories below if your CE installation # has cetools/ directory on top USE_CETOOLS_IF_EXISTS :=1 XDAIS_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/xdias_6_00_01 DSPLINK_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/dsplink_140-05p1 CMEM_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/cmem_2_00_01 FC_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/framework_components_2_00_01 BIOSUTILS_INSTALL_DIR :=/home/sandeep/dvsdk_1_30_01_41/biosutils_1_00_02 # (Mandatory) specify correct compiler paths and names for the architectures # you'll be building for: # compiler path and name for Montavista Arm 9 toolchain. NOTE: make sure the # directory you specify has a "bin" subdirectory CGTOOLS_MVARM9 =/opt/mv_pro_4.0.1/montavista/pro/devkit/arm/v5t_le CC_MVARM9 =bin/arm_v5t_le-gcc # compiler path and name for TI C64x toolchain. NOTE: make sure the # directory you specify has a "bin" subdirectory CGTOOLS_C64X =/home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15 CC_C64X =bin/cl6x # # ----------------------------------------------------------------------------- # determine which components are necessary based on DEVICES and PROGRAMS REQUIRE_CE :=1 REQUIRE_XDC :=1 REQUIRE_XDAIS :=1 REQUIRE_FC :=1 # ifneq (,$(findstring DM6446,$(DEVICES))) ifneq (, $(findstring APP_CLIENT, $(PROGRAMS) )) REQUIRE_LINK := 1 REQUIRE_CMEM := 1 endif ifneq (, $(findstring DSP_SERVER, $(PROGRAMS) )) REQUIRE_LINK := 1 REQUIRE_BIOS := 1 endif endif ifneq (,$(findstring DM355,$(DEVICES))) ifneq (, $(findstring APP_LOCAL, $(PROGRAMS) )) REQUIRE_CMEM := 1 endif endif ifneq (,$(findstring DM6437,$(DEVICES))) ifneq (, $(findstring APP_LOCAL, $(PROGRAMS) )) REQUIRE_BIOS := 1 endif endif ifneq (,$(findstring DM648,$(DEVICES))) ifneq (, $(findstring APP_LOCAL, $(PROGRAMS) )) REQUIRE_BIOS := 1 endif endif # Build the XDC path from the necessary components, verifying along the way # that the required compoments are present XDC_PATH := ERRMSG = which is invalid (could not find file "$(TEST_FILE)"). Set this in <codec engine examples>/xdcpaths.mak! See the build documentation to correct this error. # CE_INSTALL_DIR is the location of your Codec Engine. ifeq ($(REQUIRE_CE), 1) TEST_FILE := $(CE_INSTALL_DIR)/packages/ti/sdo/ce/package.xdc ifeq ($(wildcard $(TEST_FILE)),) $(error CE_INSTALL_DIR is set to "$(CE_INSTALL_DIR)", $(ERRMSG)) endif XDC_PATH := $(CE_INSTALL_DIR)/packages endif # if the CE distribution has "cetools/", we have components in the "else" branch available inside "cetools" ifeq ($(USE_CETOOLS_IF_EXISTS), 1) XDC_PATH := $(XDC_PATH);$(CE_INSTALL_DIR)/cetools/packages else # XDAIS_INSTALL_DIR is the location of your XDAIS distribution ifeq ($(REQUIRE_XDAIS), 1) TEST_FILE := $(XDAIS_INSTALL_DIR)/packages/ti/xdais/package.xdc ifeq ($(wildcard $(TEST_FILE)),) $(error XDAIS_INSTALL_DIR is set to "$(XDAIS_INSTALL_DIR)", $(ERRMSG)) endif XDC_PATH := $(XDC_PATH);$(XDAIS_INSTALL_DIR)/packages endif # DSPLINK_INSTALL_DIR is the location of your DSPLINK distribution ifeq ($(REQUIRE_LINK), 1) TEST_FILE := $(DSPLINK_INSTALL_DIR)/packages/dsplink/gpp/package.xdc ifeq ($(wildcard $(TEST_FILE)),) $(error DSPLINK_INSTALL_DIR is set to "$(DSPLINK_INSTALL_DIR)", $(ERRMSG)) endif XDC_PATH := $(XDC_PATH);$(DSPLINK_INSTALL_DIR)/packages endif # CMEM_INSTALL_DIR is the location of your CMEM distribution ifeq ($(REQUIRE_CMEM), 1) TEST_FILE := $(CMEM_INSTALL_DIR)/packages/ti/sdo/linuxutils/cmem/package.xdc ifeq ($(wildcard $(TEST_FILE)),) $(error CMEM_INSTALL_DIR is set to "$(CMEM_INSTALL_DIR)", $(ERRMSG)) endif XDC_PATH := $(XDC_PATH);$(CMEM_INSTALL_DIR)/packages endif # FC_INSTALL_DIR is the location of your Frameworks Components distribution ifeq ($(REQUIRE_FC), 1) TEST_FILE := $(FC_INSTALL_DIR)/packages/ti/sdo/fc/dskt2/package.xdc ifeq ($(wildcard $(TEST_FILE)),) $(error FC_INSTALL_DIR is set to "$(FC_INSTALL_DIR)", $(ERRMSG)) endif XDC_PATH := $(XDC_PATH);$(FC_INSTALL_DIR)/packages endif # BIOSUTILS_INSTALL_DIR is the location of your BIOSUTILS distribution ifeq ($(REQUIRE_BIOS), 1) TEST_FILE := $(BIOSUTILS_INSTALL_DIR)/packages/ti/bios/utils/package.xdc ifeq ($(wildcard $(TEST_FILE)),) $(error BIOSUTILS_INSTALL_DIR is set to "$(BIOSUTILS_INSTALL_DIR)", $(ERRMSG)) endif XDC_PATH := $(XDC_PATH);$(BIOSUTILS_INSTALL_DIR)/packages endif endif # BIOS_INSTALL_DIR is the location of your BIOS distribution ifeq ($(REQUIRE_BIOS), 1) TEST_FILE := $(BIOS_INSTALL_DIR)/packages/ti/bios/package.xdc ifeq ($(wildcard $(TEST_FILE)),) $(error BIOS_INSTALL_DIR is set to "$(BIOS_INSTALL_DIR)", $(ERRMSG)) endif XDC_PATH := $(XDC_PATH);$(BIOS_INSTALL_DIR)/packages endif # XDC_INSTALL_DIR is the location of your XDCTOOLS installation. ifeq ($(REQUIRE_XDC), 1) TEST_FILE := $(XDC_INSTALL_DIR)/packages/xdc/package.xdc ifeq ($(wildcard $(TEST_FILE)),) $(error XDC_INSTALL_DIR is set to "$(XDC_INSTALL_DIR)", $(ERRMSG)) endif endif # XDC_PATH is complete. Any other components you could add as # XDC_PATH := <your component>/packages;$(XDC_PATH) -------------- next part -------------- /* * ======== user.bld ======== * * User note: YOU MUST MODIFY THIS FILE TO SPECIFY THE COMPILER TOOL PATHS. */ // This table list the targets for which to build libraries and programs, and for // each target it lists where the compiler tools are and for what platforms // the programs should be built. For all build variants where you specify // that "doBuild" is "true", you must specify the compiler tools, and it is // desirable to comment out unwanted platforms. // Example: if you are only interested in building Arm-side examples for // evmDM6446 running Montavista Arm Linux, set doBuild: false everywhere // except for the first Arm "doBuild"; then, specify your Montavista Arm // tools directory, and comment out all platforms for that build except // for '{ platform: "evmDM6446" }'. var buildTable = { "Arm": [{doBuild: true, // standard build for Montavista Linux target: "gnu.targets.MVArm9", // MVArm tools. NOTE: make sure the directory you specify has a "bin" subdirectory cgtoolsRootDir: "/opt/mv_pro_4.0.1/montavista/pro/devkit/arm/v5t_le", platforms: [ // NOTE: comment out platforms (boards) below for which you don't want to build { description: "DaVinci evmDM6446 board, ARM-side", platform: "evmDM6446", dualCpu: true }, //{ description: "DaVinci evmDM355 board, ARM only", platform: "evmDM6446", dualCpu: false, outDir: "evmDM355" }, ], }, { doBuild: false, // build for uC Linux target: "gnu.targets.UCArm9", // UCLibc tools. NOTE: make sure the directory you specify has a "bin" subdirectory cgtoolsRootDir: "/db/toolsrc/library/vendors2005/opensource/buildroot/16012006/staging_dir", platforms: [ { description: "DaVinci evmDM6446 board, ARM-side", platform: "evmDM6446", dualCpu: true }, //{ description: "DaVinci evmDM355 board, ARM only", platform: "evmDM6446", dualCpu: false, outDir: "evmDM355" }, ], }], "DSP": [{doBuild: true, // DSP builds (DSP servers for dual-CPU platforms or full apps for DSP-only platforms) target: "ti.targets.C64P", // specify the "root directory" for the compiler tools. NOTE: make sure the directory you specify has a "bin" subdirectory cgtoolsRootDir: "/home/sandeep/dvsdk_1_30_01_41/cg6x_6_0_15", platforms: [ // NOTE: comment out platforms (boards) below for which you don't want to build { description: "DaVinci evmDM6446 board, DSP-side Server", platform: "evmDM6446" }, //{ description: "DaVinci evmDM6437 board, DSP only", platform: "evmDM6437" }, // { description: "DaVinci evmDM648 board, DSP only", platform: "evmDM648" }, ], }], "PC": [{doBuild: false, // build for PC Linux target: "gnu.targets.Linux86", cgtoolsRootDir: "/db/toolsrc/library/vendors2005/opensource/gcc/4.1.0/Linux/gcc-4.1.0-glibc-2.3.6/i686-unknown-linux-gnu", platforms: [ { platform: null, outDir: "PC" } ], }], }; // expert users: you can specify any compiler toolchain-specific options // here, for example, // C64P.ccOpts.prefix = "-pdr"; // enable remarks for the TI C64P compiler // UCArm9.lnkOpts.suffix = "-static"; // static linking // etc. // // no need to edit anything below this line // ----------------------------------------------------------------------------- var targets = []; var userbldBuildPlatforms = {}; for (var c in buildTable) { var cpu = buildTable[ c ]; for (var t = 0; t < cpu.length; t++) { if (cpu[t].doBuild) { var targ = xdc.useModule( cpu[t].target ); targets[ targets.length ] = targ; targ.rootDir = cpu[t].cgtoolsRootDir; var targName = cpu[t].target.replace( /.*\./g, "" ); userbldBuildPlatforms[ targName ] = cpu[t].platforms; } } } Build.targets = targets; ------------------------------ _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source End of Davinci-linux-open-source Digest, Vol 42, Issue 76 ********************************************************* _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
