Nand driver acts different in two different settings

[John Tobias]

Removing -j doesn't make any difference.

-john

On Wed, May 20, 2009 at 12:00 AM, Ricard Wanderlof
<ricard.wanderlof at axis.com> wrote:
>
> On Tue, 19 May 2009, John Tobias wrote:
>
>> I have tested two scenarios for writing/reading a data on my nand flash
>> and it act's differently the nand driver on DM6446. ...
>
>> I erased the said partition using flash_eraseall -j /dev/mtdblock11, write
>> the .jffs2 image on flash using nandwrite. Then, I reboot my board to boot
>> on nand. The first boot, I didn't get any errors/warnings. But, after the
>> 2nd reboot, I got the following errors:
>
> Odd that you don't get errors the first time you boot.
>
> I really don't know, but I would try omitting -j to flash_eraseall and see
> if it makes a difference.
>
> /Ricard
> --
> Ricard Wolf Wanderlöf                           ricardw(at)axis.com
> Axis Communications AB, Lund, Sweden            www.axis.com
> Phone +46 46 272 2016                           Fax +46 46 13 61 30
>