Files
openocd/tcl/target
Antonio Borneo 7a94d0a19f tcl: stm32mp15x: add target and board config files
The stm32mp15x has one or two Cortex-A7 (depending on the P/N) and
one Cortex-M4.
The second core is automatically detected by the target script.
In "engineering boot" all the cores are accessible.
In "production boot" the Cortex-M4 is kept in reset state after
power-on or NRST.

The board DK2 includes a ST-Link/V2, but only SWD is connected.

Change-Id: Ib6ebefcc696b1716e0f98694cadf0b04fd7d11d6
Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com>
Reviewed-on: http://openocd.zylin.com/5454
Tested-by: jenkins
Reviewed-by: Oleksij Rempel <linux@rempel-privat.de>
2020-04-21 08:52:48 +01:00
..
2018-03-30 09:58:21 +01:00
2020-02-08 23:27:18 +00:00
2018-03-30 09:58:21 +01:00
2018-03-30 09:58:21 +01:00
2018-03-30 09:58:21 +01:00
2010-08-15 21:54:01 +02:00
2016-05-20 21:38:03 +01:00
2016-05-20 21:38:03 +01:00
2016-05-20 21:38:03 +01:00
2016-05-20 21:38:03 +01:00
2016-05-20 21:38:03 +01: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
2016-05-20 21:38:03 +01:00
2014-06-01 18:27:09 +00:00
2020-03-07 15:31:09 +00:00
2020-02-08 23:27:18 +00:00
2014-09-22 19:39:24 +00:00
2018-03-30 09:58:21 +01:00
2018-03-30 09:58:21 +01:00
2014-09-22 19:39:24 +00:00
2018-03-30 09:58:21 +01:00
2018-03-30 09:58:21 +01:00
2019-04-24 14:11:22 +01:00
2019-04-24 14:11:33 +01:00
2019-04-10 10:16:19 +01:00
2019-04-24 14:11:07 +01:00
2019-04-24 14:11:46 +01:00
2014-09-22 19:39:24 +00:00
2014-09-22 19:39:24 +00:00
2018-03-30 09:58:21 +01:00
2018-03-30 09:58:21 +01:00
2014-09-22 19:39:24 +00:00
2020-02-08 23:27:18 +00:00
2020-03-12 09:43:55 +00:00
2020-03-12 09:43:55 +00:00
2015-11-03 21:45:28 +00:00
2011-05-03 22:07:01 +02:00
2014-09-22 19:39:24 +00:00
2015-10-30 13:14:12 +00:00
2018-12-23 15:08:36 +00:00
2018-03-30 09:58:21 +01:00
2018-03-30 09:58:21 +01:00
2018-06-06 18:12:21 +01:00
2020-02-08 23:27:18 +00:00
2020-02-08 23:27:18 +00:00
2020-02-08 23:27:18 +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 speed 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 speed in interface/xxx.cfg will be overridden by
target/xxx.cfg. adapter speed 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.