From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wm0-x22e.google.com ([2a00:1450:400c:c09::22e]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1aYsFl-0005IK-Do for barebox@lists.infradead.org; Thu, 25 Feb 2016 09:30:34 +0000 Received: by mail-wm0-x22e.google.com with SMTP id g62so18843973wme.0 for ; Thu, 25 Feb 2016 01:30:12 -0800 (PST) From: Holger Schurig In-Reply-To: (Philippe Leduc's message of "Tue, 23 Feb 2016 13:00:22 +0100") References: <20160223080530.GZ3939@pengutronix.de> Date: Thu, 25 Feb 2016 10:30:09 +0100 Message-ID: <87bn7516ji.fsf@gmail.com> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: bootm crash - bad uimage? To: Philippe Leduc Cc: barebox@lists.infradead.org Philippe Leduc writes: > Note: I am using mkimage to create bootable image of a real-time OS > (PikeOS). There is no initrd or dtc at this step for now: I guess it > is like loading an old Linux kernel without userspace. So if you don't have an initrd, do you need uImage at all? You can boot a bootable image directly I use Linux without an initrd and don't bother with an uImage at all. I have my kernel on the SD-CARD or eMMC in /boot/vmlinuz, just like on any other (x86) Linux box. Here is my env/boot/emmc script. I use "boot", not "bootm", but AFAIK boot uses bootm under the hood. global linux.bootargs.dyn.root="root=/dev/mmcblk0p${global.boot.partition} rootwait ro" global bootm.image=/emmc/boot/vmlinuz detect mmc3 mkdir -p /emmc mount /dev/mmc3.0 /emmc I have similar scripts for SD-Card and USB. The kernel is installed using the normal Linux mechanism: make -C ${KERNEL_DIR} ARCH=arm INSTALL_PATH=${IMAGE_DIR}/boot zinstall maybe PikeOS has something equivalent. The result is: $ file image/boot/vmlinuz-4.4.2 image/boot/vmlinuz-4.4.2: Linux kernel ARM boot executable zImage (little-endian) As you see, I boot directly into the vmlinuz ... and I don't use Barebox' CONFIG_DEFAULT_ENVIRONMENT_GENERIC_NEW, too. _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox