[U-Boot] How to start U-Boot for i.MX31 NAND out of RedBoot (out of RAM)

[Ulrich Gerster]

Hello.

>>> Magnus Lilja <lilja.magnus at gmail.com> 14.07.09 16.03 Uhr >>>

>> CONFIG_SYS_NAND_BASE   CS0_BASE should be correct because the Flash
>> is located at 0xA0000000 which should be CS0_BASE. Why do you think it is wrong?

> Because the NAND flash is not connected to any of the standard memory
> mapped chip selects of the i.MX31. The i.MX31 has a dedicated NAND
> interface. But I don't think CONFIG_SYS_NAND_BASE matters for the
> i.MX31, the rest of U-boot needs it to be defined to something.

I will check that. 

>> I used the patch from you out of this posting:
>> [U-Boot-Users] [PATCH RFC 3/5] i.MX31: Add i.MX31 NAND Flash Controller driver.
>> http://lists.denx.de/pipermail/u-boot/2008-August/038239.html
>>
>> They should work, or not? Do they require something else?

> I haven't tried that driver on a recent U-boot so I don't know if (or
> how) it will work when applied to a recent U-Boot.

I'm using the u-boot master release of middle of June. 
How can I ensure that your patch is working? Or how do I know what is missing that it works?

> Did you define the following two as well (they might have been renamed
> since last year).
> #define CFG_ENV_OFFSET		0x40000
> /* CFG_ENV_SIZE has to be a multiple of the NAND block size */
> #define CFG_ENV_SIZE		(128 * 1024)
>
> If CFG_ENV_OFFSET (or perhaps it's called CONFIG_ENV_OFFSET nowadays)
> is zero, then 'saveenv' will overwrite your existing redboot.

Yes, I defined them and you're right my offset was zero. But I think in a working u-boot thats no problem. But I will change that.

In your previous mail you mentioned a newer nand driver patch for the i.MX27.
Do you mean this one?
http://lists.denx.de/pipermail/u-boot/2009-June/053898.html
Does this one work with i.MX31 aswell?

Thanks a lot for your help.
Ulrich Gerster