From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [BuildRoot] at91sam9x5ek_defconfig not booting
Date: Fri, 13 Oct 2017 15:50:28 +0200 [thread overview]
Message-ID: <20171013155028.77a75504@windsurf.lan> (raw)
In-Reply-To: <CAHnuF33Z3qQeVr5o1q=K1+OgMDCEhheOQm9qCGO1TpPZrjbeVw@mail.gmail.com>
Hello,
On Fri, 13 Oct 2017 09:44:06 -0300, Alejandro Ariel Fachini wrote:
> Thanks For your help. I used the tag 2017.03 and Still got the same Result
There is no 2017.03 tag, so this is not possible.
> in fact the first thing i did was use the latest version of BuildRoot.
> If i understand correctly:
> At first Boot after Install binaries i should set environment variables,
No, the default environment variables set inside the U-Boot binary
should be good enough.
> How do I make the boot into Kernel auomatic? I believe all tthis is U-Boot
> Related? If thats so just tell me and i wont bother anymore.
This is all U-Boot related of course. Please read the materials that I
pointed in my previous e-mail. And as I said, the default U-Boot
environment should automatically load and boot a Linux kernel, if I
remember correctly.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-13 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 19:11 [Buildroot] [BuildRoot] at91sam9x5ek_defconfig not booting Alejandro Ariel Fachini
2017-10-12 20:01 ` Thomas Petazzoni
[not found] ` <CAHnuF30iK6AQeoZBn3f35q1B5Ff+SG9uGUywzKH--wPp-THVVg@mail.gmail.com>
2017-10-13 12:44 ` [Buildroot] Fwd: " Alejandro Ariel Fachini
2017-10-13 13:50 ` Thomas Petazzoni [this message]
2017-10-13 18:36 ` [Buildroot] " Alejandro Ariel Fachini
2017-10-18 20:21 ` Alejandro Ariel Fachini
2017-10-18 21:01 ` Thomas Petazzoni
2017-10-19 12:45 ` Alejandro Ariel Fachini
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=20171013155028.77a75504@windsurf.lan \
--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 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.