Files
openocd/tcl/target
Antonio Borneo f5657aa76e tcl: [1/3] prepare for jimtcl 0.81 'expr' syntax change
Jimtcl commit 1843b79a03dd ("expr: TIP 526, only support a single
arg") drops the support for multi-argument syntax for the TCL
command 'expr'.

In the TCL scripts distributed with OpenOCD there are 1700+ lines
that should be modified before switching to jimtcl 0.81.

Apply the script below on every script in tcl folder. It fixes
more than 92% of the lines

%<---%<---%<---%<---%<---%<---%<---%<---%<---%<---%<---%<---%<---
 #!/usr/bin/perl -Wpi

 my $re_sym = qr{[a-z_][a-z0-9_]*}i;
 my $re_var = qr{(?:\$|\$::)$re_sym};
 my $re_const = qr{0x[0-9a-f]+|[0-9]+|[0-9]*\.[0-9]*}i;
 my $re_item = qr{(?:~\s*)?(?:$re_var|$re_const)};
 my $re_op = qr{<<|>>|[+\-*/&|]};
 my $re_expr = qr{(
     (?:\(\s*(?:$re_item|(?-1))\s*\)|$re_item)
     \s*$re_op\s*
     (?:$re_item|(?-1)|\(\s*(?:$re_item|(?-1))\s*\))
 )}x;

 # [expr [dict get $regsC100 SYM] + HEXNUM]
 s/\[expr (\[dict get $re_var $re_sym\s*\] \+ *$re_const)\]/\[expr \{$1\}\]/;

 # [ expr (EXPR) ]
 # [ expr EXPR ]
 # note: $re_expr captures '$3'
 s/\[(\s*expr\s*)\((\s*$re_expr\s*)\)(\s*)\]/\[$1\{$2\}$4\]/;
 s/\[(\s*expr\s*)($re_expr)(\s*)\]/\[$1\{$2\}$4\]/;
%<---%<---%<---%<---%<---%<---%<---%<---%<---%<---%<---%<---%<---

Change-Id: I0d6bddc6abf6dd29062f2b4e72b5a2b5080293b9
Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com>
Reviewed-on: http://openocd.zylin.com/6159
Tested-by: jenkins
Reviewed-by: Tomas Vanek <vanekt@fbl.cz>
2021-05-08 09:48:44 +01:00
..
2020-05-09 14:37:35 +01:00
2010-08-15 21:54:01 +02:00
2020-05-09 14:37:35 +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-02-08 23:27:18 +00:00
2020-05-09 14:38:40 +01:00
2020-05-09 14:38:40 +01:00
2018-03-30 09:58:21 +01:00
2014-09-22 19:39:24 +00:00
2020-05-09 14:38:40 +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
2021-04-24 05:53:57 +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
2020-02-08 23:27:18 +00:00
2020-03-12 09:43:55 +00:00
2020-05-09 14:38:40 +01:00
2015-11-03 21:45:28 +00:00
2020-05-09 14:38:40 +01:00
2020-05-09 14:38:40 +01:00
2020-05-09 14:38:40 +01:00
2020-05-09 14:38:40 +01:00
2020-05-09 14:38:40 +01:00
2020-05-09 14:38:40 +01:00
2020-05-09 14:38:40 +01:00
2020-05-09 14:38:40 +01:00
2020-05-09 14:37:35 +01:00
2020-05-09 14:38:40 +01:00
2015-10-30 13:14:12 +00:00
2018-12-23 15:08:36 +00:00
2020-10-22 21:19:59 +01:00
2020-02-08 23:27:18 +00:00
2020-05-09 14:37:35 +01:00
2020-05-09 14:37:35 +01:00
2021-03-10 21:23:53 +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.