Ashish,
>
> Hi Vignesh,
> This is working now(READ, WRITE), after some change in fsl_qspi driver, where
> I check for 4byte op codes now.
> But now I see that erase is getting address as ZERO. Which in my opinion is
> because
> spi_nor_erase_sector() call write_reg which has
> -Original Message-
> From: Vignesh Raghavendra
> Sent: Friday, March 29, 2019 12:17 PM
> To: Ashish Kumar ; Jagan Teki
> ; u-boot@lists.denx.de
> Cc: Kuldeep Singh
> Subject: Re: saveenv corrupts QSPI flash with latest commit U-Boot
> 2019.04-
ect: Re: saveenv corrupts QSPI flash with latest commit U-Boot
>> 2019.04-rc4-
>> 00047-gcfb3e102c4
>>
>>
>>
>> On 26/03/19 7:11 PM, Ashish Kumar wrote:
>>>>
>>>> On 26/03/19 10:36 AM, Ashish Kumar wrote:
>>>>> Hello Maintaine
> -Original Message-
> From: Vignesh Raghavendra
> Sent: Wednesday, March 27, 2019 9:44 AM
> To: Ashish Kumar ; Jagan Teki
> ; u-boot@lists.denx.de; Tom Rini
>
> Cc: Kuldeep Singh
> Subject: Re: saveenv corrupts QSPI flash with latest commit U-Boot
> 2019.
On 26/03/19 7:11 PM, Ashish Kumar wrote:
>>
>> On 26/03/19 10:36 AM, Ashish Kumar wrote:
>>> Hello Maintainers,
>>>
>>>
>>>
>>> With latest commit I see that saveenv command corrupts QSPI-flash,
>>> meaning if I read QSPI-flash at 0x0 offset RCW(reset configuration
>>> word) is erased after
On 26/03/19 10:36 AM, Ashish Kumar wrote:
> Hello Maintainers,
>
>
>
> With latest commit I see that saveenv command corrupts QSPI-flash,
> meaning if I read QSPI-flash at 0x0 offset RCW(reset configuration word)
> is erased after saveenv command was executed.
>
> This is tested on
Hello Maintainers,
With latest commit I see that saveenv command corrupts QSPI-flash, meaning if I
read QSPI-flash at 0x0 offset RCW(reset configuration word) is erased after
saveenv command was executed.
This is tested on LS1088ARDB, but it should not be limited to LS1088ARDB rather
it will
7 matches
Mail list logo
