From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Load Address and EntryPoint for Kernel
Date: Sun, 28 Oct 2012 21:21:50 +0100 [thread overview]
Message-ID: <20121028212150.0ff4c78b@skate> (raw)
In-Reply-To: <508D6874.609@googlemail.com>
Dear Carsten Schoenert,
On Sun, 28 Oct 2012 18:16:36 +0100, Carsten Schoenert wrote:
> Hopefully I have taken the complete one from the original ... :/
> This complete git repo can be found here.
> http://git.coolstreamtech.de/?p=cst-public-linux-kernel.git;a=shortlog;h=refs/heads/2.6.34.13-cnxt
>
> The related kernel patches I placed under
> board/coolstream/hdx/kernel-2.6.34-patches
> The config right in board/coolstream/hdx/kernel2.6.34.13.config
The kernel sources clearly indicate that the entry point should be
0x48000. So it seems like your patches haven't been applied, or your
kernel has been badly configured, or something like that.
> > Please post your Buildroot .config and kernel .config file and more
> > details about what your hardware platform is.
>
> The platform is a ARMv6 based Settopbox with a SoC from Nexperia
> (cx2450). There are closed kernel modules that have to be used, so most
> parts of the kernel config depended on this, but some options are
> configurable without to recompile this closed source parts.
>
> I configured BR to build a GCC 4.7.1 with crosstool-ng, after some fine
> tuning this works.
>
> My BR config looks like this.
> > carsten at wheezy:~/gitprojects/buildroot [arm] $ cat configs/cst_hdx_2.6.34.13_defconfig
> > BR2_arm=y
> > BR2_CCACHE=y
> > BR2_TOOLCHAIN_CTNG=y
> > BR2_TOOLCHAIN_CTNG_eglibc=y
> > BR2_TOOLCHAIN_CTNG_CONFIG="board/coolstream/hdx/ct_ng_config"
> > BR2_TOOLCHAIN_CTNG_CXX=y
> > BR2_PACKAGE_BUSYBOX_CONFIG="board/coolstream/hdx/busybox-1.20.2.config"
> > BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y
> > BR2_PACKAGE_AUTOMAKE=y
> > BR2_TARGET_UBOOT=y
> > BR2_TARGET_UBOOT_BOARDNAME="coolstream_hdx"
> > BR2_TARGET_UBOOT_CUSTOM_TARBALL=y
> > BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION="http://ftp.denx.de/pub/u-boot/u-boot-2009.03.tar.bz2"
> > BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR="board/coolstream/hdx/u-boot"
> > BR2_LINUX_KERNEL=y
> > BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
> > BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="http://www.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6.34/linux-2.6.34.13.tar.bz2"
> > BR2_LINUX_KERNEL_PATCH="board/coolstream/hdx/linux-2.6.34-patches"
> > BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
> > BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/coolstream/hdx/kernel-2.6.34.13.config"
> > BR2_LINUX_KERNEL_INSTALL_TARGET=y
>
> The kernel config is appended.
>
> If something is missing then just let me know.
Either pastebin the entire build log (from scratch), or post all the
patches and configuration files needed to produce the problem.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-10-28 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 16:20 [Buildroot] Load Address and EntryPoint for Kernel Carsten Schoenert
2012-10-28 16:43 ` Thomas Petazzoni
2012-10-28 17:16 ` Carsten Schoenert
2012-10-28 20:21 ` Thomas Petazzoni [this message]
2012-11-16 20:36 ` Carsten Schoenert
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=20121028212150.0ff4c78b@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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