Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Good day everyone,
I am using Overo Water COM which has a 512M and would like to unsure if
setting my bootargs environment like this is ok:
" setenv bootargs "console=ttyS2,115200n8 mpurate=720 vram=12M
mem=96M@... mem=384M@... omapfb.mode=dvi:1024x768MR-16@...
omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait" "
The next question is how to allocate the Kernel and CMEM memory using the
"pools=1x????? phys_start=0x???? and phys_end=0x???" such that it will tell
the cmem on where to start and stop!
I came across this example from
0xC0000000 - 0xC4FFFFFF for kernel (80M)
0xC5000000 - 0xC5FFFFFF for cmem, (16M)
In this case, bootargs was mem=80M for kernel and in cmem,
I am trying to implement this method instead of running mmcargs "Overo #
run mmcargs" in order to avoid the Kernel mismatched version problem since
I am using kernel 3.2.0 and wouldn't like to go for kernel 2.6.34
Thanks in advance,
>From stuff that I have done--it depends on the module. If you are building
dsp modules with bitbake Cmem has to be initialized slightly different. For
example Dmai uses 0x8500000 to 0x86000000 while C6Accel or C6Run have
slightly different memory. Use TI Wiki for more information on CMEM and
If you don't initialize pools when you do it normally you will get an error
saying that the function expected a certain size buffer so then you could
just go and reset cmem with the a new pool variable with that buffer.
i'd read this too:
here is a dmai -example:
root@...:/home/DSP/GUMSTIX-Build-Directory/cmem# insmod cmemk.ko
85000000 phys_end=0x86000000 pools=20x4096,10x131072,2x1048576
CMEMK module: built on May 4 2012 at 19:50:51
Reference Linux version 2.6.34
CMEM Range Overlaps Kernel Physical - allowing overlap
CMEM phys_start (0x85000000) overlaps kernel (0x80000000 -> 0x8d000000)
allocated heap buffer 0xd1000000 of size 0xcac000
_omap3530.x470MV -c jpegdec -i
ics/fruitbasket.uyvy | tee log.txt
@0,704,651us: [+6 T:0x40022250] CE - Engine_init> CE debugging on
(CE_DEBUG=1; allowed CE_DEBUG levels: 1=min, 2=good, 3=max)
[DSP] @0x00000193:[T:0x00000000] codec_unitserver - main> Welcome to
CS1OMAP3530 DSP server's main().
Wrote UYVY frame size 202752 (352x288) to disk
End of application.
I'd start using TI alot more if you run into issues and look through TI e2e
View this message in context: http://gumstix.8.n6.nabble.com/Appropriate-pools-phys-start-and-phys-end-parameters-to-load-the-cmemk-ko-module-tp4964524p4964525.html
Sent from the Gumstix mailing list archive at Nabble.com.