Hi, all
Copying the script code to
dsplink/dsp/src/samples/loop/DspBios/Davinci/loop.tcf seems not to be work. The
script is as below.
bios.PRD.create(PRD0);
bios.PRD.instance(PRD0).order = 1;
bios.PRD.instance(PRD0).fxn = prog.extern(dotest, asm);
bios.PRD.instance(PRD0).period = 16;
Is there
Hi,
I've looking for an option of progamming NAND flash
for davinci based boards using external programmer.
The trouble I'm facing is the davinci hardware ECC
generation. It's obvious that we cannot have the
external programmer to generate the NAND ECC for the
binaries it is flashing to NAND as
Hello,
Recently I purchased the DM6446 evaluation board. I was trying to run the
gtk-demo program installed on the board and it did not work. So I tried to
compile gtk+ my self but this time to use direct framebuffer. When I run the
new gtk-demo, it works but the output is aliased as if there
Hi everybody,
I am using the TI evaluation JPEG codec and having a problem when i try to
encode.
The app code is an encode demo modified. Actually, the first frame encoded
by jpegenc is correct but after that all frames encoded are only 14 bytes in
size. Frames in input are corrects.
It appears
Hi all,
I am having a problem finding where is made the configuration of the chip
msp430 (responsible for IR comands and son on).
Is this made on the kernel or there is a process after booting that performs
the configuration of this chip?
Does anyone tried to disable this chip?
Best regards and
hi
the chip hs its internal flash and it is fully autonomous
What are u trying to do?
Albert
On 4/14/08, António Silva [EMAIL PROTECTED] wrote:
Hi all,
I am having a problem finding where is made the configuration of the chip
msp430 (responsible for IR comands and son on).
Is this made on
All,
I am having a problem building the demos for the DM355. When i try
to build the demo I receive the following error. Any thoughts? Thank you
in advance.
Linking debug/encodedecoded from debug/capture.o debug/ctrl.o
debug/display.o debug/main.o debug/ui.o debug/video1.o..
Mark,
You need to do a 'make clean' or equivalent, your build is attempting to
link in a pre-compiled config file.
Regards,
- Rob
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
] On Behalf Of Mark Keramaty
Sent: Monday, April 14, 2008 12:50 PM
To:
On Mon, 2008-04-14 at 12:16 +0800, steven.zhang wrote:
I am porting a driver supported by TI to kernel 2.6.23. But
unfortunate get a compile error. It should be easy to fix, thought I
would rather to see the best way.
The problem code is :
dev_dbg(rsz_device, __FUNCTION__ L\n);
Try this:
dev_dbg(rsz_device, %s\n, __FUNCTION__);
It seems that starting in gcc 3.2, __FUNCTION__ is treated the same
way as __func__, which is a variable, not a string literal, so it
cannot be used in string catenation.
// pseudo-definition of __func__
static const char __func__[]
Hello Xperts,
1)
KIndly comment on the following mentioned error's from the TI processor. How
do i analyse or understand the cause ?
Error's:
a) VIDDEC_process() failed with a fatal error (-1 ext: 0x81d)
b) VIDDEC_process() failed with a fatal error (-1 ext: 0x201e)
2)
1. Codec datasheets/users guides should contain the codec-specific
extended error codes. (Unfortunately, the extended error codes vary
from codec to codec, so you'll have to consult the codec docs)
3. Which version of Codec Engine? If a recent release (2.00 or later),
you can set a CE_DEBUG
Hello Xperts,
1)
KIndly comment on the following mentioned error's from the TI processor.
How do i analyse or understand the cause ?
Error's:
a) VIDDEC_process() failed with a fatal error (-1 ext: 0x81d)
b) VIDDEC_process() failed with a fatal error (-1 ext:
Hi Daniel,
I've made changes to dvflasher_1_14_080121 and added
support for factory marked bad blocks. Below are the
salient features
- Skip Factory marked Bad block during -enand
operation. Also skip such blocks during writing
ubl/u-boot. This is achieved by creating a BBT and
using this as a
14 matches
Mail list logo
