Hi,
I am woking on TMS320DM6467 EVM board. I am trying to build my code using
montavista 4.0.1 tool chain.
But I am getting segmentation fault at last with the following message
collect 2: ld terminated with signal 11.
My code is getting compiled using montavista 4.0 tool chain. The decode
demo
I've seen signal 11 errors come from ld when the linker is asked to link
libs/objs that are incompatible. On one occasion, it was trying to link object
files built with incompatible EABI flags. On another occasion it was trying to
link an ARM object file with a DSP object file(!).
You might
This is a very newbie question but how do I modify the kernel or add an
initialization script etc so that when I turn on the dvevm it
automatically logins in and runs a program (i.e. so I don't keep on
having to use the serial interface to run the program). I'm sure this is
very obvious but I
Hi,
I trying to build the latest GIT tree (2.6.25-davinci1) with the Montavista
toolchain we bought from TI 2 years ago (MV Pro 4.0) and I'm getting the
following error:
make ARCH=arm CROSS_COMPILE=arm_v5t_le- uImage
CHK include/linux/version.h
make[1]: `include/asm-arm/mach-types.h' is up
Oops, nevermind, I saw someone posted the same problem and someone else
replied. Sorry for not reading first. I'm still interested in building a new
toolchain with glibc 2.5 though. Thanks.
Regards,
Andy
- Original Message
From: Andy Ngo [EMAIL PROTECTED]
To:
Hi,
U-boot, kernel and yaffs file system are in NAND Flash, and all of them are ok
, but there are some errors when running demos(encode and decode). The
information is as follows(test.264 is ok),
[EMAIL PROTECTED]:~/CODEC_server_demo# ./decode -v test.264
Decode Debug: PAL selected
Decode
Thanks for your answer
We have bought DVD player which is capabe to send 720p component. But I
think, we have an other problem, this demo is not starting. I have
downloaded a newer release of software for this board, recovered file
system, but I suppose there are some files missing. I am new
Hi,
First the good news - you don't need to modify the kernel ;-)
The easiest way of automating a program startup is to add the required command
into /etc/rc.d/rc.local.
This should be executed after all the runlevel scripts have been processed but
before the login. However on the MV LSP
Hi Guys,
I have been playing with the audio driver. All I want to do is a simple
loopthrough function, however, I am finding that the driver locks up
quite randomly when its file handles are being closed.
Has anyone else come up with this issue? I have attached the function I
am playing with, if
Andrew Armstrong,davinci-linux-open-source，你好
yes, that is not your problem, it is a soundcard driver bug.
[EMAIL PROTECTED]
2008-06-24
- Original Message -
From: Andrew Armstrong
To: davinci-linux-open-source
Sent: 2008-06-24, 17:41:19
Subject: Buggy Audio Driver
Hi Guys,
I have
Kevin,
Ack on both suggestions. My next patch should take care of the redundant
comments.
For the tick I was thinking of replacing the whole EMAC MDIO code with linux
mdio infrastructure. With that done the timer in the driver will not be
required. If I take too much time to get the MDIO
Hi,
I think your program is not helping by reading too small chunks.
You have not configured the speed of the device, the bits/sample number of
channels etc - so what format is it using by default???
Your read will block giving plenty of scope for the output under running as
well
General
Hi, nicholas,
I need to hook up a DVB (8 bit) tuner to the EMIF. Current thinking
is to write a module to trigger DMA transfer using a GPIO interrupt on
the 'Packet Ready' output of the tuner. Anyone have anything they can
point me at that might be similar to save some time?
Take a look
Hi Steve,
The following program may help you. It is a prlgram which will flash
the DM355 Flash through the RS232 port.
http://wiki.davincidsp.com/index.php?title=Serial_Boot_and_Flash_Loading
_Utility
Downloaded, thanks.
joking mode
Just for curiosity: but why ALL single files are
Do you have idea of what could be the problem?
What should I do to exploit it?
if it could helps that's the log of mono -v.
--
Andrea Gasparini
ImaVis S.r.l.
web: www.imavis.com
Waiting for the DM35x...
Method UtilLib.IO.SerialIO:waitForSequence
Greetings Andy,
Others may correct me if I'm wrong, but Montavista back ported various
aspects of later toolchain binaries and libraries into their 4.0.1 release.
We're switching over to the git kernel because of the kernel performance +
mmc nand drivers are solid.
I built with the MV 4.0.1
In all of the documentation for GStreamer, it requires the TMS320DM6446
SoC. Will the DM6443 also work? The biggest difference is lack of
encoding in the DM6443.
I am after a framework to DECODE video/audio using the DM6443 and this
project seems to be a good start. Ideas? Thoughts? Other
I think it should work but the best thing to do is try it :-)
Sincerely,
Chase Maupin
Software Applications
Catalog DSP Products
e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
phone: (281) 274-3285
From:
[EMAIL PROTECTED]
om
[mailto:[EMAIL
Hi,
I have the dm355 EVM with all the updated software downloaded from TI. I
have gone through the new getting started guide up to section 4.5, I
have run a simple 'hello world' program on the dm355. When I get to 4.5
I copy ti-davinci into my workdir/lsp and I see there is supposed to be
a
The .gz issue turned out to be a corrupted file loaded to the wiki. We are
working to replace it with a better file.
We have had one previous report that running the utility with a USB adaptor
causes this behavior; but we have not been able to duplicate it here. Our
testing has been done
Hi Phil,
Thank you for your comments. I am disappointed to say, that the sample code is
only one of several methods I have attempted to get working properly. I do
attempt to initialise the device prior to calling this function.
It is strange that our tests show the program hanging when trying
Thanks David. Do you know what are the differences between MV 4.0 and MV
4.0.1? We're still using MV 4.0 (dvevm 1.10, bios 5.30, cmem 1.01, CE 1.02,
dsplink 1.30.08.02, etc). I was able to build the latest GIT kernel using
using our current MV 4.0 development tools. Can I rebuild cmemk and
Andrew,
I spent many a day debugging the audio driver write lockup issue and to this
day, I still haven't figured it out. However, I did pinpoint the hanging
problem when closing the device to an audio_sync call in the audio_release
function in davinci-audio.c. Try this, comment out the call
Thanks, jp_liu. I will try that out. This is similarly to David Conrad's
initial breakthrough post a while back but it sounds promising. By the way, I
too am using the McASP as the master and not the AIC33 codec.
Regards,
Andy
- Original Message
From: jp_liu [EMAIL PROTECTED]
To:
Andy Ngo,Andrew Armstrong,PQuiney,davinci-linux-open-source,
yes, I changed it base david's version(btw, thanks david). the sound is bad
because commented out if (AUDIO_QUEUE_LAST(s)){ ... } in function
sound_dma_irq_handler().
but another issue is cannot set clock-rate to 8000 when using the
Hi all.
Can anyone please guide me to the volume control operations on the DaVinci's
DM6446??
Please do reply.
Thanks Regards,
Rubyna
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and
26 matches
Mail list logo
