Re: IMX6UL: Booting kernel with initramfs blocks

[Patrick Boettcher <patrick.boettcher@posteo.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