Files
openocd/tcl/target
Gianluca Renzi ed3632d9c7 Added support for NXP LPC1850 Microcontroller
Added a new configuration file for LPC18xx based boards, such as
HitexLPC1850RevA Evaluation Board, and all other based on the
same microcontroller by NXP.

Change-Id: I68c3827be535b6d09a5c70b6d57191937d00354d
Signed-off-by: Gianluca Renzi <gianlucarenzi@eurekelettronica.it>
Reviewed-on: http://openocd.zylin.com/930
Tested-by: jenkins
Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk>
2012-11-06 14:34:37 +00:00
..
2012-02-27 10:01:44 +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
2012-02-13 12:03:26 +00:00
2011-05-03 22:07:01 +02:00
2012-03-14 20:30:45 +00:00
2010-03-15 08:37:43 -07:00
2012-01-09 09:48:34 +00:00
2012-07-11 10:32:39 +00:00
2012-01-13 10:25:36 +00:00
2010-10-10 14:41:11 -07:00
2012-01-15 22:17:42 +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.