Ryan,
I'd recommend looking inside the generated linker command file contributions
file (package/cfg/xavsc_ateme_server_x64P.xdl) and searching for 'DDR'. This
will tell you which contributing package(s) (likely a codec) reference 'DDR',
and you'll see something like this just above the
]
Sent: 12 February 2009 21:30
To: Monk, Roger; David Chan
Cc: davinci-linux-open-source@linux.davincidsp.com
Subject: RE: Dsplink.dsp?
I opened my linker command file
(package/cfg/xavsc_ateme_server_x64Pcfg.cmd) and added:
_DDR2 = DDR;
Under the OBJECT ALIASES section. That seems to have done
Hi Steve,
What target - DM6446?
What version of Codec Engine?
What version of the AAC encoder?
What params are you passing to _create call?
What dynamicParams are you configuring in _control()?
What args are you passing to _process()?
Cheers,
~Roger
-Original Message-
From: [EMAIL
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Hi folks,
Looks like we're got an issue with external folks posting to the list. We're
working this issue and hope to resolve soon.
Thanks for the test response messages.
Cheers,
~Roger
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Monk
Which version of CE and DSPLINK are you using?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ashuaria Lee
Sent: 10 June 2008 12:34
To: Davinci-linux-open-source@linux.davincidsp.com
Subject: Unclean CODEC engine shutdown.
Hi,
I wonder how you're
John - what's the issue - think the mail list might have stripped the
attachment?
~rog
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John J
Sent: 08 June 2008 10:20
To: davinci-linux-open-source@linux.davincidsp.com
Subject: Codec engine problem
Hi,
Really, for codec engine usage/consumption - you should use a RTSC package
which includes the library - it's not safe to mix and match packages/libraries
- the package is tightly coupled to the library and contains additional
information required in order to integrate the algorithm into
David,
It would be good to understand the issues you are facing better - if
possible, since building with CE 2.0.1 should make life a lot easier
than it seems to have done for you. Sorry you've not had a good
experience so far.
Couple of comments (which you may already know, but thought worth
Forwarding for archive :-
Thanks Vasiliev - glad working ok now.
Cheers,
~roger
-Original Message-
From: Alexander Vasiliev [mailto:[EMAIL PROTECTED]
Sent: 24 January 2008 15:10
To: Monk, Roger
Subject: Re: DMA transfer from ARM RAM
Thank you, Roger.
Now it works well.
2008/1/24, Monk
Hi Virginia,
A couple of notes here :-
- At RTSC program configuration time, all packages that are part of an
application (e.g. OS, CodecEngine, FrameworkComponents, Codecs, etc) are given
the opportunity to contribute a set of libraries (via getLibs) and some
corresponding linker command
Hi Vivin, this sounds excellent - and is good to hear - can you please provide
some more details on the edma issues you faced? - maybe someone on the list has
some ideas for more 'favourable' operation techniques? + it would be useful on
ti side to understand the issues for next generation
Hi Anton,
I've just tried this and seems to work ok for me. I made exactly the
modifications you detailed below to viddec_copy.c, adding 2 additional
memTab entries to algAlloc. I then built this into the all_codecs
server and video_copy server and tested both with video_copy/dualcpu
Hi Darren,
A couple of quick pointers.
If you are using a DVEVMv1.1 installation and the accompanying dsplink,
then your dsplink base sources will be installed in the following path
:-
'DVEVM_INSTALL_DIR'/dsplink_1_30_08_02/packages/dsplink
[where 'DVEVM_INSTALL_DIR' is expanded to you real
Hi Avishai,
This warning is showing you the problem I believe. This means that
there is a section in your library (.tables) that is not being placed
explicitly in memory via the linker command file. When it is not
placed, it will be allocated into the first memory area found, which may
not
Steve - some more questions to help us track this down :-
Is this on standard evm or custom hardware?
Which version of Uboot are you using? - Is it the latest from the ti
extranet?
Which version of linux kernel? - the one that comes with dvevm v1.10?
Does reboot work successfully from NOR
Hi Daniel,
This sounds like you may be hitting errata 1.3.24 (detailed in
http://focus.ti.com/lit/er/sprz241e/sprz241e.pdf) - this relates to potential
errors when multiple masters access ARM DTCM internal memory concurrently. -
i.e. in your case, ARM and EDMA.
~roger
George,
Have you double checked SW3-4 = ON?
~roger
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of George Gu
Sent: 29 November 2006 01:49
To: Ring, Chris; davinci-linux-open-source@linux.davincidsp.com
Subject: RE: RE: Use small size
Hi Santhosh,
Some thoughts..
- Do other codec engine apps work ok?
- Have you checked the SW3-4 switch to make sure it's in the 'ON'
position?
- error 0x80008013 means 'parameter out of range' - is your application
using the same memory map as other codec engine examples that are
working
Hi Sameer,
A good first check is that you are setting
Base Profile and using Level 3.0 (not level 3.1).
~roger
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of snaik er
Sent: 01 November 2006 05:40
To:
davinci-linux-open-source@linux.davincidsp.com
Subject:
Did you check that SW3-4 is in the on position?
Is the decode only demo working ok?
~roger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Alan Li
Sent: 28 September 2006 23:21
To: davinci-linux-open-source@linux.davincidsp.com
Subject: DVEVM 1.10
21 matches
Mail list logo
