auracaster/openocd
3
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

NOR: lpc2000 Add support for LPC84x devices

Browse Source 
These devices differ from LPC8xx devices in that they have a different
IAP entry point, but everything else is the same.  Using Tcl to pass
different IAP entry point.
no new Clang analyser warnings and no new build sanitizers issues.

Change-Id: I2d654dd250f416e74262c0228cad8713a283402f
Signed-off-by: Rod Boyce <developer@teamboyce.co.uk>
Reviewed-on: http://openocd.zylin.com/4684
Reviewed-by: Jean-Christian de Rivaz <jcamdr70@gmail.com>
Tested-by: jenkins
Reviewed-by: Tomas Vanek <vanekt@fbl.cz>
This commit is contained in:
Rod Boyce
2018-12-16 17:41:39 +00:00
committed by Tomas Vanek
parent 8f777bc1a6
commit b3ed97a492
4 changed files with 51 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/openocd.texi
View File

@@ -5910,7 +5910,7 @@ The LPC2888 is supported by the @var{lpc288x} driver.
The LPC29xx family is supported by the @var{lpc2900} driver.
@end quotation
The @var{lpc2000} driver defines two mandatory and one optional parameters,
The @var{lpc2000} driver defines two mandatory and two optional parameters,
which must appear in the following order:
@itemize
@@ -5937,6 +5937,8 @@ table, the boot ROM will almost certainly ignore your flash image.
However, if you do provide it,
with most tool chains @command{verify_image} will fail.
@end quotation
@item @option{iap_entry} ... optional telling the driver to use a different
ROM IAP entry point.
@end itemize
LPC flashes don't require the chip and bus width to be specified.