Hi Robert,
The Linaro project has a script that started as your setup_sdcard.sh called linaro_media_create. As part of our release process we need to have licenses for our files and since our script is based on yours, your choice of license affects what choices we have. So long story short, your file has no license included so care to add one or just tell us what the license is so we can give our script a compatible if not identical one?
Thanks John
On Tue, Aug 31, 2010, John Rigby wrote:
The Linaro project has a script that started as your setup_sdcard.sh called linaro_media_create. As part of our release process we need to have licenses for our files and since our script is based on yours, your choice of license affects what choices we have. So long story short, your file has no license included so care to add one or just tell us what the license is so we can give our script a compatible if not identical one?
And a full list of Copyright holders would be needed too; that is, yourself and any other significant contributor
On Wed, Sep 1, 2010 at 3:26 AM, Loïc Minier loic.minier@linaro.org wrote:
On Tue, Aug 31, 2010, John Rigby wrote:
The Linaro project has a script that started as your setup_sdcard.sh called linaro_media_create. As part of our release process we need to have licenses for our files and since our script is based on yours, your choice of license affects what choices we have. So long story short, your file has no license included so care to add one or just tell us what the license is so we can give our script a compatible if not identical one?
And a full list of Copyright holders would be needed too; that is, yourself and any other significant contributor
-- Loďc Minier
Sure, that's no problem guys. I'm pretty bad at remembering to use a license from the start (no one will ever use this script.. ;) ).. I usually use a simple MIT/X11 license, so that should be forward compatible with what you guys need..
I'm the primary author for most of it, if I draw the 'significant' line before localizations.. (German(1) spelling versions of "Disk") So that leaves one author for dealing with "/dev/mmcblk0[p]" (2)
So i'll contact Mario and hopefully get his blessing.
Regards,
1: http://bazaar.launchpad.net/~beagleboard-kernel/%2Bjunk/image-builder/revisi...
2: http://bazaar.launchpad.net/~beagleboard-kernel/%2Bjunk/image-builder/revisi...
On Wed, Sep 01, 2010, Robert Nelson wrote:
I'm the primary author for most of it, if I draw the 'significant' line before localizations..
Ok; I added Copyright 2010 Robert Nelson robertcnelson@gmail.com at the top of our fork; thanks!
(German(1) spelling versions of "Disk")
I just removed the need for the translation in our fork of the script (changed "sudo sfdisk [...]" calls to "sudo LC_ALL=C sfdisk [...]")
You might want to do the same for your script, to support any language.
So that leaves one author for dealing with "/dev/mmcblk0[p]" (2)
Apparently, we don't have this feature; I guess our script doesn't work on real MMC drives on laptops, only on USB ones.
Our version was GPLv3 licensed; I'm not sure whether it's GPLv3+ or GPLv3 though. I think it would be best to move to BSD style licensing, but that needs some kind of approval. Our version is in lp:linaro-image-tools BTW (linaro-media-create script).
Thanks for your help in sorting this out!
On Wed, Sep 1, 2010 at 7:38 AM, Loïc Minier loic.minier@linaro.org wrote:
On Wed, Sep 01, 2010, Robert Nelson wrote:
I'm the primary author for most of it, if I draw the 'significant' line before localizations..
Ok; I added Copyright 2010 Robert Nelson robertcnelson@gmail.com at the top of our fork; thanks!
(German(1) spelling versions of "Disk")
I just removed the need for the translation in our fork of the script (changed "sudo sfdisk [...]" calls to "sudo LC_ALL=C sfdisk [...]")
You might want to do the same for your script, to support any language.
Thanks Loïc, that definitely will work alot better. I was playing with LANG='s this morning not have much luck, wish i was bi-lingual. (does Canadian count?)
So that leaves one author for dealing with "/dev/mmcblk0[p]" (2)
Apparently, we don't have this feature; I guess our script doesn't work on real MMC drives on laptops, only on USB ones.
Yeah i didn't run into that myself till this summer with my new laptop with built-in mmc card.. So it'll probally come up at some point as a bug for you guys..
Our version was GPLv3 licensed; I'm not sure whether it's GPLv3+ or GPLv3 though. I think it would be best to move to BSD style licensing, but that needs some kind of approval. Our version is in lp:linaro-image-tools BTW (linaro-media-create script).
Thanks for your help in sorting this out!
Regards,
On Wed, Sep 1, 2010 at 9:58 AM, Robert Nelson robertcnelson@gmail.com wrote:
On Wed, Sep 1, 2010 at 7:38 AM, Loïc Minier loic.minier@linaro.org wrote:
On Wed, Sep 01, 2010, Robert Nelson wrote:
I'm the primary author for most of it, if I draw the 'significant' line before localizations..
Ok; I added Copyright 2010 Robert Nelson robertcnelson@gmail.com at the top of our fork; thanks!
(German(1) spelling versions of "Disk")
I just removed the need for the translation in our fork of the script (changed "sudo sfdisk [...]" calls to "sudo LC_ALL=C sfdisk [...]")
You might want to do the same for your script, to support any language.
Thanks Loïc, that definitely will work alot better. I was playing with LANG='s this morning not have much luck, wish i was bi-lingual. (does Canadian count?)
So that leaves one author for dealing with "/dev/mmcblk0[p]" (2)
Apparently, we don't have this feature; I guess our script doesn't work on real MMC drives on laptops, only on USB ones.
Yeah i didn't run into that myself till this summer with my new laptop with built-in mmc card.. So it'll probally come up at some point as a bug for you guys..
Our version was GPLv3 licensed; I'm not sure whether it's GPLv3+ or GPLv3 though. I think it would be best to move to BSD style licensing, but that needs some kind of approval. Our version is in lp:linaro-image-tools BTW (linaro-media-create script).
Thanks for your help in sorting this out!
Guys, just a heads up for util-linux-ng 2.18, (I've been tweaking my script for Fedora 14/15 usage..)
It looks like 'fdisk' can no longer create the new partition at sector 1, (thru forcing dos compatibly mode, i can get it down to sector 62, however that isn't bootable on my Bx/Cx beagles).. I know you use sfdisk, but you might run into the same issue since it's from the same project..
http://bazaar.launchpad.net/~linaro-maintainers/linaro-image-tools/linaro-im...
I'm looking into using parted from the command line, and so far it seems to be working on maverick just have to confirm on fedora..
Regards,
On Sat, Dec 4, 2010 at 9:06 AM, Robert Nelson robertcnelson@gmail.com wrote:
On Wed, Sep 1, 2010 at 9:58 AM, Robert Nelson robertcnelson@gmail.com wrote:
On Wed, Sep 1, 2010 at 7:38 AM, Loïc Minier loic.minier@linaro.org wrote:
On Wed, Sep 01, 2010, Robert Nelson wrote:
I'm the primary author for most of it, if I draw the 'significant' line before localizations..
Ok; I added Copyright 2010 Robert Nelson robertcnelson@gmail.com at the top of our fork; thanks!
(German(1) spelling versions of "Disk")
I just removed the need for the translation in our fork of the script (changed "sudo sfdisk [...]" calls to "sudo LC_ALL=C sfdisk [...]")
You might want to do the same for your script, to support any language.
Thanks Loïc, that definitely will work alot better. I was playing with LANG='s this morning not have much luck, wish i was bi-lingual. (does Canadian count?)
So that leaves one author for dealing with "/dev/mmcblk0[p]" (2)
Apparently, we don't have this feature; I guess our script doesn't work on real MMC drives on laptops, only on USB ones.
Yeah i didn't run into that myself till this summer with my new laptop with built-in mmc card.. So it'll probally come up at some point as a bug for you guys..
Our version was GPLv3 licensed; I'm not sure whether it's GPLv3+ or GPLv3 though. I think it would be best to move to BSD style licensing, but that needs some kind of approval. Our version is in lp:linaro-image-tools BTW (linaro-media-create script).
Thanks for your help in sorting this out!
Guys, just a heads up for util-linux-ng 2.18, (I've been tweaking my script for Fedora 14/15 usage..)
It looks like 'fdisk' can no longer create the new partition at sector 1, (thru forcing dos compatibly mode, i can get it down to sector 62, however that isn't bootable on my Bx/Cx beagles).. I know you use sfdisk, but you might run into the same issue since it's from the same project..
http://bazaar.launchpad.net/~linaro-maintainers/linaro-image-tools/linaro-im...
I'm looking into using parted from the command line, and so far it seems to be working on maverick just have to confirm on fedora..
nm figured out a work-around with fdisk that works
"-c=dos -u=cylinders"
so you might run into it too..
Regards,
On Saturday 04 December 2010 18:05:03 Robert Nelson wrote:
Guys, just a heads up for util-linux-ng 2.18, (I've been tweaking my script for Fedora 14/15 usage..)
It looks like 'fdisk' can no longer create the new partition at sector 1, (thru forcing dos compatibly mode, i can get it down to sector 62, however that isn't bootable on my Bx/Cx beagles).. I know you use sfdisk, but you might run into the same issue since it's from the same project..
http://bazaar.launchpad.net/~linaro-maintainers/linaro-image-tools/linaro-im...
I'm looking into using parted from the command line, and so far it seems to be working on maverick just have to confirm on fedora..
nm figured out a work-around with fdisk that works
"-c=dos -u=cylinders"
so you might run into it too..
We really need to fix the boot loaders here. Anything that writes to SD cards at unaligned sectors is rather broken, better make sure that setup_sdcards always aligns the start of each partition to multiples of 4MB from the start of the medium, and that all boot loaders know how to deal with this!
Arnd
On Sat, Dec 4, 2010 at 11:49 AM, arnd@arndb.de wrote:
On Saturday 04 December 2010 18:05:03 Robert Nelson wrote:
Guys, just a heads up for util-linux-ng 2.18, (I've been tweaking my script for Fedora 14/15 usage..)
It looks like 'fdisk' can no longer create the new partition at sector 1, (thru forcing dos compatibly mode, i can get it down to sector 62, however that isn't bootable on my Bx/Cx beagles).. I know you use sfdisk, but you might run into the same issue since it's from the same project..
http://bazaar.launchpad.net/~linaro-maintainers/linaro-image-tools/linaro-im...
I'm looking into using parted from the command line, and so far it seems to be working on maverick just have to confirm on fedora..
nm figured out a work-around with fdisk that works
"-c=dos -u=cylinders"
so you might run into it too..
We really need to fix the boot loaders here. Anything that writes to SD cards at unaligned sectors is rather broken, better make sure that setup_sdcards always aligns the start of each partition to multiples of 4MB from the start of the medium, and that all boot loaders know how to deal with this!
Well, the good news, the bootloaders, x-load and u-boot do a better job at this on the omap family....
However, it's actually the bootrom, inside the omap3 that's the problem..
Regards,
Hi Robert,
On Sat, 2010-12-04 at 09:06 -0600, Robert Nelson wrote: [...]
Guys, just a heads up for util-linux-ng 2.18, (I've been tweaking my script for Fedora 14/15 usage..)
It looks like 'fdisk' can no longer create the new partition at sector 1, (thru forcing dos compatibly mode, i can get it down to sector 62, however that isn't bootable on my Bx/Cx beagles).. I know you use sfdisk, but you might run into the same issue since it's from the same project..
http://bazaar.launchpad.net/~linaro-maintainers/linaro-image-tools/linaro-im...
I'm looking into using parted from the command line, and so far it seems to be working on maverick just have to confirm on fedora..
I know you found a workaround with fdisk so you're probably no longer using parted, but I was wondering if you were able to use parted to change the geometry in the partition table to 255heads/63sectors as the boot rom seems to require?
I ask because I'm working on converting our script to python and it'd be nice if I could use python-parted for that, but it doesn't seem to be able to.
Cheers,
Hi Guilherme,
I know you found a workaround with fdisk so you're probably no longer using parted, but I was wondering if you were able to use parted to change the geometry in the partition table to 255heads/63sectors as the boot rom seems to require?
Actually with current x-loader/u-boot the 255heads/63sectors isn't a hard requirement anymore for the boot partition, so i've dropped it..
https://github.com/RobertCNelson/omap-image-builder/blob/master/tools/setup_...
So far tested on:
Beagle B6 (oldest still booting beagle i have, any boards before that had serial-ic overheating problems and eventually die under warrente.) Beagle C2 & C4 Beagle xM A2
with angstrom's: MLO-beagleboard-1.44+r16 & u-boot-beagleboard-2010.03+r65
Panda A1
with mlo/u-boot from: http://gitorious.org/pandaboard
So right now i use parted to create the second partition. We could drop fdisk for the first, if we could figure out how to make parted create a partition starting at the first cylinder.
For example, I've tried this and it doesn't boot:
parted --script ${MMC} mkpart primary fat16 0 64
I ask because I'm working on converting our script to python and it'd be nice if I could use python-parted for that, but it doesn't seem to be able to.
Regards,
Hi,
On Tue, Dec 7, 2010 at 3:10 PM, Robert Nelson robertcnelson@gmail.com wrote:
Hi Guilherme,
I know you found a workaround with fdisk so you're probably no longer using parted, but I was wondering if you were able to use parted to change the geometry in the partition table to 255heads/63sectors as the boot rom seems to require?
Actually with current x-loader/u-boot the 255heads/63sectors isn't a hard requirement anymore for the boot partition, so i've dropped it..
https://github.com/RobertCNelson/omap-image-builder/blob/master/tools/setup_...
So far tested on:
Beagle B6 (oldest still booting beagle i have, any boards before that had serial-ic overheating problems and eventually die under warrente.) Beagle C2 & C4 Beagle xM A2
with angstrom's: MLO-beagleboard-1.44+r16 & u-boot-beagleboard-2010.03+r65
Panda A1
with mlo/u-boot from: http://gitorious.org/pandaboard
So right now i use parted to create the second partition. We could drop fdisk for the first, if we could figure out how to make parted create a partition starting at the first cylinder.
For example, I've tried this and it doesn't boot:
parted --script ${MMC} mkpart primary fat16 0 64
I ask because I'm working on converting our script to python and it'd be nice if I could use python-parted for that, but it doesn't seem to be able to.
What about sfdisk? This is by far the simplest tool and works well for parts of linaro-media-create: by direct consequence of its simplicity it seems to be the most controllable and has the fewest unexpected limitations and failure modes among the tools I've played with, as well as being friendly to being program-driven. For manually generating an optimal partition layout for Beagles I've also found this the best tool to use.
Certainly it's horrible to have to use a different partitioner to create each partition...
sfdfisk works well for me though, e.g.:
S=63; H=255 BC=5 cat <<EOF | sfdisk -S63 -H255 -C523 -L -uS <device> $S,$((5*BC*S-S)),0xc,* $(((5*BC*S+2047)/2048*2048)) EOF
...will set up by 4GB card a treat, with a working boot partition and an aligned filesystem partition, with the CHS fields for the first partition filled in correctly:
00000000 80 01 01 00 0c fe 3f 04 3f 00 00 00 86 39 01 00 00000010 00 19 15 05 83 2a a0 0a 00 40 01 00 00 c0 7e 00 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
(BC is the number of cylinders for the boot partition. The only constraint here is that the partition must be unambiguously FAT32, i.e. > 65534 clusters -- which gives a minimum sector count of 66593. 5 is simply (65593 + 63*255-1)/(63*255))
Of course, the DOS partition table format is so trivial that if we're having to jump through a lot of hoops, it's tempting to suggest we could implement it ourselves (though I know I'm not supposed to say that due to fragmentation etc., etc....)
Cheers ---Dave
On Tue, 2010-12-07 at 15:33 +0000, Dave Martin wrote:
Hi,
On Tue, Dec 7, 2010 at 3:10 PM, Robert Nelson robertcnelson@gmail.com wrote:
Hi Guilherme,
I know you found a workaround with fdisk so you're probably no longer using parted, but I was wondering if you were able to use parted to change the geometry in the partition table to 255heads/63sectors as the boot rom seems to require?
Actually with current x-loader/u-boot the 255heads/63sectors isn't a hard requirement anymore for the boot partition, so i've dropped it..
https://github.com/RobertCNelson/omap-image-builder/blob/master/tools/setup_...
So far tested on:
Beagle B6 (oldest still booting beagle i have, any boards before that had serial-ic overheating problems and eventually die under warrente.) Beagle C2 & C4 Beagle xM A2
with angstrom's: MLO-beagleboard-1.44+r16 & u-boot-beagleboard-2010.03+r65
Panda A1
with mlo/u-boot from: http://gitorious.org/pandaboard
So right now i use parted to create the second partition. We could drop fdisk for the first, if we could figure out how to make parted create a partition starting at the first cylinder.
For example, I've tried this and it doesn't boot:
parted --script ${MMC} mkpart primary fat16 0 64
I ask because I'm working on converting our script to python and it'd be nice if I could use python-parted for that, but it doesn't seem to be able to.
What about sfdisk? This is by far the simplest tool and works well for parts of linaro-media-create: by direct consequence of its simplicity it seems to be the most controllable and has the fewest unexpected limitations and failure modes among the tools I've played with, as well as being friendly to being program-driven. For manually generating an optimal partition layout for Beagles I've also found this the best tool to use.
sfdisk works indeed, but it'd be nicer if I could use a python library since I'm converting the whole script. The python-parted API is crap and undocumented, though, so I'll stick to running sfdisk in a subprocess.
Certainly it's horrible to have to use a different partitioner to create each partition...
Yeah, I was not planning to do that, although we currently use parted to create a fresh partition table. It'd be nice if we could use sfdisk to do that, but I don't think we can?
sfdfisk works well for me though, e.g.:
S=63; H=255 BC=5 cat <<EOF | sfdisk -S63 -H255 -C523 -L -uS <device> $S,$((5*BC*S-S)),0xc,* $(((5*BC*S+2047)/2048*2048)) EOF
...will set up by 4GB card a treat, with a working boot partition and an aligned filesystem partition, with the CHS fields for the first partition filled in correctly:
00000000 80 01 01 00 0c fe 3f 04 3f 00 00 00 86 39 01 00 00000010 00 19 15 05 83 2a a0 0a 00 40 01 00 00 c0 7e 00 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
(BC is the number of cylinders for the boot partition. The only constraint here is that the partition must be unambiguously FAT32, i.e. > 65534 clusters -- which gives a minimum sector count of 66593. 5 is simply (65593 + 63*255-1)/(63*255))
Of course, the DOS partition table format is so trivial that if we're having to jump through a lot of hoops, it's tempting to suggest we could implement it ourselves (though I know I'm not supposed to say that due to fragmentation etc., etc....)
Cheers ---Dave
On Wed, Dec 8, 2010 at 1:07 PM, Guilherme Salgado salgado@canonical.com wrote:
On Tue, 2010-12-07 at 15:33 +0000, Dave Martin wrote:
Hi,
On Tue, Dec 7, 2010 at 3:10 PM, Robert Nelson robertcnelson@gmail.com wrote:
Hi Guilherme,
I know you found a workaround with fdisk so you're probably no longer using parted, but I was wondering if you were able to use parted to change the geometry in the partition table to 255heads/63sectors as the boot rom seems to require?
Actually with current x-loader/u-boot the 255heads/63sectors isn't a hard requirement anymore for the boot partition, so i've dropped it..
https://github.com/RobertCNelson/omap-image-builder/blob/master/tools/setup_...
So far tested on:
Beagle B6 (oldest still booting beagle i have, any boards before that had serial-ic overheating problems and eventually die under warrente.) Beagle C2 & C4 Beagle xM A2
with angstrom's: MLO-beagleboard-1.44+r16 & u-boot-beagleboard-2010.03+r65
Panda A1
with mlo/u-boot from: http://gitorious.org/pandaboard
So right now i use parted to create the second partition. We could drop fdisk for the first, if we could figure out how to make parted create a partition starting at the first cylinder.
For example, I've tried this and it doesn't boot:
parted --script ${MMC} mkpart primary fat16 0 64
I ask because I'm working on converting our script to python and it'd be nice if I could use python-parted for that, but it doesn't seem to be able to.
What about sfdisk? This is by far the simplest tool and works well for parts of linaro-media-create: by direct consequence of its simplicity it seems to be the most controllable and has the fewest unexpected limitations and failure modes among the tools I've played with, as well as being friendly to being program-driven. For manually generating an optimal partition layout for Beagles I've also found this the best tool to use.
sfdisk works indeed, but it'd be nicer if I could use a python library since I'm converting the whole script. The python-parted API is crap and undocumented, though, so I'll stick to running sfdisk in a subprocess.
Yeah, sure. Really, the best thing would to communitywise do would be to fix libparted to work with our use case (assmuing it can't do the right thing already of course). But I'm not very familiar with it, so I don't know what this would involve.
Certainly it's horrible to have to use a different partitioner to create each partition...
Yeah, I was not planning to do that, although we currently use parted to create a fresh partition table. It'd be nice if we could use sfdisk to do that, but I don't think we can?
sfdisk won't _just_ create an empty partition table if my understanding is correct.
But if you tell sfdisk to set up partitions on a device with no partition table it will set one up.
sfdisk doesn't appear to create a disk signature at offset 0x1B8 - it's left as-is. Some other partitioners, such as fdisk, set up an ID when creating an MBR-style partition table. We might decide not to care about that...
Cheers ---Dave
On Tue, 2010-12-07 at 09:10 -0600, Robert Nelson wrote:
Hi Guilherme,
I know you found a workaround with fdisk so you're probably no longer using parted, but I was wondering if you were able to use parted to change the geometry in the partition table to 255heads/63sectors as the boot rom seems to require?
Actually with current x-loader/u-boot the 255heads/63sectors isn't a hard requirement anymore for the boot partition, so i've dropped it..
I thought the 255h/63s requirement came from the boot ROM?
https://github.com/RobertCNelson/omap-image-builder/blob/master/tools/setup_...
I partitioned a card with the exact same commands you use in setup_sdcard.sh (fdisk to create the boot partition and parted for the root one), and then used our script to populate it (without changing the partitions), but it didn't boot. This is what I got on my xM.
Texas Instruments X-Loader 1.4.4ss (Sep 30 2010 - 14:44:32) Beagle xM Rev A Reading boot sector Error: reading boot sector u-boot.bin not found or blank nand contents - attempting serial boot . . . ## Ready for binary (kermit) download to 0x80008000 at 115200 bps...
Maybe I did something wrong when partitioning?
So far tested on:
Beagle B6 (oldest still booting beagle i have, any boards before that had serial-ic overheating problems and eventually die under warrente.) Beagle C2 & C4 Beagle xM A2
with angstrom's: MLO-beagleboard-1.44+r16 & u-boot-beagleboard-2010.03+r65
Panda A1
with mlo/u-boot from: http://gitorious.org/pandaboard
So right now i use parted to create the second partition. We could drop fdisk for the first, if we could figure out how to make parted create a partition starting at the first cylinder.
For example, I've tried this and it doesn't boot:
parted --script ${MMC} mkpart primary fat16 0 64
libparted (which I'm using indirectly via python-parted) allows you to specify the geometry of a partition in sectors, but it has an awful and undocumented API, so I couldn't get it to make a partition that my xM can boot. I guess we'll have to live with [s]fdisk for some time still, but I'll let you know if I manage to replace them with libparted/parted.
Cheers,
On Tue, Dec 7, 2010 at 1:10 PM, Guilherme Salgado salgado@canonical.com wrote:
On Tue, 2010-12-07 at 09:10 -0600, Robert Nelson wrote:
Hi Guilherme,
I know you found a workaround with fdisk so you're probably no longer using parted, but I was wondering if you were able to use parted to change the geometry in the partition table to 255heads/63sectors as the boot rom seems to require?
Actually with current x-loader/u-boot the 255heads/63sectors isn't a hard requirement anymore for the boot partition, so i've dropped it..
I thought the 255h/63s requirement came from the boot ROM?
That was my impression to for the last couple years, but we had discussion about it on the beagleboard group. The rom doesn't care, it was x-loader that was coded for sector 63..
http://www.sakoman.com/cgi-bin/gitweb.cgi?p=x-loader.git%3Ba=commit%3Bh=f243...
Discussion:
http://groups.google.com/group/beagleboard/browse_thread/thread/2a41df7801ec...
https://github.com/RobertCNelson/omap-image-builder/blob/master/tools/setup_...
I partitioned a card with the exact same commands you use in setup_sdcard.sh (fdisk to create the boot partition and parted for the root one), and then used our script to populate it (without changing the partitions), but it didn't boot. This is what I got on my xM.
Texas Instruments X-Loader 1.4.4ss (Sep 30 2010 - 14:44:32) Beagle xM Rev A Reading boot sector Error: reading boot sector u-boot.bin not found or blank nand contents - attempting serial boot . . . ## Ready for binary (kermit) download to 0x80008000 at 115200 bps...
Maybe I did something wrong when partitioning?
Here's mine for comparison:
Texas Instruments X-Loader 1.4.4ss (Sep 22 2010 - 16:12:19) Beagle xM Rev A Reading boot sector Loading u-boot.bin from mmc
U-Boot 2010.03-dirty (Oct 18 2010 - 11:31:58)
OMAP3630/3730-GP ES1.0, CPU-OPP2, L3-165MHz, OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MB NAND: 256 MiB *** Warning - bad CRC or NAND, using default environment
In: serial Out: serial Err: serial
Probing for expansion boards, if none are connected you'll see a harmless I2C error.
No EEPROM on expansion board Beagle xM Rev A Die ID #51b200001bf00000015739ea0700c02c
fdisk -l (note: the physcial/logical warning seems to just be this microSD card, i don't have another around to test..)
Disk /dev/sdd: 3965 MB, 3965190144 bytes 122 heads, 62 sectors/track, 1023 cylinders Units = cylinders of 7564 * 512 = 3872768 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0005702e
Device Boot Start End Blocks Id System /dev/sdd1 * 1 18 65560 e W95 FAT16 (LBA) Partition 1 has different physical/logical beginnings (non-Linux?): phys=(0, 1, 1) logical=(0, 0, 17) Partition 1 has different physical/logical endings: phys=(1023, 3, 16) logical=(17, 41, 6) Partition 1 does not end on cylinder boundary. /dev/sdd2 18 1007 3741073 83 Linux Partition 2 has different physical/logical beginnings (non-Linux?): phys=(8, 41, 34) logical=(17, 41, 7) Partition 2 has different physical/logical endings: phys=(473, 230, 47) logical=(1006, 62, 54) Partition 2 does not end on cylinder boundary.
Regards,
-
arnd＠arndb.de -
Dave Martin -
Guilherme Salgado -
John Rigby -
Loïc Minier -
Robert Nelson