On Thursday, January 16, 2014 9:22:12 AM UTC-7, RobertCNelson wrote: > > Okay, just dropped it to 3700.. > > > https://github.com/beagleboard/image-builder/commit/b6288e9ebbe3a688b4c9623ce3c94bfdb9e5e305 > > > Success... finally. :-)
It took a while to figure out ship.sh was using the setup_sdcard.sh inside the image file. I had pulled the new version into the image_builder dir, but I didn't rerun the entire build. I was just rerunning the ship.sh script. After editing the setup_sdcard.sh in the image it worked. I have booted my BBB using the new 4GB wheezy SD card. Everything seems to be working as expected. > What i'd really like to see is a script that can be run on target to > automatically re-size it, even on bootup... > > Because, if your already running linux, instead of resizing the *.img > for your microSD, you can just already call "--mmc /dev/sdX" with > setup_sdcard.sh and it'll auto partition your microSD using all the > available space. > > Of course the "--img" option allows you to easily share a completed > image that doesn't need network access to pull in the extra bits > setup_sdcard.sh.. > I was thinking more along the lines of always building a standard image the exact size needed for the BBB eMMC (i.e. 2 GB) since they are all the same size. Then using a minimal system and a compressed copy of this standard image to build the eMMC_flasher image which I think would also fit into 2 GB. The same compressed standard image could be distributed for use with a small script that would expand the image onto an SD card of any larger size (i.e. 4 GB, 8 GB, 16 GB, etc) and then expand the partition and filesystem to match the size of the SD card. This would work well for linux host systems, but perhaps not so well for Windows or OS X hosts. So perhaps the larger images will still be needed for these systems. I noticed that the ship.sh script seems to build each image from scratch rather than basing one image on the other (i.e. it calls setup_sdcard.sh once for each image). The only thing I saw that is done for the eMMC_flasher image is the creation of a file called flash-eMMC.txt. It wasn't obvious to me how that file is used. I assume the startup code looks for that file and runs the flashing commands if it's found as the system boots the flasher image. Are there other differences between a normal image (say the 4GB image) and a eMMC_flasher image as they are currently being built? Dennis Cote -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
