From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Between 2015.10 and 2016.01, SPI flash changed erase size, and saveenv stopped working
Date: Mon, 30 May 2016 05:21:28 +0200 [thread overview]
Message-ID: <574BB1B8.8010400@denx.de> (raw)
In-Reply-To: <20160529204041.GA8588@amd>
Hi Pavel,
On 29.05.2016 22:40, Pavel Machek wrote:
> Hi!
>
> On board with Altera Cyclone 5:
>
> => version
>
> U-Boot 2016.01-05658-g81689ec (May 29 2016 - 22:25:45 +0200)
> arm-linux-gnueabi-gcc (GCC) 4.8.2
> GNU ld (GNU Binutils) 2.24
> Saving Environment to SPI Flash...
> spi_flash_std_probe: slave=0bf367d0, cs=0
> SF: Detected N25Q512 with page size 256 Bytes, erase size 64 KiB,
> total 64 MiB
> offset 0x40000 is protected and cannot be erased
>
> ...
>
> => version
>
> U-Boot 2015.10-04078-g3b6d086 (May 29 2016 - 22:33:36 +0200)
> arm-linux-gnueabi-gcc (GCC) 4.8.2
> GNU ld (GNU Binutils) 2.24
> SF: Detected N25Q512 with page size 256 Bytes, erase size 4 KiB, total
> 64 MiB
>
>
> Does anyone else see the problem? Any ideas?
I think you have run into the S-bit / cache issue with version
the 2016 U-Boot version. This was fixed with these patches:
mtd: cqspi: Simplify indirect write code
mtd: cqspi: Simplify indirect read code
Please use the v2016.05 release.
Thanks,
Stefan
next prev parent reply other threads:[~2016-05-30 3:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 20:40 [U-Boot] Between 2015.10 and 2016.01, SPI flash changed erase size, and saveenv stopped working Pavel Machek
2016-05-30 3:21 ` Stefan Roese [this message]
2016-05-30 7:04 ` Pavel Machek
2016-05-30 8:33 ` Pavel Machek
2016-05-30 8:52 ` Pavel Machek
2016-05-30 13:43 ` Fabio Estevam
2016-05-30 20:25 ` Pavel Machek
2016-05-30 21:23 ` Fabio Estevam
2016-06-01 21:24 ` [U-Boot] socfpga 2016.07-rc0: have to disable parts of flash probing and limit read size to get SPL to work Pavel Machek
2016-06-02 13:41 ` [U-Boot] Between 2015.10 and 2016.01, SPI flash changed erase size, and saveenv stopped working Pavel Machek
2016-06-04 20:38 ` Fabio Estevam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=574BB1B8.8010400@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.