From mboxrd@z Thu Jan  1 00:00:00 1970
From: Fabio Estevam <festevam@gmail.com>
Date: Mon, 30 May 2016 18:23:49 -0300
Subject: [U-Boot] Between 2015.10 and 2016.01,
 SPI flash changed erase size, and saveenv stopped working
In-Reply-To: <20160530202513.GB25685@amd>
References: <20160529204041.GA8588@amd> <574BB1B8.8010400@denx.de>
 <20160530083315.GA18126@amd>
 <CAOMZO5CN0FhJYdJ7SJDAaEkVvifA_ve9SSpVSqBhc6Yhn89VHg@mail.gmail.com>
 <20160530202513.GB25685@amd>
Message-ID: <CAOMZO5BN8-iy1u1Kax88PR4Ek_L9HpauArUBi311AdGPUejMZQ@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Mon, May 30, 2016 at 5:25 PM, Pavel Machek <pavel@denx.de> wrote:

> Yes, it helps. Thanks! I can now write to the enviornment.

Ok, good. What happens if you revert the hack and boot a fresh 2016.05 U-boot?

Are you able to write/save to the env?

I want to understand if your flash always come up with the SR bits
protected or not.