Files
openocd/tcl/target
Andrey Yurovsky 2d64cf92ae stm32lx_dual_bank.cfg: fix typo in file path
s/stm32l1x/stm32lx

...this makes tm32lx_dual_bank.cfg work again.

Change-Id: I04dc617523caa6b46c675fe9b700d1bbe88170e6
Signed-off-by: Andrey Yurovsky <yurovsky@gmail.com>
Reviewed-on: http://openocd.zylin.com/1832
Tested-by: jenkins
Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk>
2013-12-14 21:48:22 +00:00
..
2013-05-02 16:39:18 +00:00
2010-12-18 21:04:22 +01:00
2010-08-15 21:54:01 +02:00
2010-06-25 21:37:53 +02:00
2011-03-03 22:49:47 +01:00
2011-03-03 22:49:47 +01:00
2011-03-03 22:49:46 +01:00
2011-03-03 22:49:47 +01:00
2013-04-28 08:55:31 +00:00
2013-10-29 22:49:35 +00:00
2013-05-02 16:39:18 +00:00
2013-04-28 08:55:31 +00:00
2013-04-28 08:55:31 +00:00
2011-05-03 22:07:01 +02:00
2013-09-26 09:52:56 +00:00
2013-04-02 15:12:44 +00:00
2010-03-15 08:37:43 -07:00
2012-12-23 21:46:20 +00:00
2012-01-13 10:25:36 +00:00
2010-10-10 14:41:11 -07:00
2013-11-06 13:06:41 +00:00
2013-04-28 08:56:04 +00:00

Prerequisites:
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:

1. The configuration script should be defined such as , for example, the following sequences are working:
	reset
	flash info <bank>
and
	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 the configuration file).

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...)

flash write_image [file] <parameters>
verify_image [file] <parameters>

4. adapter_khz sets the maximum speed (or alternatively RCLK). If invoked
multiple times only the last setting is used.

interface/xxx.cfg files are always executed *before* target/xxx.cfg
files, so any adapter_khz in interface/xxx.cfg will be overridden by
target/xxx.cfg. adapter_khz in interface/xxx.cfg would then, effectively,
set the default JTAG speed.

Note that a target/xxx.cfg file can invoke another target/yyy.cfg file,
so one can create target subtype configurations where e.g. only
amount of DRAM, oscillator speeds differ and having a single
config file for the default/common settings.