Files
openocd/tcl/target
Tarek BOCHKATI 678fb4f60b target/stm32h7x: add support of dual core variant of STM32H7
STM32H7x7 and STM32H7x5 devices contains two cores : CM7 + CM4
The second core creation is only done when
  * DUAL_CORE variable is set to true
  * non HLA interface is used

A second check for the second core existence is done in cpu1 examine-end
Once the second core is detected it gets examined.

Furthermore, the script provides a configurable CTI usage in order to halt
the cores simultaneously.

Tested on Rev X and V devices.

PS: the indentation was a mix of spaces and tabs, all changed to tabs.

Change-Id: Iad9c30826965ddb9be5dee628bc2e63f953bbcb8
Signed-off-by: Tarek BOCHKATI <tarek.bouchkati@gmail.com>
Reviewed-on: http://openocd.zylin.com/5130
Tested-by: jenkins
Reviewed-by: Tomas Vanek <vanekt@fbl.cz>
2019-12-07 13:07:00 +00:00
..
2019-10-18 09:18:41 +01: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
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
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
2018-03-30 09:58:21 +01:00
2016-05-20 21:38:03 +01:00
2018-10-31 21:15:52 +00:00
2014-06-01 18:27:09 +00: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
2018-10-16 11:58:24 +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
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
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
2014-09-22 19:39:24 +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
2014-09-22 19:39:24 +00:00
2018-03-30 09:58:21 +01:00
2018-12-23 15:08:36 +00:00
2015-11-03 21:45:28 +00:00
2018-03-30 09:58:21 +01:00
2011-05-03 22:07:01 +02:00
2014-09-22 19:39:24 +00:00
2018-03-30 09:58:21 +01:00
2015-10-30 13:14:12 +00:00
2018-03-30 09:58:21 +01:00
2018-03-30 09:58:21 +01: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-03-30 09:58:21 +01: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
2013-04-02 15:12:44 +00:00
2018-06-06 18:12:21 +01: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
2018-03-30 09:58:21 +01:00
2014-09-22 19:39:24 +00:00
2018-03-30 09:58:21 +01:00
2017-12-07 07:53:13 +00:00
2017-12-07 07:53:13 +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
2014-09-22 19:39:24 +00: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

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.