omap3530.cfg: use new "reset-assert" event

[openocd] / tcl / target / readme.txt

diff --git a/tcl/target/readme.txt b/tcl/target/readme.txt
index ca23c64bb0214e4f78d0abca029d08302832f2db..39f8d124085c3131e76e475310f8a957f3afaf38 100644 (file)
--- a/tcl/target/readme.txt
+++ b/tcl/target/readme.txt
@@ -1,5 +1,5 @@
 Prerequisites:
-The users of OpenOCD as well as computer programs interacting with OpenOCD are expecting that certain commands 
+The users of OpenOCD as well as computer programs interacting with OpenOCD are expecting that certain commands
 do the same thing across all the targets.
 
 Rules to follow when writing scripts:
@@ -8,20 +8,20 @@ Rules to follow when writing scripts:
        reset
        flash info <bank>
 and
-       reset 
+       reset
        flash erase_address <start> <len>
 and
        reset init
        load
-       
-In most cases this can be accomplished by specifying the default startup mode as reset_init (target command 
+
+In most cases this can be accomplished by specifying the default startup mode as reset_init (target command
 in the configuration file).
- 
-2. If the target is correctly configured, flash must be writable without any other helper commands. It is 
+
+2. If the target is correctly configured, flash must be writable without any other helper commands. It is
 assumed that all write-protect mechanisms should be disabled.
 
 3. The configuration scripts should be defined such as the binary that was written to flash verifies
-(turn off remapping, checksums, etc...) 
+(turn off remapping, checksums, etc...)
 
 flash write_image [file] <parameters>
 verify_image [file] <parameters>