NOR damage problem

[Alexander Shiyan]

Hello.

Oh, the spi-mem driver update also includes a major spi core update.
I'll try to make minimal changes just for the atmel-quadspi driver.

Thanks!

вт, 1 апр. 2025 г. в 15:05, Ahmad Fatoum <a.fatoum at pengutronix.de>:
>
> Hello Alexander,
>
> On 4/1/25 13:56, Alexander Shiyan wrote:
> > 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).
>
> The spi-mem core is also limited to 1 bit currently. Just saying in case
> you want to fix that as well. I haven't been successful to talk Oleksij
> into it. :D
>
> Cheers,
> Ahmad
>
> >
> > Thanks!
> >
> >
>
> --
> Pengutronix e.K.                  |                             |
> Steuerwalder Str. 21              | http://www.pengutronix.de/  |
> 31137 Hildesheim, Germany         | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |
>