WARNING: This server is unstable and will be retired in the next days.
If you want to keep this forum available, please request immediately a migration
on the Nabble Support forum.
Forums that don't receive any migration request will be deleted forever.
I'm running in a situation where I'm using a USB card reader to connect my 16G microSD Card to the development machine (PC). when I use the mount or df command, no names such as /dev/mmcblk0p1 or /dev/sde1 appear; only /dev/sda5 appears under "dev" directory. But when I manually open the "dev" directory, I can figure out that sdb, sdc, sdd, sde, sg2, sg3, sg4, and sg5 are added to the directory (dev) and if I disconnect the USB card reader, these (sdb, sdc, sdd, sde, sg2, sg3, sg4, and sg5) disappear from the "dev" directory. I tried to follow http://www.gumstix.org/create-a-bootable-microsd-card.html but when applied to sdb, sdc, sdd, and sde, it says No medium found however when applied to sg2, sg3, sg4, and sg5, I got this picture here attached with a warning saying "partition 1 extends past end of disk".
Is there a way to merge sg2 ... sg5 to sg such that the disk size could be enough to handle booth partitions?
An suggestion is welcome, Gutembert.
PS. Steve I am sorry for giving you a wrong name.
On Mon, Apr 2, 2012 at 9:40 PM, zoso1234 [via Gumstix] <[hidden email]> wrote:
I have never thought of putting two images onto SD card..I'm not sure if that can be done..
regarding the bootable sd card once you create the two partitions (boot section FAT32 and rootfs ext3 ) you just copy MLO(first!) and u-boot.bin, and uImage into boot-naming matters. then cd into rootfs and untar your dsp image onto it. I can send you the commands I did to create the bootable sd card but they are pretty standard and follow closely with the doc's on gumstix.net and sakoman.
If your uImage/u-boot.bin and rootfs are expecting different kernels you are going to run into issues. When I leave preferred version out of the local.conf every thing builds to the 3.0 kernel and it works okay (except for desktop build) but when I try 2.6.34 the kernel is getting matched to 3.0 but rootfs wants something else.
Also if you have messed around with the u-boot environment-which you need to do in order to give memory to the dsp. you might consider nand erase command..which resets your u-boot environment-I would only do this if when you put everything on the two sections(boot and rootfs) and try booting you don't get much output(do modules get listed?)..and maybe consider doing this with a prebuilt image(MLO,u-boot.bin,uImage and rootfs) just in case there are issues with yours files.
here is the command for nand erase:
Overo # nand erase 240000 20000
NAND erase: device 0 offset 0x240000, size 0x20000
Erasing at 0x240000 -- 100% complete.
Overo # reset
Steve(not alex :) )
If you reply to this email, your message will be added to the discussion below: