From: "Guillaume Fournier" <gfournier@brioconcept.com>
To: <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 15:43:31 -0500 [thread overview]
Message-ID: <001001cff939$297f3b90$7c7db2b0$@brioconcept.com> (raw)
To try and figure out where the problem resides, I started from scratch.
1) got latest BSP: repo init -u
https://github.com/Freescale/fsl-community-bsp-platform -b dizzy
2) modified local.conf so MACHINE is imx6dlsabresd
3) On "bitbake meta-toolchain", I got these QA warnings:
WARNING: QA Issue: gcc-cross-canadian-arm: found library in wrong location:
/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gnuea
bi/gcc/arm-poky-linux-gnueabi/4.9.1/liblto_plugin.so
gcc-cross-canadian-arm: found library in wrong location:
/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gnuea
bi/gcc/arm-poky-linux-gnueabi/4.9.1/liblto_plugin.so.0.0.0
gcc-cross-canadian-arm: found library in wrong location:
/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gnuea
bi/gcc/arm-poky-linux-gnueabi/4.9.1/liblto_plugin.so.0 [libdir]
I'm not sure these are relevant to my problem so I kept on going.
4) got latest u-boot: git clone https://github.com/Freescale/u-boot-fslc.git
5) started a fresh shell, ran toolchain environment script, cd to
u-boot-fslc
6) make LDFLAGS="" CC="$CC" mx6dlsabresd_config
7) make LDFLAGS="" CC="$CC" u-boot.imx
8) Programmed u-boot.imx on SD card: cfimager -f u-boot.imx -raw -offset
1024 -d d
9) Try to boot target -> not booting, no UART output
Could the problem be related to the Device Configuration Data since u-boot
spits out something on the UART pretty early ?
Guillaume Fournier
Brioconcept Consulting Inc.
next reply other threads:[~2014-11-05 20:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 20:43 Guillaume Fournier [this message]
2014-11-05 21:04 ` Unable to get u-boot running on i.MX6 SABRE for Smart Devices Eval Board Otavio Salvador
2014-11-05 21:50 ` Guillaume Fournier
-- strict thread matches above, loose matches on Subject: below --
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
2014-11-04 22:44 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
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
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='001001cff939$297f3b90$7c7db2b0$@brioconcept.com' \
--to=gfournier@brioconcept.com \
--cc=meta-freescale@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.