All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Clay D. Montgomery" <clay@montgomery1.com>
To: yocto@yoctoproject.org
Subject: Problem Booting Yocto 1.7.3
Date: Tue, 17 Nov 2015 18:37:54 -0600	[thread overview]
Message-ID: <564BC862.2080308@montgomery1.com> (raw)

Hello,

    I'm trying to update from Yocto (Dizzy) 1.7.2 to 1.7.3 for a 
Wandboard Quad, but it hangs at the point where u-boot is trying to 
start the kernel. I'm guessing maybe this is because my image has u-boot 
2014 and I need u-boot 2015?  I have read that u-boot 2015 is required 
for Yocto 1.8 (Fido), because it has a newer kernel (3.14). But, my 
Yocto 1.7.3 build is still the 3.10.17 kernel.  Is it possible Bitbake 
built this image with u-boot and kernel versions that are not 
compatible, or am I missing the real issue?

   I am pasting my boot log below, up to the point where it hangs. I 
would really appreciate any help.

Thanks, Clay Montgomery


U-Boot 2014.10+fslc+g5fd0b60 (Nov 14 2015 - 17:25:56)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: Wandboard
I2C:   ready
DRAM:  2 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
auto-detected panel HDMI
Display: HDMI (1024x768)
In:    serial
Out:   serial
Err:   serial
Net:   FEC [PRIME]
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
reading boot.scr
** Unable to read file boot.scr **
reading zImage
5442368 bytes read in 359 ms (14.5 MiB/s)
Booting from mmc ...
reading imx6q-wandboard.dtb
43370 bytes read in 21 ms (2 MiB/s)
Kernel image @ 0x12000000 [ 0x000000 - 0x530b40 ]
## Flattened Device Tree blob at 18000000
    Booting using the fdt blob at 0x18000000
    Using Device Tree in place at 18000000, end 1800d969

Starting kernel ...


             reply	other threads:[~2015-11-18  0:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18  0:37 Clay D. Montgomery [this message]
2015-11-19  3:23 ` Problem Booting Yocto 1.7.3 nick

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=564BC862.2080308@montgomery1.com \
    --to=clay@montgomery1.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.