Files
sw_openocd/tcl/target
Felipe Balbi 589affe35b tcl: target: am437x.cfg: pass correct dbgbase
Since commit ec9ccaa288 (arm_adi_v5: make dap_lookup_cs_component()
traverse subtables and handle multicore) AM437x devices can't be used
with OpenOCD anymore. The reason is that dbgbase used to be set to zero
before that commit and that just happens to work with AM437x devices.

A more robust solution is to pass correct dbgbase when creating the
target, which this commit does.

Signed-off-by: Felipe Balbi <balbi@ti.com>
Change-Id: Iaf2617804324de8094b25137943e08b84f14c75f
Reviewed-on: http://openocd.zylin.com/2602
Tested-by: jenkins
Reviewed-by: Paul Fertser <fercerpav@gmail.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
2015-04-14 10:59:08 +01: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
2014-06-01 18:27:09 +00:00
2014-09-22 19:39:24 +00:00
2014-09-22 19:39:24 +00:00
2014-09-22 19:39:24 +00:00
2014-09-22 19:39:24 +00:00
2014-09-22 19:39:24 +00:00
2014-09-22 19:39:24 +00:00
2014-09-22 19:39:24 +00:00
2014-09-22 19:39:24 +00:00
2015-02-22 16:23:48 +00:00
2015-01-30 09:40:55 +00:00
2011-05-03 22:07:01 +02:00
2014-09-22 19:39:24 +00:00
2013-04-02 15:12:44 +00:00
2014-09-22 19:39:24 +00:00
2014-09-22 19:39:24 +00:00
2010-03-15 08:37:43 -07:00
2014-09-22 19:39:24 +00:00
2014-09-22 19:39:24 +00:00
2014-09-22 19:39:24 +00:00
2014-09-22 19:39:24 +00:00
2014-09-22 19:39:24 +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.