diff options
| author | David Brownell <dbrownell@users.sourceforge.net> | 2010-02-27 00:31:35 -0800 |
|---|---|---|
| committer | David Brownell <dbrownell@users.sourceforge.net> | 2010-02-27 00:31:35 -0800 |
| commit | e70d42a727bebc5ae0ce0b1386620d30ea00b05b (patch) | |
| tree | 10a999847449419eaf789fe41eec065a67448b25 /tools/xsvf_tools/xsvfdump.py | |
| parent | 3ef9beb52cd0ed57ae6d28f7858001bfb68d7e86 (diff) | |
| download | openocd_libswd-e70d42a727bebc5ae0ce0b1386620d30ea00b05b.tar.gz openocd_libswd-e70d42a727bebc5ae0ce0b1386620d30ea00b05b.tar.bz2 openocd_libswd-e70d42a727bebc5ae0ce0b1386620d30ea00b05b.tar.xz openocd_libswd-e70d42a727bebc5ae0ce0b1386620d30ea00b05b.zip | |
new "stellaris recover" command
Stellaris chips have a procedure for restoring the chip to
what's effectively the "as-manufactured" state, with all the
non-volatile memory erased. That includes all flash memory,
plus things like the flash protection bits and various control
words which can for example disable debugger access. clearly,
this can be useful during development.
Luminary/TI provides an MS-Windows utility to perform this
procedure along with its Stellaris developer kits. Now OpenOCD
users will no longer need to use that MS-Windows utility.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Diffstat (limited to 'tools/xsvf_tools/xsvfdump.py')
0 files changed, 0 insertions, 0 deletions