+@itemize @bullet
+@item @b{load_binary}
+@cindex load_binary
+use @option{load_image} command with same args
+@item @b{target}
+@cindex target
+@option{target} no longer take the reset_init, reset_run, run_and_halt, run_and_init. The @option{reset} command
+always does a @option{reset run} when passed no arguments.
+@item @b{dump_binary}
+@cindex dump_binary
+use @option{dump_image} command with same args
+@item @b{flash erase}
+@cindex flash erase
+use @option{flash erase_sector} command with same args
+@item @b{flash write}
+@cindex flash write
+use @option{flash write_bank} command with same args
+@item @b{flash write_binary}
+@cindex flash write_binary
+use @option{flash write_bank} command with same args
+@item @b{arm7_9 fast_writes}
+@cindex arm7_9 fast_writes
+use @option{arm7_9 fast_memory_access} command with same args
+@item @b{flash auto_erase}
+@cindex flash auto_erase
+use @option{flash write_image} command passing @option{erase} as the first parameter.
+@item @b{daemon_startup}
+@cindex daemon_startup
+this config option has been removed, simply adding @option{init} and @option{reset halt} to
+the end of your config script will give the same behaviour as using @option{daemon_startup reset}
+and @option{target cortex_m3 little reset_halt 0}.
+@item @b{arm7_9 sw_bkpts}
+@cindex arm7_9 sw_bkpts
+On by default. See also @option{gdb_breakpoint_override}.
+@item @b{arm7_9 force_hw_bkpts}
+@cindex arm7_9 force_hw_bkpts
+Use @option{gdb_breakpoint_override} instead. Note that GDB will use hardware breakpoints
+for flash if the gdb memory map has been set up(default when flash is declared in
+target configuration).
+@item @b{run_and_halt_time}
+@cindex run_and_halt_time
+This command has been removed for simpler reset behaviour, it can be simulated with the
+following commands: