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

Magnus Lilja lilja.magnus at gmail.com
Tue Jul 14 19:42:48 CEST 2009


Hi

2009/7/14 Ulrich Gerster <gersteru at dhbw-loerrach.de>:
> Hello.
>
>>>> Magnus Lilja <lilja.magnus at gmail.com> 14.07.09 16.03 Uhr >>>
>
>>> 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?

You need to use either a debugger or add printf's to see what's going
on (to the mxc_nd.c or whatever the file is called.

>> 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.

I do think that's a problem in a working u-boot since it defines the
offset for the environment from the start of the flash.

>
> 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

Yes.

> Does this one work with i.MX31 aswell?

Don't know, but the author claims that it should work (perhaps with
some adjustments).

Regards, Magnus


More information about the U-Boot mailing list