From: "Paul B. Henson" <henson@acm.org>
To: barebox@lists.infradead.org
Subject: imx23evk NAND support
Date: Sat, 12 Jan 2013 19:24:24 -0800 [thread overview]
Message-ID: <50F228E8.8050000@acm.org> (raw)
I'm working with a freescale i.MX23EVK board prototyping a project that
is going to need to boot from NAND. I'm trying to get barebox installed
on the NAND chip on this board, with the next step being getting a linux
kernel and filesystem on NAND as well.
I've compiled barebox from git as of today, and successfully booted it
from SD and USB, but have been unable to get the NAND device recognized.
Booting from SD with the mci driver enabled:
devices:
`---- platform
`---- stm_serial0
`---- cs0
`---- mem0
`---- 0x00000000-0x01ffffff: /dev/ram0
`---- mem1
`---- 0x00000000-0xfffffffe: /dev/mem
`---- mxs_mci0
`---- mci0
`---- fs
`---- ramfs0
`---- devfs0
`---- global
drivers:
stm_serial
ramfs
devfs
mxs_nand
mci
mxs_mci
mem
Booting from SD without the mci driver:
devices:
`---- platform
`---- stm_serial0
`---- cs0
`---- mem0
`---- 0x00000000-0x01ffffff: /dev/ram0
`---- mem1
`---- 0x00000000-0xfffffffe: /dev/mem
`---- mxs_mci0
`---- fs
`---- ramfs0
`---- devfs0
`---- global
drivers:
stm_serial
ramfs
devfs
mxs_nand
mem
In both cases, it seems to find the mci device, but not the nand device.
(On a side note, running mci0.probe=1 with the mci driver enabled
appears to completely lock up the board).
My understanding is that the SD card and the NAND chip cannot be used at
the same time due to a pin conflict. Considering the possibility that
perhaps the NAND cannot be accessed if booting from SD, I tried booting
via USB, with the same result:
devices:
`---- platform
`---- stm_serial0
`---- cs0
`---- mem0
`---- 0x00000000-0x01ffffff: /dev/ram0
`---- mem1
`---- 0x00000000-0xfffffffe: /dev/mem
`---- mxs_mci0
`---- fs
`---- ramfs0
`---- devfs0
`---- global
drivers:
stm_serial
ramfs
devfs
mxs_nand
mem
The SD card device is found, but not the nand device.
Am I missing something? Given its inclusion in barebox, I'm assuming
*somebody* has gotten the i.mx23 NAND driver working :). Any assistance
much appreciated, thanks.
I wonder why they didn't hook the SD interface up to SSP1 rather than
SSP2 to avoid the NAND conflict. It looks like you can't use the SD
device and the ethernet device simultaneously either :(.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2013-01-13 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 3:24 Paul B. Henson [this message]
2013-01-13 5:19 ` Paul B. Henson
2013-01-13 10:47 ` Juergen Beisert
2013-01-15 20:30 ` Paul B. Henson
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=50F228E8.8050000@acm.org \
--to=henson@acm.org \
--cc=barebox@lists.infradead.org \
/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