Let's assume that, because a software bug, an application has accidentally set the lock bit of the flash sector used to store the U-Boot environment. In this case, when trying to store a new environment with the saveenv command, U-Boot would not be able to complete the operation. Is it enough to define CFG_FLASH_PROTECTION in order to handle this situation and to allow U-Boot to unlock the sector (same thing would happen in case the locked sectors fall in the memrory area devoted to store kernels or ramsisks)? If no, how do you suggest to manage this situation?
Use MTD tools under Linux to unlock the flash?
Indeed this is a possible solution but I'm looking for a general one implemented in u-boot. In fact it must work with any operating system and I must assume o.s. might not provide MTD or similar tools.