From: Neil C. <nc...@ba...> - 2011-07-12 16:00:13
|
I have just baked the new Verdex git repository but find that the image is greater than the 32Meg of internal flash: -rw-r--r-- 1 nco nco 35912804 2011-07-08 00:32 Angstrom-verdex-console-image-glibc-ipk-2010.4-test-20110707-gumstix-verdex.rootfs.jffs2 Is there an easy step to get this to fit inside 32Meg? I just followed the on line steps to bake the image. It eventually compiled properly but I am left with a 35Meg jffs file. Can I easily take something out I do not need to squeeze into 32Meg? If so then how? I have already changed the u-boot loader for the large kernel (katload 160000) since the kernel is 1.3Meg. Do I need to boot from microSD instead? I understand microSDHC doesnt work for booting in Verdex PRO. What is the largest microSD card I can use? Id like to partition the remaining space for data storage. Many thanks Neil -- View this message in context: http://old.nabble.com/Verdex-PRO-image-too-big-tp32047005p32047005.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <ash...@gm...> - 2011-07-12 16:09:21
|
Hi Neil, On Tue, Jul 12, 2011 at 9:00 AM, Neil Cobbett <nc...@ba...> wrote: > Is there an easy step to get this to fit inside 32Meg? I just followed the > on line steps to bake the image. It eventually compiled properly but I am > left with a 35Meg jffs file. Can I easily take something out I do not need > to squeeze into 32Meg? If so then how? Using a bootable microSD is the easiest. It is possible to strip out some packages from the console image depending on eactly what packages you need. > > I have already changed the u-boot loader for the large kernel (katload > 160000) since the kernel is 1.3Meg. > > Do I need to boot from microSD instead? I understand microSDHC doesnt work > for booting in Verdex PRO. What is the largest microSD card I can use? Id > like to partition the remaining space for data storage. The standard microSD spec includes drives up to and including 2GB. -Ash |
From: Neil C. <nc...@ba...> - 2011-07-13 09:26:20
|
Thanks Ash! That did the trick. Having issues with not booting direct from mmc. I do the following: mmcinit fatload mmc 0 a2000000 uimage setenv bootargs console=ttyS0,115200n8 root-/dev/mmcblk0p2 rw rootdelay=1 saveenv bootm a2000000 BUT on reboot I need to type it again. For some reason it is not being stored as the default boot options. Any ideas? Neil Ash Charles wrote: > > Hi Neil, > > On Tue, Jul 12, 2011 at 9:00 AM, Neil Cobbett <nc...@ba...> wrote: >> Is there an easy step to get this to fit inside 32Meg? I just followed >> the >> on line steps to bake the image. It eventually compiled properly but I >> am >> left with a 35Meg jffs file. Can I easily take something out I do not >> need >> to squeeze into 32Meg? If so then how? > Using a bootable microSD is the easiest. It is possible to strip out > some packages from the console image depending on eactly what packages > you need. >> >> I have already changed the u-boot loader for the large kernel (katload >> 160000) since the kernel is 1.3Meg. >> >> Do I need to boot from microSD instead? I understand microSDHC doesnt >> work >> for booting in Verdex PRO. What is the largest microSD card I can use? >> Id >> like to partition the remaining space for data storage. > The standard microSD spec includes drives up to and including 2GB. > > -Ash > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/Verdex-PRO-image-too-big-tp32047005p32052125.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <ash...@gm...> - 2011-07-18 17:25:48
|
Hi Neil, On Wed, Jul 13, 2011 at 2:26 AM, Neil Cobbett <nc...@ba...> wrote: > BUT on reboot I need to type it again. For some reason it is not being > stored as the default boot options. Any ideas? It does seem bizarre. Are you able to store a single variable e.g. # setenv foo bar # saveenv # printenv foo # reset # printenv foo ? Are the flash sectors unlocked? (I think the 'protect' command with no arguments shows the flash locking map.) -Ash |