From: John Rigby <jrigby@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] Freescale NFC NAND driver
Date: Wed, 05 Nov 2008 11:16:16 -0700 [thread overview]
Message-ID: <4911E2F0.3040602@freescale.com> (raw)
In-Reply-To: <48337.96276.qm@web51007.mail.re2.yahoo.com>
Fabio Estevam wrote:
>
>> +#define NFC_BUF_ADDR (NFC_REG_BASE + 0x1E04)
>> +#define NFC_FLASH_ADDR (NFC_REG_BASE + 0x1E06)
>> +#define NFC_FLASH_CMD (NFC_REG_BASE + 0x1E08)
>> +#define NFC_CONFIG (NFC_REG_BASE + 0x1E0A)
>> +#define NFC_ECC_STATUS1 (NFC_REG_BASE + 0x1E0C)
>> +#define NFC_ECC_STATUS2 (NFC_REG_BASE + 0x1E0E)
>> +#define NFC_SPAS (NFC_REG_BASE + 0x1E10)
>> +#define NFC_WRPROT (NFC_REG_BASE + 0x1E12)
>> +#define NFC_NF_WRPRST (NFC_REG_BASE + 0x1E18)
>> +#define NFC_CONFIG1 (NFC_REG_BASE + 0x1E1A)
>> +#define NFC_CONFIG2 (NFC_REG_BASE + 0x1E1C)
>> +#define NFC_UNLOCKSTART_BLKADDR0 (NFC_REG_BASE + 0x1E20)
>> +#define NFC_UNLOCKEND_BLKADDR0 (NFC_REG_BASE + 0x1E22)
>> +#define NFC_UNLOCKSTART_BLKADDR1 (NFC_REG_BASE + 0x1E24)
>> +#define NFC_UNLOCKEND_BLKADDR1 (NFC_REG_BASE + 0x1E26)
>> +#define NFC_UNLOCKSTART_BLKADDR2 (NFC_REG_BASE + 0x1E28)
>> +#define NFC_UNLOCKEND_BLKADDR2 (NFC_REG_BASE + 0x1E2A)
>> +#define NFC_UNLOCKSTART_BLKADDR3 (NFC_REG_BASE + 0x1E2C)
>> +#define NFC_UNLOCKEND_BLKADDR3 (NFC_REG_BASE + 0x1E2E)
>>
>
> On MX31 and also according to the current MPC5121 Reference Manual on the web the offsets of the registers above seem to have an extra offset of 0x1000.
>
> MX31 and MPC5121 manuals state the following offsets:
>
> #define NFC_BUF_ADDR (NFC_REG_BASE + 0xE04)
> #define NFC_FLASH_ADDR (NFC_REG_BASE + 0xE06)
> ...
>
> Is there a newer MPC5121 manual that changed the NAND registers offsets?
>
As the patch states this is for silicon rev2. One of the changes with
rev2 was support for 4k nand so the number of 512 byte buffers is now 8
instead of 4 so everything else has moved up by 2K (0x1000).
The rev2 manual is available online here:
http://www.freescale.com/files/32bit/doc/ref_manual/MPC5121ERM.pdf
> Regards,
>
> Fabio Estevam
>
>
>
>
>
next prev parent reply other threads:[~2008-11-05 18:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 2:02 [U-Boot] [PATCH v3] Freescale NFC NAND driver John Rigby
2008-11-05 13:27 ` Fabio Estevam
2008-11-05 18:16 ` John Rigby [this message]
2008-11-05 23:06 ` Scott Wood
2009-06-04 13:18 ` Stefan Roese
2009-06-04 15:34 ` John Rigby
2009-06-04 16:08 ` Scott Wood
2009-01-23 23:27 ` Wolfgang Denk
2009-01-26 16:39 ` Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2010-01-25 1:08 Yang, Lin
2010-01-25 8:25 ` Wolfgang Denk
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=4911E2F0.3040602@freescale.com \
--to=jrigby@freescale.com \
--cc=u-boot@lists.denx.de \
/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