From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Right board to use -- buildroot begniers
Date: Tue, 8 Sep 2015 15:26:22 +0200 [thread overview]
Message-ID: <20150908152622.52c11f06@free-electrons.com> (raw)
In-Reply-To: <CAKpDV8tWg7ZU6UUZSvp=jM6CM2KnTSNvzy6cfx0OhkCMY+gxwg@mail.gmail.com>
Dinesh,
Could you improve a bit the way you quote text when replying to
e-mails? Your quoting style makes it quite hard to reply.
On Tue, 8 Sep 2015 18:04:28 +0530, Dinesh Guleria wrote:
> >> don't need that.
> But seggers jlink(i.e jtag tool) can be used as an alternative tool to burn
> uboot , kernel to NAND of this board right ?
Yes, probably.
> >> The Atmel SoCs have a built-in "monitor" that you
> can talk to over the USB device port. It requires a tool called SAM-BA.
> Ok great. So i need only a hardware USB cable for this no external hardware
> device right ?
Yes, correct.
> So i can burn uboot, kernel & rfilesystem to the board NAND flash using usb
> cable & SAM-BA software tool, right ?
Absolutely.
> >> you're looking at beginning with the Atmel Xplained, you can follow
> the slides/labs
> Thanks for pointing me to such a wonderful material, it means a lot to me.
> Do these two below link point to same board which is mentioned on your site
> ?
> http://www.element14.com/community/mobile/mobile-access.jspa#jive-content?content=%2Fapi%2Fcore%2Fv3%2Fcontents%2F625493
>
> http://www.atmel.com/tools/ATSAMA5D3-XPLD.aspx
Yes, it is this board.
> >> Atmel's plan is to deprecate their Buildroot fork
> >> It is deprecated, this will be announced this week.
> I did not understood this statement on one hand you are saying buildroot
> supports Atmel SAM soc & on other hand you are saying support will be
> depreciated from next week.
Atmel used to have a fork of Buildroot with the support for their
boards. Instead of having such a fork, they decided to now support
their boards directly in the official Buildroot. Their fork is
therefore no longer necessary and will be deprecated. Just use the
official Buildroot.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-09-08 13:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 12:36 [Buildroot] Right board to use -- buildroot begniers Dinesh Guleria
2015-09-07 19:38 ` Arnout Vandecappelle
2015-09-08 2:13 ` Dinesh Guleria
2015-09-08 7:17 ` Arnout Vandecappelle
2015-09-08 8:56 ` Dinesh Guleria
2015-09-08 10:00 ` Thomas Petazzoni
2015-09-08 16:16 ` Luca Ceresoli
2015-09-08 18:03 ` Dinesh Guleria
2015-09-12 11:11 ` Dinesh Guleria
2015-09-13 11:51 ` Dinesh Guleria
2015-09-08 10:01 ` Thomas Petazzoni
2015-09-08 11:28 ` Alexandre Belloni
2015-09-08 12:34 ` Dinesh Guleria
2015-09-08 13:26 ` Arnout Vandecappelle
2015-09-08 13:26 ` Thomas Petazzoni [this message]
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=20150908152622.52c11f06@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