[Gumstix-users] trouble reflashing gumstix

[Colin S. <cj...@ab...>]

I am trying to upgrade the flash image on a Verdex XM4. I dd'ed the image
from another verdex by doing:

mount / -o remount,ro
cd /tmp
dd if=/dev/mtd1 of=rootfs.jffs2
dd if=/dev/mtd2 of=uImage

then copying these images over to the a PC and flashing them in uboot (via
tftp). However when I flash the filesystem image I get the following error
about blocks being locked:

GUM> pro on 1:0-1 && jera all && cp.b a2000000 40000 ${filesize}
Protect Flash Sectors 0-1 in Bank # 1
.. done
Erase Flash Bank # 1 - Warning: 2 protected sectors will not be erased!
..............................................................Flash erase
error at address 800000
Block Erase Error.
Block locked.
Flash erase error at address 820000
Block Erase Error.
Block locked.
................................................................. done
Flash buffer write error at address 800000
Locking Error
Block locked.
Flash buffer write error at address 820000
Locking Error
Block locked.


I then tried doing

GUM> protect off 800000 +2

to unprotect the first block but it still complains it locked.

So I then tried "protect off all" thinking that it would certianly remove
the lock and it flashed without error. However I think I somehow overwrote
uboot in the process and now the gumstix does nothing when I turn it on.

It was my understanding that the "cp.b a2000000 40000 ${filesize}" command
would only overwrite the OS image part of the flash (what linux calls
mtd1) and not uboot??

Has anyone else seen this problem? Any ideas why the sector would be
locked like that? Is this a sign the gumstix has faulty memory? Its less
than a year old and hasn't been used that heavily (probably been used for
less than 40 days total), I think its had one previous reflash which
worked without any trouble.


Colin.







Colin Sauze
PhD Student, Intelligent Robotics Group
Department of Computer Science
Aberystwyth University
http://users.aber.ac.uk/cjs06