All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Guillaume Fournier" <gfournier@brioconcept.com>
To: "'Wally Yeh'" <wally.yeh@atrustcorp.com>,
	"'meta-freescale'" <meta-freescale@yoctoproject.org>
Subject: Re: Unable to get u-boot running on i.MX6 SABRE for Smart Devices Eval Board
Date: Wed, 5 Nov 2014 10:24:33 -0500	[thread overview]
Message-ID: <008801cff90c$9a3397f0$ce9ac7d0$@brioconcept.com> (raw)
In-Reply-To: <CANdq1hLKPhkzCxEBQz8mbU_U0SuQq=j_0BhZWSsrneTdx5dJaQ@mail.gmail.com>

>>I want to get a working cross-compiling toolchain so I can build u-boot and the
>>kernel outside of Yocto.  I understand the subject of this post is therefore a bit misleading since u-
>>boot does boot when using Yocto build output...  It just doesn't when using the cross-compiling toolchain.
>
>Um... sometimes I just download the cross-compiler from linaro homepage
>and build the u-boot, works fine as usual. if you want build your own cross-compiler
>from yocto, just bitbake meta-toolchain, and execute <yocto path>/build/tmp/deploy
>/sdk/poky-eglibc-i686-meta-toolchain-cortexa9hf-vfp-neon-toolchain-1.6.1.sh

I just did that (bitbake meta-toolchain + install script) and I can get u-boot to build without errors but the u-boot.bin is not booting on the target.

>I even use a sfp cross-compiler to build u-boot and booting hfp uImage, and still can boot into linux system.
I downloaded the little-endian linaro toochain binaries v4.9 (gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux.tar.xz) and installed it.  I was able to compile u-boot without errors.  When I try the output u-boot.bin, it does not boot on the target.

I'm starting to think something with my u-boot configuration is wrong.  Could the "make LDFLAGS="" CC="$CC" mx6dlsabresd_config" be the culprit ?

Guillaume



  reply	other threads:[~2014-11-05 15:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 22:44 Unable to get u-boot running on i.MX6 SABRE for Smart Devices Eval Board Guillaume Fournier
2014-11-05  0:03 ` Fabio Estevam
2014-11-05 14:38   ` Guillaume Fournier
2014-11-05 14:52     ` Wally Yeh
2014-11-05 15:24       ` Guillaume Fournier [this message]
2014-11-05 14:56     ` Daiane Angolini
2014-11-05 15:37       ` Guillaume Fournier
2014-11-05 15:45         ` Otavio Salvador
2014-11-05 16:05           ` Guillaume Fournier
2014-11-05 15:42     ` Otavio Salvador
2014-11-05 15:50       ` Guillaume Fournier
2014-11-05 15:54         ` Otavio Salvador
2014-11-05 15:59           ` Wally Yeh
2014-11-05 16:15           ` Guillaume Fournier
2014-11-05 16:21             ` Gary Thomas
2014-11-05 16:40               ` Otavio Salvador
2014-11-05 16:41               ` Guillaume Fournier
2014-11-05  0:23 ` Eric Bénard
2014-11-05 14:51   ` Guillaume Fournier
2014-11-05 17:25     ` Eric Bénard
  -- strict thread matches above, loose matches on Subject: below --
2014-11-05 20:43 Guillaume Fournier
2014-11-05 21:04 ` Otavio Salvador
2014-11-05 21:50   ` Guillaume Fournier
2014-11-06 17:31 Guillaume Fournier
2014-11-06 17:47 ` Otavio Salvador
2014-11-06 17:53   ` Gary Thomas
2014-11-06 17:56     ` Otavio Salvador

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='008801cff90c$9a3397f0$ce9ac7d0$@brioconcept.com' \
    --to=gfournier@brioconcept.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=wally.yeh@atrustcorp.com \
    /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.