From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Newbie: AT91SAM9260 NAND Boot
Date: Tue, 23 Feb 2010 23:32:21 +0000 (UTC) [thread overview]
Message-ID: <hm1oi5$1dg$1@dough.gmane.org> (raw)
In-Reply-To: 815f0bd71002231515m11ed502bxa3268af876dcdafb@mail.gmail.com
On Wed, Feb 24, 2010 at 10:15:18AM +1100, Roo wrote:
>>> I am new to buildroot and have been given a AT91SAM9260 SOM to
>>> work with. The latest buildroot does not appear to include a
>>> defconfig for a NAND boot system.
>>
>> Can you explain what a "NAND boot system" is?
>>
>> When I boot an AT91SAM9xxx from NAND, I tell buildroot to
>> build a JFFS2 root image, a uImage kernel with MTD/JFFS2
>> support, put the resulting kernel and root image into NAND,
>> and configure U-Boot to boot from NAND.
>
> I believe that I had some of the terminology wrong.
>
> I would like a jffs (or a readonly FS) to reside in NAND as
> you had described, but I was confused by the
> dataflash/dataflashcard terminology. I thought it was
> referring to a SD or micro SD card and I do not want the
> rootfs or kernel to reside on the card.
Dataflash is a serial NOR-flash part that's attached to an SPI
interface. It's sort of similar to an SD-card, but the
interface/protocol is a little different.
> My understanding now is that configurations relate to where
> the bootloader resides rather than where the rootfs resides. I
> am little embarrassed that I didn't realise this earlier and
> if I am right this just got easier. :)
You're probably right. Buildroot can build U-Boot and, IIRC,
also the low-level SAM9 bootloader: it's what is initially
loaded by the MCU's built-in bootloader from somewhere (NAND,
NOR, SDcard, dataflash) into internal SRAM and run -- it
enables SDRAM, and then loads U-Boot from somewhere (same
choices as before) into SDRAM, and then runs U-Boot. U-Boot
then loads a kernel image into SDRAM (and optionally loads a
rootfs into SDRAM), and boots the kernel.
And there's no rule that says the low-level SAM9 bootloader,
U-Boot, the kernel, and the rootfs can't all be on different
media.
I've never selected either the bootloader or U-Boot in
buildroot, so I don't know what configuration options are
available for them -- but I would guess that support for the
various boot media are configurable.
--
Grant Edwards grante Yow! World War III?
at No thanks!
visi.com
next prev parent reply other threads:[~2010-02-23 23:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 3:51 [Buildroot] Newbie: AT91SAM9260 NAND Boot Roo
2010-02-23 15:40 ` Grant Edwards
2010-02-23 23:15 ` Roo
2010-02-23 23:32 ` Grant Edwards [this message]
2010-02-23 22:51 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2010-02-23 21:22 Sagaert Johan
2010-02-23 23:30 ` Roo
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='hm1oi5$1dg$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.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