mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Holger Schurig <holgerschurig@gmail.com>
To: Philippe Leduc <ledphilippe@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: bootm crash - bad uimage?
Date: Thu, 25 Feb 2016 10:30:09 +0100	[thread overview]
Message-ID: <87bn7516ji.fsf@gmail.com> (raw)
In-Reply-To: <CABQt-Um-ENNbt_MbbF4NP42jmufsmgxV6pVvEsTFjw0O=++=ow@mail.gmail.com> (Philippe Leduc's message of "Tue, 23 Feb 2016 13:00:22 +0100")

Philippe Leduc <ledphilippe@gmail.com> 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

  reply	other threads:[~2016-02-25  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 15:31 Philippe Leduc
2016-02-23  8:05 ` Sascha Hauer
2016-02-23 12:00   ` Philippe Leduc
2016-02-25  9:30     ` Holger Schurig [this message]
2016-02-25  9:50       ` Philippe Leduc
2016-02-26  9:22         ` Philippe Leduc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bn7516ji.fsf@gmail.com \
    --to=holgerschurig@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=ledphilippe@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox