From: Joseph H. <jos...@gm...> - 2011-06-24 20:17:36
|
I've been using the minimal image Scott Ellis detailed here: http://www.jumpnowtek.com/index.php?option=com_content&view=article&id=65:gumstix-quick-boot&catid=35:gumstix&Itemid=67 However, I'm only seeing 128MB of RAM rather than the 256MB I know the Overo Earth has. Other images make use of the full RAM size. Can this be fixed simply? Is it a kernel config setting gone wrong? |
From: Joseph H. <jos...@gm...> - 2011-06-24 20:25:19
|
For reference, this is the defconfig for that image. https://github.com/scottellis/overo-oe/blob/minimal/recipes/linux/linux-omap3-2.6.34/overo/defconfig |
From: David A. <cy...@ho...> - 2011-06-24 20:36:18
|
We had this problem before. I think, that u-boot and x-load versions are not matched very well. Probably x-load is too old on your NAND. Build new one and re-flash your NAND. Recipe: 'x-load' (it will build x-load-overo.bin.itf file) Put binary image on FAT partition and from u-boot console execute this script (modify binary file name): if mmc init; then echo "Flashing x-load-overo.bin from x-load-overo.bin... (mtd0)" if fatload mmc 1 ${loadaddr} x-load-overo.bin; then nandecc hw nand erase 0 80000 nand write ${loadaddr} 0x00000000 0x00080000 else echo "ERROR: couldn\'t find x-load-overo.bin..." fi else echo "Please insert a microSD and reboot the board" fi -david Joseph Hickman wrote: > > I've been using the minimal image Scott Ellis detailed here: > http://www.jumpnowtek.com/index.php?option=com_content&view=article&id=65:gumstix-quick-boot&catid=35:gumstix&Itemid=67 > > However, I'm only seeing 128MB of RAM rather than the 256MB I know the > Overo > Earth has. Other images make use of the full RAM size. > > Can this be fixed simply? Is it a kernel config setting gone wrong? > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense.. > http://p.sf.net/sfu/splunk-d2d-c1 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/Minimal-Image-tp31922769p31922908.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Joseph H. <jos...@gm...> - 2011-06-24 21:47:30
|
Thanks, I'll give this a try on Monday. However, u-boot does report 256MB of RAM. I guess I didn't explain that. It was using the "free" or "top" commands where I saw 128MB total memory being reported. If u-boot is able to find all the RAM, could the problem still be with x-load? |
From: Joseph H. <jos...@gm...> - 2011-06-27 15:28:19
|
Thanks for the tip. Even though I don't understand what was going on, updating MLO/x-load solved the problem. |