RE: DSP Server debugging on CCS3.2

Hi Tom, Fyi, below is some information on ways to debug a prebuilt DSP server using CCS. Debugging the DSP in CCS in a CE application Procedures == There are two common scenarios when debugging the DSP that require slightly different

RE: RE: RE: Use small size memory issue!

George, Did you check to see if you have enough heap space available for the h264 decoder? The DDRALGHEAP section in the .tcf file must be at least large enough to fit the algorithm’s external memory requirement. You can try comparing the info in the decoder’s data sheet with the section

RE: RE: how to make use of performanceof the davinci's dsp

Hi Qi, There are a couple of things you need to do: 1. Update the file \dsplink\config\all\CFG_Davinci.TXT in dsplink to map the memory area that you wish to load into by adding a memory entry. Make sure you add 1 to MEMENTRIES. This informs the dsplink loader of this memory region at load

RE: Linking/mapping data to IRAM or L1SDRAM on the DSP

Hi Andy, See comments below... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Ngo Sent: Wednesday, January 24, 2007 3:31 PM To: davinci-linux-open-source Subject: Linking/mapping data to IRAM or L1SDRAM on the DSP Hi all,

RE: cache alignment error!!!

Hi Varsha, How are you allocating the input and output buffers that are passed to your video encoder's process call? Make sure you are using contiguous buffers allocated by CMEM by calling Memory_contigAlloc() - suggest you look at how that's done in the original encode demo. The memory managed

RE: codecs?

I assume that you are trying to run the video_copy codecs on the DSP. Unfortunately, it is not possible to use two engines simultaneously if they use different server images. Opening an engine implicitly loads the DSP with the server image required by the engine if it is not already loaded, and

RE: Changing Memory Map for Codec Engine Applications

Hi Tom, We are in the process of productizing that doc into an app note. If you or others have any input on the topic, we'd be happy to hear. Best regards, Vincent -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of T Ziomek Sent: Tuesday, February 20,

RE: booting linux AND accessing DSP

Hi Robert, This page may help if you are debugging a Codec-Engine-based application: http://wiki.davincidsp.com/index.php?title=Debugging_the_DSP_side_of_a_C E_application_on_DaVinci_using_CCS Best regards, Vincent -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On

RE: Copts in Package.bld in codecs

Hi Josh, Which codec engine or dvsdk example are you trying to build? Sounds like you might want to play with the profile setting in the package.bld file. For example, selecting a release profile will automatically insert -o2 to the compiler invocation. If you have both -o2 and -o3 for

RE: xDM vs xDAIS

Hi Asa, I'd suggest you take a look at the application note Spraae7b.pdf (http://focus.ti.com/general/docs/techdocsabstract.tsp?abstractName=spraae7b). You are not so much interested in the adapter concept introduced in this app note; however, the companion code does show an example

RE: Cannot build the DMAI with DVSDK 1_40_00_21 on DM6467.

Hi Omikiran, It seems to me you might not be using the latest Linux LSP. The latest one is versioned 1_03_00_070 and can be downloaded from the DVEVM update site: https://www-a.ti.com/extranet/cm/product/dvevmsw/dspswext/general/dm6467 _dvevm.shtml. Filename is

RE: building dsplink

Hi Brian, If you haven't already done so, I suggest you take a look at the example codec_engine_2_10_01\examples\ti\sdo\ce\examples\apps\video_copy\dualcpu_separateconfig_dll. It does something similar to what you are trying to accomplish, ie., wrap CE into a DLL. This might give you a clue as

RE: Opening several CE servers

Hi Asa, You cannot open/load multiple servers at the same time. However (not sure if this helps in your case), you can try the following: ceHandle_1 = Engine_open(engineName_1, NULL, NULL); codecHandle_1 = xxx_create(ceHandle_1,...); xxx_delete(ceHandle_1); Engine_close(engineName_1);