From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] booting JFFS2 or UBIFS created with buildroot
Date: Mon, 21 Feb 2011 23:42:07 +0100 [thread overview]
Message-ID: <20110221234207.53607d77@surf> (raw)
In-Reply-To: <AANLkTik=ec9qxhe9Cwv-ZHMoLAD5Wup6=WuCUbMgkXm0@mail.gmail.com>
Hello,
On Mon, 21 Feb 2011 14:29:35 -0800
Charles Krinke <charles.krinke@gmail.com> wrote:
> First of all, I appreciate greatly the time you are taking to discuss this
> issue. Thank you very much.
You're welcome!
> My flash layout is:
>
> 0xFE340000 to top of flash rootfs.jffs2 programmed here
> 0xFE120000 uImage here
> 0xFE080000 deviceTree here (1 sector)
> 0xFE000000 u-boot here
>
> Now with that said, here are my recipes assuming I counted the number of
> 128k sectors properly for the offset to get to JFFS2 in the bootargs line.
Ok, sounds correct.
> Linux version 2.6.36.1 (ckrinke at Yin) (gcc version 4.3.5 (Buildroot 2010.11)
> ) #1 Thu Feb 17 19:04:48 PST 2011
The problem seems to be in your kernel: there are no lines indicating
that a MTD device has been detected. So maybe the MTD device is not
described in your device tree, or improperly described, or the
corresponding kernel driver is missing.
Here are the messages you typically see when a NAND device is being
detected by the kernel (on an ARM AT91 platform) :
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 464 at 0x03a00000
Bad eraseblock 1694 at 0x0d3c0000
Bad eraseblock 3101 at 0x183a0000
Bad eraseblock 3199 at 0x18fe0000
Bad eraseblock 3866 at 0x1e340000
Bad eraseblock 5478 at 0x2acc0000
Bad eraseblock 6473 at 0x32920000
Bad eraseblock 6606 at 0x339c0000
3 cmdlinepart partitions found on MTD device atmel_nand
Creating 3 MTD partitions on "atmel_nand":
0x00000000-0x00100000 : "bootloader"
0x00100000-0x00400000 : "kernel"
0x00400000-0x40000000 : "rootfs"
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-02-21 22:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 20:53 [Buildroot] booting JFFS2 or UBIFS created with buildroot Charles Krinke
2011-02-21 21:19 ` ANDY KENNEDY
2011-02-21 21:30 ` Charles Krinke
2011-02-21 21:40 ` Thomas Petazzoni
2011-02-21 21:53 ` Charles Krinke
2011-02-21 22:09 ` Thomas Petazzoni
2011-02-21 22:29 ` Charles Krinke
2011-02-21 22:42 ` Thomas Petazzoni [this message]
2011-02-21 23:12 ` Charles Krinke
2011-02-21 23:31 ` Yann E. MORIN
2011-02-21 23:29 ` ANDY KENNEDY
2011-02-21 23:35 ` Charles Krinke
2011-02-22 8:08 ` Guillaume Gardet
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=20110221234207.53607d77@surf \
--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