Am 04/18/2011 09:24 PM, schrieb Rogan Dawes: > > Hi Alexandre, > > Your working cfi definition worked for me, too, after adjusting > addresses and sizes. Thanks you! Now the flash is recognized, and all > the sectors are properly identified. > > However, I am still not able to flash a replacement firmware to the > part. It seem that the unprotect command fails, and thus the file cannot > be written to the flash. > > I placed a debug log of the following command: > > openocd -f buspirate.cfg -f dns323.cfg -d3 -l openocd.log \ > -c "flash probe 0" \ > -c "flash info 0" \ > -c "flash erase_address pad unlock 0xfffd0000 0x30000" \ > -c "flash write_image erase unlock mtdblock4 0xfffd0000" \ > -c "shutdown" > > at: > > http://dawes.za.net/rogan/openocd-20110418-211900.log.gz > > The only difference in config files is the flash definition changed to: > > flash bank eightMB cfi 0xff800000 0x800000 1 1 $_TARGETNAME x16_as_x8 > jedec_probe > > as suggested. > > 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 _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
