Re: NOR damage problem

[Alexander Shiyan <eagle.alexander923@gmail.com>]

Hello.

> > Found NOR partition damage after use ubiformat.
> > There is a NOR memory (256M) connected via atmel-qspi.
...
> The messages above say that 64bytes were written which matches the
> number of bytes that are corrupted here. Maybe this can be a starting
> point where to look at. Also the 64 bytes were written without the block
> being erased. You could erase the block manually before calling
> ubiformat, then you could see what the code really tried to write here.
>
> Just an idea: Is the size of your Flash correctly detected? When writing
> past the device then the write operations could roll over to the first
> block.

The problem is more complex than I thought...
ATMEL QSPI only works in the mapping range up to 128 MB,
larger chips will not work correctly.
To solve this, we will have to update the spi-mem and atmel-quadspi
drivers and add spi_transfer() support to the driver (and in the kernel too).

Thanks!