mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Paul B. Henson" <henson@acm.org>
To: barebox@lists.infradead.org
Subject: Re: imx23evk NAND support
Date: Tue, 15 Jan 2013 12:30:08 -0800	[thread overview]
Message-ID: <50F5BC50.50607@acm.org> (raw)
In-Reply-To: <201301131147.10661.jbe@pengutronix.de>

On 1/13/2013 2:47 AM, Juergen Beisert wrote:

> IIRC ivt/non-ivt is relevant for the i.MX28 firmware, not for
> i.MX23.

Ah, okay. I actually have an mx28 eval board too, but started with the 
23 and haven't looked at the 28 board yet. I'm using the freescale tool 
to generate the bootstream, which knows it's intended for an i.MX23, 
you'd think (or wish I suppose) it would be smart enough not to generate 
the ivt versions if they're not relevant for that architecture.

> On the other hand, for some i.MX23 based systems the encryption must
> be enabled for the bootstream, but with an empty key.

The bootstream file seems to work fine from SD. I don't think it 
requires a different format for burning to NAND vs booting from SD, so I 
think I have a good file. The kobs-ng tool that burns the bootstream to 
NAND claims it is a valid image and that it is successfully burned, but 
then it just won't boot :(. I'd be interested in trying to burn it from 
barebox to see if that makes a difference, but a prerequisite for that 
is getting the NAND to work in barebox <sigh>.

It looks like the i.MX23/28 NAND support was ported from u-boot? u-boot 
doesn't actually support the i.MX23 board at the moment. There's 
somebody working on that, but they told me that the 23 and 28 NAND 
implementation is a bit different, and their current support for the 28 
needs to be updated to work with the 23. Perhaps the barebox NAND driver 
only works with the 28 board as well? I'll give it a try on that board 
and see what happens.

Has anyone successfully accessed the NAND on an i.MX23 board with barebox?


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2013-01-15 20:30 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
2013-01-13 10:47   ` Juergen Beisert
2013-01-15 20:30     ` Paul B. Henson [this message]

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=50F5BC50.50607@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