All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Richard Leitner - SKIDATA <Richard.Leitner@skidata.com>
Cc: "Yocto Project Discussion ML \(yocto@yoctoproject.org\)"
	<yocto@yoctoproject.org>
Subject: Re: Problem with own kernel recipe on Dora
Date: Tue, 22 Apr 2014 09:23:02 +0100	[thread overview]
Message-ID: <1398154982.16672.25.camel@ted> (raw)
In-Reply-To: <F7680723A1CA6840825A59020FA77064010BC709@sdexmbx1srv.skidata.net>

On Tue, 2014-04-22 at 07:52 +0000, Richard Leitner - SKIDATA wrote:
> Hi Yocto-Community,
> as the subject already says I've a problem with my kernel recipe after the "migration" from the Dylan to the Dora (10.0.1) branch.
> I've tried the 10.0.1 release tag as well as the current dora master (50e9ccb2aff7b9f9dca4fda99a6832c60f64de3b).
> 
> The kernel recipe I'm using is derived from the skeleton:
> DESCRIPTION = "Linux Kernel"
> SECTION = "kernel"
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
> inherit kernel
> KSRC = "/home/leri/VCS/git/linux"
> KBRANCH = "master"
> SRC_URI = "git://${KSRC};protocol=file;branch=${KBRANCH};name=kernel;nocheckout=1"
> SRCREV = "2014_03_07"
> PR = "sd_15.2"
> LINUX_VERSION = "${PV}"
> LINUX_VERSION_EXTENSION = "-${PR}+${SRCREV}"
> COMPATIBLE_MACHINE = "skidata-harmony|smartcpu"
> KERNEL_IMAGETYPE = "uImage"
> SRC_URI += "file://defconfig"
> require recipes-kernel/linux/linux-yocto.inc
> 
> 
> This recipe was working well with the Dylan branch and following changes:
> -SRC_URI = "git://${KSRC};protocol=file;branch=${KBRANCH};name=kernel;nocheckout=1"
> +SRC_URI = "git://${KSRC};protocol=file;branch=${KBRANCH};name=kernel"
> +S = "${WORKDIR}/git"
> 
> 
> When compiled with the dora branch the kernel hangs at "Starting kernel..." and doesn't start:
> ## Booting kernel from Legacy Image at 00000000 ...
>    Image Name:   Linux-3.1.10-sd_15.2
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    3181616 Bytes = 3 MiB
>    Load Address: 00008000
>    Entry Point:  00008000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
> 
> Starting kernel ...
> 
> 
> I've already looked through the migration notes in the manual but I'm unable to find any hints...
> Are there any ideas why the kernel doesn't start with the Dora branch?

We saw an issue recently on beaglebone that looked very like this. It
turned out the load address for the kernel was conflicting in memory
with the device tree binary.

It easily be something different but I thought I'd mention it.

Cheers,

Richard



  reply	other threads:[~2014-04-22  8:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22  7:52 Problem with own kernel recipe on Dora Richard Leitner - SKIDATA
2014-04-22  8:23 ` Richard Purdie [this message]
2014-04-22  9:08   ` Richard Leitner - SKIDATA
2014-04-22  9:30     ` Richard Purdie
2014-04-22 11:34 ` Nicolas Dechesne
2014-04-22 12:11   ` Richard Leitner - SKIDATA

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=1398154982.16672.25.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Richard.Leitner@skidata.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.