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);
ceHandl
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
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 mvl_4_0_1_demo_lsp_setuplinux_01_
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 algorith
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 t
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
B
Hi Ben,
To increase the size of the heap in "DDR" (or "DDR2" as renamed in the
more recent examples), you can add the following line to your BIOS .tcf
file if it does not already exists:
bios.DDR.heapSize = 0x1;
Set the size to a value larger than the amount of memory you are tryi
Hi Brian,
Does the codec uses DMA to fill the buffer? If it does, make sure it
adheres to the rules in XDAIS (e.g. the DMA and CPU cannot both
read/write from the same external memory buffer). The standard is
defined in this doc:
http://focus.ti.com/dsp/docs/dspsupporttechdocsc.tsp?sectionId=3&
, July 25, 2007 4:33 PM
To: Wan, Vincent
Cc: T Ziomek; davinci-linux
Subject: RE: Changing Memory Map for Codec Engine Applications
Cleaning out the emailbox...
Since so much time, has passed, here is the ref this is in reply to:
<http://linux.omap.com/pipermail/davinci-linux-open-source/200
Hi mafaqing,
>From the error, it looks like there might be some confusion regarding
g711 encoder and decoder. I believe there are two versions of G711 which
are supplied, one in codec_servers_1_00 and another one under the CE
examples in \examples\codecs\g711. I don't think the first one contai
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, 2007
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 the
y, January 25, 2007 2:16 PM
To: Wan, Vincent
Cc: davinci-linux-open-source
Subject: Re: Linking/mapping data to IRAM or L1SDRAM on the DSP
Hi Vincent,
Thanks for you help. I have another question that maybe you can help.
I want to add
a library (i.e. mylib.a) to the ARM application but I cou
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
by
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,
Thanks
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 tim
Hi Andy,
I suggest you look into buying the DVSDK, which should enable you to
develop on the DSP side. It is a great way to save you from the many
headaches of trying to gather a tested permutation of the various
software.
If you really wish to do this on your own, here is what's being used in
th
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 siz
ZhouXiao,
Some more info...
Since you are writing your own server and algorithm, you might be
interested in debugging these components on the DSP side. Fyi, I have
attached a recent thread that talks about this topic.
The VIDENC_create API sends a message to the DSP's RMS server task w
Title: Message
Hi XhouZiao,
See responses below…
Best regards,
Vincent
From: davinci-linux[EMAIL PROTECTED]
[mailto:davinci-linux[EMAIL PROTECTED]
On Behalf Of X. Zhou
Sent: Monday, November 06, 2006
5:23 AM
To: davinci-linux[EMAIL PROTECTED]
Subject: about memory map s
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 approac
21 matches
Mail list logo