HI Jagan
sorry for the delay response.
And I have checked the maser. There is still a problem with this feature。
reproduce steps:
1. enable the flash protect function
2. using sf cmd to erase the flash. I can get the erase "OK",not the "error".
I think the root cause is that the detection mechanism is missing and to judge
the permissions of the action
So pull this PR to improve the erase flow
another question:
how can I visit the u-boot-spi/next? do there any link?
BRs
Chao
At 2021-06-29 21:50:28, "Jagan Teki" <ja...@amarulasolutions.com> wrote:
>On Tue, Jun 22, 2021 at 10:51 AM chao zeng <chaochao2021...@163.com> wrote:
>>
>> From: Chao Zeng <chao.z...@siemens.com>
>>
>> When operating the write-protection flash,spi_flash_std_write() and
>> spi_flash_std_erase() would return wrong result.The flash is protected,
>> but write or erase the flash would show "OK".
>>
>> Check the flash write protection state if the write-protection has enbale
>> before operating the flash.
>>
>> Signed-off-by: Chao Zeng <chao.z...@siemens.com>
>> ---
>
>Does it broken on master? if yes can you check in u-boot-spi/next?
>
>Jagan.
