Getting kernel uImage build issue on omap2+

[Javier Martinez Canillas]

On Sat, Mar 16, 2013 at 5:44 AM, Anil Kumar <anilk4.v at gmail.com> wrote:
> Hi,
>
> I am getting kernel uImage build issue on omap2+ log[1]
>
> Taken kernel branch "for_3.10/dts" from
> https://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
>
> Taking reference from
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/tmlind/linux-omap/+/omap-for-v3.9/multiplatform-enable-signed-v2
>
> Am I missing some thing ?
>
> [1]
> anil at anil-laptop:~/Anil/omap3/bcousson$  mkimage -A arm -O linux -T
> kernel -C none -a 0x80008000 -e 0x80008000 -n "Linux" -d
> zImage-omap2plus uImage-omap2plus
> mkimage: Can't open zImage-omap2plus: No such file or directory
> anil at anil-laptop:~/Anil/omap3/bcousson$
>
> Thanks,
> Anil
>

Hi Anil,

It seems that Tony's email assumed that you generated a bunch of
zImages for different platforms and then naming them zImage-$platform.

e.g:

$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig
$ make -j 4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- zImage modules
zImage-omap2plus
$ cp cp arch/arm/boot/zImage zImage-omap2plus

and then you can use the command in [1]:

$  mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e
0x80008000 -n "Linux" -d zImage-omap2plus uImage-omap2plus

anyways, the problem is that zImage-omap2plus does not exist and you
have to use the zImage generated by "make zImage". What I usually do
is just:

$ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e
0x80008000 -n "Linux" -d arch/arm/boot/zImage uImage-omap2plus

and then copy uImage-omap2plus as uImage on either my board MMC/SD or
Flash memory.

Also, if you find this inconvenient, you can add CONFIG_CMD_BOOTZ to
your board header config file in U-Boot so it can boot a zImage
directly instead of an uImage. Not sure when did was introduced on
U-Boot but should be available on any decent-ish version.

Hope it helps,
Javier