[fedora-arm] changing kernel w/ uboot
dennis at ausil.us
Wed Mar 14 19:29:08 UTC 2012
-----BEGIN PGP SIGNED MESSAGE-----
On Wed, 14 Mar 2012 15:06:04 -0400 (EDT)
Matthew Galgoci <mgalgoci at redhat.com> wrote:
> > Date: Wed, 14 Mar 2012 19:49:18 +0100
> > From: Niels de Vos <devos at fedoraproject.org>
> > To: Matthew Galgoci <mgalgoci at redhat.com>
> > Cc: arm at lists.fedoraproject.org
> > Subject: Re: [fedora-arm] changing kernel w/ uboot
> > On 14 Mar 2012 14:02, "Matthew Galgoci" <mgalgoci at redhat.com> wrote:
> > >
> > >
> > > How does one change the kernel that uboot loads from mtdflash and
> > > instead boots a kernel from an ext filesystem on an attached
> > > (uboot supported) usb flash drive? Furthermore, is there a way to
> > > get uboot to also load an initial ram file (disk or fs)? The
> > > hardware in question is a guru plug and I've got the jtag and
> > > console adapter.
> > http://fedoraproject.org/wiki/Architectures/ARM/GuruPlug should
> > probably be your starting point.
> That was an ok starting point, and actually one of the first
> documents I had looked at. The problem with that guide is it doesn't
> actually change the kernel, just the rootfs.
> Additionally, I've learned that the uboot that ships with the guruplug
> is somewhat older and doesn't support reading files from ext
> filesystems, just fat.
> This is similar to what I experienced:
> I was able to get uboot to see the partitions and filesystems on a usb
> stick (though not the micro sd card in the onboard slot). Perhaps it
> has something to do with the sd card being a 16G card.
> The issue I am at now is as follows:
> Marvell>> fatls usb 1:1
> 134819692 initrd-pae.img
> 4134432 vmlinuz-pae
> 11049080 initramfs-3.3.0-0.rc4.git3.1.fc17.armv5tel.img
> 3630488 vmlinuz-3.3.0-0.rc4.git3.1.fc17.armv5tel
> 4 file(s), 1 dir(s)
> Marvell>> fatload usb 1:1 0x6400000
> Marvell>> vmlinuz-3.3.0-0.rc4.git3.1.fc17.armv5tel 368
> reading vmlinuz-3.3.0-0.rc4.git3.1.fc17.armv5tel
> 3630488 bytes read
> Marvell>> bootm 0x6400000
> Wrong Image Format for bootm command
> ERROR: can't get kernel image!
> Obviously the -PAE i686 kernels don't apply, I am not trying to load
> one of those.
> Does anyone see anything patently wrong with what I did above?
> I suppose I could try using the stock uboot to load a newer uboot.
you have to run mkimage on the vmlinuz image for uboot to recognise it
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the arm