________________________________
From: Tharmarajan Ganeshan [mailto:tha...@e-consystems.com]
Sent: Wednesday, July 14, 2010 8:17 AM
To: Tivy, Robert
Cc: davinci-linux-open-source@linux.davincidsp.com; maharajan; dhineshkumar
Subject: RE: DM355 - 256MB RAM memory issue
Hi Robert,
I have built the cmemk.ko by running the command 'make debug'.
But I could not find any extra messages while loading this
cmemk driver.
Here I have attached two log files when mem=50M and mem=168M
to the kernel. CMEM is reserved with 88M.
Regards,
Tharmarajan G
I don't know why you suspect CMEM here. Both your logs show CMEM being loaded
properly - from your "50M" log:
cmemk: no version for "struct_module" found: kernel tainted.
ioremap_nocache(0x89800000, 109051904)=0xc3880000
allocated heap buffer 0xc3880000 of size 0x3204000
cmem initialized 14 pools between 0x89800000 and 0x90000000
The kernel "panics" don't show any CMEM-related function either.
But you do seem to have other problems, here's just a sample of some from your
50M log:
insmod: cannot insert `dm350mmap.ko': Bad address (-1): Bad address
BusyBox v1.01 (2005.12.18-04:57+0000) multi-call binary
Usage: mknod [OPTIONS] NAME TYPE MAJOR MINOR
Create a special file (block, character, or pipe).
Options:
- m create the special file using the specified mode (default a=rw)
TYPEs include:
b: Make a block (buffered) device.
c or u: Make a character (un-buffered) device.
p: Make a named pipe. MAJOR and MINOR are ignored for named pipes.
insmod: cannot insert `sbull.ko': Bad address (-1): Bad address
insmod: cannot insert `musb_hdrc.ko': Bad address (-1): Bad address
I don't know anything about those problems, I was just seeing if I could help
with what I do know about - CMEM - but I don't see any problems related to CMEM
in your logs.
Regards,
- Rob
On Mon, 2010-07-12 at 16:32 -0500, Tivy, Robert wrote:
________________________________
From: davinci-linux-open-source-boun...@linux.davincidsp.com
[mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of
Tharmarajan Ganeshan
Sent: Saturday, July 10, 2010 8:35 AM
To: todd.fisc...@ridgerun.com; Ring, Chris
Cc: davinci-linux-open-source@linux.davincidsp.com; dhineshkumar; Mohamed
Thalib H; maharajan
Subject: Re: DM355 - 256MB RAM memory issue
Hi Todd and Chris,
Thank for your suggestion. We tried the option 'hole in the
kernel memory space'. But that is not solving our issue.
We tried to reserve memory 30MB at various place in RAM. But
these trials does not help us to solve this issue.
And also we tried to get the memory for this 5MP image
capturing from the CMEM driver. For this we allocated 86MB to CMEM driver. But
the kernel is hanging while loading this CMEM driver.
Is there any limitation in CMEM driver ?
As far as we know there is no limitation on the size of the physical block
granted to CMEM.
If you'd like to pursue this approach (getting your 5MP image memory from CMEM)
then I could help, but would need to see the debug output of the CMEMK kernel
module that you say is "hanging while loading this CMEM driver." To produce
debug output, build the "debug" version by:
% cd <linuxutils>/ti/sdo/linuxutils/cmem/src/module
% make debug
Then 'insmod' this cmemk.ko and observe CMEMK debug output on the Linux console.
Regards,
- Rob
Regards,
Tharmarajan G
On Tue, 2010-07-06 at 09:00 -0600, Todd Fischer wrote:
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
Davinci-linux-open-source@linux.davincidsp.com<mailto:Davinci-linux-open-source@linux.davincidsp.com>
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
