From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Right board to use -- buildroot begniers
Date: Mon, 7 Sep 2015 21:38:14 +0200 [thread overview]
Message-ID: <55EDE7A6.4060902@mind.be> (raw)
In-Reply-To: <CAKpDV8sGQrmePsmbhrQo0YMGTLLTZb4Rsq90W3Y4nfMZTrcS+A@mail.gmail.com>
On 07-09-15 14:36, Dinesh Guleria wrote:
> Hi,
>
> I am new to buildroot & looking forward to try my hands on creating :--:
> linux Kernel
> Rfile system
> Uboot
>
> For embedded system.
>
> I want to know from your experience which board shall i go for :--
> Raspberrypi b version
Problem with Raspberry Pi is that it's rather difficult to understand the SoC,
and its software support is pretty unusual (i.e., far from upstream).
> AT91SAM9260
That's a SoC, not a board. There are a bunch of devboards with the processor,
but can you still get them? Probably the at91sam9g45m10ek or
atmel_sama5d3_xplained are a better fit.
The MIPS creator CI20 is also nice. But that's not ARM, of course.
> What i think as something is already existing in buildroot & linux kernel for
> support of these two boards, so its good for freshers to learn all these process
> on these boards.
>
> Means 32 bit controller whose specs are clearly define so that one can try hand
> on creating/configuring memory drivers for sdram or Nand , creating device
> drivers , configuring uboot & architecture specific files, porting linux &
> rfsystem & uboot made by yourself ?
These things are _not_ something I would advise for an absolute beginner.
Experienced consultants like me plan two to four weeks of full-time work for
porting everything from a devboard to a custom board. So starting from scratch
is definitely an ambitious goal.
Start out with just building and installing the boot loader, kernel and rootfs
for which support already exists. Then maybe you can bump the U-Boot and kernel
version (and contribute patches, of course).
Anyway, any devboard you can get probably already has U-Boot and kernel
support, otherwise they wouldn't be able to sell it. So unless you're developing
a custom board, re-implementing those from scratch is just duplicate work.
Regards,
Arnout
>
> Regards,
> Katoch
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-09-07 19:38 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 [this message]
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
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=55EDE7A6.4060902@mind.be \
--to=arnout@mind.be \
--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