i am working on MeeGo on BeagleBoard and i'd like to simplify the installation as far as possible. So
i wonder if there's a script somewhere that can automate the somewhat tricky formatting of a given sd card.
Does such a script exist?
Regard,
Till
There's 2/3 variations:
Angstrom's:
http://www.sakoman.com/cgi-bin/gitweb.cgi?p=openembedded.git;a=blob;f=contrib/angstrom/omap3-mkcard.sh;hb=HEAD
(angstrom's cgit seems down for me at the moment:
http://cgit.openembedded.org/cgit.cgi/openembedded/ )
Mine:
https://github.com/RobertCNelson/omap-image-builder/blob/master/tools/setup_sdcard.sh
Linaro's media create:
http://bazaar.launchpad.net/~linaro-maintainers/linaro-image-tools/linaro-image-tools/annotate/head:/linaro-media-create
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
thanks, exactly what i was looking for!
Till
--
You received this message because you are subscribed to the Google Groups "Beagle Board" group.
To post to this group, send email to beagl...@googlegroups.com.
To unsubscribe from this group, send email to beagleboard...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.
Hi,
Yeah, the parameters to create the first 'fat' partition are pretty
unique.. It's more off, these settings seem to work best with the
internal bootrom, then what is optimized for the end user's specific
sd card..
It's actually been a long time since i've used slackware.. (386 days)...
currently the script does:
sudo mkfs.vfat -F 16 ${MMC}${PARTITION_PREFIX}1 -n ${BOOT_LABEL} &>
${DIR}/sd.log
so does
sudo mkdosfs -F 16 ${MMC}${PARTITION_PREFIX}1 -n ${BOOT_LABEL} &> ${DIR}/sd.log
work just fine for you?
I'm thinking of doing a 'whereis on mkfs.vfat' if not found, then try
'whereis mkdsofs'.. to detect this issue.
Or are you thinking a differnet way? i'd like to keep away from
detecting every possible distribution, as there is only a few tools
actually being used in the script..
mkimage from u-boot
mkfs.vfat
mkfs.ext2
mkfs.ext3
mkfs.ext4
mkfs.btrfs
1) there is no disk
2) there are no cylinders
3) the boot rom does not care about the C/H/S values in the partition table.
Retested on my Bx/Cx/xM seems safe now without this old tweak/workaround...