[Apologies for duplicates, I used the wrong address to send to the list] Not sure which protection mechanism applies to me, as I have overwritten these segments before using uboot. (That's what got me into this mess in the first place! :-) )
I certainly did not apply 12V manually. Rogan ------Original Message------ From: Mathias K. To: Rogan Dawes Cc: Michael Schwingen Cc: [email protected] Subject: Re: [Openocd-development] OpenOCD and 16-bit CFI flash on an 8-bitbus Sent: Apr 19, 2011 09:24 Hello, there are several mechanism to protect or unprotect the sectors (factory/customer). If the "Secured Silicon Sector" locked you need 12V at the reset pin to execute the "Temporary Sector Group Unprotect" command. If the "Secured Silicon Sector" not locked you are able to unlock the sectors permanently inside the "Secured Silicon Sector Command Sequence". Regards, Mathias Am 19.04.2011 07:37, schrieb Rogan Dawes: > On 2011/04/18 10:00 PM, Michael Schwingen wrote: > >>> Any ideas why the flash unprotect might fail? >> AFAIR, this is not implemented for AMD/Spansion parts, since these parts >> never had any protection mechanism when they started. >> In Contrast, many Intel flashes come up protected out of reset and >> *need* the unprotect operation. >> >> Are you sure your flash *does* have protection and *needs* unprotect? >> >> Otherwise, you can simple remove the "unprotect" option. >> >> cu >> Michael > > Hi Michael, > > Well, "flash info 0" shows that certain sectors are protected and that others > are not, which > suggests that protection is actually present and implemented in this > particular chip. > > I'll try to dig into this in a bit more detail. > > Thanks > > Rogan > _______________________________________________ > Openocd-development mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/openocd-development > _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
