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.html 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
### Davinci SBC Module?
Hi Folks, We have wrapped up our Davinci design and I was thinking of asking some folks here on the forum to gauge interest in a davinci SBC module Is there any interest in such a module? I was thinking something like a davinci + nand + ddr + etherent + usb + video in + video out The circuitry would be on something like a DDR memory stick footprint so you could easily make a mother board to then use the Davinci in a product. Any ideas? Thanks Steve Spano FLE ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: ***SPAM*** Score/Req: 09.40/05.00 - Fwd: Is Code Engine necessary
Hi, It is possible to do that, you can refer the doc and examples in TI BIOS LINK. 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] .com] On Behalf Of [EMAIL PROTECTED] Sent: 2007年1月7日 21:55 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; davinci-linux-open-source@linux.davincidsp.com Subject: ***SPAM*** Score/Req: 09.40/05.00 - Fwd: 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 interface, so that you will only need to implement the functions in the xDM interface and then use the speech encoder and decoder examples to build the package. You may also consider registering for the 4-day DaVinci workshop. Over the course of 4 days, this workshop takes you through building an audio/video application starting with the Linux drivers and then building in progressively more of the Codec Engine until you are building a custom server. It is a great overview for someone just staring with DaVinci. For more info: http://focus.ti.com/docs/training/catalog/events/event.jhtml?sku=4DW1026 44 Regards, Steve Preissig Texas Instruments Technical Training Organization 9260 Waits Ferry Crossing Duluth, GA 30097 [EMAIL PROTECTED] (770) 840-0783 ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Question about DVEVM software
Hi everyone, I has a question. I want to boot the box and setup u-boot to use the hard disk (/dev/hda1) as its root file system. Then can run our new demo application. (not download files from ftp://128.247.27.36/sanbdavinci/1_00_00_32/restore/, is our moditfy/rebuilding DVEVM software for target) could someone give me a hint? Best regards, Garris,Lin ___ 您的生活即時通 － 溝通、娛樂、生活、工作一次搞定！ http://messenger.yahoo.com.tw/___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: Sample AIC33 loopback test
Hello All, Wanted to enquire if this is also true for OMAP2430 processors. I have a OMAP2430 SDP and we are trying to build a custom board with SDP as reference. We wanted to have the Audio Codec AIC31B's I2S (data channel ) interface driver on the DSP core side, and the AIC31B's I2C ( control channel ) on the ARM core side. Warm Regards, Raghu. On 1/5/07, Andy Ngo [EMAIL PROTECTED] wrote: Hi All, FYI, I got my answer from TI yesterday: -- Andy, Thank you for the inquiry to TI. The Service Request #x-xx has been assigned to your inquiry. Please refer to this number for any other questions regarding this inquiry. After checking around I am fairly certain that we have no audio examples available that run solely on the DSP core. Part of the reason for this is that the design around DaVinci was to put all of the I/O onto the ARM core to offload it from the DSP. As you can see this is the direct opposite approach you were trying to take. With most of our other DSP devices we included some sort of Chip Support Library (CSL) which was an API used to control the peripherals. The DM6446 lacks this as once again everything is controlled in the Linux world through the Linux drivers. I did verify that what you are trying to do is physically possible (the DSP can access the ASP without going through the ARM) but unfortunately it looks like you would be on your own as far as creating a driver to do so. I apologize for the inconvenience, but hopefully this approach will still at least work out for you. I hope this helps, but please let me know if I can be of further assistance. Best Regards, Tim Harron -- I guess for now, I will have to do audio processing on the ARM side and only offload encoding/decoding responsibility to the DSP side. Regards, Andy ___ 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
When i'm trying to compile the kernel with the new configuration, it's showing so many errors. I didn't have errors. Please, post the errors you have. Regards, 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: Problems of buliding codec engine examples
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=2fami lyId=132tabId=489 http://focus.ti.com/dsp/docs/dspplatformscontenttp.tsp?sectionId=2fami lyId=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_INS TALL_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 /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: ***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
