mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Patrick Boettcher <patrick.boettcher@posteo.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org, Mikael Pann <Mikael.pann@stimio.fr>
Subject: Re: IMX6UL: Booting kernel with initramfs blocks
Date: Fri, 26 Oct 2018 12:38:07 +0200	[thread overview]
Message-ID: <20181026123807.3f980f28@yaise-pc1> (raw)
In-Reply-To: <20181026102342.lhx6hpcnobqe2g4k@pengutronix.de>

Hi,

Thanks for your super fast answer.

On Fri, 26 Oct 2018 12:23:42 +0200
Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > When trying to boot the image with bootm -o .. .. it takes some time
> > (to load I guess) and then blocks.  
> 
> Could you copy the image out from UBI to /somefile first to get UBI
> out of the equation first?

I copied 

  cp /dev/nand0.root.ubi.kernel-recovery test 
  md5sum test

The md5sum is identical with the one from my deploy dir.

Comparing the start of the zImage-initramfs file "manually" (some
bytes) with the zImage-image reveals that it is identical.

I'm using v2017.04.0-phy3 of phytec's fork of barebox, btw.
 
> Doing bootm -v -v might reveal some more information then.


  Loading ARM Linux zImage '/dev/nand0.root.ubi.kernel-recovery'
  OS image not yet relocated
  Passing control to ARM zImage handler
  no OS load address, defaulting to 0x888e1000
  no initrd load address, defaulting to 0x8a542000
  Loading devicetree from '/dev/nand0.root.ubi.oftree-recovery'
  Failed to fixup node in of_state_fixup+0x1/0x1ac: No such device
  commandline: consoleblank=0 console=ttymxc0,115200n8 rootwait ro fsck.repair=yes 
  {
    <device-tree dumped, looks good to me >
  };
 
  Starting kernel at 0x888e1000, oftree at 0x8a542000...
  nv variables modified, saving them
  <... blocks here ...>


--
Patrick.

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

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26 10:05 Patrick Boettcher
2018-10-26 10:23 ` Sascha Hauer
2018-10-26 10:38   ` Patrick Boettcher [this message]
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=20181026123807.3f980f28@yaise-pc1 \
    --to=patrick.boettcher@posteo.de \
    --cc=Mikael.pann@stimio.fr \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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