summaryrefslogtreecommitdiff
path: root/testing/examples/SAM7S256Test/test_rom.map
diff options
context:
space:
mode:
authorDavid Brownell <dbrownell@users.sourceforge.net>2010-03-03 12:59:53 -0800
committerDavid Brownell <dbrownell@users.sourceforge.net>2010-03-03 13:08:16 -0800
commit99939c3c75f3bef44d4cd176e90a6c5fe8b833da (patch)
tree118817302be98c3d887bdffa7b61c0d2106c027c /testing/examples/SAM7S256Test/test_rom.map
parent2119c0a7641d05ad8b6b8feb64d4c315716f6d3a (diff)
downloadopenocd_libswd-99939c3c75f3bef44d4cd176e90a6c5fe8b833da.tar.gz
openocd_libswd-99939c3c75f3bef44d4cd176e90a6c5fe8b833da.tar.bz2
openocd_libswd-99939c3c75f3bef44d4cd176e90a6c5fe8b833da.tar.xz
openocd_libswd-99939c3c75f3bef44d4cd176e90a6c5fe8b833da.zip
NOR: stellaris message tweaks
Give a more accurate failure message when trying to unprotect; don't complain about pages being write protected, just say that unprotect is not supported by the hardware ... referencing the new "recover" command, which is the way to achieve that. Likewise, when trying to protect, talk about "pages" (matching hardware doc) not "sectors" (an concept that's alien to these chips). Also make the helptext for the "recover" command mention that it also erases the device. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Diffstat (limited to 'testing/examples/SAM7S256Test/test_rom.map')
0 files changed, 0 insertions, 0 deletions