From: "Paul B. Henson" <henson@acm.org>
To: barebox@lists.infradead.org
Subject: Re: imx23evk NAND support
Date: Sat, 12 Jan 2013 21:19:51 -0800 [thread overview]
Message-ID: <50F243F7.4080009@acm.org> (raw)
In-Reply-To: <50F228E8.8050000@acm.org>
On 1/12/2013 7:24 PM, Paul B. Henson wrote:
> My understanding is that the SD card and the NAND chip cannot be used at
> the same time due to a pin conflict.
Hmm, it seems what I read on this wasn't entirely correct. I ended up
booting the BSP linux kernel and root file system off of SD, and it was
able to access the NAND device while simultaneously using the SD device
(as the root filesystem source) so there doesn't seem to be any inherent
hardware limitation preventing bareboot from accessing it.
Just for fun, I tried to use the kobs-ng freescale tool from within the
linux environment to burn the bareboot bootstream to NAND. However,
after trying to boot, I receive the error code 0x80501003 from the ROM
loader, which evidently indicates "The file signature or file version is
incorrect". The exact same bootstream on an SD card boots fine, so I
don't think there's anything wrong with it. I also tried to burn the BSP
linux kernel bootstream, with the same result. (Side question, what's
the difference in the bootstream files that contain "ivt" in the
filename? I used the non-ivt versions on SD, I tried both on NAND with
neither working).
The board came from the factory with a working kernel on NAND, so I know
it can work. Given I'm using the freescale supplied linux environment
and their nand bootstream burning tool you'd think it would be fairly
straightforward…
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-01-13 5:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 3:24 Paul B. Henson
2013-01-13 5:19 ` Paul B. Henson [this message]
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=50F243F7.4080009@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