Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754831Ab3CPJXH (ORCPT ); Sat, 16 Mar 2013 05:23:07 -0400 Received: from mail-we0-f173.google.com ([74.125.82.173]:61240 "EHLO mail-we0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753091Ab3CPJXE (ORCPT ); Sat, 16 Mar 2013 05:23:04 -0400 MIME-Version: 1.0 X-Originating-IP: [95.21.89.116] In-Reply-To: References: Date: Sat, 16 Mar 2013 10:23:01 +0100 Message-ID: Subject: Re: Getting kernel uImage build issue on omap2+ From: Javier Martinez Canillas To: Anil Kumar Cc: "linux-omap@vger.kernel.org" , Tony Lindgren , "devicetree-discuss@lists.ozlabs.org" , Benoit Cousson , linux-arm , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2145 Lines: 63 On Sat, Mar 16, 2013 at 5:44 AM, Anil Kumar 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@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@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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/