mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Patrick Boettcher <patrick.boettcher@posteo.de>
To: barebox@lists.infradead.org
Cc: Mikael Pann <Mikael.pann@stimio.fr>
Subject: IMX6UL: Booting kernel with initramfs blocks
Date: Fri, 26 Oct 2018 12:05:58 +0200	[thread overview]
Message-ID: <20181026120558.1ef80a86@yaise-pc1> (raw)

Hi,

we are using a Phytec IMX6UL-module and would like to use a
kernel+initramfs as a rescue/recovery system (when bootchooser bails
out).

We are building the initramfs-zIamge with Yocto using a
customized Phytec-distribution (not many changes). 

What we added to get an initramfs'd kernel is 

   INITRAMFS_IMAGE = "<image-name>"
   INITRAMFS_IMAGE_BUNDLE = "1"

to local.conf.

bitbaking the thing gives us the zImage-initramfs-file.

Then we created two static volumes within the UBI-partition on the
NAND one for the image, one for the dtb.

When trying to boot the image with bootm -o .. .. it takes some time
(to load I guess) and then blocks.

Putting the zImage "kernel-only" on the same volumes and booting works
(except that there is no rootfs).

Our zImage with initramfs is 28MiB big, the kernel alone 7.

Could anyone advise what's wrong with this setup? Is it is
size-problem in barebox? 

Is it a Yocto-problem? I'm aware that asking here might the wrong
thing, as barebox is only one part of the system.

Thanks in advance for any help.

best regards,
--
Patrick.






_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2018-10-26 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26 10:05 Patrick Boettcher [this message]
2018-10-26 10:23 ` Sascha Hauer
2018-10-26 10:38   ` Patrick Boettcher
2018-10-26 11:24     ` Sascha Hauer
2018-10-26 14:25       ` Patrick Boettcher
2018-10-26 14:36         ` Lucas Stach
2018-10-28 14:29           ` Patrick Boettcher

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=20181026120558.1ef80a86@yaise-pc1 \
    --to=patrick.boettcher@posteo.de \
    --cc=Mikael.pann@stimio.fr \
    --cc=barebox@lists.infradead.org \
    /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