From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Help for another newbie, AT91sam9x25 incorrect defconfig or incorrect rootfs.ubi
Date: Sun, 24 May 2015 13:02:50 +0200 [thread overview]
Message-ID: <20150524130250.36ebd47d@free-electrons.com> (raw)
In-Reply-To: <1432452387471-101939.post@n4.nabble.com>
Dear Ted Salazar,
On Sun, 24 May 2015 00:26:27 -0700 (PDT), Ted Salazar wrote:
> 1. Built the At91Bootstrap Ver 3.7.2:
> location: tsalazar at Ubuntu14-64:~/at91bootstrap/binaries/
> Output file: at91sam9x5ek-nandflashboot-uboot-3.7.2.bin
>
> 2. Built Uboot ver 2015.01:
> location: tsalazar at Ubuntu14-64:~/u-boot-at91/
> Output file: u-boot.bin
>
> 3. Built the Kernel ver 3.6.9 (I plan to upgrade to 3.18 but I'm trying to
> duplicate a working demo first)
> location: tsalazar at Ubuntu14-64:~/linux-at91/arch/arm/boot/
> Output file: at91sam9x25ek.dtb
> location: tsalazar at Ubuntu14-64:~/linux-at91/arch/arm/boot/
> Output file: zImage
Why do you build AT91Bootstrap, U-Boot and the kernel? Buildroot will
build them for you, no need to build these manually.
> 4. Built buildroot-at91 ver 2014.05 ( This is where I have all my problems)
>
> https://github.com/linux4sam/buildroot-at91/tree/buildroot-2014.05-at91/configs
This is the Atmel fork of Buildroot. You're contacting the official
Buildroot mailing list, we only support the mainline Buildroot.
You should rather try the updated Atmel defconfigs recently posted by
Alexandre Belloni (they are only available in the Buildroot patchwork
for the moment, since they haven't been applied yet).
> Q1) Does someone know where I can get an at91sam9x25ek_defconfig file for
> BuildRoot-at91 Ver 2014.05?
No, because you're talking about an Atmel fork of Buildroot, and this
mailing list is only supporting the official Buildrot.
You should apply the patch http://patchwork.ozlabs.org/patch/473928/ on
the mainline Buildroot and use the at91sam9x5ek_defconfig. Also, make
sure to apply http://patchwork.ozlabs.org/patch/473935/ and read the
readme.txt file. These patches should be applied to the next Buildroot
version.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-05-24 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 7:26 [Buildroot] Help for another newbie, AT91sam9x25 incorrect defconfig or incorrect rootfs.ubi Ted Salazar
2015-05-24 11:02 ` Thomas Petazzoni [this message]
2015-05-25 2:06 ` Ted Salazar
2015-05-25 14:38 ` Alexandre Belloni
2015-05-25 21:18 ` Ted Salazar
[not found] ` <C7F5ED2AEEF9C0468B6F205055DC2A1D23DC4424DF@ITSVLEX06.it.maxim-ic.internal>
2015-05-27 6:58 ` [Buildroot] Newbie help, AT91sam9x25 patch Installation Questions Ted Salazar
2015-05-27 9:58 ` Alexandre Belloni
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=20150524130250.36ebd47d@free-electrons.com \
--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