Am 04/19/2011 04:59 PM, schrieb Rogan Dawes: > Hi *, > > So it seems that there is something more seriously wrong. I tried to > write to one of the sectors that was shown as unprotected (per "flash > info 0" output), using 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 0xffff0000 0x10000" \ > -c "flash write_image erase unlock mtdblock4-3 0xffff0000" \ > -c "shutdown" > > That failed with the following error: > > Error: 348629 73825 cfi.c:1808 cfi_spansion_write_block(): flash write > block failed status: 0x0 > Error: 348630 73825 core.c:98 flash_driver_write(): error writing to > flash at address 0xff800000 at offset 0x007f0000 > Debug: 348631 73825 command.c:638 run_command(): Command failed with > error code -902 > User : 348632 73826 command.c:679 command_run_line(): Command handler > execution failed > in procedure 'flash' > > The detailed log file is at: > > http://dawes.za.net/rogan/openocd-20110419-1625.log.gz > > Any ideas on what I can do to debug this further? Try removing the working area from your config - that will force OpenOCD to run single-cycle accesses from the host, without relying on target-based code or RAM.
It will be dead slow (on the order of some 10 bytes/s), but you can trace the individual accesses and see what goes wrong. And if nothing goes wrong, you have a (slow) recovery method, and you know that your memory / working area setup is wrong. cu Michael _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
