Hi,
I am working on DaVinci6446 platform.
In my application I am using DSPLINK (Version 1.40) for ARM DSP communication.
For communication I am using only DSPLINK not other modules like Codec
Engine, CMEM etc.
With default memory map configuration its working fine.
To optimize the memory
Hi,
I'm trying the DVFlasher_1_14 with the custom designed board with 32MB NOR
Flash (Intel) and 128MB RAM.
I know the UBL is hardcoded to run on boards with 256MB RAM, so i changed nor.h
accordingly
#define MAX_IMAGE_SIZE (0x0100) //org:(0x0200)
#define
Hi,
I really need to see the exact error here
Did you also update the kernel source?
I don't understand how updating the DVSDK affects the kernel build - the two
are independant.
You should have the following files (these are the Apr 15 updates)
dvsdk_setuplinux_1_30_00_40.bin
Also check firewall SELinux settings on the NFS server.
If possible try NFS mounting the root filesystem to another Linux box on your
network to confirm operation.
I also noticed your default route is garbage (255.255.255.255). This is because
you did not specify the ip= parameter correctly.
Hi, all.
I download dvevm 1.30 from TI site and am glad to see that
montavista is upgraded to 4.0.1.
But when I try
# /mv_pro_4.0.1/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc
--version
only to find that its version is 3.4.3 while anyone would expect it
should be 4.0.1.
What could
Hi,
I thought the 4.0.1 referred to MV pro version not the version of gcc.
Regards
Phil Q
Phil Quiney, Senior Software Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T: +44(0)1223-435536
F: +44(0)1223-435560
www.trinityconvergence.com
-Original
Thanks, Phil Q.
But I check the gcc version in mv 3.4.3, its version is 3.4.3 too.
So, I thought new version of mv should provides 4.0.1 gcc.
On Mon, 2008-06-16 at 09:44 +0100, Phil Quiney wrote:
Hi,
I thought the 4.0.1 referred to MV pro version not the version of gcc.
Regards
Phil Q
Hi,
i'm wondering if initrd could be loaded through serial port, as vmlinuz
does, at boot time.
Or, in alternative, tell the usart loaded kernel, to load itself another
executable (elf) through serial port.
I want this to make a more simple testrescue program for our board.
(talking with
And what can be the new of MV4.0.1 comparing to MV3.4.3?
Thanks.
On Mon, 2008-06-16 at 09:44 +0100, Phil Quiney wrote:
Hi,
I thought the 4.0.1 referred to MV pro version not the version of gcc.
Regards
Phil Q
Phil Quiney, Senior Software Engineer
Trinity Convergence
Cambridge
I had a similar problem, to fix it I had to mknod a console. This had to
be done as part of the boot as I could not log on!
Apologies if my terminology is not quite right - I am new to this, but
here goes
in /etc/inittab, I already had the lines
===
# This
I have read the Understanding the Davinci Resizer,and download the
sprc381.gz sprc382.gz. The sprc381.gz is project code.
My question is how can i use the project code in linux. And where can i
download the resizer_zoom.c's source code?
Your help would be much appreciated.
I suggest you study the MontaVista web page
http://www.mvista.com/product_features_pro.php to find out.
Regards
Phil Q
Phil Quiney, Senior Software Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T: +44(0)1223-435536
F: +44(0)1223-435560
Hi,
When we moved to the new dm355 v1.3 that is on the TI website, we needed to add
a link -
cd ~/workdir/lsp/ti-davinci/include/asm
ln -s arch-davinci arch
then all compiled ok. I don't remember doing this with the version that came
on the dm355 evm disks.
Hope this helps,
Bob
-
Hi,
Ideally, these sym-links would be created by the kernel build procedure.
At the ~/workdir/lsp/ti-davinci directory, if you execute the following
commands �C “make davinci_dm355_evm_defconfig” and “make uImage”, you will see
include/asm and include/asm/arch sym-links created to the right
Hi,
Unfortunately this did not fix the problem.
I investigated it a little further by sending some text to /dev/console from my
remote shell:
cat /proc/interrupts | grep serial
40: 36 AINTC serial
echo hello /dev/console
cat /proc/interrupts | grep serial
40: 36
Hi,
On the latest release, the link does not get created. We have 2 development
setups, happened on both.
We are using RedHat Enterprise v5 Client.
Regards,
Bob
_
From: Narnakaje, Snehaprabha [mailto:[EMAIL PROTECTED]
Sent: Monday, June 16, 2008 10:35 AM
To: Robert
This assertion is produced when VISA_freeMsg() is called more times than
VISA_allocMsg(). These APIs are used by the VISA codec class
'process()' and 'control()' functions, as well as asynchronous SPIs
'processAsync()' [calls VISA_allocMsg()]and 'processWait()' [calls
VISA_freeMsg()].
It's
If you're a codec _producer_, there are details about these files in the
Algorithm Creator User's Guide: http://www-s.ti.com/sc/techlit/sprued6
You can also use the Codec Packaging Wizard to automate generation of
these files in many cases:
Hi,
While running the Decode demo proramme I am finding the ARM and DSP CPU load
being shown on the OSD. I want to know, how the ARM CPU laod is calculateed for
DVEVM.
Can you tell me about this or point to any documents.
THANKS
MANAS KUMAR
From Chandigarh to Chennai - find friends
Manas,You can use the functions Cpu_getLoad() and Engine_getCpuLoad() to find
the CPU load for ARM and DSP side respectively. Regards,YogeshOn Mon, 16 Jun
2008 23:33:37 +0530 (IST) [EMAIL PROTECTED] wroteHi,While running the Decode
demo proramme I am finding the ARM and DSP CPU load being shown
Thanks A lot for the Reply,
But can you tell me how Cpu_getLoad() and Engine_getCpuLoad() operates to
calculate the load.
--- On Tue, 17/6/08, Yogesh Gupta [EMAIL PROTECTED] wrote:
From: Yogesh Gupta [EMAIL PROTECTED]
Subject: Re :Can Anybody tell me how the ARM CPU load is calculated for
21 matches
Mail list logo