Chris,
I've only went through this exercise on the DM64x products and
wrongfully assumed that it would still build the two libraries for the
DM3xx devices, even if it just finally linked them all together in the end.
Steve
On 07/06/2010 10:59 AM, Ring, Chris wrote:
DM355 doesn't include a DSP, and therefore has no Codec Server. The
Codecs are configured to run 'locally' on the ARM.
Chris
------------------------------------------------------------------------
*From:* [email protected]
[mailto:[email protected]]
*On Behalf Of *Todd Fischer
*Sent:* Tuesday, July 06, 2010 8:00 AM
*To:* [email protected]
*Cc:* [email protected];
dhineshkumar; Mohamed Thalib H; maharajan
*Subject:* Re: DM355 - 256MB RAM memory issue
Tharmarajan,
I believe you need to rebuild your codec server with a different
memory map. Another idea is to have a hole in the kernel memory
space (specify mem= in the kernel command line twice). I am not
sure if the kernel version you are using for dm355 supports a hole
in the kernel memory space.
Todd
On Mon, 2010-07-05 at 19:44 +0530, Tharmarajan Ganeshan wrote:
Hi All,
We are working on a DM355 processor based Development
board. The Board has 256MB mDDR RAM and 5MP image sensor MT9P031.
We are using the kernel version 2.6.10
We have modified the driver code for capturing 5MP
raw image and converting this 5MP raw into YUV. For this 5MP
image capturing , we have reserved 30MB.
We have allocated 56MB to the CMEM driver.
The reserved memory 30MB and the 56MB memory for
CMEM are at top of the RAM.
We are passing the remaining memory size to the
kernel in bootargs as mem=170M. And we are using the NFS
rootfilesystem.
But we are getting kernel hanging issues while
testing the IPNC_APP applications and 5MP still image capturing.
Sometimes the kernel is hanging while booting itself.
If we reserve the 30MB from the address region
0x83200000 - 0x84FFFFFF and pass the memory size to kernel in
bootargs as mem=50M, then we are NOT having any issues in running
the applications. But we want to use the exact remaining memory.
And also we are not able to program the NAND flash
memory in kernel level if we are not passing the mem=50M in bootargs.
What could be the cause for this kernel hanging issue ?
Are we missing any configurations while building the
kernel image ?
Our Bootargs is :
mem=50M console=ttyS1,115200n8 root=/dev/nfs rootwait rw
ip=192.168.1.90:192.168.1.99:192.168.1.1:255.255.255.0
nfsroot=192.168.1.99:/tftpboot/bellatrix_rootfilesystem,nolock
eth=00:0C:0C:A0:01:FE v4l2_video_capture=:device=MT9P031
Regards,
Tharmarajan G
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
<mailto:[email protected]>
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
