From mboxrd@z Thu Jan 1 00:00:00 1970 From: llandre Date: Fri, 21 Jul 2006 13:22:20 +0200 Subject: [U-Boot-Users] Setting strataflash lock bit accidentally In-Reply-To: <20060721110214.1BC74352660@atlas.denx.de> References: <20060721110214.1BC74352660@atlas.denx.de> Message-ID: <44C0B8EC.8090405@dave-tech.it> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de >> 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. -- llandre DAVE Electronics System House - R&D Department web: http://www.dave-tech.it email: r&d2 at dave-tech.it