RE: Re: ***SPAM*** Score/Req: 09.40/05.00 - Fwd: Is Code Engine necessary
Carlos, In dsp_link1_30_08 setup package, when you setup, you can find them, both examples and documents. If you do not want to use CE, you can use the proc and message queue modules in dsp_link to interface your ARM linux application and DSP alg. Thanks George Gu (Xiangyu Gu) Wintech Digital System Co. Beijing, China Ph: 8610-8278-2828 ext.168 Fax: 8610-8278-0028 http://www.wintechdigtal.com -Original Message- From: Carlos Ojea [mailto:[EMAIL PROTECTED] Sent: 2007年1月8日 15:48 To: George Gu Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; davinci-linux-open-source@linux.davincidsp.com Subject: Fwd: Re: ***SPAM*** Score/Req: 09.40/05.00 - Fwd: Is Code Engine necessary Where could we find that TI BIOS LINK ? Thanks, Carlos ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: Is Code Engine necessary
As George Gu posted, it's entirely possible to use DSP Link without Codec Engine. However, if this is only because you've found that CE API modules may take up quite a bit of memory, I'd encourage you post your findings to the list and let us help you explore ways to reduce that memory before inventing your own framework. There are ways to modify/minimize the memory map described here: http://www.mail-archive.com/[EMAIL PROTECTED] om/msg01238.html CE is clearly not the best framework for all architectures, so there are valid reasons _not_ to use it. But I'd be surprised if the memory footprint is significantly more than a custom framework (and if it is, we should fix it!); and there are real benefits to using the CE framework (robust, portable, extensible, integrated tooling, etc). Chris From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, January 07, 2007 5:55 AM To: Preissig, Steve; Ring, Chris; davinci-linux-open-source@linux.davincidsp.com Subject: Is Code Engine necessary Hi Steve, Chris and everyone, For the last couple of weeks, I have been reading and learning how to use the CE API to get a better picture of how to do stuff; I'm new to the CE API world. I've played around with the codecs example. I just realized that the custom Davinci board we have has limited dedicated SRAM for the DSP (only 512 Kbytes). As a result, I don't have much memory resources for the DSP; I noticed that the CE Server with all the supporting CE API modules may take up quite a bit of memory resources. Is it possible to do my own codecs without using the CE API? For example, I would have to create a codec application (under CCS 3.2) with DSP/BIOS and load it via the DSP Link under Linux? Would I then do intercommunication between the ARM and DSP via DSP Link? Can anyone please point me to examples or documentation that show me how to do such a design without CE and how to do intercommunication between the ARM and DSP? FYI, I'm not doing anything advanced (like video stuff), so I have no need for the nice CE API; I've posted many times here already that I'm just doing a simple speech codec on the DSP side and have an application on the ARM side that uses it. Thanks! Regards, Andy Ngo --- From steve-p at ti.com Mon Dec 4 08:44:22 2006 From: steve-p at ti.com (Preissig, Steve) Date: Mon Dec 4 08:44:26 2006 Subject: Beginner Needing Help! Andy, The application you describe is well suited to the DaVinci architecture, although you will probably want to re-organize your input/output scheme. You describe in your post that the DSP samples a mic and plays to a speaker. With the current Codec Engine framework, the general model is that the Arm handles all I/O and uses the DSP as a coprocessor to encode and decode. Currently, there are no DSP-side I/O drivers developed, but the Linux OSS driver should meet your needs for both sampling the mic and outputting to speakers. Qn 1: (documents/source for building a server) - The basic reference for this is the Codec Engine Server Integrator's Guide, lit# sprued5: http://focus.ti.com/lit/ug/sprued5/sprued5.pdf The Codec Engine package that comes with the DVEVM is the only source code example I know of for building a server, but should provide a good starting point for you. These examples are located at: $(DVEVM_INSTALL_DIR)/codec_engine_1_02/examples/servers And use the codecs which are provided at: $(DVEVM_INSTALL_DIR)/codec_engine_1_02/examples/codecs Qn 2: (building a server without DVSDK) - In order to build servers, you need the TMS320C6000 code generation tools (compiler, assembler, linker) as well as DSP/BIOS for the 'C6000. These both come with the SDK, or it is possible to purchase them separately. Qn 3: (simplest design) - In order to build your Speex codec into a DSP Server, you will need to implement the xDM (xDAIS for Digital Media) interface for it to communicate with the Codec Engine framework, and you will need to package it in a RTSC package. Both of these are described in the Codec Engine Algorithm Creator's User Guide, sprued6: http://focus.ti.com/lit/ug/sprued6a/sprued6a.pdf And the codec examples at $(DVEVM_INSTALL_DIR)/codec_engine_1_02/examples/codecs Implement both as examples. Hopefully you will be able to use the predefined SPHENC and SPHDEC codec classes for this
Issue regarding USB support
Hi there, I've been getting so many errors, while i'm trying to compile the montavista kernel with the USB support option. Can anyone please help me out with this. I'm listing the errors that i'm getting. [EMAIL PROTECTED] ti-davinci]$ make ARCH=arm CROSS_COMPILE=arm_v5t_le- uImage CHK include/linux/version.h CC arch/arm/kernel/asm-offsets.s In file included from include/asm/page.h:27, from include/asm/cpu-single.h:33, from include/asm/proc-fns.h:154, from include/asm/system.h:95, from include/asm/bitops.h:22, from include/linux/bitops.h:77, from include/linux/thread_info.h:20, from include/linux/spinlock.h:12, from include/linux/capability.h:45, from include/linux/sched.h:7, from arch/arm/kernel/asm-offsets.c:13: include/asm/glue.h:111:2: #error Unknown data abort handler type In file included from include/asm/cpu-single.h:33, from include/asm/proc-fns.h:154, from include/asm/system.h:95, from include/asm/bitops.h:22, from include/linux/bitops.h:77, from include/linux/thread_info.h:20, from include/linux/spinlock.h:12, from include/linux/capability.h:45, from include/linux/sched.h:7, from arch/arm/kernel/asm-offsets.c:13: include/asm/page.h:92:2: #error Unknown user operations model In file included from include/asm/semaphore.h:10, from include/linux/sched.h:18, from arch/arm/kernel/asm-offsets.c:13: include/linux/rwsem.h:38:65: asm/rwsem.h: No such file or directory In file included from include/asm/semaphore.h:10, from include/linux/sched.h:18, from arch/arm/kernel/asm-offsets.c:13: include/linux/rwsem.h: In function `compat_down_read': include/linux/rwsem.h:56: warning: implicit declaration of function `__down_read' include/linux/rwsem.h: In function `compat_down_read_trylock': include/linux/rwsem.h:67: warning: implicit declaration of function `__down_read_trylock' include/linux/rwsem.h: In function `compat_down_write': include/linux/rwsem.h:79: warning: implicit declaration of function `__down_write' include/linux/rwsem.h: In function `compat_down_write_trylock': include/linux/rwsem.h:90: warning: implicit declaration of function `__down_write_trylock' include/linux/rwsem.h: In function `compat_up_read': include/linux/rwsem.h:101: warning: implicit declaration of function `__up_read' include/linux/rwsem.h: In function `compat_up_write': include/linux/rwsem.h:111: warning: implicit declaration of function `__up_write' include/linux/rwsem.h: In function `compat_downgrade_write': include/linux/rwsem.h:121: warning: implicit declaration of function `__downgrade_write' include/linux/rwsem.h: In function `init_rwsem': include/linux/rwsem.h:132: warning: implicit declaration of function `compat_init_rwsem' In file included from arch/arm/kernel/asm-offsets.c:13: include/linux/sched.h: At top level: include/linux/sched.h:355: error: field `mmap_sem' has incomplete type In file included from include/linux/fs.h:213, from include/linux/mm.h:15, from arch/arm/kernel/asm-offsets.c:14: include/linux/kobject.h:151: error: field `rwsem' has incomplete type In file included from include/linux/fs.h:300, from include/linux/mm.h:15, from arch/arm/kernel/asm-offsets.c:14: include/linux/quota.h:288: error: field `dqptr_sem' has incomplete type In file included from include/linux/mm.h:15, from arch/arm/kernel/asm-offsets.c:14: include/linux/fs.h:453: error: field `i_alloc_sem' has incomplete type In file included from include/linux/mm.h:15, from arch/arm/kernel/asm-offsets.c:14: include/linux/fs.h:772: error: field `s_umount' has incomplete type make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 1 make: *** [arch/arm/kernel/asm-offsets.s] Error 2 I need to resolve this and i don't have much time for it. Kindly, please help me out with this. Regards, Akhil Kaushal P ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Software tools install problem
Hello I am new to Davinci DVEVM. I try to install DVEVM software tools on my PC (Red Hat Enterprise Linux v3) There is no InstallShield Wizard will show out and no error message after I execute the mvl_setuplinux_x_xx_xx_xx.bin (I already set the DISPLALY environment varialbe to cnabcx) How to solve this problem? Regards, Brady ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: RE: Problems of buliding codec engine examples
Hello,Chris Thanks for your kindly help. And now I have correctly build the examples of the codec engine. Before I run the examples I want to make clearly of this question: We know from TI that the DVEVM board should have 256MB DDR Memory, but the DVEVM board I boughth from Wintech(the dealer of TI in China) has only 64MB DDR Meomory on the board! Now, how can I set the memory map of the Davinci to run the exanples? Since the rules of setting the memory map is so complex in the build_instructions.html file. It is there any easy way to do this? Best Regards! Beny 1. If you _just_ want to rebuild the ARM-side examples, you can comment out C64P and Linux86 from the Build.targets array. What are these targets? * C64P == the DSP side of DaVinci target. It's one of TI's DSP processor families (http://focus.ti.com/dsp/docs/dspplatformscontenttp.tsp?sectionId=2familyId=132tabId=489). * MVArm9 == MontaVista Arm 9 target. This is the ARM side of DaVinci. * Linux86 == Intel's x86 target. A not-always-understood detail about Codec Engine is that it can run natively on x86 processors. This feature's got some limitations (codecs must be local, and must not access hardware since they run in user mode), but you can do a fair amount of development on this environment. 2 3. As you correctly supposed, BIOS is only needed if you're building DSP-side content (same with FC - Framework Components). You should set REQUIRE_BIOS = 0. BUT... Looks like you've identified a bug in xdcpaths.mak where it's always verifying your FC_INSTALL_DIR, even if you're only building for the ARM. Bummer. In your case, since you don't have (or need!) a valid FC installation, you can safely comment out the $(error ...) statement in xdcpaths.mak: --- ifeq ($(wildcard $(FC_INSTALL_DIR)/packages/ti/sdo/fc/dskt2/package.xdc),) #$(error FC_INSTALL_DIR is set to $(FC_INSTALL_DIR), which is invalid. Set this in codec engine examples/xdcpaths.mak! See the build documentation to correct this error.) endif --- As well as the assignment of MISC_PACKAGES to include $(FC_INSTALL_DIR)/packages at the very end: --- MISC_PACKAGES = $(XDAIS_INSTALL_DIR)/packages;$(DSPLINK_INSTALL_DIR)/packages;$(CMEM_INSTALL_DIR)/packages/;$(FC_INSTALL_DIR)/packages --- We'll fix this in a future CE release. Thanks for flagging this, and let me know if you have any other questions/issues. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ] On Behalf Of Beny Zhang Sent: Sunday, January 07, 2007 6:27 AM To: davinci-linux-open-source Cc: zwx304 Subject: Problems of buliding codec engine examples Hi All I have installed the DVEVM 1.10.00.30 software and now I am following the …./dvevm_1_10/codec_engine_1_02/examples/build_instructions.ht ml file to try to build the example. And I am confuse with below questions: 1 “The Build.targets array specifies which targets you want to build for. By default, the C64P, MVArm9, and Linux86 targets are enabled.” And I am using the DVEVM board with DM6446, but I want to treat the DSP-side as a black-box, so does it mean I should choose “MVArm9” here? Should I comment the “C64P” and “Linux86” in the user.bld file? And what is the exactly meaning of the “C64P” and the “MVArm9” here? 2 “Specify where your BIOS installation is: Uncomment the BIOS_INSTALL_DIR= line and specify the absolute path to your DSP/BIOS installation directory (Currently, DSP/BIOS is not available for ARM or x86, so this is only necessary when building DSP-side content).” I can’t find the BIOS_INSTALL_DIR at all, does it release with the DVEVM Software? And I can’t find the FC_INSTALL_DIR either. 3 As I can’t find the BIOS_INSTALL_DIR and FC_INSTALL_DIR, I think maybe I can do something without building DSP-side content. Then I modify the “REQUIRE_BIOS=0”, comment the “FC_INSTALL_DIR=…” in the xdcpaths.mak file. When I try to build example codec and change the …./dvevm_1_10/codec_engine_1_02/examples/codec dir and type gmake clean the shell tell me that the FC_INSTALL_DIR is wrong. So can I build the example codec running in the DVEVM board without building DSP-side content? How? And can I download the DSP/BIOS and FC from TI freely? Or I should pay for them? Thank you very much! Best Regards! Beny ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Issue regarding USB support
Do you compile without errors when you uncheck your USB options? (just to dismiss things like environment variables, links, and so on) Thanks, Carlos ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Issue regarding USB support
What is the version of DVEVM tools you are using 1.00,1.10,1.10.01 ? USB has been enabled in the kernel in the latest version. Once you upgrade you need to install everything including the GCC, target,lsp,codec servers. Thanks Harsha Hi there, I've been getting so many errors, while i'm trying to compile the montavista kernel with the USB support option. Can anyone please help me out with this. I'm listing the errors that i'm getting. [EMAIL PROTECTED] ti-davinci]$ make ARCH=arm CROSS_COMPILE=arm_v5t_le- uImage CHK include/linux/version.h CC arch/arm/kernel/asm-offsets.s In file included from include/asm/page.h:27, from include/asm/cpu-single.h:33, from include/asm/proc-fns.h:154, from include/asm/system.h:95, from include/asm/bitops.h:22, from include/linux/bitops.h:77, from include/linux/thread_info.h:20, from include/linux/spinlock.h:12, from include/linux/capability.h:45, from include/linux/sched.h:7, from arch/arm/kernel/asm-offsets.c:13: include/asm/glue.h:111:2: #error Unknown data abort handler type In file included from include/asm/cpu-single.h:33, from include/asm/proc-fns.h:154, from include/asm/system.h:95, from include/asm/bitops.h:22, from include/linux/bitops.h:77, from include/linux/thread_info.h:20, from include/linux/spinlock.h:12, from include/linux/capability.h:45, from include/linux/sched.h:7, from arch/arm/kernel/asm-offsets.c:13: include/asm/page.h:92:2: #error Unknown user operations model In file included from include/asm/semaphore.h:10, from include/linux/sched.h:18, from arch/arm/kernel/asm-offsets.c:13: include/linux/rwsem.h:38:65: asm/rwsem.h: No such file or directory In file included from include/asm/semaphore.h:10, from include/linux/sched.h:18, from arch/arm/kernel/asm-offsets.c:13: include/linux/rwsem.h: In function `compat_down_read': include/linux/rwsem.h:56: warning: implicit declaration of function `__down_read' include/linux/rwsem.h: In function `compat_down_read_trylock': include/linux/rwsem.h:67: warning: implicit declaration of function `__down_read_trylock' include/linux/rwsem.h: In function `compat_down_write': include/linux/rwsem.h:79: warning: implicit declaration of function `__down_write' include/linux/rwsem.h: In function `compat_down_write_trylock': include/linux/rwsem.h:90: warning: implicit declaration of function `__down_write_trylock' include/linux/rwsem.h: In function `compat_up_read': include/linux/rwsem.h:101: warning: implicit declaration of function `__up_read' include/linux/rwsem.h: In function `compat_up_write': include/linux/rwsem.h:111: warning: implicit declaration of function `__up_write' include/linux/rwsem.h: In function `compat_downgrade_write': include/linux/rwsem.h:121: warning: implicit declaration of function `__downgrade_write' include/linux/rwsem.h: In function `init_rwsem': include/linux/rwsem.h:132: warning: implicit declaration of function `compat_init_rwsem' In file included from arch/arm/kernel/asm-offsets.c:13: include/linux/sched.h: At top level: include/linux/sched.h:355: error: field `mmap_sem' has incomplete type In file included from include/linux/fs.h:213, from include/linux/mm.h:15, from arch/arm/kernel/asm-offsets.c:14: include/linux/kobject.h:151: error: field `rwsem' has incomplete type In file included from include/linux/fs.h:300, from include/linux/mm.h:15, from arch/arm/kernel/asm-offsets.c:14: include/linux/quota.h:288: error: field `dqptr_sem' has incomplete type In file included from include/linux/mm.h:15, from arch/arm/kernel/asm-offsets.c:14: include/linux/fs.h:453: error: field `i_alloc_sem' has incomplete type In file included from include/linux/mm.h:15, from arch/arm/kernel/asm-offsets.c:14: include/linux/fs.h:772: error: field `s_umount' has incomplete type make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 1 make: *** [arch/arm/kernel/asm-offsets.s] Error 2 ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: Re: RE: Problems of buliding codec engine examples
Zhang, It seems there is no simple way to change the memory map, because the DSP executable need a fix memory map, so when you changed your memory map you will rebuild all things related to DSP, such as dsp link, codec engine. you can following this link:http://www.mail-archive.com/[EMAIL PROTECTED] com/msg01238.html Thanks George Gu (Xiangyu Gu) Wintech Digital System Co. Beijing, China Ph: 8610-8278-2828 ext.168 Fax: 8610-8278-0028 http://www.wintechdigtal.com http://www.wintechdigtal.com/ _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Beny Zhang Sent: 2007年1月8日 17:15 To: Ring, Chris; davinci-linux-open-source Cc: zwx304 Subject: Fwd: Re: RE: Problems of buliding codec engine examples Hello,Chris Thanks for your kindly help. And now I have correctly build the examples of the codec engine. Before I run the examples I want to make clearly of this question: We know from TI that the DVEVM board should have 256MB DDR Memory, but the DVEVM board I boughth from Wintech(the dealer of TI in China) has only 64MB DDR Meomory on the board! Now, how can I set the memory map of the Davinci to run the exanples? Since the rules of setting the memory map is so complex in the build_instructions.html file. It is there any easy way to do this? Best Regards! Beny 1. If you _just_ want to rebuild the ARM-side examples, you can comment out C64P and Linux86 from the Build.targets array. What are these targets? * C64P == the DSP side of DaVinci target. It's one of TI's DSP processor families ( http://focus.ti.com/dsp/docs/dspplatformscontenttp.tsp?sectionId=2familyId =132tabId=489 http://focus.ti.com/dsp/docs/dspplatformscontenttp.tsp?sectionId=2familyId= 132tabId=489). * MVArm9 == MontaVista Arm 9 target. This is the ARM side of DaVinci. * Linux86 == Intel's x86 target. A not-always-understood detail about Codec Engine is that it can run natively on x86 processors. This feature's got some limitations (codecs must be local, and must not access hardware since they run in user mode), but you can do a fair amount of development on this environment. 2 3. As you correctly supposed, BIOS is only needed if you're building DSP-side content (same with FC - Framework Components). You should set REQUIRE_BIOS = 0. BUT... Looks like you've identified a bug in xdcpaths.mak where it's always verifying your FC_INSTALL_DIR, even if you're only building for the ARM. Bummer. In your case, since you don't have (or need!) a valid FC installation, you can safely comment out the $(error ...) statement in xdcpaths.mak: --- ifeq ($(wildcard $(FC_INSTALL_DIR)/packages/ti/sdo/fc/dskt2/package.xdc),) #$(error FC_INSTALL_DIR is set to $(FC_INSTALL_DIR), which is invalid. Set this in codec engine examples/xdcpaths.mak! See the build documentation to correct this error.) endif --- As well as the assignment of MISC_PACKAGES to include $(FC_INSTALL_DIR)/packages at the very end: --- MISC_PACKAGES = $(XDAIS_INSTALL_DIR)/packages;$(DSPLINK_INSTALL_DIR)/packages;$(CMEM_INSTALL _DIR)/packages/;$(FC_INSTALL_DIR)/packages --- We'll fix this in a future CE release. Thanks for flagging this, and let me know if you have any other questions/issues. Chris -Original Message- From: [EMAIL PROTECTED] [ mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] On Behalf Of Beny Zhang Sent: Sunday, January 07, 2007 6:27 AM To: davinci-linux-open-source Cc: zwx304 Subject: Problems of buliding codec engine examples Hi All I have installed the DVEVM 1.10.00.30 software and now I am following the …./dvevm_1_10/codec_engine_1_02/examples/build_instructions.ht ml file to try to build the example. And I am confuse with below questions: 1 “The Build.targets array specifies which targets you want to build for. By default, the C64P, MVArm9, and Linux86 targets are enabled.” And I am using the DVEVM board with DM6446, but I want to treat the DSP-side as a black-box, so does it mean I should choose “MVArm9” here? Should I comment the “C64P” and “Linux86” in the user.bld file? And what is the exactly meaning of the “C64P” and the “MVArm9” here? 2 “Specify where your BIOS installation is: Uncomment the BIOS_INSTALL_DIR= line and specify the absolute path to your DSP/BIOS installation directory (Currently, DSP/BIOS is not available for ARM or x86, so this is only necessary when building DSP-side content).” I can’t find the BIOS_INSTALL_DIR at all, does it release with the DVEVM Software? And I can’t find the FC_INSTALL_DIR either. 3 As I can’t find the BIOS_INSTALL_DIR and FC_INSTALL_DIR, I think maybe I can do something without building DSP-side content. Then I modify the “REQUIRE_BIOS=0”, comment the “FC_INSTALL_DIR=…” in the xdcpaths.mak file. When I try to build example codec and change the
Re: RE: Re: RE: Problems of buliding codec engine examples
Hello, George Thank you very much! I am confuse that why Wintech just use only 64MB DDR memory on the DVEVM board? As we know that the DDR memory isn't expensive at all now. As all the software pakages release withe the DVEVM are set to map the 256MB DDR, it will be very difficult for as to use the board with 64MB DDR memory! Thanks again and with my best wishes to you! Beny Zhang, It seems there is no simple way to change the memory map, because the DSP executable need a fix memory map, so when you changed your memory map you will rebuild all things related to DSP, such as dsp link, codec engine. you can following this link:http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg01238.html Thanks George Gu (Xiangyu Gu) Wintech Digital System Co. Beijing, China Ph: 8610-8278-2828 ext.168 Fax: 8610-8278-0028 http://www.wintechdigtal.com From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Beny Zhang Sent: 2007年1月8日 17:15 To: Ring, Chris; davinci-linux-open-source Cc: zwx304 Subject: Fwd: Re: RE: Problems of buliding codec engine examples Hello,Chris Thanks for your kindly help. And now I have correctly build the examples of the codec engine. Before I run the examples I want to make clearly of this question: We know from TI that the DVEVM board should have 256MB DDR Memory, but the DVEVM board I boughth from Wintech(the dealer of TI in China) has only 64MB DDR Meomory on the board! Now, how can I set the memory map of the Davinci to run the exanples? Since the rules of setting the memory map is so complex in the build_instructions.html file. It is there any easy way to do this? Best Regards! Beny 1. If you _just_ want to rebuild the ARM-side examples, you can comment out C64P and Linux86 from the Build.targets array. What are these targets? * C64P == the DSP side of DaVinci target. It's one of TI's DSP processor families (http://focus.ti.com/dsp/docs/dspplatformscontenttp.tsp?sectionId=2familyId=132tabId=489). * MVArm9 == MontaVista Arm 9 target. This is the ARM side of DaVinci. * Linux86 == Intel's x86 target. A not-always-understood detail about Codec Engine is that it can run natively on x86 processors. This feature's got some limitations (codecs must be local, and must not access hardware since they run in user mode), but you can do a fair amount of development on this environment. 2 3. As you correctly supposed, BIOS is only needed if you're building DSP-side content (same with FC - Framework Components). You should set REQUIRE_BIOS = 0. BUT... Looks like you've identified a bug in xdcpaths.mak where it's always verifying your FC_INSTALL_DIR, even if you're only building for the ARM. Bummer. In your case, since you don't have (or need!) a valid FC installation, you can safely comment out the $(error ...) statement in xdcpaths.mak: --- ifeq ($(wildcard $(FC_INSTALL_DIR)/packages/ti/sdo/fc/dskt2/package.xdc),) #$(error FC_INSTALL_DIR is set to $(FC_INSTALL_DIR), which is invalid. Set this in codec engine examples/xdcpaths.mak! See the build documentation to correct this error.) endif --- As well as the assignment of MISC_PACKAGES to include $(FC_INSTALL_DIR)/packages at the very end: --- MISC_PACKAGES = $(XDAIS_INSTALL_DIR)/packages;$(DSPLINK_INSTALL_DIR)/packages;$(CMEM_INSTALL_DIR)/packages/;$(FC_INSTALL_DIR)/packages --- We'll fix this in a future CE release. Thanks for flagging this, and let me know if you have any other questions/issues. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ] On Behalf Of Beny Zhang Sent: Sunday, January 07, 2007 6:27 AM To: davinci-linux-open-source Cc: zwx304 Subject: Problems of buliding codec engine examples Hi All I have installed the DVEVM 1.10.00.30 software and now I am following the …./dvevm_1_10/codec_engine_1_02/examples/build_instructions.ht ml file to try to build the example. And I am confuse with below questions: 1 “The Build.targets array specifies which targets you want to build for. By default, the C64P, MVArm9, and Linux86 targets are enabled.” And I am using the DVEVM board with DM6446, but I want to treat the DSP-side as a black-box, so does it mean I should choose “MVArm9” here? Should I comment the “C64P” and “Linux86” in the user.bld file? And what is the exactly meaning of the “C64P” and the “MVArm9” here? 2 “Specify where your BIOS installation is: Uncomment the BIOS_INSTALL_DIR= line and specify the absolute path to your DSP/BIOS installation directory (Currently, DSP/BIOS is not available for ARM or x86, so this is only necessary when building DSP-side content).” I can’t find the BIOS_INSTALL_DIR at all, does it release with the DVEVM Software? And I can’t find the FC_INSTALL_DIR either. 3
diskboot command in u-boot
Hi, Currently diskboot command is not supported in u-boot for davinci. I'll start to add this support. Any pointers in this regard will be helpful a lot Thanks __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Sources for DaVinci EVM Target Content
this error.) endif --- As well as the assignment of MISC_PACKAGES to include $(FC_INSTALL_DIR)/packages at the very end: --- MISC_PACKAGES = $(XDAIS_INSTALL_DIR)/packages;$(DSPLINK_INSTALL_DIR)/packages;$(CMEM_INSTALL_DIR)/packages/;$(FC_INSTALL_DIR)/packages --- We'll fix this in a future CE release. Thanks for flagging this, and let me know if you have any other questions/issues. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ] On Behalf Of Beny Zhang Sent: Sunday, January 07, 2007 6:27 AM To: davinci-linux-open-source Cc: zwx304 Subject: Problems of buliding codec engine examples Hi All I have installed the DVEVM 1.10.00.30 software and now I am following the ¡./dvevm_1_10/codec_engine_1_02/examples/build_instructions.ht ml file to try to build the example. And I am confuse with below questions: 1 ¡°The Build.targets array specifies which targets you want to build for. By default, the C64P, MVArm9, and Linux86 targets are enabled.¡± And I am using the DVEVM board with DM6446, but I want to treat the DSP-side as a black-box, so does it mean I should choose ¡°MVArm9¡± here? Should I comment the ¡°C64P¡± and ¡°Linux86¡± in the user.bld file? And what is the exactly meaning of the ¡°C64P¡± and the ¡°MVArm9¡± here? 2 ¡°Specify where your BIOS installation is: Uncomment the BIOS_INSTALL_DIR= line and specify the absolute path to your DSP/BIOS installation directory (Currently, DSP/BIOS is not available for ARM or x86, so this is only necessary when building DSP-side content).¡± I can¡¯t find the BIOS_INSTALL_DIR at all, does it release with the DVEVM Software? And I can¡¯t find the FC_INSTALL_DIR either. 3 As I can¡¯t find the BIOS_INSTALL_DIR and FC_INSTALL_DIR, I think maybe I can do something without building DSP-side content. Then I modify the ¡°REQUIRE_BIOS=0¡±, comment the ¡°FC_INSTALL_DIR=¡¡± in the xdcpaths.mak file. When I try to build example codec and change the ¡./dvevm_1_10/codec_engine_1_02/examples/codec dir and type gmake clean the shell tell me that the FC_INSTALL_DIR is wrong. So can I build the example codec running in the DVEVM board without building DSP-side content? How? And can I download the DSP/BIOS and FC from TI freely? Or I should pay for them? Thank you very much! Best Regards! Beny = = = = = = = = = = = = = = = = = = = = = = Ö Àñ£¡ Beny Zhang [EMAIL PROTECTED] ¡¡2007-01-08 -- next part -- An HTML attachment was scrubbed... URL: http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20070108/fc9fc402/attachment-0001.htm -- Message: 2 Date: Mon, 8 Jan 2007 03:36:36 -0800 (PST) From: Amol Lad [EMAIL PROTECTED] Subject: diskboot command in u-boot To: davinci-linux-open-source@linux.davincidsp.com Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ascii Hi, Currently diskboot command is not supported in u-boot for davinci. I'll start to add this support. Any pointers in this regard will be helpful a lot Thanks __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source End of Davinci-linux-open-source Digest, Vol 13, Issue 16 * __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Montavista forum anywhere?
I'm having issues with getting a simple build running correctly. Fear it is my system. Have a few questions Cheers, Lloyd ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
HAS ANYONE USED USB Keyboard with DaVinci EVM???
I'm having problems in compiling the kernel with the USb keyboard support options. If anyone has already used a keyboard with USB interface, kindly please help me out in compiling the kernel with the required support options. Regards, Akhil Kaushal P ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Davinci-linux-open-source Digest, Vol 13, Issue 16
As I know, wintech has released a modified version of the whole davinci software refered to 64M DDR2 memory. And the price for a single 128M DDR2 chip memory is relatively high. From: Beny Zhang [EMAIL PROTECTED] To: George Gu [EMAIL PROTECTED], 'Ring, Chris' [EMAIL PROTECTED], 'davinci-linux-open-source' davinci-linux-open-source@linux.davincidsp.com Date: Mon, 8 Jan 2007 18:49:32 +0800 Subject: Re: RE: Re: RE: Problems of buliding codec engine examples Hello, George Thank you very much! I am confuse that why Wintech just use only 64MB DDR memory on the DVEVM board? As we know that the DDR memory isn't expensive at all now. As all the software pakages release withe the DVEVM are set to map the 256MB DDR, it will be very difficult for as to use the board with 64MB DDR memory! Thanks again and with my best wishes to you! Beny -- blog site:blog.csdn.net/freasy ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
does the USB host driver support endpoint more than 4
spue35.pdf says the dm6446 usb controller Supports 4 simultaneous RX and TX endpoints, more can be supported by dynamically switching, Does the USB host driver support endpoint more than 4? -- blog site:blog.csdn.net/freasy ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
