Hi Takahiro, On Tue, Sep 15, 2026 at 6:08 PM <[email protected]> wrote: > > Hi, > > > Add protected property for SPI flash mx25l4005a, mx25l3205d, mx25l6405d, > > and m25p32. > > This will enable spi_nor_init() to unlock these SPI flash automatically. > > Please make sure the locking feature works properly with the HAS_LOCK flag > enabled. The HAS_LOCK flag should not be added just to support startup > unlocking.
Of course you're right. My patch description should have mentioned the datasheets and the tests that I've done to verify the locking feature is working. I was about to send in a V2 patch, but realized that we have a related issue in the saveenv command. If the SPI flash is *locked*, the user can change envs and saveenv behaves like the flash was updated and saved, but in reality it was not saved. I think I will track that down before sending the V2 version of this patch. Thanks, Tony
