From: Vanalme Filip <F.Vanalme@TELEVIC.com>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: NAND flash
Date: Mon, 21 Mar 2011 16:19:03 +0100 [thread overview]
Message-ID: <6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3BF5211@SRV-VS06.TELEVIC.COM> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1515 bytes --]
Hi,
On our own i.MX27 based boards, we have Micron NAND flash memory (MT29F2G08ABBEAH4). Besides the BI-swapping problem for 2K NAND flashes, I can see that this chip needs an initial reset command before it becomes operational. This is something that has to be done in the early boot code, so before loading the first page of bootloader code (the reset should be sent before the first page of code can be read from flash).
From Freescale doc, I found that we have to blow certain fuses to make the i.MX27 boot from internal ROM. According to the document, the ROM code takes care about the initial reset before loading the first page of code from the NAND flash.
I'm however a little concerned about this figure in the document :
[cid:image002.png@01CBE7E3.B1A2CCA0]
If I understand well, this should be the structure of the 2K NFC buffer when booting from internal ROM. I don't think this will be the structure when loading the first page of Barebox code, correct ?
Anyone familiar with this Micron specific flash problem ? And the consequences for Barebox ? Do we have to make modifications in the Barebox code to tackle this ?
(because the Freescale document is rather WinCE related, I'm not sure this also applies to Barebox/Linux based systems...)
I hope we didn't make a bad choice of NAND flash in combination with i.MX27... ? ;-)
Best Regards,
Filip
(Btw : anyone can tell me what CSF and DCD stand for... ? Did not find any explanations in the i.MX27 reference manual yet)
[-- Attachment #1.1.2: Type: text/html, Size: 6384 bytes --]
[-- Attachment #1.2: image002.png --]
[-- Type: image/png, Size: 51367 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2011-03-21 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 15:19 Vanalme Filip [this message]
2011-03-21 16:11 ` Eric Bénard
2011-03-22 8:41 ` Vanalme Filip
2011-03-22 9:04 ` Eric Bénard
2011-03-22 12:21 ` Vanalme Filip
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=6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3BF5211@SRV-VS06.TELEVIC.COM \
--to=f.vanalme@televic.com \
--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