All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kövesdi György" <kgy@teledigit.eu>
To: beagleboard@googlegroups.com, poky@yoctoproject.org,
	 angstrom-distro-devel@linuxtogo.org
Subject: Building kernel for Beagleboard-C4
Date: Thu, 25 Dec 2014 12:46:18 +0100	[thread overview]
Message-ID: <549BF90A.40109@teledigit.eu> (raw)

Hi,

I tried to build image for my Beagleboard-C4 using the recent version of 
Angstrom and Yoctoproject/Poky, but got the following problem:
I compiled all kernels I found compatible with my board: 3.2, 3.3, 3.4, 
3.7, 3.8, 3.14, including mainline and ti-staging, but none of them 
running on my board. The result is the same for all:

--------------- 8< -------------------
...
Loading file "/boot/uImage" from mmc device 0:2 (xxa2)
3394824 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 80200000 ...
    Image Name:   Linux-3.3.7
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    3394760 Bytes = 3.2 MiB
    Load Address: 80008000
    Entry Point:  80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
--------------- 8< -------------------

No more output, heartbeat LED is not blinking.

Except the version 3.14.25: it runs perfectly, but I could not compile 
the package omap3-sgx-modules because it seems incompatible with this 
kernel (4.05, 4.09, 5.01 versions). I can compile it with older kernels 
(using the 4.09 version) but they do not run at all.

How can I build a working kernel+omap3-sgx-modules? Some years ago it 
worked for me.

Thanx in advance
Gyorgy Kovesdi



             reply	other threads:[~2014-12-25 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-25 11:46 Kövesdi György [this message]
2014-12-27  8:33 ` [Angstrom-devel] Building kernel for Beagleboard-C4 Koen Kooi

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=549BF90A.40109@teledigit.eu \
    --to=kgy@teledigit.eu \
    --cc=angstrom-distro-devel@linuxtogo.org \
    --cc=beagleboard@googlegroups.com \
    --cc=poky@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.