Thanks for the reply ...
DSP-side configuration mismatch/failure
0 - success
Positive value - DSP-side failure code.
(Uint32) -1- DSP-side component was not initialized.
DRV configuration status[0x0]
IPS configuration status[0x0]
POOL configuration status
You can rebuild DSP-side:
http://tiexpressdsp.com/wiki/index.php?title=Building_DSPLink
Regards,
Mugdha
From: Deepak Mundra [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 11:38 AM
To: Kamoolkar, Mugdha
Cc:
Looping in open-source list again ...
Deepak,
This is not a problem.
http://tiexpressdsp.com/wiki/index.php?title=DSPLink_FAQs#Why_am_I_getting_a_struct_module_warning_when_inserting_the_DSPLink_kernel_module_on_Linux.3F
Regards,
Mugdha
From: Deepak Mundra
Hi this code is to print hello world ..
= Hello Test ==
Entered Hello_Create()
PROC_Setup successful
PROC_Attach successful
PROC_Load successful
I don't think the issue will be with POOL enabling. It's likelier to be that
POOL instance was not configured on DSP-side. You can refer to DSP/BIOS
documentation for how to configure POOLs, or refer to one of DSPLink sample
applications for how this is done.
Regards,
Mugdha
Hi,
How to convert the other format video file into the mpeg-4 format what can be
decode on DM355? What tool can do it? Thanks.
Best Regards,
Jeff
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
Hi .. As mentioned in the site .. i compiled both dsp and gpp side .. and
copied hellogpp and hello.out to board and also
dsplink/gpp/export/BIN/Linux/Davinci/RELEASE/dsplinkk.ko Using
loadmodules.sh inserted and ran ./hellogpp hello.out .. but as i
mentioned in another mail .. im getting error
Deepak,
Please look through DSP/BIOS documentation on POOL module to see how POOL
instances must be created in BIOS. Also, you can use DSPLink sample
applications as reference:
E.g.: /dsplink/dsp/src/samples/message/message_config.c
static POOL_Obj pools [NUM_POOLS] =
{
{
Hi thanks for the reply
enabled only proc and in hello.c file i have set
#define NUM_ARGS 0 and using in PROC_Load as bellow
44if (DSP_SUCCEEDED(status)) {
45 status = PROC_Load(ID_PROCESSOR, dspExecutable, NUM_ARGS, NULL);
46 if (DSP_FAILED (status)) {
47
* So to fix that you need to convert your gray scale to YUV format
- and thats simple since gray scale is just the Y component, and you
would just fill zeros into the UV. Then you feed that transformed image
to the codec and your output is all compressed for you.
AFAIR it's fill in 128
Deepak,
The first scenario seems valid. But DSP_ENOTFOUND error from PROC_start
indicates that DSPLink is not able to find a symbol it was looking for. Have
you linked in the re-built (in PROC-only mode) dsplink.lib on DSP-side? Also,
which version of DSPLink is this?
The second scenario
Hi
dsp link version is dsplink_140-05p1..
The steps which i followed was
1] cd dsplink/etc/host/scripts/Linux
./dsplinkcfg
The selected configuration is:
GPP OS = Linux
DSP OS = DspBios
GPPDISTRIBUTION= davinci_mvlpro4.0
GPPOSVERSION = 2.6
Setting CE_DEBUG=2 (or 3) will provide more details. Turning on trace is the
right way to start.
CMEM provides memory for the algorithm - there are some CMEM-related debugging
techniques documented here:
http://wiki.davincidsp.com/index.php?title=CMEM_Overview
Chris
Yes you are right, I forgot about the shift for UV...
Arie Muijnck wrote:
Ø So to fix that you need to convert your gray scale to YUV
format - and thats simple since gray scale is just the Y component,
_and you would just fill *zeros* into the UV_. Then you feed that
transformed image
I don't think I've ever seen a CMEM allocation problem hang a codec
before. Unless of course you feed the encoder with a bad address - but
that is sort of self inflicted pain ;)
I assume that either one of the codec's run individually - but it's the
combination that hangs?
Steve
Ring,
I have done something pretty similar. I am currently encoding the video
using MPEG4 and on command snapping a JPEG still. Not quite MJPEG but on the
frames that I am snapping the JPEG still it is executing both algorithms on
the same frame.
As previously stated, if you have one of the buffers
Hi,
This error comes when provided line offset is not correct as per the detected
mode. Please go through the VPIF capture user guide to get to know how to
configure line offset.
Thanks,
Brijesh Jadav
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
17 matches
Mail list logo
